Configuring the LDAP Binding Component for Clustering

The LDAP BC is stateless, which means it scales in a clustered environment because the instances do not need to coordinate state and each maintains its own connections. In a failover system, the original caller or last persistence point re-delivers the message if configured for at least once delivery (the default) or once and only once delivery (XA transactions). When the message is re-delivered to the LDAP BC, it performs the same operation again.

In case of failure, messages are processed as follows:

• For operations in which multiple processes do not affect the result (such as read or search operations), the request processing continues as before the failure.

• For operations that modify, delete, and add, it is not guaranteed that each of these operations is only executed once per message because LDAP does not support transactional behavior on its own. It behaves in the same manner in a non-clustered environment.

The LDAP BC is not dependent on any shared libraries.

To Add the LDAP Binding Component to the Cluster

1. Add the LDAP BC to the cluster as described in To Add a Java CAPS JBI Component to a Cluster.

   The name of the LDAP BC node is sun-ldap-binding.

2. Before you click OK on the Manage Targets page, modify the values of the runtime properties as you typically would for the LDAP BC.