JNDI

You need a .bindings context for the JNDI connection of the Integration Server. You can create one in the MQ Explorer. Simply right-click JMS Administered Objects and select Add Initial Context.

Now you have to enter the location details of the JNDI namespace.

Then a Connection Factory has to be defined.

The name can be chosen freely since it can be set in configuration file ./etc/message.xml. The important thing is the transport type.

If the Integration Server is on the same computer as the MQ server, the transport type Bindings can be selected. Otherwise, you have to choose type MQ Client.

If you use transport type MQ Client, you can set the IP and the port of the MQ server in menu item Connection.

Now we have to define a destination.

The name of the destination can be chosen freely but you also have to set it in configuration file ./etc/message.xml.

You have to enter the Queue manager and the Queue in menu item General.

In order for the (Integration Server to be able to connect, the .bindings file created after defining the destinations must be placed in folder ./conf/JNDI.

For client access, the Integration Server still requires the following libraries, which can be taken from the WebSphere MQ installation.

./extlib:

./lib:

The DLLs are also part of the WebSphere MQ server installation and can be copied from the following paths.

For older versions, e.g. WebSphere version 5.3, the above-mentioned libraries do not exist. In these cases, the libraries from version 8.0 can be used.