Search This Blog

Tuesday, March 3, 2015

Plugins folder and JavaTasks folder - danger

This blog is regarding the plugins and JavaTasks folders in OIM 11gR2++

Most people know that you can easily deploy plugins to the plugins folder found in the $OIM_HOME folder.  It is a very simple way to be able to quickly test changes to your event handlers and scheduled tasks.

Some people know about the JavaTasks folder, which does not exist OOTB, but if created in the $OIM_HOME folder, any Jar files contained therein will be taken in just as if they had been uploaded.  It still normally requires a restart, but some people don't like the DeleteJars and UploadJars process.

So there is a downside to using these.  You cannot export Scheduled Jobs that were built with plugins folder based Scheduled Task plugins.  They don't show up in the export list.  And even if you register the plugin, when you export, the Job won't import.  I suspect similar issues will occur with PTA's built from the JavaTasks folder.

If you have built scheduled jobs from a plugins folder plugin, do this:

1) Screenshot the scheduled job so you remember what you had in it.  If any field goes past the end of the editor, just open the screen shot with paint and type in a text box with the data.  Save the screenshot.
2) Delete all scheduled jobs that were built from this plugin.
3) Remove the plugin from the plugins folder.  I like to just mv them to the plugin_utiliity folder.
4) Watch the oim_serverX-diagnostic.log for the line indicating the plugin has been removed from the cache.
5) Register the plugin
6) Create the scheduled jobs new.
7) Now you can export and import the jobs.  Make sure the scheduled task is also registered on the downstream environment.

One more thing:

Never use UpdateJars.sh - even if the file has the same name it sometimes fails to update the jar.  Always use DeleteJars.sh, then check the OIMHOME_JARS table, then use UploadJars.sh, and then check the table again.

Peace be with you.

No comments:

Post a Comment