A custom user registry can use a DB2 database to maintain the user and password information.
You cannot use the legacy DB2 for z/OS JDBC Driver or a type 2 DB2 Universal JDBC Driver because both of these drivers use Resource Recovery Services (RRS). If you use these drivers, the custom user registry DB2 server requests interfere with the user application processing under the same thread.
For example, do not define a DB2 for z/OS JDBC Provider (RRS) because the legacy DB2 for z/OS JDBC Driver cannot coexist with the DB2 Universal JDBC Driver.
The data source or connection must not rely on any WebSphere Application Server resource management. For example, the data source or connection cannot rely on Java Naming and Directory Interface (JNDI) lookup, pooling, datastore helpers, XA resource or transaction processing, connection management, and so on.
Complete the following steps to define the JDBC driver for WebSphere Application Server. You must set up the following DB2 JDBC Universal Driver configuration before you define your custom user registry for the WebSphere Application Server for z/OS security component.
In this information ... | IBM Redbooks, demos, education, and more(Index) |