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

Why and when to perform this task

WebSphere application server Version 5 applications can use JMS resources provided by the default messaging provider of WebSphere
application server version 6. You can use the WebSphere administrative console to manage the JMS connection factories and destinations for WebSphere Application Server Version 5 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 Version 5 default messaging resources for both Version 6 and Version 5 nodes in the cell.

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

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

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

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

• Listing Version 5 default messaging resources

• Configuring Version 5 default JMS resources

• Managing Version 5 JMS servers in a deployment manager cell

• Configuring authorization security for a Version 5 default messaging provider

Related tasks
Managing WebSphere Version 5 JMS use of WebSphere version 6 JMS resources
Migrating from Version 5 embedded messaging to version 6