As part of installing WebSphere for the driver, you should complete the following tasks consecutively. These instructions are for Windows*, but you can follow the same procedure for other platforms.
On your messaging server, locate the following jar files:
com.ibm.mq.jar
com.ibm.mqjms.jar
connect.jar
dhbcore.jar
jta.jar
fscontext.jar
jndi.jar
Copy the jar files to the Identity Manager server.
The following table identifies where to place jar files on an Identity Management server, by platform.
Locate where you installed the installation script during the JMS driver installation. The following table indicates the default directories where scripts are installed, by platform.
Copy the script to your messaging server.
If necessary, restart your eDirectory™ server.
The following instructions are for Windows; equivalent steps vary by platform.
Click > > > .
Right-click the > folder.
Select > .
Select the .
Fill in the field.
If you don’t name the queue, you might later see an error indicating “MQJMS5053:*** No broker response. Please ensure that the broker is running. If you are using the WebSphere MQ broker, check that your brokerVersion is set to V1.***” This error is a side effect caused by the OS application event log filling up (on Windows).
Type SYSTEM.DEAD.LETTER.QUEUE for the field.
Click the button and wait for the operation to finish.
Continue with Setting Up Auto-Start for the Topic Message Broker.
Click > > >
Right-click the > > > > folder.
Select > .
Fill in the field. (For example, startBroker.)
Under :
Set the field to .
Set the field to .
Set the field to .
Click and wait for a success message.
From the command line, change directories to Program Files\IBM\WebSphere MQ\Java\bin.
From the command line, execute the following command:
runmqsc QM < idm_mq_install.mqsc
This file is provided only as an example; you might need to customize the content .
From the command line, execute the following command:
strmqbrk -m QM
You should see a message indicating that the broker is running.
From the command line, execute the following command:
runmqsc QM < MQJMS_PSQ.mqsc
You should see some tracing, indicating successful queue creation.
NOTE:If you don’t enter this command, you might see the following error: “MQJMS1111: JMS 1.1 The required Queues/Publish Subscribe services are not set up {0} error.”
Click > > > .
Expand the subtree.
Right-click the folder, then select .
Specify a username. The scripts referenced in these instructions assume .
Specify a password. The scripts referenced in these instructions assume .
Deselect the check box.
Click the button.
Click the button.
Right-click the newly created user, then click .
Select the tab.
Left-click the mqm group
Click .
Click twice.
Edit the Program Files\IBM\WebSphere MQ\Java\bin\JMSAdmin.bat file
@echo off ::add this line at the beginning of the file setlocal ::add the following line before call to java set JRE_PATH=C:\Program Files\IBM\WebSphere MQ\gskit\jre ::replace call to Java "%JRE_PATH%\bin\java" -cp "%CLASSPATH%" -DMQJMS_INSTALL="%MQ_JAVA_INSTALL_PATH%" -DMQJMS_LOG_DIR="%MQ_JAVA_DATA_PATH%"\log -DMQJMS_TRACE_DIR="%MQ_JAVA_DATA_PATH%"\errors -DMQJMS_INSTALL_PATH="%MQ_JAVA_INSTALL_PATH%" com.ibm.mq.jms.admin.JMSAdmin %1 %2 %3 %4 %5 ::add this line at end of file endlocal
Edit the Program Files\IBM\WebSphere MQ\Java\bin\JMSAdmin.config file.
# comment out all of the INITIAL_CONTEXT_FACTORY lines using # comment char “#” and add this line: INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory # comment out all PROVIDER_URL lines and add this one: PROVIDER_URL=file://<hostmname>:<port>/<path of binding file>
Locate where you installed the installation script during the driver installation. The following table indicates the default directories where scripts are installed by platform.
Copy the following scripts to the Program Files\IBM\WebSphere MQ\Java\bin directory on your messaging server:
idm_jms_install.scp
idm_jms_uninstall.scp
idm_mq_install.mqsc
idm_mq_uninstall.mqsc
install.bat
uninstall.bat
Update the connection factory IP addresses and port in idm_jms_install.scp.
Update the listener port in idm_mq_install.mqsc.
From the command line, change directories to Program Files\IBM\WebSphere MQ\Java\bin.
From the command line, execute the following command:
JMSAdmin.bat -v < idm_jms_install.scp
This file is provided as an example only; you may need to customize the content.
From the command line, manually start the publish/subscribe broker by executing the following command:
Program Files\IBM\WebSphere MQ\bin\strmqbrk.exe.
From the command line, ensure that the publish/subscribe broker is configured correctly by executing the following command:
Program Files\IBM\WebSphere MQ\Java\PSIVTRun.bat -nojndi -t
Make sure the .bindings file resides in the correct location.
If the driver, WebSphere MQ, Metadirectory engine, and Identity Vault are all on the same server, make sure the .bindings file resides in the location specified by the PROVIDER_URL option for the driver configuration (seeShow standard JNDI context parameters).
If the driver and WebSphere MQ are on one server and the Metadirectory engine and Identity Vault are on another server (a Metadirectory server), copy the .bindings file to the Metadirectory server and make sure the PROVIDER_URL includes the correct path to the file. If multiple Metadirectory servers connect to the WebSphere MQ server, copy the .bindings file to the PROVIDER_URL path on each Metadirectory server.
The .bindings file is generated during the Websphere MQ configuration. When you run the JMSAdmin.bat -v idm_jms_install.scp command, the .bindings file is generated under the path specified in the JMSAdmin.config file.