JMS servers are environment-related configuration entities that act as management containers for JMS queue and topic destinations in JMS modules that are targeted to them. Multiple JMS modules can be targeted to each JMS server in a domain.
In a clustered server environment, a JMS server can targeted to a migratable target. A migratable target is a special target that can serve as a grouping of migratable JMS services, such as a JMS server, and which is active on only server member in a WebLogic cluster. In a cluster, a recommended best practice is to target a JMS server to a migratable target, so that a member server will not be a single point of failure. This way the JMS server can be manually migrated from an unhealthy server onto a healthy server, either in the event of server crash or for scheduled maintenance.
To create a JMS server:
Note: Once you create a JMS server, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
Note: When a JMS server is targeted to a migratable target (see Step 4), it cannot use the default file store, so a custom file store must be configured and targeted to the same migratable target.
Note that there are many optional parameters that can be set on the JMS server configuration tabs, including General configuration parameters, Thresholds and Quotas, Logging, and Server Session Pools. For more information about configuring these parameters, see Configure JMS servers.