Having multiple LDAP entries with the same service name in unique branches of the LDAP directory provides you with the most flexibility in setting the properties for the components. Using this method assumes that you have set up unique branches in your LDAP server under which the entries can reside (as defined in the distinguished name for each service). The Info*Engine Property Administration utility does not create branches; they must exist before you open Property Administration to add the LDAP entries. Required branches can be created through the Create Repository option in the Task Delegate Administration utility.

This method can work well when you have a complex branching system set up in your LDAP directory and when you have multiple Info*Engine environments. You can restrict access to certain components to certain environments, but allow for load balancing in other environments.

For example, assume that there are three data repositories with unique properties for each repository and that the same JDBC adapter is installed three times, one for each repository. To set up load balancing across all three adapters, you could set the following attributes on the adapter LDAP entries:

Also, assume that each entry has a unique DBUSER attribute that identifies the username for accessing the database. Therefore, in each LDAP entry the service name value is the same (com.myCompany.JDBC) and the host, port, database user, and distinguished name subtree values are unique. In this example, the entries each have unique ptcRuntimeServiceName attributes so that each component has its unique set of properties.

When the Naming Service receives requests for an instance of “com.myCompany.JDBC” and the Naming Service search base is set at the LDAP entry of “dc=myCompany,dc=com,” the Naming Service balances the load across all three JDBC adapters. To do load balancing, Info*Engine randomly selects which of the three adapters receives each query and each adapter connects to a different database.