Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(3 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

HOW TO: Configure PowerExchange for JMS with IBM WebSphere MQ
Solution

The following instructions cover using PowerExchange for JMS with an IBM WebSphere MQ (version 7.0):

Step 1. Add IBM required Jar files

Add the following WebSphere MQ libraries to $INFA_HOME/server/bin/javalib (or $CLASSPATH):

  • com.ibm.mq.allclient.jar
  • com.ibm.mq.axis2.jar
  • com.ibm.mq.commonservices.jar
  • com.ibm.mq.defaultconfig.jar
  • com.ibm.mq.headers.jar
  • com.ibm.mq.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.jms.Nojndi.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mq.pcf.jar
  • fscontext.jar
  • jms.jar
  • providerutil.jar
  • com.ibm.mq.postcard.jar
  • com.ibm.mq.soap.jar
  • com.ibm.mq.tools.ras.jar
  • com.ibm.mq.traceControl.jar
  • com.ibm.mqjms.jar
  • jndi.jar
  • jta.jar
  • ldap.jar
  • rmm.jar

Step 2. Configure WebSphere MQ JMS Provider

UNIX/Linux

  1. Edit the JMSAdmin.config file located in <WebSphereMQ>/Java/bin directory.

  2. Set the following properties:

    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    PROVIDER_URL=file:/var/mqm/jndi

  3. Create the directory /var/mqm/jndi.
    This directory will hold the JNDI bindings for looking up JMS Connection Factories and Destinations within MQSeries.

Windows

  1. Edit the JMSAdmin.config file located in <WebSphereMQ>\Java\bin directory

  2. Set the following properties:

    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    PROVIDER_URL=file://localhost/D:/JNDIBindings

  3. Create the directory D:\JNDIBindings 
    This directory will hold the JNDI bindings for looking up JMS Connection Factories and Destinations within MQSeries.

Step 3. Create JMS connection factory

Create the JMS connection factory using the WebSphere MQ Explorer as follows:

  1. Right click on JMS Administered Objects.

  2. Select Add Initial Context ....

  3. Select File System. 

  4. In the Bindings Director field, enter file:/var/mqm/jndi (UNIX) or file://localhost/D:/JNDIBindings (Windows).

  5. Click Finish.
    When finished, a JNDI bindings file called .bindings should appear in the directory specified above.

  6. Right-click on the Connection Factories folder and select New > Connection Factory.

  7. Enter Connection_Factory in the name field and click Next.

  8. Select Queue Connection Factory in the Type list.

  9. Click Finish.

Step 4. Create JMS destination

 Create a JMS destination using the WebSphere MQ Explorer as follows:

  1. Click on the plus (+) sign next to the Queue Manager name to expand the view and see all the folders.

  2. Right click on the Queues folder and select New > Local Queue.

  3. Enter INPUTQ in the name field and click Finish.

  4. Repeat the above to define another local queue called OUTPUTQ.

Step 5. Configure the PowerExchange for JMS session

In the PowerCenter Workflow Manager do the following:

  1. Create a JNDI Application connection, and set the properties as follows:

    • JNDI Context Factory = com.sun.jndi.fscontext.RefFSContextFactory

    • JNDI Provider URL = file:/var/mqm/jndi (UNIX) OR file://localhost/D:/JNDIBindings (Windows)

  2. Create a JMS Application connection, and set the properties as follows:

    • JMS Connection Factory Name = Connection_Factory

    • JMS Destination = INPUTQ (to read from INPUTQ) OR OUTPUTQ (to write to OUTPUTQ)

  3. Create a JMS session with these JNDI/JMS connections.

​​
More Information
Disclaimer: 
The sample configuration provided above, using IBM WebSphere 7.0, is an example for illustration purposes only.  There are other approaches to establish connection to a queue or topic. Since message queues or topics are provided by third party vendors, we strongly encourage you to discuss your approach to hardening or securing message queues with IBM messaging specialists. Products can evolve; hence, processes for hardening them might change over time.  The list of IBM required jar files mentioned above can be also changed.

If you have any problems with the processes discribed in this document, we ask you to work with the IBM Technical Support Team directly. You should use these recommendations as a starting point and customize the configuration for your specific operating environment.

Java archive (JAR) file: com.ibm.mqbind.jar
This section gives information in relation to the com.ibm.mqbind.jar file. The Java archive (JAR) file com.ibm.mqbind.jar has been deprecated and is no longer supplied with WebSphere® MQ. If your Java applications have been relying on the contents of this file, you will need to change them to use the file com.ibm.mq.jar when you migrate to WebSphere MQ, Version 6.0.
Reference
Applies To
Product: PowerExchange
Problem Type: Performance
User Type: Administrator
Project Phase: Configure
Product Version: PowerExchange for JMS
Database:
Operating System:
Other Software:
Attachments
Last Modified Date:5/22/2019 9:13 AMID:113581
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)