Sunday, May 4, 2014

Various JMS Queues Used By OIM

OIM versions prior to 9.1 were using a single JMS queue named xlQueue for all the asynchronous operation like user requests (self registration and approval), reconciliation, attestation and auditing. Because all the process were using a single JMS queue, every aforementioned operations used to depend on each other. For example when reconciliation was running the queue xlQueue is filled with messages for reconciliation and request processing needs to wait till all the reconciliation was done. This was creating inter dependency between the modules of the application.
 
From OIM version 9.1 onwards, separate JMS queues for each asynchronous functionality were introduced.
 
Below are the details of the JMS queues used by OIM:
 
xlQueue
This queue is used to handle request (self registration and approval) related operations.
 
xlReconQueue
This queue is used to handle Reconciliation.
 
xlAuditQueue
This queue is used to handle Auditing.
 
xlAttestationQueue
This queue is used to handle Attestation.
 
xlProcessQueue
This queue is for future usage.
 
xlErrorQueue
This is the queue where the messages will end up after being tried 5 times.
For example, if the recon messages picked up by ReconMDBs fail during processing, they are tried for 5 times to process. If they still fail then the messages will be sent to this error queue.

Encryption Standard for OIM Database Key

OIM uses the AES -128 encryption standard in its Database key and to encrypt Answers for Challenge Response Security Questions for user account.

Note: It not possible to change Encryption method.

Exporting all of the MDS data for OIM 11g

If you want to export/backup all the MDS configuration files for OIM, then use the below WLST command:
 
Step1: Create a directory where you want all the configuration to be exported, for example MDSExport.
 
Step2: From the shell/command prompt, navigate to $MW_HOME/oracle_common/common/bin
 
Step3: Execute the wlst.sh/wlst.cmd and issue the connect() command.
 
Step4: Provide the weblogic username, password and URL to Admin Server.
 
Step5: Execute the exportMetadata command providing at least the following arguments: application, server and toLocation.
 
For example, exportMetadata(‘OIMMedata’,’oim_server1’,’<<Full Path to MDSExport’)
 
Step6: You should see a list of the files exported, at that point you can issue the disconnect() command followed by the exit() command.
 
you can also save the above commands in a .py file, let’s say MDSExport.py and it can be executed directly without entering the credentails and URL everytime.
 
MDSExport.py
 
connect('weblogic',<<PASSWORD>>,'t3://<<server:7001>>)
exportMetadata(application='OIMMetadata', server='oim_server1', toLocation=<<Full Path to MDSExport’)
disconnect()
exit()
 
Now, you can simply run the below command:
./wlst.sh MDSExport.py
 
Note: You cannot export all the configuration files using Deployment Manager (DM) and also, DM doesn’t have version control.




Monday, April 28, 2014

Creating Access Policy in OIM 11g R2

From 11g R2 onwards, accounts and entitlements can either be revoked or disabled if policy no longer applies. There is no longer an option to leave any option deselected.
 
You have to use the class tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType to specify if you want the entitlements to be revoked or disabled when the access policy is no longer applicable.
 
If you are creating the access policy using the tcAccessPolicyOperationsIntf, then use the below to specify the revoke/disable option for your access policy.
 
static tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType revokeFlag = tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType.REVOKE; 

static tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType disableFlag = tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType.DISABLE;

tcAccessPolicyOperationsIntf.PolicyNLAObjectActionType[] actionIfPolNotApply = {revokeFlag};

moAccesspolicyutility.createAccessPolicy(attr, provObjKeys,                    actionIfPolNotApply, denyObjKeys, groupKeys, policyData);

 
References:
 
http://docs.oracle.com/cd/E27559_01/admin.1112/e27149/accesspolicies.htm

http://docs.oracle.com/cd/E17904_01/apirefs.1111/e17334/Thor/API/Operations/tcAccessPolicyOperationsIntf.html
 

Thursday, April 17, 2014

All Java SE Downloads

If you are looking for a single place to find all the binaries for all Java SE versions, please refer to below note on MOS:
 
 

OIM 11gR2: How to Roll back A Published Sandbox

 
If your OIM is messed after publishing your sandbox, then here is what you can try to fix the issue.
 
1. Login to Enterprise Manager

2. In Application Deployments select oracle.iam.console.identity.self-service.ear or oracle.iam.console.identity.sysadmin.ear link.

3. Right Click and select MDS Configuration (from the drop-down)

4. At the bottom of the screen choose "Runtime MBean Browser" (under the Advanced Configuration section)

5. The right side of the screen should refresh and then click on the "Operations" tab.

6. Scroll down and identify the MBean operation "listMetadataLabels" and invoke it (choose the one that takes no parameters).
Select the sandbox pre-create to which you want to restore and copy it to the clipboard.

For example the value you might copy might look something like - Creation_IdM_test_09:25:00

7. Now go back to Operations by clicking Return.

8. Find the MBean operation "promoteMetadataLabel" (the first one in the list)

9. Invoke the "promoteMetadataLabel" MBean operation and enter the value saved to the clipboard in step 6.

10. Restart OIM.

 
Now, if your issue is still not fixed, then I will recommend looking at /file/User.xml file to see if all UDFs are properly defined or not.
 
References:
 
 

How To Solve "Error On Publishing A Sandbox" with the message "There Is A Concurrent "UPDATE" Operation On The Document ?

If you are seeing the below error while publishing your OIM sandbox, then you can try the workaround I am able to use successfully everytime:

Publish Sandbox Failed

Basically, here is 3 step I follow:

1. Export the sandbox to your local directory.
2. Delete the sandbox from OIM.
3. Import the Sandbox in OIM, activate it and hit the publish button.

While doing the impor, make sure that zip contains all the sandbox files. It shouldn't contain any top-level directory.

Obviously, this issue is legit if multiple users are working in OIM on the sandbox. However, I have also seen this issue when you make changes on /identity and /sysadmin console using the same sandbox and same user.