WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Installing and configuring a JMS provider

This topic provides information about using JMS providers with WebSphere Application Server. A JMS provider enables use of the Java Message Service (JMS) and other message resources in WebSphere Application Server, for example when interoperating with a WebSphere MQ network.

About this task

WebSphere Application Server supports asynchronous messaging through the use of JMS providers and their related messaging systems. These JMS providers conform to JMS 1.1. To use message-driven beans (MDBs), JMS providers must include Application Server Facility (ASF), an optional feature which is part of the same specification, or alternatively they must use an inbound resource adapter that conforms to JCA 1.5.

WebSphere Application Server itself can act as a messaging system if you configure a service integration bus that can be accessed through the default messaging provider. You install this as part of WebSphere Application Server, and configure and manage it using the administrative console. This type of messaging is fully integrated with the WebSphere Application Server runtime.

WebSphere MQ can also be used as an external JMS messaging provider, where you to configure the resources needed for connecting to any queue manager on the WebSphere MQ network. The preferred solution for publish and subscribe messaging with WebSphere MQ as an external JMS messaging provider is to use a message broker such as WebSphere MQ Event Broker. If you install WebSphere MQ as an external JMS messaging provider, you use the WebSphere Application Server administrative console to administer the WebSphere MQ JMS resources, for example queue connection factories. You administer security through WebSphere MQ.

WebSphere Application Server includes the following JMS providers:
  • WebSphere default messaging provider. This provider represents a fully integrated messaging engine. This provider is based on WebSphere MQ messaging and is designed for use by new JMS applications.
  • WebSphere v5 default messaging provider. This provider is identical to the v5 default provider. Only the name has changed. It provides backwards compatibility. WebSphere Application Server v6 also supports a WebSphere Application Server v5 emulation mode that allows applications running in a mixed cell in WebSphere Application Server v5 to connect with and use resources that are managed by WebSphere Application Server v6. This provider allows you to create WebSphere Application Server v5 resource definitions that enable WebSphere Application Server v6 applications to connect to WebSphere Application Server v5 resources in a mixed cell. The WebSphere Application Server v5 infrastructure is not carried over into WebSphere Application Server v6.
  • WebSphere MQ messaging provider. This provider has additional attributes, and supports the JMS 1.1 unified connection factory. The WebSphere MQ messaging provider is an external provider that allows you to define resources for connecting directly to the queues in a WebSphere MQ network.
  • Generic messaging provider. This provider supports the JMS 1.1 unified connection factory. It allows you to use other, arbitrary JMS providers.

For more information about the support for JMS providers, see JMS provider support .

For more information about installing and using JMS providers, see Installing the default messaging provider, and Installing WebSphere MQ as a JMS provider.

For more information about scenarios and considerations for using WebSphere MQ with WebSphere Application Server, see the White Papers and Red books provided by WebSphere MQ; for example, through the WebSphere MQ library Web page at http://www-3.ibm.com/software/ts/mqseries/library/.

If you want to use a JMS provider other than the default messaging provider or WebSphere MQ, see Defining the JMS provider to WebSphere Application Server.
Note: You can use the WebSphere Application Server administrative console to administer JMS connection factories and destinations (within WebSphere Application Server) for a generic provider, but cannot administer the JMS provider or its resources outside of WebSphere Application Server.

Procedure




Sub-topics
Installing the default messaging provider
Related concepts
JMS provider support
Related tasks
tmj_instm.html
Defining a generic messaging provider
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tmj_inst0.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)