IBM Websphere JMS Server through Adeptia Suite

 Web Sphere MQ allows connection in two modes

  • Binding – In this mode the Web Sphere MQ and the client should be on the same system. This is usually preferable for security point of view.
  • Client – In this mode the client connects to the Web Sphere MQ using the TCP protocol. In this mode appropriate channel should be opened in the Web Sphere MQ to send/receive the data.

 

Jar Name

Location

Needed for Connection Mode

com.ibm.mq.headers.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client

com.ibm.mq.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client

com.ibm.mq.jmqi.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client & Binding

com.ibm.mq.jms.Nojndi.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client & Binding

com.ibm.mqjms.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client & Binding

dhbcore.jar

Located in

[WebsphereMQInstallDir]/java/lib

Client & Binding

 

  • Additional configuration(for Binding Mode only)
    • Set any one of the following System properties

 

Property Name

Value

java.library.path

[WebsphereMQInstallDir]/java/lib64

com.ibm.mq.cfg.jmqi.libpath

[WebsphereMQInstallDir]/java/lib64

 

  • Properties for Initial Context object

Property Name

Default/Sample Value

java.naming.factory.initial

com.ibm.mq.jms.Nojndi

 

  • Queue Connection Factory Name

Connection Mode

Connection Factory Name

Binding

(connectQueueManager(<QueueManagerName>))

Parameters List

  • <QueueManagerName> - refers to the Queue Manger as defined in the Web Sphere MQ.

E.g. (connectQueueManager(JMSDEMO))

Client

(connectQueueManager(<QueueManagerName>)binding(client)clientChannel(<ChannelName>)clientConnection(<ServerHostName>:<Portno>))

Parameters List

  • <QueueManagerName> - refers to the Queue Manger as defined in the Web Sphere MQ.
  • <ChanneNamel> - refers to the Channel as defined in the Web Sphere MQ. If the auto channel creation is enabled then the above channel will be created if it does not exist on the Server side.
  • <ServerHostName> - IP address or name for the remote Web Sphere MQ Server.
  • <Portno> - port on which a TCP listener is running for the Remote Web Sphere MQ Server.

E.g. (connectQueueManager(JMSDEMO)binding(client)clientChannel(myChannel1)clientConnection(localhost:1414))

 

 

 

When using IBM Websphere JMS server though Adeptia, you'll need to make the following change:

1) Comment the entry “web/libs/VLTrader/com.ibm.mq.jar” from “etc/launcher.properties” file by adding a pound (#) sign before this entry e.g. “# web/libs/VLTrader/com.ibm.mq.jar” in the “launcher.properties” file.

Launcher.Prop.jpg

2) Restart the Adeptia Server.

This is because “web/libs/VLTrader/com.ibm.mq.jar” jar gets conflicted with the IBM Websphere JMS server “com.ibm.mq.jar” jar which we load on classpath at runtime. This conflict creates a problem in the integration of IBM Websphere JMS server with Adeptia Suite.

Have more questions? Submit a request

0 Comments

Article is closed for comments.