JMS system modules contains configuration JMS resources, such queues,
topics, templates, and connections factories, and are defined by XML
documents that conform to the
System modules configured through the Administration Console are stored
in the config\jms subdirectory of the domain
directory, and a reference to the module is added in the domain's
configuration file as a
JMSSystemResource element. This
reference includes the path to the JMS module file and a list of target
JMS servers, servers, and clusters on which the module is deployed.
System modules are globally available for targeting to servers and clusters configured in the domain, and therefore are available to all applications deployed on the same targets and to client applications.
Note: JMS configuration resources can also be managed as deployable application modules, either with a Java EE application as a packaged module, which is available only to the enclosing application, or as a stand-alone module that provides global access to the resources defined in that module. For more information about configuring JMS application modules, see Configuring JMS Application Modules for Deployment
While creating a JMS system module, you can also add JMS resources to the module by selecting the Would you like to add resources? check box. The remaining steps explain how to create resources by using the Summary of Resources table on a JMS module's Configuration page.
For more information on using the default connection factories, see Connection Factory Configuration