On your messaging server, locate the following jar files:

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.

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 .

Continue with Section 3.1.3, Starting the Publish/Subscriber Broker.

From the command line, execute the following command:

strmqbrk -m QM

You should see a message indicating that the broker is running.

Continue with Section 3.1.4, Installing System Queues Necessary for Publish/Subscribe.

From the command line, execute the following command:

runmqsc QM < MQJMS_PSQ.mqsc

You should see some tracing, indicating successful queue creation.

Continue with Section 3.1.5, Creating a User Account.

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:

Edit the idm_jms_install.scp configuration file with definitions for each queue that is defined to connect with the Identity Manager JMS driver. For example, if the queue manager name is QM1, the publisher queue name is PQ1, and the subscriber queue is SQ1, then the definitions in the idm_jms_install.scp configuration file should be as follows:

-- Queue connection factory definition
define qcf(QueueConnectionFactory) +
       qmgr(QM1) +
       tran(CLIENT) +
       host(hostname) +
       port(1414)
 
-- Publisher Queue Definition---
define q(PQ1) +
       qmgr(QM1) +
       queue(PQ1)
 
-- Subscriber Queue Definition---
define q(SQ2) +
       qmgr(QM1) +
       queue(SQ2)

    -- q is the jndi name used in the JMS driver configuration.
    -- qmgr is the queue manager name.
    -- queue is the queue name.
    -- host is the IP address or host Name of the IBM Websphere MQ server.
    -- port is the queue manager listener port.

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 might 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.

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.

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 (see PROVIDER_URL).

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.