> # Domain Partition: Resource Groups: Services: JMS Modules and Servers

> Column Display Related Tasks Related Topics

> The following JMS modules have been explicitly targeted to this domain partition resource group. JMS resources are configured and stored as modules similar to standard Java EE modules. Such resources include queues, topics, connection factories, templates, destination keys, quota, distributed queues, distributed topics, foreign servers, and JMS store-and-forward (SAF) destinations.

> NOTE: WebLogic Server Multitenant domain partitions, resource groups, resource group templates, and virtual targets are deprecated in WebLogic Server 12.2.1.4.0. The related Console and help pages will be removed in the next release.

> #### 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 module.
> Type | The type of JMS module. JMS system modules are configured through the Administration Console, JMX, or WLST, and are stored in the `config\jms` subdirectory of the domain directory, with a reference to the module added to the domain's configuration file. JMS system modules are globally available for targeting to servers and clusters configured in the domain. A stand-alone JMS application module is deployed as a stand-alone resource using the Administration Console or the `weblogic.Deployer` utility, and is typically available to the server or cluster targeted during the deployment process.
> Scope | The scope in which the JMS module is created.
> Domain Partitions | The partitions where this JMS module is accessible.

> #### 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. If the JMS server has a store configured, then the configured store is used to store persistent messages.

> The disk-based file store or JDBC-accessible database store that you specify must be targeted to the same server, cluster, or migratable target 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 the PersistentStore field nor the Store field are set, the JMS server supports persistent messaging using the default persistent store for the targeted WebLogic Server instance.

> If the value is changed and activated, you need to restart any servers to which the MBean is targeted before the value will take effect (even though you do not get a warning in the Console that the server needs to be restarted).

> MBean Attribute:
> `JMSServerMBean.PersistentStore`

> Changes take effect after you redeploy the module or restart the server.

> Target | The server instances, clusters, or a migratable targets defined in the current domain that are candidates for hosting the JMSSerer. In a clustered environment, a recommended best practice is to use a cluster as a target or target a JMSServer to the same migratable target as the Persistent Store that it uses, so that a member server will not be a single point of failure. A JMSServer can also be configured to automatically migrate from an unhealthy server instance to a healthy server instance with the help of the automatic service migration feature.

> MBean Attribute:
> `JMSServerMBean.Targets`

> Scope | The scope in which the JMS module is created.
> Domain Partitions | The partitions where this JMS module is accessible.

> Related Tasks

> - Create JMS servers
> - Configure JMS servers
> - Create JMS system modules
> - Configure JMS system modules

> Related Topics

> - Configuring Messaging
> - Understanding JMS Resource Configuration
> - Understanding WebLogic JMS