JNDISwiftlet

 
 

Online Documentation    Property Configuration    JNDISwiftlet

 
 

[Swiftlet Name]     [External JNDI Server Config File]     [JNDI Object Aliasing]     [Aliases Names]     [Map To]     [Static Remote Queues]     [Thread Names for Threadpool dispatch]    
[Document Index]

 
     
 
  Swiftlet Name

The Swiftlet name of the JNDISwiftlet is sys$jndi.

External JNDI Server Config File

SwiftMQ is able to register entries of its own JNDI repository additionally to any external JNDI server. This property specifies the name of the configuration file of the external JNDI server. For detailed information, please have a look at 'JNDI Implementation Notes'.

Property definition:


 swiftlet.sys$jndi.external.jndi.configfile=<filename>

Example:


 swiftlet.sys$jndi.external.jndi.configfile=../../conf/weblogic.properties

JNDI Object Aliasing

The JNDISwiftlet stores administered JMS objects, listens to the predefined topic swiftmq.jndi for client lookup requests and replies if there is an entry for a requested object.

All administered objects are stored automatically from other Swiftlets under their full qualified name. For connection factories this is the name of the JMS inbound listener, extended with the local router name. For PTP queues this is the queue name, also extended with the local router name. Only topics are stored under their topic name without a router extension, because topics are location independent.

To make clients independent of router locations from specific connection factories and queues, and to provide the flexibility to have their locations changed by an administrator, the JNDISwiftlet supports alias mapping to registered administered objects.

Aliases Names

Optional property that specifies a list of alias names. For every defined alias name, sub-properties can be defined as described in the following sections.

Property definition:


 swiftlet.sys$jndi.aliases.names=<alias name 1>,<alias name 2>,..,<alias name n>

Example:


 swiftlet.sys$jndi.aliases.names=QueueConnectionFactory,TopicConnectionFactory

Map To

Specifies the registered name of an administered object that is referenced from an alias.

Property definition:


 swiftlet.sys$jndi.aliases.<alias name>.mapto=<registered name>

Example:


 swiftlet.sys$jndi.aliases.QueueConnectionFactory.mapto=plainsocket@router4

Static Remote Queues

Optional property that specifies a list of remote queue names. Every queue name has to be fully qualified with the remote routername as <queue>@<router>. In the case the specific remote router is disconnected, the local JNDI Swiftlet will return a Queue object on a JNDI lookup request of a client if that queue is defined in this property.

Property definition:


 swiftlet.sys$jndi.remote.queues.names=<queue 1>,<queue 2>,<queue n>

Example:


 swiftlet.sys$jndi.remote.queues.names=testqueue@router2,testqueue@router3

Thread Names for Threadpool dispatch

The JNDISwiftlet starts the following thread. The thread name can be used to dispatch it to specific thread pools. See ThreadpoolSwiftlet configuration for details.

Thread NameStarted WhenDoes What
sys$jndi:listenerOn Swiftlet startupJNDI request listener; listens for lookup requests

 
 
     
 

[Swiftlet Name]     [External JNDI Server Config File]     [JNDI Object Aliasing]     [Aliases Names]     [Map To]     [Static Remote Queues]     [Thread Names for Threadpool dispatch]    
[Document Index]

 
 

Online Documentation    Property Configuration    JNDISwiftlet

 
 

 Copyright © 2000, IIT GmbH, Bremen/Germany. All rights reserved.
SwiftMQ and Swiftlet are registered trademarks of IIT GmbH.
All other product names mentioned herein are trademarks of their respective owners.