This page describes an older version of the product. The latest stable version is 15.2.

XAP JNDI

XAP runs a JNDI service where JMS objects can be bound by name. The administrator configures JMS destinations in the space configuration file. When the space is started, it creates and binds the configured destinations to JNDI, making them available for use.

The application uses a JNDI context to obtain these objects, and to start working with JMS. The context is initialized with the values specified in the jndi.properties file in the GigaSpaces classpath. After obtaining the context, the client calls the context.lookup() method, passing the name of the required resource. If the resource is found in JNDI, it is returned to the client.

Obtaining ConnectionFactory Instances from JNDI

It is not possible to configure connection factories.

When JMS services in JNDI are enabled, the space creates and binds the following connection factories: