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.
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 store, so a custom store must be configured and targeted to the same migratable target.
Note: In a clustered server environment, 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. A JMS server can also be automatically migrated from an unhealthy server instance to a healthy server instance, with the help of the server health monitoring services.
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.