![Red Hat Application Server Скачать руководство пользователя страница 261](http://html.mh-extra.com/html/red-hat/application-server/application-server_manual_1427406261.webp)
Chapter 35.
Using WebSphere MQ JMS
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.
35.1. Architectural Rules
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 indepen-
dent 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:
1. Starting a registry.
2. Creating and binding WebSphere MQ JMS objects.
3. 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.
35.2. Setting the JOnAS Environment
The suggested architecture requires two JOnAS server instances. You can do this as follows:
1. Create two base directories. For example
JONAS_REGISTRY
and
JONAS_EJB
.
2. Set the JONAS_BASE environment variable so that it points towards the
JONAS_REGISTRY
directory.
Содержание Application Server
Страница 1: ...Red Hat Application Server JOnAS User Guide ...
Страница 8: ......
Страница 22: ...14 Chapter 1 Java Open Application Server JOnAS a J2EE Platform ...
Страница 58: ...50 Chapter 3 JOnAS Configuration ...
Страница 66: ...58 Chapter 5 JOnAS Class Loader Hierarchy ...
Страница 78: ...70 Chapter 6 JOnAS Command Reference ...
Страница 80: ......
Страница 86: ...78 Chapter 7 Developing Session Beans ...
Страница 136: ...128 Chapter 9 Developing Message Driven Beans ...
Страница 142: ...134 Chapter 10 Defining the Deployment Descriptor ...
Страница 148: ...140 Chapter 11 Transactional Behavior of EJB Applications ...
Страница 158: ...150 Chapter 14 EJB Packaging ...
Страница 162: ...154 Chapter 15 Application Deployment and Installation Guide ...
Страница 164: ......
Страница 176: ...168 Chapter 18 WAR Packaging ...
Страница 178: ......
Страница 184: ...176 Chapter 20 Defining the Client Deployment Descriptor ...
Страница 186: ...178 Chapter 21 Client Packaging ...
Страница 188: ......
Страница 192: ...184 Chapter 23 EAR Packaging ...
Страница 194: ......
Страница 200: ...192 Chapter 24 JOnAS Services ...
Страница 204: ...196 Chapter 25 JOnAS and the Connector Architecture ...
Страница 222: ...214 Chapter 27 Ant EJB Tasks Using EJB JAR ...
Страница 234: ...226 Chapter 29 Web Services with JOnAS ...
Страница 236: ......
Страница 260: ...252 Chapter 34 How to use Axis in JOnAS ...
Страница 270: ...262 Chapter 36 Web Service Interoperability between JOnAS and BEA WebLogic ...
Страница 296: ......