Skip navigation.
Downloads | Product Documentation | Support

Administration Console Online Help

# JMS Servers

Column Display Related Tasks Related Topics

JMS servers act as management containers for the queues and topics in JMS modules that are targeted to them.

This page summarizes the JMS servers that have been created in the current WebLogic Server domain.

#### 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 | The list of all WebLogic Server instances that have been defined in the current domain and are therefore candidates for hosting this JMS server. MBean Attribute: `JMSServerMBean.Targets`

Related Tasks

- Configure JMS servers
- Configure JMS system modules

Related Topics

- Configuring and Managing WebLogic JMS