C Using IBM WebSphere Application Server MQ as JMS Provider

This appendix provides an overview for using WebSphere MQ as JMS provider for Oracle Identity Manager. For detailed information you have to refer to WebSphere and WebSphere MQ documentation.

Using WebSphere MQ as JMS provider for Oracle Identity Manager involves the following steps:

• Creating a Backup of the WebSphere 6.1 Configuration

• Preparing WebSphere MQ

• Uninstalling Applications

• Removing Resources for Default Messaging

• Changing the xlJMSLogin Credentials

• Creating WebSphere MQ Resources

• Changing Deployment Descriptors

• Restarting IBM WebSphere Application Server

• Running the patch_websphere Patch

• Restarting WebSphere Application Server

C.1 Creating a Backup of the WebSphere 6.1 Configuration

Oracle recommends that you create a backup of the WebSphere configuration for all the WebSphere profiles involved in the installation of Oracle Identity Manager. You need the WebSphere configuration backup to restore to the previous working state, if anything goes wrong. Refer to IBM documentation on how to use the backupConfig and restoreConfig utilities for creating backup and restoring the WebSphere configuration respectively.

To create a backup of the WebSphere configuration for all the profiles in WebSphere 6.1, run the WAS_HOME/profiles/PROFILE_NAME/bin/backupConfig.sh or backupConfig.cmd script.

In addition, create a backup of the OIM_HOME directory before starting the procedure described in this appendix.

C.2 Preparing WebSphere MQ

Install MQ in one or more computers. For example, for failover, install MQ in one computer with hardware-based failover, or install MQ in multiple computers and create a clustered queue manager.

Create six separate JMS queues in the Queue Manager by naming the queues appropriately. For example, create queues named xlQueue, xlAuditQueue, xlAttestationQueue, xlReconQueue, xlProcessQueue, and xlErrorQueue. xlErrorQueue is intended to be used as a dead letter queue for all other five queues.

C.3 Uninstalling Applications

Uninstall Oracle Identity Manager applications already deployed from the IBM application server for integrating WebSphere MQ with Oracle Identity Manager. To do so:

1. In the WebSphere Admin Console, navigate to Applications, and then to Enterprise Applications.

2. Select Xellerate, and then select Nexaweb.

3. Click Uninstall.

C.4 Removing Resources for Default Messaging

To remove resource for default messaging:

1. In the WebSphere Admin Console, navigate to Resources, JMS, Queue Connection Factories.

2. Set the scope to the Cell Level for clustered and to the server level for nonclustered installations.

3. Select xlConnectionFactory, and then click Delete to remove it.

4. Navigate to Resources, JMS, Queues.

5. Set the scope to the Cell Level for clustered and to the server level for nonclustered installations.

6. Select all the queues that start with xl, and then click Delete.

7. Navigate to Resources, JMS, Activation Specification.

8. Set the scope to the Cell Level for clustered and to the server level for nonclustered installations.

9. Select all the activation specifications, and then click Delete to remove all.

10. Navigate to Service Integration, and then to Buses.

11. Select XellerateBus, and then click Delete to remove.

12. Click Save to save the changes in the main configuration.

    Note:

    For a clustered installation of Oracle Identity Manager, make sure to click Preferences, and select Synchronize changes with Nodes before clicking Save.

C.5 Changing the xlJMSLogin Credentials

To change the xlJMSLogic credentials:

1. Navigate to Security, Secure administration, applications and infrastructure, Java Authentication and Authorization Service (Under Authentication), J2C authentication data.

2. Click XLJMSLogin, and change the User ID and Password to the WebSphere MQ user name and password.

C.6 Creating WebSphere MQ Resources

To create WebSphere MQ resources:

1. Create queue connection factory. To do so:

   1. In the WebSphere Admin Console, navigate to Resources, JMS, Queue Connection Factories.

   2. Set the scope to the Cell Level for clustered and to the server level for nonclustered installations.

   3. Click New, and select WebSphere MQ messaging provider, and then click OK.

   4. For Name and JNDI name, enter xlConnectionFactory.

   5. Enter the other required information related to WebSphere MQ.

