Using WebSphere MQ V7 as JMS Provider for WebSphere Application Server V7, V8.0 and V8.5, and MQ 9.0 for WAS V9.0
To demonstrate the use of a simple but functional Message Driven Bean (MDB) in WebSphere Application Server V7, V8.0 and V8.5, which interacts with WebSphere MQ V7 as the Java™ Messaging Service (JMS) provider. WAS 9.0 ships with MQ RA 9.0.
The MDB was created with Rational Application Developer (RAD) 7.5 and the Enterprise Archive File (EAR) file which contains the MDB can be downloaded from this techdoc.
The main scenario is to show how to configure both WebSphere Application Server and WebSphere MQ V7.x, in order for an MDB to get messages from MQ, using a WebSphere Application Server Listener Port from a Queue (Point to Point).
What is new in this update:
- On Aug-2012, the procedures in this techdoc were successfully tested with a queue manager running on MQ 126.96.36.199 and a WAS server 188.8.131.52 (using MQ RA 184.108.40.206).
- On May-2013, the procedures in this techdoc were successfully tested with a queue manager running on MQ 220.127.116.11 and a WAS server 18.104.22.168 (using MQ RA 22.214.171.124).
- On Aug-2016, the procedures were tested with a queue manager running on MQ 126.96.36.199 and a WAS server 188.8.131.52 (using MQ RA 184.108.40.206)
- When using MQ 7.1 or 7.5 queue managers, if the MQ JMS client in WAS gets a RC 2035, one possibility is that the "channel authentication records" are enabled. For more details see the following technote:
WMQ 7.1 or 7.5 queue manager - RC 2035 MQRC_NOT_AUTHORIZED when using client connection as an MQ Administrator
Additional scenarios are provided to illustrate the following:
- How to use MQ Topics to exploit Publish/Subscribe from MQ.
- How to use a WebSphere Application Server Activation Specification, instead of a Listener Port from WebSphere Application Server.
This document shows all of the screen shots needed for beginners.
This document has the following chapters:
- MQ V7 configuration: queue and topic
- WebSphere Application Server V7 and V8 configuration: JNDI objects
- WebSphere Application Server V7 and V8 deployment and testing of MDB
- Additional scenarios: Topic, Activation Specification
The MDB used in this presentation, was created with IBM Rational Application Developer (RAD) 7.5 as part of an Enterprise Java Bean, which is provided in an EAR file. The steps for its creation and testing are documented in a related techdoc:
Developing and testing an MDB using RAD 7.5, WebSphere Application Server V7 and MQ V7 as JMS Provider
Using an MDB with JMS message selectors with WebSphere MQ V7 and WebSphere Application Server V7 and V8.x
Includes sample code to create a message property "color"
Sample MDB: SampleJMSSelectorMdbEjbEAR.ear
Sample Java code: SampleJMSMsgProperty.java
Using an MDB that always rolls back a message to test the handling of poison messages (WebSphere MQ V7, WebSphere Application Server V7 and V8.x)
Includes sample MDB: SamplePoisonMsgMdbEjbEAR.ear
The following files are included as attachments to this techdoc:
- Using MQ V7 as JMS Provider for WAS V7 V8.pdf
- EAR file with MDB: SampleMDBEJB.ear
- Text file with code excerpt: onMessage.txt
Using MQ V7 as JMS Provider for WAS V7 and V8.x, and MQ V9 for WAS V9.pdf
File name: Using MQ V7 as JMS Provider for WAS V7 and V8.x, and MQ V9 for WAS V9.pdf
File size: 1.1 MB
File name: SampleMDBEJB.ear
File size: 3.57 KB
File name: onMessage.txt
File size: 1 KB
|Application Servers||WebSphere Application Server||Java Message Service (JMS)||AIX, HP-UX, Linux, Solaris, Windows||220.127.116.11, 8.5, 8.0, 7.0|
|Business Integration||IBM MQ|
WebSphere MQ WMQ
More support for:
Software version: 7.0, 7.1, 7.5, 8.0, 9.0
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows
Reference #: 7016505
Modified date: 2016-08-17