Defining WebSphereMQ (MQ Series) JMS Provider Settings

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

• You are configuring a JMS adapter.
• The default values on the interface relate to WebSphereMQ 5.3.

1. Enter the Topic/QueueConnectionFactory Java Class.

   This is the WebSphereMQ implementation of the Topic/QueueConnectionFactory.

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

2. Enter the Queue/TopicJava 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. 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.

8. 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.

     Note

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

9. Under Target Client, select one of the following:
   • WebSphereMQ (Non-JMS)

     The receiver uses the WebSphereMQ API.

   • JMS-Compliant

     The receiver uses the JMS API.

10. Determine whether you want to use a topic or a queue as the JMS destination, then perform one of the following sub steps:
    • To use a queue, enter the JMS Queue/Topic.
    • To use a topic, then perform the following sub steps:
      1. Select Enable Topic Support
      2. Enter the JMS Queue/Topic.
      3. Enter the Subscription ID and Client ID.

Defining Connection Pooling Settings

1. If you want to enable the sharing of a single TCP/IP socket connection for multiple JMS sessions from a single JMS connection object then in the  Connection Pool section, select Use Connection Pool.
   Note

   You use this option only with WebSphere MQ V6.0 and below. Connection pooling is a new feature in WebSphere MQ V7.0 and above, hence this feature should not be used with WebSphere MQ V7.0.

Enabling Security

1. If you want to secure the communication between the JMS adapter and the IBM WebSphere MQ JMS provider, in the Enable Security  section, select Use SSL.
   Note  

   The MQ QueueManager certificate should be present in the PI JEE engine TrustedCAs keystore.

2. Determine how you want to specify the cipher suite and select one of the options mentioned below.

To select the cipher suite from a list of predefined values, in the SSL Cipher Suite select WebSphere MQ Cipher Spec, and in the WSMQ Cipher Specselect the cipher specification.

To manually specify the cipher suite, select Other in the SSL Cipher Suite,  and in the Other Cipher Suite enter the cipher suite.

1. If you want to enable client authentication, select Client Authentication and select the keystore view and certificate and private key.
   Note

The PI certificate used for client authentication should be imported in the IBM QueueManagers key database.