WebSphere MQ (formerly MQSeries) is the messaging platform developed by IBM; it provides Java and JMS interfaces. Section 3.5.9 Configuring the JMS Service has information on the JMS service.
This chapter explains how WebSphere MQ can be used as a JMS provider within a JOnAS application server.
Refer to http://www-3.ibm.com/software/integration/mqfamily/library/manualsa/ for WebSphere MQ documentation.
WebSphere MQ, in contrast to JORAM and SwiftMQ, cannot run collocated with JOnAS. WebSphere MQ is an external software package that must be independently administered and configured.
Administering WebSphere MQ consists of the following steps:
Creating and configuring resources (such as queues) through the WebSphere MQ Explorer tool.
Creating the corresponding JMS objects (javax.jms.Queue, javax.jms.Topic, javax.jms.QueueConnectionFactory, etc.), and binding them to a registry.
The link between JOnAS and WebSphere MQ is established through the JOnAS registry. WebSphere MQ JMS objects are bound to the JOnAS registry. JMS lookups then return the WebSphere MQ JMS objects, and messaging takes place through these objects.
Given the complex configuration of WebSphere MQ JMS objects, it is not possible to create these objects from JOnAS. Therefore, during the starting phase, a JOnAS server expects WebSphere MQ JMS objects to have already been bound to the registry. It thus becomes necessary to start an independent registry, to which WebSphere MQ may bind its JMS objects, and which may also be used by the starting JOnAS server. The start-up sequence looks as follows:
Starting a registry.
Creating and binding WebSphere MQ JMS objects.
Launching the JOnAS server.
The following architecture is recommended:
A JOnAS server (for example called "Registry") that provides only a registry.
A JOnAS server (for example called "EJB") using the registry service of server "Registry".
Plus, of course, a WebSphere MQ server running locally.