Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with a third-party or (deprecated) V5 default messaging provider
Maintain (deprecated) v5 default messaging resources
We can use the console to manage the JMS connection factories and destinations for WAS v5.1 applications. JMS connection factories and destinations for the WAS v5.1 default messaging provider are not the same as those for the default messaging provider in WAS Version 6 and later. Such JMS resources are maintained as V5 default messaging resources.
In a dmgr cell, you can use V5 default messaging resources to maintain v5 default messaging resources for nodes in the cell that are at later versions.
- V5 default messaging configured against a node in a later version of the product provides a JMS transport to a messaging engine of a service integration bus that supports the default messaging provider in that later version. 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.
Procedure
- List Version 5 default messaging resources.
- Configure Version 5 default messaging resources.
- Manage Version 5 JMS servers in a dmgr cell.
Related
List v5 default messaging resources
Configure v5 default messaging resources
Manage v5 JMS servers in a dmgr cell
JMS components on v5 nodes
Configure authorization security for v5 default messaging
Manage messaging with a third-party or (deprecated) V5 default messaging provider
Enable WAS v5.1 JMS usage of messaging resources in later versions of the product
Migrate from WAS v5 embedded messaging
Related
JMS provider settings