Add a plugin element for each scheduled task that you are adding.

Developing Scheduled Tasks 6-5 plugin pluginclass= oracle.iam.scheduler.TestScheduler version=1.0.1 name=scheduler element plugin plugins oimplugins 4. Save and close the plugin.xml file.

6.6 Create the Directory Structure for the Scheduled Task

The final step in configuring the scheduled task is to create a plugin.zip file with the directory structure specified in Example 6–2 . In this example, a single plug-in is being added, but there can be multiple pugins in the plugin.zip file. Scheduler requires that files be zipped in a particular structure and named according to a particular naming convention. This ensures that Oracle Identity Manager identifies the custom scheduled tasks and makes it available in Oracle Identity Manager Administrative and User Console while creating jobs Example 6–2 Directory Structure for the Scheduled Task plugin plugin.xml lib CLASS_NAME1.jar Note that: ■ The XML file for the plug-in must be named plugin.xml. ■ The lib directory must contain only .JAR files. The lib directory consists of JAR files that contains the classes implementing the plug-in logic and the dependent library JAR files. In most instances, this directory consists of a single JAR file with the implementation of all the plug-ins that are specified in plugin.xml. See Developing Plug-ins on page 7-5 for for information about the directory structure. ■ The directory for the scheduled task must contain the following files: – XML for the plug-in – JAR files ■ There is one plugin.zip file for all the plug-ins that you create. In the preceding example, CLASS_NAME.JAR is the JAR file that you create in Section 6.4, Develop the Scheduled Task Class . After you create the plugin.zip file, if deploying in a clustered environment, register the plug-in to the database by using appropriate APIs. See Registering and Unregistering Plug-ins By Using APIs on page 7-6 for details about registering plug-ins to Oracle Identity Manager by using APIs. Note: The XML for the plug-in must be named plugin.xml. Ensure that the lib directory contains only JAR files. 6-6 Oracle Fusion Middleware Developers Guide for Oracle Identity Manager