Exception considerations

You can refer to the considerations discussed here while working on exceptions.

Every environment and solution created for a particular environment using IBM® Security Verify Directory Integrator is typically unique. User-defined rules are custom-built and the functionality is made available so solutions can automatically attempt to reconnect based on the exceptions specific to the environment or solution. Refer to the IBM® Security Verify Directory Integrator Java™ API documentation for information about specific exceptions that are returned by the IBM® Security Verify Directory Integrator APIs for each Connector.

Additionally, some IBM® Security Verify Directory Integrator components rely on underlying libraries and the APIs of these libraries throw exceptions for specific situations. Below we list a few core IBM® Security Verify Directory Integrator components where you can look for additional information on exceptions and what may be the cause of the exceptions. This information is helpful when deciding if you want to attempt to create custom reconnect rules for specific exceptions that may be encountered:

• LDAP Connector - The LDAP Connector depends on the JNDI libraries shipped with the JRE. For more information on the JNDI interface, its APIs, and the exceptions it may throw, see https://docs.oracle.com/en/java/javase/17/docs/api/java.naming/javax/naming/package-summary.html.
• JDBC Connector - The JDBC Connector depends on the configured JDBC Driver. The Java API documentation or reference material for the configured JDBC driver should be consulted for more information on the possible exceptions that may be thrown. The "Understanding JDBC Drivers" subsection in the JDBC Connector section in Reference contains links to the JDBC Driver documentation for a set of commonly used JDBC drivers.