IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Linux and UNIX systems: configuring the queue manager to coordinate JMS resources

Define a stanza in the broker's queue manager qm.ini file for each new JMS provider, where the JMS provider can be specified by a JMS node included in a message flow that is running on the broker.

The parameters that are defined in XAOpenString are comma delimited and positional. Represent missing optional parameters by a comma if you include other parameters later in the string.

The following stanza entry is an example that you can add when using WebSphere® MQ Java™ as the JMS provider:

XAResourceManager:
    Name=WBIWMQJMS 
    SwitchFile=/install_dir/lib/libDynJMSSwitch.so
    XAOpenString=<Initial Context Factory>,
              <location of JNDI bindings>'
              <LDAP Principal>,
              <LDAP Credentials>,
              <Recovery Connection Factory Name>,
              <JMS Principal>,
              <JMS Credentials>  
              ThreadOfControl=THREAD

where:

install_dir: Is the location of the IBM® Integration Bus installation. This value is mandatory where the LDAP parameters are omitted, but a user-defined Queue Connection Factory is specified for recovery.
<Initial Context Factory>: Is the Initial Context Factory identifier for the JMS provider; this value is required.
<Location of JNDI bindings>: Is 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. When supplying the file path to the bindings file, do not include the file name. See the JMSInput or JMSOutput node for further details on creating the JNDI administered objects; this value is required.
<LDAP Principal>: Is an optional parameter used to specify the principal (user ID) that might be required when an LDAP database is used to hold the JNDI administered objects. LDAP Principal is not currently supported, it is reserved for future use.
<LDAP Credentials>: Is an optional parameter used to specify the Credentials (password) that might be required if a password protected LDAP database is used to hold the JNDI administered objects. LDAP Credentials is not currently supported, it is reserved for future use.
<Recovery Connection Factory Name>: Is an optional parameter used to specify 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>: Is an optional parameter for the user ID required to connect to a JMS provider, using a secure JMS Connection Factory. JMS Principal is not currently supported, it is reserved for future use.
<JMS Credentials>: Is an optional parameter for the password required to connect to the same JMS provider in conjunction with the JMS principal. JMS Credentials is not currently supported, it is reserved for future use.

Switch files are installed in the install_dir /lib directory. To simplify the contents of the qm.ini file, create a symbolic link to the switch file for the queue manager to retrieve.

On all Linux and UNIX systems except Linux on x86, set up links in the /var/mqm/exits64 directory.

On Linux on x86, set up links in the /var/mqm/exits directory.

The file name for all platforms is libDynJMSSwitch.so.

Specify the same name of the switch file, libDynJMSSwitch, or your own value, in the /exits64 or /exits directory, as relevant. For example, on AIX®:

ln -s install_dir/lib/libDynJMSSwitch.so /var/mqm/exits64/libDynJMSSwitch

The values for the Initial Context factory and Location of JNDI bindings in the stanza must match the values that you specified in the JMS or SOAP 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.

The following example shows the format of a stanza in the qm.ini file that describes a JMS provider for global transactions:

XAResourceManager:
    Name=XAJMS_PROVIDER1 
    SwitchFile=/opt/var/mqsi/lib/libDynJMSSwitch.so
    XAOpenString= com.sun.jndi.fscontext.RefFSContextFactory,
              /Bindings/JMSProvider1_Bindings_Directory,
              ,
              ,
              ,  
              myJMSuser1,
              passwd 
              ThreadOfControl=THREAD

where:

XAJMS_PROVIDER1: Is the user-defined name for the resource manager
/opt/var/mqsi: Is the <Installation Path>
com.sun.jndi.fscontext.RefFSContextFactory: Is the <Initial Context Factory>
/Bindings/JMSProvider1_Bindings_Directory: Is the location of the bindings
myJMSuser1: Is the <JMS Principal>
passwd: Is the password used in <JMS Credentials>

In this example, the optional fields <LDAP Principal>, <LDAP Credentials>, and <Recovery Connection Factory Name> are not required, therefore the positional comma delimiters only are configured in the XAOpenString stanza.

ac28610_.htm |

Last updated Friday, 21 July 2017