Servers: Services: JMS

The following JMS sysem modules have been explicitly targeted to this server. JMS system resources are configured and stored as modules similar to standard J2EE modules. Such resources include queues, topics, connection factories, templates, destination keys, quota, distributed queues, distributed topics, foreign servers, and JMS store-and-forward (SAF) parameters.

The following JMS modules and JMS servers have been explicitly targeted to this server. JMS servers act as management containers for the queues and topics in JMS modules that are targeted to them.

Column Display

You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.

The following table lists all of the data points that you can display in columns on this page.

Name	Description
Name	The name of this JMS server.
Persistent Store	The file or database in which this JMS server stores persistent messages. If unspecified, the JMS server uses the default persistent store that is configured on each targeted WebLogic Server instance. The disk-based file store or JDBC-accessible database store that you specify must be targeted to the same server instance as this JMS server. Multiple services on the same WebLogic Server instance, including multiple JMS servers, may share the same persistent store. Each service's persistent data will be kept apart. If you specify a PersistentStore, the deprecated Store field must not be set. If neither PersistentStore nor the Store field are set, the JMS server will support persistent messaging using the default persistent store for the targeted WebLogic Server instance. MBean Attribute: `JMSServerMBean.PersistentStore` Changes take effect after you redeploy the module or restart the server.
Target
Name
Type
System
Standalone