Windows® systems: configuring the queue manager to coordinate JMS resources

Use WebSphere® MQ Explorer (if you have WebSphere MQ Version 6.0) or WebSphere MQ Services (if you have WebSphere MQ Version 5.3) to configure the XA resource managers for the queue manager.

Complete the following steps:

  1. Open WebSphere MQ Explorer or WebSphere MQ Services.
  2. Select the queue manager for your broker and click Properties.
  3. Select XA resource managers in the left pane and click Add.
  4. Complete the fields to define a new resource manager:
    • Name: Enter the name of the resource manager; for example, WBIWMQJMS.
    • SwitchFile: Enter the full path of the switch file; for example, install_dir\bin\JMSSwitch.dll.
    • XAOpenString: Enter the following values, which are comma delimited and positional. Represent missing optional parameters by a comma if you include other parameters later in the string.
      Initial Context Factory
      The Initial Context Factory identifier for the JMS provider; this value is required.
      Location of JNDI bindings
      Either the file path to the bindings file, or the LDAP directory location of the JNDI administered objects that can be used to create an initial context factory for the JMS connection. If you supply the file path to the bindings file, do not include the file name. See the JMSInput or JMSOutput node for further details about creating the JNDI administered objects; this value is required.
      LDAP Principal
      Optional: The principal (user ID) that might be required when an LDAP database is used to hold the JNDI administered objects.
      LDAP Credentials
      Optional: The credentials (password) that might be required if a password protected LDAP database is used to hold the JNDI administered objects.
      Recovery Connection Factory Name
      Optional: The name of a Queue Connection Factory object in the JNDI administered objects for recovery purposes, when the non default name is required.
      JMS Principal
      The user ID that is required to connect to a JMS provider, using a secure JMS Connection Factory.
      JMS Credentials
      The password that is required to connect to the same JMS provider in conjunction with the JMS principal.

      The values for the Initial Context factory and Location of JNDI bindings in the stanza must match the values that you specified in the JMSInput or JMSOutput nodes in the message flows.

      All LDAP parameters must match the values that you specified on the mqsicreatebroker or mqsichangebroker command.

      The Recovery Factory Name must match a Queue Connection Factory name that is created in the JNDI administered objects. If you do not specify a name, a default factory called recoverXAQCF is used. In either case, this value must refer to a JNDI administered object that has already been created.

      The JMS Principal and JMS Credentials must be configured together.

    • XACloseString: Leave this field blank.
    • ThreadOfControl: Set the value Thread.
  5. Click OK to complete the XA resource manager definition.
  6. Click OK to close the queue manager properties dialog.
  7. Click File > Exit to close WebSphere MQ Explorer or WebSphere MQ Services.
  8. Copy the switch file (for example, JMSSwitch.dll) to the \exits subdirectory in the WebSphere MQ installation directory.
Start of changeNext: modify the queue manager authorization.End of change
Related tasks
Configuring JMSInput and JMSOutput nodes to support global transactions
Windows systems: modifying the queue manager authorization
Related reference
mqsicreatebroker command
mqsichangebroker command
JMSInput node
JMSOutput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:39:58

ac28620_