In order to custom develop OIM's scheduled tasks or event handlers, you must first enable the custom logging. In OIM 11g and above, you can now instantiate the logging within enterprise manager (em) and leverage off the logging setting available from the GUI. In order to do this, you must first instantiate the logging instance within your schedule task and deploy this successfully. This blog assumes you've already deployed the schedule task or event handler though there's a quick blog post on preparing the OIM 11g Custom Plugin files within JDeveloper if you haven't done this already.

You will need to 'import com.thortech.util.logging.Logger' class within your custom code. If the package cannot be located then you need to ensure the oimclient.jar is also associated to your design. For this example, don't use the other java.util.logging.Logger import within your code

import com.thortech.util.logging.Logger

Once that's imported in successfully, ensure you have a 'private static final logger' instance within your custom connector or plugin. Because this is static

For example

private static final logger LOGGER = Logger.getLogger(ExampleClass.class.getName())

Now you have the freedom to us the LOGGER instance anywhere within your code. The log levels available can be located within the post, Logging in Oracle Identity Manager By Using log4j.

For example

LOGGER.info("***** THIS IS THE LOG *****");

Once you've compiled your code and imported this into OIM, run the code at least once for OIM (and the logger configuration) to acknowledge your custom code. If it's a custom scheduled task for example, just run the schedule task within the OIM GUI Once you've executed the plugin, go to Oracle's Enterprise Manager (URL will be hostname:7001/em). Got to Weblogic Domains -- idmdomain -- oim_sever1 then right click on the server and select Logs, Log Configuration Once you've done that, expand out to see your class by navigating through the packages (This is obviously the package you provided to the custom code). If you cannot see the custom code class, it's possible that because you're not looking hard enough, or that the custom code was not executed, or the code was executed though never reached any of your LOGGER methods within your code. Once you have located the class, click down on the Oracle diagnostic Logger Level (Java Level) and select the logger lever. IMPORTANT - you must make a change to this. If the logger lever is already set, you need to save to another log level, then make another change.. Before you save, click on the 'Persist log level state across component restarts'. This must be ticked for your logger handler to acknowledge this. Once you've saved this, you should see the persistant log level state populated. Once you've done that, click on the 'log files' tab

The handler will acknowledge any changes to your custom code and populate that information into a dedicated log file. I would probably recommend clicking on the 'create like' so most of it's already configured for you. Obviously you'll need to alter the logger name, the file name, etc... it's fairly self-explanatory. Once you've done that, save the logging handler and execute the OIM schedule task or event handler to then determine the population of the logging.

About the author