2. Create queue references on WebSphere:

   1. In the WebSphere Admin Console, navigate to Resources, JMS, Queues.

   2. Set the scope to the Cell Level for clustered and to the server level for nonclustered installations.

   3. Click New, and select WebSphere MQ messaging provider, and then click OK.

   4. Enter Name as xlQueue, JNDI name as queue/xlQueue, Base queue name as the name of the appropriate queue on Websphere MQ.

   5. Create six new queues with the following JNDI names:

      queue/xlQueue, queue/xlReconQueue, queue/xlAuditQueue, queue/xlAttestationQueue, queue/xlProcessQueue, and queue/xlErrorQueue

3. Create listener ports. To do so, in the WebSphere Admin Console, navigate to Servers, Application Servers, SERVER_NAME, Messaging, Message Listener Service, Listener Ports. Then create the following listener ports:

   • MessageHandlerMDB_JMSPort:

     • Name: MessageHandlerMDB_JMSPort

     • Connection factory JNDI name: xlConnectionFactory

     • Destination JNDI name: queue/xlQueue

   • ReconMessageHandlerMDB_JMSPort:

     • Name: ReconMessageHandlerMDB_JMSPort

     • Connection factory JNDI name: xlConnectionFactory

     • Destination JNDI name: queue/xlReconQueue

   • AuditMessageHandlerMDB_JMSPort:

     • Name: AuditMessageHandlerMDB_JMSPort

     • Connection factory JNDI name: xlConnectionFactory

     • Destination JNDI name: queue/xlAuditQueue

   • AttestationMessageHandlerMDB_JMSPort:

     • Name: AttestationMessageHandlerMDB_JMSPort

     • Connection factory JNDI name: xlConnectionFactory

     • Destination JNDI name: queue/xlAttestationQueue

   • ProcessMessageHandlerMDB_JMSPort:

     • Name: ProcessMessageHandlerMDB_JMSPort

     • Connection factory JNDI name: xlConnectionFactory

     • Destination JNDI name: queue/xlProcessQueue

   Note:

   For a clustered installation of Oracle Identity Manager, the step for creating listener ports must be repeated for all the servers in XL_CLUSTER.

C.7 Changing Deployment Descriptors

To make the message driven beans listen to MQ destinations, change the deployment descriptors. To do so:

1. Open the OIM_HOME/DDTemplates/BO/ibm-ejb-jar-bnd.xmi file.

2. Replace all occurrences of activationSpecJndiName with listenerInputPortName.

3. Replace xlQueueSpec with MessageHandlerMDB_JMSPort.

4. Replace xlReconQueueSpec with ReconMessageHandlerMDB_JMSPort.

5. Replace xlAuditQueueSpec with AuditMessageHandlerMDB_JMSPort.

6. Replace xlAttestationQueueSpec with AttestationMessageHandlerMDB_JMSPort.

7. Replace xlProcessQueueSpec with ProcessMessageHandlerMDB_JMSPort.

8. Save the ibm-ejb-jar-bnd.xmi file.

Note:

For a clustered installation of Oracle Identity Manager, copy the ibm-ejb-jar-bnd.xmi file to all the nodes on which Oracle Identity Manager is deployed.

C.8 Restarting IBM WebSphere Application Server

Restart WebSphere Application Server. For a clustered installation of Oracle Identity Manager, restart all the application servers as well as the Deployment Manager.

C.9 Running the patch_websphere Patch

Run the following patch utility to deploy Oracle Identity Manager with MQ integration:

• For UNIX:

  OIM_HOME/setup/patch_websphere.sh XELSYSADM_PASSWD OIM_DB_PASSWD

• For Microsoft Windows:

  OIM_HOME/setup/patch_websphere.cmd XELSYSADM_PASSWD OIM_DB_PASSWD

C.10 Restarting WebSphere Application Server

Restart WebSphere Application Server. For a clustered installation of Oracle Identity Manager, restart all the application servers as well as the Deployment Manager.

C.11 Rolling Back MQ Configuration

If required, then restore OIM_HOME and rollback the changes to IBM WebSphere Application Server by using the WAS_HOME/profiles/PROFILE_NAME/bin/restoreConfig.sh or restoreConfig.cmd script. Refer to IBM documentation for more information on how to use this utility.