JMS Space Configuration

Added by Gilad David Maayan, last edited by Aleia Hutcherson on May 15, 2008  (view change)
  Search Here
Searching XAP 6.0 Documentation

                                               
Summary: The space configuration file has several tags related to JMS, nested under <engine> / <jms>.

Overview

The space configuration file has several tags related to JMS, nested under <engine> / <jms>. These are:

  • <config-name> - The default JMS configuration name of the file containing the JMS details required when the space is running in cluster mode.
  • <connections> - The JMS Administrated Object names listed in the lookup service (defined in the container and client configuration files) for the topic and queue connection factories. Also, the container and space names that are associated with the JMS connection factories.
  • <administrated-destinations> - names of persistent topics and queues.
    You only need to set JMS parameters in the configuration file of the space that contains the JMS destinations. This space should be referenced in all bonded names (and optionally, in the space URL) in the client configuration file.

Cluster Example

...
<engine>
  <jms>
    <!--default jms configuration file, used in a cluster-->
    <config-name>DefaultConfig</config-name>
   ...
Tag Description
<config-name> The default JMS configuration file name, used in a cluster.

RMI port example

<!--The JMS Admin Connection Factories details:
        The container and space names which are associated to this JMS Connection Factory-->
        <connections>
             <!--the rmi port which is used for the spaceURL of the
              JMS connection factory. Default 10098 port is used.-->
              <rmi-port>10098</rmi-port>
        </connections>
    ...
  </jms>
</engine>
...
Tag Description
<rmi-port> Used for the space URL of the JMS connection factory. Default 10098 port is used.
These JMS destinations are considered persistent only when the space itself is persistent.

Persistent Topics and Queues

...
<engine>
  <jms>
    ...
    <administrated-destinations>
      <topics>
        <topic-names>MyTopic,TempTopic</topic-names>
      </topics>
      <queues>
        <queue-names>MyQueue,TempQueue</queue-names>
      </queues>
    </administrated-destinations>
    ...
  </jms>
</engine>
...
Tag Description
<topics> The <topic-names> tag contains a list of persistent topics, separated by commas. There may be additional (transient temporary) JMS topics, but they will not survive a system restart and must be re-created as part of the application.
<queues> The <queue-names> tag contains a list of persistent queues separated by commas. There may be additional (transient temporary) JMS queues, but they will not survive a system restart.

The Durable Service Worker

To enable durable subscriber have the following as part of the space schema file:

<workers>
                <worker-names>DurableServiceWorker,QueryProcessorWorker,MulticastNotifyWorker</worker-names>
                <!--interrupt the worker on shutdown-->
                <interrupt>false</interrupt>
                <DurableServiceWorker>
                     <enabled>false</enabled>
                     <class-name>com.j_spaces.jms.DurableServiceWorkerImpl</class-name>
                     <arg>
                     </arg>
                     <description>Provides JMS Durable Subscriber capabilities for jms clients</description>
                </DurableServiceWorker>
     </workers>

The QueryProcessorWorker is deprecated in GigaSpaces version 6.0.1 and onwards. If you are using this version, do not include it in the worker-names element above.


GigaSpaces 6.0 Documentation Contents (Current Page in Bold)

    Java

    C++

    .NET

    Middleware Capabilities

    Configuration and Management

Add GigaSpaces wiki search to your browser search engines!
(works on Firefox 2 and Internet Explorer 7)

Labels

 
(None)