Message Acknowledgement The following adapter services acknowledge messages: • Request-response service • Subscription service Message Acknowledgement by the Request-Response Service The following scenarios are applicable for message acknowledgement by the request-response service: • LDAP Server is Not Running • LDAP Server does Not Respond in Time • LDAP Server Returns an LDAP Error Code • LDAP Server Returns a Success Code with Data LDAP Server is Not Running If the LDAP server is not running, the adapter verifies that the message was received by the LDAP server and informs you that the server is unavailable. The adapter then tries to reconnect to the LDAP server. You can configure the number of retries that must be attempted and the interval between each retry in the adapter’s properties file. If the adapter is not able to reconnect to the LDAP server, it will stop attempting to reconnect after the maximum number of retries has been reached. LDAP Server does Not Respond in Time In this scenario, a connection timeout results. The adapter returns a timeout message. The adapter then tries to reestablish a connection with the server. LDAP Server Returns an LDAP Error Code If the LDAP server returns an LDAP error code because an error has occurred, the adapter returns a message that contains this code. LDAP Server Returns a Success Code with Data If the operation is completed successfully, the LDAP server returns a success code with the processed data. The adapter then sends a response message that contains the success code and the data received from the LDAP server. Message Acknowledgement by the Subscription Service The following scenarios are applicable for message acknowledgement by the subscription service: • LDAP Server is not Running • LDAP Server is Running, but the API Fails • LDAP Server is Running and the API Succeeds LDAP Server is not Running In this scenario, the adapter attempts to reconnect to the server immediately. The adapter does not confirm that the messages were received, nor does the adapter inform you that the LDAP server is not running. You can configure the number of retries that must be attempted and the interval between each retry in the adapter’s properties file. If the adapter is not able to reconnect to the LDAP server, it will stop attempting to reconnect after the maximum number of retries has been reached. LDAP Server is Running, but the API Fails In this scenario, an error message is returned by the API. This message can be viewed on the console as well as in the log file. LDAP Server is Running and the API Succeeds In this scenario, if you have configured the logging roles, the success code can be viewed in the log messages.
