JMS Container 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 container configuration file has several tags related to JMS, nested under <directory_services> / <jms_services>.

Overview

The container configuration file has several tags related to JMS, nested under <directory_services> / <jms_services>. These are shown and described below.
You only need to set JMS parameters for the configuration file of the container that holds the space which contains the JMS destinations. This container should be referenced in all bonded names (and optionally, in the space URL) in the client configuration file.
To specify the External JNDI properties that the JMS Administrated Objects use to create a JNDI InitialContext, create a file called jndi.properties that contains your JNDI provider's configuration properties and add the directory that contains the file to your classpath.
For example, if you are using WebLogic 8.1 as your JNDI provider, your jndi.properties file would contain:

java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.provider.url=t3://localhost:7001
java.naming.security.principal=system
java.naming.security.credentials=weblogic
A default jndi.properties file already exists, with default values, in the <GigaSpaces ROOT>/config/jms folder.


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)