Windows clustered server: Change DB2 driver types

WebSphere Portal requires the use of either the IBM DB2Legacy JDBC driver in type 2 mode or the IBM DB2 Universal JDBC driver in type 4 mode when connecting to DB2.

Before you begin, ensure that the following conditions are met:

• The WebSphere Portal database has been successfully transferred to DB2 using the database-transfer configuration task.

• The files wkplc_dbdomain.properties and wkplc_dbtype.properties have been modified to set the correct values for the DB2 drivers that you are switching to:
  In the file wkplc_dbdomain.properties set each <Domain>.DbUrl property using the following formats:

  # db2 (type 2):        { jdbc:db2:wpsdb }
  # db2 (type 4):        { jdbc:db2://<YourDatabaseServer>:50000/wpsdb:returnAlias=0; }

  In the file wkplc_dbtype.properties set the db2.DbLibrary property using the following format: If you are using DB2 Version 9.1 use the db2jcc.jar file. You will need to replace references to db2jcc4.jar with db2jcc.jar in this topic. If you are not using this specific version of DB2, use the db2jcc4.jar file.

  # For DB2 Type 2 driver use <SQLLIB>/java/db2jcc4.jar
  # For DB2 Type 4 driver use <SQLLIB>/java/db2jcc4.jar;<SQLLIB>/java/db2jcc_license_cu.jar

  In the file wkplc_dbtype.properties set the db2.DbDriver property using the following format:

  # For DB2 Type 2 driver use com.ibm.db2.jcc.DB2Driver
  # For DB2 Type 4 driver use com.ibm.db2.jcc.DB2Driver

Prerequisites

Windows clustered server: Install DB2
Windows clustered server: Modify DB2 database properties
Windows clustered server: Create groups and assigning users
Windows clustered server: Create DB2 databases
Windows clustered server: Set up DB2 automatically or manually
Windows clustered server: Configure WebSphere Portal to use DB2
Windows clustered server: Configure DB2 for large file handling in WCM

1. Open a command prompt and
   cd WP_PROFILE/ConfigEngine

2. Enter the ConfigEngine.bat validate-database -DWasPassword=foo command to validate configuration properties.
   Add -DTransferDomainList to specify the domains to validate; for example: -DTransferDomainList=jcr.

3. From the same command prompt as the previous steps, cd WP_PROFILE/bin.

4. Stop both the server1 and WebSphere_Portal servers:

   • stopServer.bat server1 -username admin_userid -password foo

   • stopServer.bat WebSphere_Portal -username admin_userid -password foo

5. Change to the directory WP_PROFILE/ConfigEngine.

6. To change from one supported driver to the other, run the following task to connect the database, including only the domains that require the switch.

   ConfigEngine.bat connect-database -Drelease.DbPassword=foo
   
   
    -Dcustomization.DbPassword=foo -Dcommunity.DbPassword=foo
   
   
    -Djcr.DbPassword=foo -Dfeedback.DbPassword=foo
   
   
    -Dlikeminds.DbPassword=foo
   
   
   -DWasPassword=foo

7. Change to the directory WP_PROFILE/bin.

8. Start the WebSphere Portal server.
   See Start and stopping servers, dmgrs, and node agents for instructions.

Parent

Windows clustered server: Set up a remote DB2 database

Previous

Windows clustered server: Configure DB2 for large file handling in WCM

 

+

Search Tips   |   Advanced Search