JNDI Configuration

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 5 General Activities Palette : JNDI Configuration

JNDI Configuration

Shared Configuration

The JNDI Configuration shared configuration resource provides a way to specify JNDI connection information that can be shared by other resources. This resource can be specified in any resource that permits JNDI connections. For example, JDBC Connection and JMS Connection can use JNDI connections.

Configuration

The Configuration tab has the following fields.

Field

Global Var?

Description

Name

No

The name to appear as the label for the resource.

Description

No

Short description of the shared resource.

JNDI Context Factory

No

The initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_
FACTORY). You can choose from the drop down list of supported classes.

See IBM WebSphere and JNDI Context Caching for more information when using IBM WebSphere.

Note: TIBCO ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the JAR file supplied by your JNDI service provider to the CLASSPATH environment variable to use JNDI.

JNDI Context URL

Yes

The URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected.

See your JNDI provider documentation for the syntax of the URL.

JNDI User Name

Yes

User name for logging into the JNDI server (javax.naming.Context.SECURITY_
PRINCIPAL). If the JNDI provider does not require access control, this field can be empty.

JNDI Password

Yes

Password for logging into the JNDI server (javax.naming.Context.SECURITY_
CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.

Test Configuration Button

The Test Configuration button allows you to test that the specified configuration fields result in a valid connection to a JNDI server.

Advanced

The Advanced tab has the following fields.

Field

Global Var?

Description

Validate JNDI Security Context

No

Some application servers store the security context on the thread used to establish the JNDI connection (at the time of this release, only the WebLogic application server does this). In that case, the first activity to use this resource establishes the security context, then subsequent activities use the same security context, unless this field is checked. Checking this field ensures that each activity that uses this resource examines the security context to determine if the activity uses the same security context as the security context established on the thread. If they are different, the activity’s configured security context is used.

Checking this field causes additional overhead for activities that use this resource. Therefore, only check this field when necessary.

Optional JNDI Properties

No

The table in this field contains optional properties to pass to the JNDI server. Use the +, X, and arrow keys to add, delete, and move properties in the list. Each property requires the property name, the datatype for the property, and the value for the property. See the documentation for your JNDI provider for more information about properties that can be passed to the JNDI server.

IBM WebSphere and JNDI Context Caching

The IBM WebSphere application server provides a mechanism for caching the JNDI context object to improve the performance of JNDI lookup operations. TIBCO ActiveMatrix BusinessWorks also caches the JNDI context object when resources such as EJB activities, JMS activities, JDBC activities, or JTA UserTransactions use JNDI. BusinessWorks performs best when using its own caching mechanism. Therefore, you must disable the IBM WebSphere caching mechanism when using IBM WebSphere with BusinessWorks. See the IBM WebSphere documentation for a complete description of its caching features.

You can disable the IBM WebSphere JNDI context caching feature by performing the following procedure:

1.

Configure a JNDI Configuration resource.

2.

On the Advanced tab, click the + button next to the table in the Optional JNDI Properties field to add a property.

3.

In the Name field of the property, enter com.ibm.websphere.naming.jndicache.cacheobject.

4.

Leave the Type field as the default value of string.

5.

In the Value field, enter none.

6.

Click Apply to accept the changes.

7.

Use the JNDI Configuration resource in an EJB Connection, JMS Connection, or JTA UserTransaction shared configuration resource.

Field	Global Var?	Description
Name	No	The name to appear as the label for the resource.
Description	No	Short description of the shared resource.
JNDI Context Factory	No	The initial context factory class for accessing JNDI. (javax.naming.Context.INITIAL_CONTEXT_ FACTORY). You can choose from the drop down list of supported classes. See IBM WebSphere and JNDI Context Caching for more information when using IBM WebSphere. Note: TIBCO ActiveMatrix BusinessWorks attempts to find the class. However, you may need to add the JAR file supplied by your JNDI service provider to the CLASSPATH environment variable to use JNDI.
JNDI Context URL	Yes	The URL to the JNDI service provider (javax.naming.Context.PROVIDER_URL). An example URL is provided when one of the supported JNDI context factory classes is selected. See your JNDI provider documentation for the syntax of the URL.
JNDI User Name	Yes	User name for logging into the JNDI server (javax.naming.Context.SECURITY_ PRINCIPAL). If the JNDI provider does not require access control, this field can be empty.
JNDI Password	Yes	Password for logging into the JNDI server (javax.naming.Context.SECURITY_ CREDENTIALS). If the JNDI provider does not require access control, this field can be empty.