Java Naming and Directory Interface
This feature enables the use of Java Naming and Directory Interface (JNDI) to access server configured resources such as DataSources or JMS Connection Factories. It also allows access to Java primitives configured in the server as a jndiEntry.
Enabling this feature
To enable the Java Naming and Directory Interface feature, add the following element declaration inside the featureManager element in your
server.xml file:
<feature>jndi-1.0</feature>
Supported Java™ Versions
- JavaSE-1.6
- JavaSE-1.7
- JavaSE-1.8
Developing a feature that depends on this feature
If you are developing a feature that depends on the Java Naming and Directory Interface feature, include the following item in the Subsystem-Content header in the feature manifest file for your new feature:
com.ibm.websphere.appserver.jndi-1.0; type="osgi.subsystem.feature"
Features that enable this feature
- appClientSupport-1.0 - Application Client Support for Server
- batch-1.0 - Batch API 1.0
- distributedMap-1.0 - Distributed Map interface for Dynamic Caching
- ejbLite-3.1 - Enterprise JavaBeans Lite 3.1
- ejbLite-3.2 - Enterprise JavaBeans Lite 3.2
- ejbPersistentTimer-3.2 - Enterprise JavaBeans Persistent Timers 3.2
- javaeeClient-7.0 - Java EE V7 Application Client
- jdbc-4.0 - Java Database Connectivity 4.0
- jmsMdb-3.1 - JMS Message-Driven Beans 3.1
- jpa-2.0 - Java Persistence API 2.0
- jpa-2.1 - Java Persistence API 2.1
- managedBeans-1.0 - Java EE Managed Bean 1.0
- mdb-3.1 - Message-Driven Beans 3.1
- mdb-3.2 - Message-Driven Beans 3.2
- osgi.jpa-1.0 - OSGi Java Persistence API
- sessionDatabase-1.0 - Database Session Persistence
- webProfile-6.0 - Java EE Web Profile 6.0
- webProfile-7.0 - Java EE Web Profile 7.0
Feature configuration elements
You can use the following elements in your server.xml file to configure the Java Naming and Directory Interface feature: