To Configure Client Affinity for Client—Based Routing

If an application makes an update using one connection from the pool but then uses a different connection to do the search for that entry, the affinity setting on the connection used to do the update is not used because the search is done from a different connection. The search operation could also be routed to a different server than where the update was performed. In this case, the affinity feature works only within the same client connection.

To resolve this, affinity should be defined at the client level such as an IP address or bind DN. When an update is made by a client, all the connections from that client follow the same affinity rule.

1. Specify the criteria to determine if the requests are coming from the same client.

   dpconf set-ldap-data-source-pool-prop -h host -p port pool-name \ client-affinity-criteria:ip-address-and-bind-dn

   For all the options, see client-affinity-criteria(5dpconf).

   The server matches the bind DN as well as the IP address of the client requests, if the entries meet the criteria then they are from the same client.

2. Specify the regular expressions that the bind DN of the connection must match to consider that requests come from the same client.

   dpconf set-ldap-data-source-pool-prop -h host -p port pool-name \ client-affinity-bind-dn-filters:"uid=boss*"

3. Specify the IPv4 or IPv6 address that the IP address of the connection must match to consider that requests come from the same client.

   dpconf set-ldap-data-source-pool-prop -h host -p port pool-name \ client-affinity-ip-address-filters:129.157.192.108