Using a Different Kerberos Ticket Cache File with each JDBC Connection Pool
You can configure each JDBC pool to use a different Kerberos ticket cache by using the DataDirect connection parameter "loginConfigName".
To use a different Kerberos ticket cache file with each JDBC connection pool on
Integration Server1. Create a new login context in the is_jaas.cnf file located in the folder: Integration Server_directory /instances/instanceName/config.
2. Within the new login context, specify the ticket cache that you want to use for the login context.
For example:
JDBC_ISInternal {
com.sun.security.auth.module.Krb5LoginModule required
useTicketCache="true"
ticketCache="/opt/krb_tickets/isinternal.kd";
};
3. Add the login context to the database URL for the JDBC connection pool by including the parameter loginConfigName=<loginContext>.
For example, it the login context in the is_jaas.cnf file is named JDBC_ISInternal, add the following the database URL for the JDBC connection pool: loginConfigName=JDBC_ISInternal
The DataDirect driver will use the ticket cache and other details found in the JDBC_ISInternal JAAS login context to connect to the database.