Is there a way to configure LDAP to use the Alternate database so the Primary is not used and not have any performance impacts? .
Knowing that the app will be pulling the entire Db at a time and doing rule to user lookups, what are the performance considerations?
Are there any tweaks we can do to reduce those impacts?
Release : 16.0
Component : CA ACF2 for z/OS
No, You cannot do access to backup databases with CA LDAP Server.
The ldap server will act like any other user issuing validations - against the live databases
The important part is to make sure that the slapd.env file with is updated with
correct cell pool values so that the server runs efficiently.
Here is a link to the documentation to discussed this process
Note that for a list like(-) type process CA ACF2 does not allow a user to hold up the request queue - it will be allowed to do a few requests,
let others in the queue to run their quick requests and then be allowed back in to run some more of the list request.
In this way performance should not be impacted.