Create a JNDI Adapter Entry

Adapter properties are maintained as attributes in Info*Engine adapter LDAP entries. Use the Info*Engine Property Administration utility to add or modify Info*Engine adapter LDAP entries. You can access the property administration utility by navigating to Site

> Utilities and clicking Info*Engine Administration.

To create a new adapter service LDAP entry, select JNDI Adapter from the Create Entry drop-down menu on the Info*Engine Property Administration main page. Enter values into the form; required fields on the form are indicated with an asterisk (*).

For information about using the Info*Engine Property Administration utility, see Property Administration Main Page.

The property administration utility automatically populates the Service Name, Distinguished Name, and Runtime Service Name fields with suggested names. These names are based on information provided when you logged on to the administration utility and also information that is stored in the form:

◦ Service Name—Ensure that this name is unique. If you are providing a new name, give special consideration when using the period character (“.”) as described below.

◦ Distinguished Name—Use the name suggested by the property administration utility. If you enter a new service name, the distinguished name field is updated in response.

◦ Runtime Service Name—This name must be identical to the service name.

You can opt to change these names to match the criteria set up for your site LDAP entries. However, note that the period character (“.”) has unique significance when naming a new JNDI adapter. Including a period character (“.”) influences the format of the name that must be used for the corresponding repository definition.

Many repository names and repository types specify a hierarchical structure, requiring a value formatted as an Internet domain. Therefore Info*Engine adapters are commonly given names that reflect their relationship to the network in which they are deployed. For example:

Because this service name includes the period character (“.”), you would need to reverse parts of the name when creating and naming a new repository definition. Therefore, if you choose to name your JNDI adapter com.company.host.Ldap, the corresponding Info*Engine repository must be named:

To avoid this, you can provide an adapter name that does not include the period (“.”) character. For example, if you name your JNDI adapter EnterpriseDirectory1, then you would also name the corresponding repository definition EnterpriseDirectory1. For instructions on creating a new repository definition, see Create a Repository Definition.

Such naming convention requirements are only necessary when connecting Windchill to an LDAP directory service that maintains user and group information. However, no such requirements are necessary for other Info*Engine integration configurations.

The Service Class property identifies the Java class for the adapter. Use the default provided by the property administration utility.

Specify the URL used to access your enterprise directory server.

Specify the distinguished name of the LDAP node under which all user information is located. All user searches will use this as the base.

These can be used to define the distinguished name and password of the Windchill user who access the enterprise directory. However, PTC recommends that these fields should be left blank and you use the MapCredentials file instead. For more information, see Set Authentication in the MapCredentials.xml File.

Unless you have a specific reason, all other fields should be left blank.

You can find more information on the remaining adapter properties using the following options:

• Hover your cursor over the property name to view a short description of the property.