Advanced Customization > Info*Engine Implementation > Configuring for Load Balancing and Failures > System-Wide Load Balancing and Failure Processing > Using One LDAP Entry for Multiple Components
  
Using One LDAP Entry for Multiple Components
Creating one LDAP entry with multiple host and port attributes for redundant components is a quick way to provide for loading balancing and failures. This method requires that all component properties are the same for the components and that the components are accessed through a TCP host and port connection.
This method works well in the following situations:
• You have redundant out-of-process adapters that connect to the same data repository.
• You have multiple task processors, each with the same properties except for its host and port.
For example, assume that you have set up three JDBC adapters on three different hosts that are all configured identically to access the same database. If this is true, the properties for the adapters can be the same, except for the host and port used to access the adapters. To set up load balancing across all three adapters, you could set the following attributes on one adapter LDAP entry:
Service Name
Host
Port
com.myCompany.JDBC
oradb1.co.com
10003
oradb2.co.com
10004
oradb3.co.com
10005
* 
If you have a Windchill environment that has multiple method servers, do not attempt to use one LDAP entry for multiple Windchill adapters. Windchill adapter auto-registration automatically creates and removes service definitions as necessary. Separate adapter definitions are necessary to maintain proper session affinity during distributed transaction processing.