Change driver types

WebSphere Portal requires either JDBC Type 2 or Type 4 drivers. View the steps to switch from one driver type to the other. 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_comp.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_comp.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:

  # For DB2 Type 2 driver use SQLLIB/java/db2java.zip
  # For DB2 Type 4 driver use SQLLIB/java/db2jcc.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.jdbc.app.DB2Driver
  # For DB2 Type 4 driver use com.ibm.db2.jcc.DB2Driver
  
  

Prerequisites

Installing DB2

Create users

Creating remote databases

Modifying database properties

Configure WebSphere Portal to use DB2

Configure DB2 for large file handling in Web Content Management

1. Open a command prompt and change to the directory profile_root/ConfigEngine.

2. Enter the following commands to validate configuration properties.

   ConfigEngine.bat validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
   
   

   ConfigEngine.bat validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=password
   
   

3. From the same command prompt as the previous steps, change to the directory profile_root\bin.

4. Stop both WAS and the WebSphere Portal server:

   Option	Description
   WAS	stopServer.bat server1-username admin_userid -password admin_password
   WebSphere Portal	stopServer.bat WebSphere_Portal-username admin_userid -password admin_password

5. cd profile_root/ConfigEngine.

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

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

7. Change to the directory profile_root\bin.

8. Enter the following command to start the WebSphere Portal server: startServer.bat WebSphere_Portal

Parent topic:

Set up a remote DB2 database

Previous topic:

Configure DB2 for large file handling in Web Content Management

---