Defining WebSphereMQ (MQ Series) JMS Provider Settings 

Use

Make specifications for the JMS provider WebSphereMQ (MQ Series).

Prerequisites

●      You are configuring a JMS adapter.

●      The default values on the interface relate to WebSphereMQ 5.3.

Procedure

...

       1.      Enter the QueueConnectionFactory Java Class.

This is the WebSphereMQ implementation of the QueueConnectionFactory.

The adapter uses a QueueConnectionFactory object to generate QueueConnection objects of the JMS provider.

       2.      Enter the Queue Java Class.

A queue object encapsulates a provider-specific queue name. This enables a client to make the queue JMS API methods known.

       3.      Enter the IP Address or Server Name of the machine on which the JMS provider is running.

If this is a local machine, the value is localhost.

       4.      Specify the Server Port.

       5.      Under Queue Manager Name, enter the display name of the queue manager.

       6.      Under Channel Name, specify the access channel for all queues.

       7.      Enter the name of theJMS Queue.

       8.      Under Character Set ID (CCSID) for Non-ASCII Names, specify the character set for the names specified above.

This entry does not affect the character set of the transferred messages.

       9.      Select the Transport/Network Protocol:

○       TCP/IP

The JMS adapter communicates with the MQ Series server using TCP/IP sockets.

○       WebSphereMQ

Communication takes place using dynamic libraries. For example, Microsoft uses files with the ending .DLL; Unix uses files with the ending .SO or .SL.

In a 64-bit operating system, the libraries must also be 64 bit.

If the libraries in a 64-bit operating system are not 64 bit, see SAP Note 790963.

   10.      Under JMS-Compliant, select one of the following:

○       WebSphereMQ (Non-JMS)

The receiver uses the WebSphereMQ API.

○       JMS-Compliant

The receiver uses the JMS API.