Maintaining V5 default messaging resources

This topic is the entry-point into a set of topics about maintaining messaging resources provided for WebSphere Application Server V5 applications by the default messaging provider.

Overview

WebSphere Application Server V5 applications can use JMS resources provided by the default messaging provider of WebSphere application server V6. You can use the WebSphere Application Server administrative console to manage the JMS connection factories and destinations for WebSphere Application Server V5 applications. Such JMS resources are maintained as V5 Default Messaging resources. In a deployment manager cell, you can use V5 Default Messaging resources to maintain V5 default messaging resources for both version 6 and V5 nodes in the cell.

• V5 Default Messaging configured against a V6 node provides a JMS transport to a messaging engine of a service integration bus that supports the V6 default messaging provider. The messaging engine emulates the service of a V5 JMS server.

• V5 Default Messaging configured against a V5 node provides a JMS transport to a V5 JMS server.

You can also use the administrative console to manage a JMS server on a V5 node.

For more information about maintaining Version 5 default messaging resources, see the following topics:

Procedure

• Listing V5 default messaging resources

• Configuring V5 default JMS resources

• Managing V5 JMS servers in a deployment manager cell

• Configuring authorization security for a V5 default messaging provider

Related tasks