Overview

The GigaSpaces JMS interface is configured in the following files:

• Default JMS configuration name – This file includes the default JMS configuration for clustered spaces, ensuring that clustered spaces have one common JMS configuration and allowing for them to be set up easily in clustered JMS environments.
• Client configuration file – an XML file that stores client-specific JMS settings. By default, this file is called jms-config.xml, and is located on the machine that runs the JMS application (which uses the JMS API). The Default JMS configuration, cluster, container and space configuration files contain settings for the GigaSpaces server-side which stores the actual JMS messages in the following directory: <GigaSpaces ROOT>/config/jms.
• Container configuration file - the container XML file that holds the space that contains the JMS destinations.
• Space configuration file – the space XML file that holds the JMS destinations and the message data as JavaSpaces Entries.
• Cluster configuration file-- if a space is defined as clustered, its JMS configuration is taken from the cluster configuration file to ensure that all cluster spaces use the same JMS configuration.

The client configuration file contains settings for the JMS application (which uses the JMS API). The Default JMS configuration, cluster, container and space configuration files contain settings for the GigaSpaces server-side which store the actual JMS messages.

For more details on the JMS configuration process, refer to the JMS Configuration Process section.