3.1 Installing IBM WebSphere MQ on Win32

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.

3.1.1 Placing Prerequisite Jar Files and Scripts

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

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

    Platform

    Directory Path

    Windows

    Local installation: novell\NDS\lib

    Remote installation: novell\RemoteLoader\lib

    Linux*/UNIX*

    Local installation: /usr/lib/dirxml/classes (pre-eDirectory 8.8) or opt/novell/eDirectory/lib/dirxml/classes (eDirectory 8.8)

    Remote installation: /usr/lib/dirxml/classes (pre-eDirectory 8.8) or /opt/novell/eDirectory/lib/dirxml/classes (eDirectory 8.8)

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

    Platform

    Directory Path

    Windows

    C:\Novell\NDS\DirXMLUtilities\jms\webmq

    Linux\UNIX

    install-dir/lib/dirxml/rules/jms\webmq

  4. Copy the script to your messaging server.

  5. If necessary, restart your eDirectory™ server.

3.1.2 Creating a Default Queue Manager

The following instructions are for Windows; equivalent steps vary by platform.

Manually Creating a Queue Manager through WebSphere MQ Explorer

  1. Click Start > Programs > IBM WebSphere MQ > WebSphere MQ Explorer.

  2. Right-click the IBM WebSphere MQ > Queue Managers folder.

  3. Select New > Queue Manager.

  4. Select the Make this the default queue manager.

  5. Fill in the Name 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).

  6. Type SYSTEM.DEAD.LETTER.QUEUE for the Dead Letter Queue field.

  7. Click the Finish button and wait for the operation to finish.

  8. Continue with Setting Up Auto-Start for the Topic Message Broker.

Setting Up Auto-Start for the Topic Message Broker

  1. Click Start > Programs > IBM WebSphere MQ > WebSphere MQ Explorer

  2. Right-click the IBM WebSphere MQ > Queue > Managers > Advanced > Services folder.

  3. Select New > Service.

  4. Fill in the Name field. (For example, startBroker.)

  5. Under General:

    1. Set the Service control field to Queue Manager Start.

    2. Set the Start command field to strmqbrk.

    3. Set the Stop command field to endmqbrk.

  6. Click Finish and wait for a success message.

3.1.3 Creating a Server-Connection Channel and Queues

  1. From the command line, change directories to Program Files\IBM\WebSphere MQ\Java\bin.

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

3.1.4 Starting the Publish/Subscriber Broker

  1. From the command line, execute the following command:

    strmqbrk -m QM

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

3.1.5 Installing System Queues Necessary for Publish/Subscribe

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

3.1.6 Creating a User Account

Creating a User

  1. Click Start > Programs > Administrative Tools > Computer Management.

  2. Expand the Local Users and Groups subtree.

  3. Right-click the Users folder, then select New User.

  4. Specify a username. The scripts referenced in these instructions assume idm.

  5. Specify a password. The scripts referenced in these instructions assume novell.

  6. Deselect the User must change password at next login check box.

  7. Click the Create button.

  8. Click the Close button.

Making the User a Member of the mqm Group

  1. Right-click the newly created user, then click Properties.

  2. Select the Member Of tab.

  3. Left-click the mqm group

  4. Click Add.

  5. Click OK twice.

3.1.7 Setting Up JMS

  1. 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
    
  2. 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>
    
  3. Locate where you installed the installation script during the driver installation. The following table indicates the default directories where scripts are installed by platform.

    Platform

    Directory Path

    Windows

    C:\Novell\NDS\DirXMLUtilities\jms\webmq

    Linux/UNIX

    install-dir/lib/dirxml/rules/jms/webmq

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

  5. Update the connection factory IP addresses and port in idm_jms_install.scp.

  6. Update the listener port in idm_mq_install.mqsc.

  7. From the command line, change directories to Program Files\IBM\WebSphere MQ\Java\bin.

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

  9. From the command line, manually start the publish/subscribe broker by executing the following command:

    Program Files\IBM\WebSphere MQ\bin\strmqbrk.exe.

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

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

Generating a .bindings File

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.