Maintain (deprecated) V5 default messaging resources
This page is the entry-point into a set of topics about maintaining messaging resources provided for WAS V5.1 applications by the V5 default messaging provider.
JMS applications running on WAS V5.1 can use JMS resources provided by the V5 default messaging provider in WAS Version 7. Use the WAS admin console to manage the JMS connection factories and destinations for WAS V5.1 applications. Such JMS resources are maintained as V5 default messaging resources. In a dmgr cell, we can use V5 default messaging resources to maintain V5 default messaging resources for V7, V6 and V5 nodes in the cell.
- V5 default messaging configured against a V7 node provides a JMS transport to a messaging engine of a service integration bus that supports the default messaging provider in WAS V7. The messaging engine emulates the service of a JMS server running on WAS Version 5.1.
- V5 default messaging configured against a V5.1 node provides a JMS transport to a JMS server running on WAS V5.1.
On a WAS V5.1 node in a dmgr cell, a JMS server provides the functions of the JMS provider. We can also use the admin console to manage a JMS server on a V5.1 node.
Listing V5 default messaging resources
Set V5 default messaging resources
Manage V5 JMS servers in a dmgr cell
Related concepts
JMS components on V5 nodes
Related tasks
Set authorization security for V5 default messaging
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Manage WAS V5 JMS use of messaging resources in later versions of WAS ND
Migrate from WAS V5 embedded messaging
Related
JMS provider settings