DB Connector supports container-managed sign-on and component-managed sign-on.
The features of each method are as follows:
- In container-managed sign-on
- When you use a container-managed sign-on, the user name and password set for DB Connector is used to access the database.
- In component-managed sign-on
- When you use a component-managed sign-on, the user name and password passed to the getConnection method of the connection factory is used to access the database.
- Note that when you use DBConnector_DABJ_XA.rar (when you use a global transaction), only the user name and password specified in the XAOpen string is enabled. Therefore, you cannot perform a component-managed sign-on where you specify the user name and password with the getConnection method.
If you use the sign-on optimization functionality when you perform a container-managed sign-on, the container-managed sign-on operations are optimized and the performance of obtaining a database connection improves.
You specify the settings for optimizing the container-managed sign-on for DB Connector by customizing the J2EE server properties. For details on customizing the settings for the J2EE server operations, see 3.14.10 Settings in the execution environment.
- Note
- Use the container-managed sign-on optimization when you do not want to perform a component-managed sign-on. If you perform the container-managed sign-on optimization, the component-managed sign-on cannot be used.
- When you use the connection pool clustering functionality, you cannot mix container-managed sign-on and component-managed sign-on in one clustered connection pool.