Overview

This file is the default JMS configuration for the GigaSpaces JMS in a cluster context only. It is generated automatically whenever:

• A cluster is built, used as a default config for each and every space node in the cluster.
• No other config file was created.
  This file resides in the cluster config xml file (under <jms> tag), the same place as the DCache config file.
  For more details about tags mentioned in the procedures below, see the respective sections.
  To configure the client side of the GigaSpaces JMS interface:

1. Open the client configuration file (either the default file, for example, config/jms/jms-config.xml, or a copy).
2. If you are using an external JNDI registry, update the jndi.properties file and add the directory that contains the file to your classpath.
3. Define the container name associated with this JMS connection factory in <container-prefix>.
4. Define the space name associated with this JMS connection factory in <space-prefix>.
5. If you want to override the default space URL, (the space URL of the space associated with this JMS ConnectionFactory), enter the new space URL in <overwrite-space-url>.
6. If you want to turn on the debug mode, set <jms-debug> to true.

   If you've activated the debug mode, to view the output, go to <GigaSpaces Root Directory>\logs.

7. Copy the client configuration file to all the computers running JMS client applications. Alternatively, you can include the JMS configuration file in your installer.
8. Ensure that the client applications pass the correct path of the client configuration file when calling the GSJMSAdmin.getInstance() method.
   To configure the server side of the GigaSpaces JMS interface:
9. Open the container configuration file of the container holding the space that contains the JMS destinations.
10. Check that the JMS <enabled> tag is set to true.
11. You may choose to bind the JMS objects on either of two JNDI registries, an internal rmi registry, or an external JNDI registry. To do so:
12. Set <internal-jndi-enabled> to true if you want to use the GigaSpaces Server's lookup service for the JMS destinations and connection factories lookup.
13. Set <ext-jndi-enabled> to true if you want to use an external lookup service, such as any of the ApplicationServers JNDI registry implementations.
14. If you enabled an external JNDI registry, update your JNDI provider's configuration properties inside the jndi.properties file and add the directory that contains the file to your classpath.
15. Open the space configuration file of the space that contains the JMS destinations.
16. Define the comma separated list of topic names in the <topics> tag, under <administered-destinations>.
17. Define the comma separated list of queue names in the <queues> tag, under <administered-destinations>.
18. Save the container and space configuration files, and restart the space container.

    Even if topics and queues are persistent, their data is not necessarily saved to a database for surviving a system shutdown. Persistent topics and queues are defined as part of the configuration file, and the application does not need to define these when it starts. To define topic and queue messages as persistent for saving into a database , define the relevant space and store them as a persistent space. See Persistent topics and queues.