Administration Console Online Help

Configure path
services

A path service is a 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.

The default persistent file store requires no additional
configuration. However, if you require a custom file store or JDBC
store to suit your specific needs, you need to create the custom
store before creating a path service.

If you skipped the targeting step when you created a path
service, or want to modify the current targeting parameters, you can
do so at anytime. You can retarget a path service to a different
cluster member or migratable target. Migratable targets define a set
of WebLogic Server instances in a cluster that can potentially host a
pinned service, such as a path service. See Change path service
targets.

Note: A recommended best practice is to target a 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.