Maintaining (deprecated) Version 5 default messaging resources

You can use the WebSphere® Application Server administrative console to manage the JMS connection factories and destinations for WebSphere Application Server Version 5.1 applications. JMS connection factories and destinations for the WebSphere Application Server Version 5.1 default messaging provider are not the same as those for the default messaging provider in WebSphere Application Server Version 6 and later. Such JMS resources are maintained as V5 default messaging resources.

About this task

In a deployment manager cell, you can use V5 default messaging resources to maintain Version 5 default messaging resources for Version 7.0, Version 6 and Version 5 nodes in the cell.
  • V5 default messaging configured against a Version 7.0 node provides a JMS transport to a messaging engine of a service integration bus that supports the default messaging provider in WebSphere Application Server Version 7.0. The messaging engine emulates the service of a JMS server running on WebSphere Application Server Version 5.1.
  • V5 default messaging configured against a Version 5.1 node provides a JMS transport to a JMS server running on WebSphere Application Server Version 5.1.

On a WebSphere Application Server Version 5.1 node in a deployment manager cell, a JMS server provides the functions of the JMS provider. You can also use the administrative console to manage a JMS server on a Version 5.1 node.

Procedure




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 5, 2014 9:49:51 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tmv5_ep
File name: tmv5_ep.html