A path service is persistent map that can be used to store the mapping of a group of messages to a messaging resource, such as a member of a distributed destination or a store-and-forward agent. It provides a way to enforce message ordering by pinning messages to a member of a cluster hosting servlets, distributed queue members, or store-and-forward agents.
Note: Once you create a path service, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
Note: When a path service is targeted to a migratable target (see Step 4), it cannot use the default store, so a custom store must be configured and targeted to the same migratable target. And, as a best practice, the path service and its store should be the only users of that migratable target.
Note: A recommended best practice is to target the path service to a migratable target, so that a member server will not be a single point of failure. A path service can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services. See Configure migratable targets for JMS-related services.
After you finish