To keep using the DB2 legacy CLI-based type2 driver after upgrading
to WebSphere Application Server version 7.0 you must set the old driver before
upgrading.
About this task
By default, virtual member manager looks for the DB2 JCC type4 instead
of the DB2 legacy CLI-based type2 in WebSphere Application Server 7.0. If
you are using the DB2 legacy CLI-based type2 driver in WAS 6.1, you need to
explicitly set the old driver name before upgrading to WebSphere Application
Server 7.0. This is necessary to keep using the old driver after the upgrade.
Procedure
Use the following command to explicitly set the old driver name
on WebSphere Application Server 6.1: - Database repositories
- wsadmin> $AdminTask updateIdMgrDBRepository {-id <dbId>
-dbURL <dbURL> -JDBCDriverClass COM.ibm.db2.jdbc.app.DB2Driver}
- Property extension repository
- wsadmin> $AdminTask setIdMgrPropertyExtensionRepository {-dbURL <dbURL>
-JDBCDriverClass COM.ibm.db2.jdbc.app.DB2Driver -databaseType <databaseType>
-dataSourceName <dataSourceName> -dbAdminId <dbAdminId> -dbAdminPassword <dbAdminPassword>}
- Entry mapping repository
- wsadmin> $AdminTask setIdMgrEntryMappingRepository {-dbURL <dbURL>
-JDBCDriverClass COM.ibm.db2.jdbc.app.DB2Driver -databaseType <databaseType>
-dataSourceName <dataSourceName> -dbAdminId <dbAdminId> -dbAdminPassword <dbAdminPassword>}
What to do next
After upgrading, switch over to the new driver using the instructions
in
Configuring a JDBC provider and datasource for virtual member manager.