It took my a while to determine why my custom-made scheduled tasks were not showing up after following the new 11g 'how to create a scheduled task via plugin'. Turns out the META-INF folder is an optional which contains the metadata (task definition). If you don't have this file, you need to import the metadata file into the MDS manually.
Here are the steps below on how to import the custom plugin metadata file manually
You need to perform the following steps:
- 1. Setup the metadata configuration
- 2. Export out the current metadata
- 3. Place your new custom scheduler plugin configuration file
- 4. Import the metadata back into the MDS
Simple right?
1. Setup the metadata configuration
Go to the OIM_HOME/server/bin directory and vi into weblogic.properties. In this file, hard code all the paths of the variables.
You need to change the following variables:
- wls_servername: is the name of the managed server of OIM
- application_name: Stays as OIMMetadata
- metadata_from_loc and metadata_to_loc: Te directory of the server/metadata. It makes things simple if they are identical though you will often overwrite
- metadata_files: Stays as /db/*
2. Export the current metdata
Within the same directory as the weblogic.properties file, run the weblogicExportMetadata.sh file the follow the steps. You need to log into the OIM managed server by pointing to the managed server (not the WLS admin) with the weblogic credentials. Once you've successfully executed the command, you should then be able to see the matadata within your db directory.
3. Place your new custom scheduler plugin configuration file
Place your scheduled task xml into the db directory current metadata, place your scheduled task xml (in my case, it's the OIMSampleScheduledTask.xml) file into the metadata/db directory.
4. Import the metadata back into the MDS
Again, in the same directory, run the weblogicImportMetadata.sh file and follow the steps.
Assuming you've followed the HOW TO:Import your OIM 11g custom plugin, you should now be able to see the scheduled task within your admin console/
COMMON ISSUES
I did have to remind myself the correct configurations when trying to connect though discovering the MDS-91020: MDS Application runtime MBean for "OIMMetadata" is not available in server "oim_server1" issue.
About the author
Daniel is a Technical Manager with over 10 years of consulting expertise in the Identity and Access Management space.Daniel has built from scratch this blog as well as technicalconfessions.com
Follow Daniel on twitter @nervouswiggles
Comments
Other Posts
AS I was migrating my environment into an S3 environment, I wanted to leverage off the SES services that AWS provide, more specifically, to leverage the off the SMTP functionality by sending an email via PHP
Read More...
The WeMos D1 is a ESP8266 WiFi based board is an extension to the current out-of-the-box library that comes with the Arduino installation. Because of this, you need to import in the libraries as well as acknowledging the specific board. This process is highly confusion with a number of different individuals talking about a number of different ways to integrate.
Read More...
NameID element must be present as part of the Subject in the Response message, please enable it in the IDP configuration.
Read More...
For what I see, there's not too many supportive documentations out there that will demonstrate how provision AD group membership with the ICF connector using OpenIDM. The use of the special ldapGroups attribute is not explained anywhere in the Integrators guides to to the date of this blog. This quick blog identifies the tasks required to provision AD group membership from OpenIDM to AD using the LDAP ICF connector. However this doesn't really explain what ldapGroups actually does and there's no real worked example of how to go from an Assignment to ldapGroups to an assigned group in AD. I wrote up a wiki article for my own reference: AD group memberships automatically to users This is just my view, others may disagree, but I think the implementation experience could be improved with some more documentation and a more detailed example here.
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
ForgeRock IDM - org.forgerock.script.exception.ScriptCompilationException: missing ; before statement
Read More...
When performing the attempt of a reconciliation from ForgeRock IDM to Active Directory, I would get the following error
Read More...
In the past, the similar error occurred though for the Oracle Identity Management solution. invalidcredentialexception remote framework key is invalid Because they all share the ICF connector framework, the error/solution would be the same.
Read More...
During the reconcilation from OpenIDM to the ICF google apps connector, the following error response would occur. ERROR Caused by com.google.api.client.auth.oauth2.TokenResponseException 400 Bad Request - invalid_grant
Read More...
Tags
Recent Posts
Monthly Activity
Group by date