a
JNDI Configuration
JNDI stands for Java Naming and Directory Interface, and is a standard API for accessing objects bound within a naming service. A naming service maps string names to objects, and is a useful way of letting code obtain resources without having to know the resource implementation or location. There are two ways to access JNDI in a J2EE setup: via the web applications Environment Naming Context (ENC) and via the global context. More information on JNDI is available at http://java.sun.com/products/jndi/tutorial/
This is perhaps the most common way to access JNDI from with a web application, which is how AltioLive is installed. To use the ENC, you need to ensure that there are no JNDI Parameters set in the Presentation Server Administration Tool. This means that JNDI is accessed without any parameters, which forces it to pick up the ENC. The information available via the ENC is controlled by the information in the web.xml file (located under WEB-INF in the web application). If the J2EE server you are using has a graphical interface, then this information can usually be set from there. The names used to access retrieve objects from the ENC are normally of the form java:comp/env/jms/myTopic.
This is useful if you are using a naming service that is not closely tied in with your J2EE server. As JNDI is an interface, you need to tell it information to allow it to find the implementation of that interface as well as how/where to connect to the target naming service. To so this you set a name-value pairs (JNDI parameters) in the Presentation Server Admin Tool. Some of the more common parameters are:
java.naming.factory.initial
java.naming.provider.url
java.naming.factory.url.pkgs
A full list of parameters can be found in the javadocs for the JNDI classes.
If your application uses JMS, the JDK (Java Development Kit) version used must be 1.3 or above. If you wish to use a JDK 1.2 the JNDIsection in altioserver.xmlmust be commented out (and thus JMS will be disabled). It is strongly recommended that AltioLive Presentation Server is run using the JDK 1.3 as this version gives improved performance. It can be downloaded from http://java.sun.com/j2se/
JNDI is only required if you will be using JMS, the Java Message Service. You must have a reasonable knowledge of Java development in order to do this.
It is optional if you are using JDBC Service Functions.
Allows customization of JNDI via zero or more name value pairs. These name value pairs map directly to the Hashtable that is used to configure the InitialContext access to the naming service (see any JNDI book for details). To use the ENC do not set any of these parameters.
Used with JMS, for publish-and-subscribe messaging. Before using any topics in JMS, you must first create a connection to a topic using a topic connection factory. This object is usually located in the JNDI namespace under the name TopicConnectionFactory. The presence of this element allows you to change the name that the topic connection factory is looked up in the naming service under.
Used with JMS, for point-to-point messaging. In JMS before using any queues, you must first create a connection to a queue using a queue connection factory. This object is normally located in the JNDI namespace under the name QueueConnectionFactory, but is not always so. The presence of this element allows you to change the name under which the queue connection factory is looked up in the naming service.