Solaris 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:

If WebSphere Portal is installed on the same machine as the DB2 server and you switch from a JDBC Type 4 connection to a JDBC Type 2 connection, verify that you have created the alias names for the DB2 databases as described in Create remote databases and that the alias names are specified for the databases in the file wkplc_dbdomain.properties.

When switching from a JDBC Type 2 connection to a JDBC Type 4 connection, remove the database alias names and refer to the databases directly. This is required because of a limitation in the DB2 Universal JDBC driver.


Prerequisites


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

  1. Open a command prompt and

      cd WP_PROFILE/ConfigEngine

  2. Use a JDBC Type 2 driver only, export the DB2 user profile that you created when installing DB2 onto the administrative user using the following command. This command exports the DB2 user's profile onto the administrative user so that they can access the DB2 utilities.

      . /home/db2inst1/sqllib/db2profile

      where db2inst1 represents database instance You must complete this step before running database tasks and before enabling security.

  3. Enter the ./ConfigEngine.sh validate-database -DWasPassword=foo command to validate configuration properties.

      Add -DTransferDomainList to specify the domains to validate; for example: -DTransferDomainList=jcr.

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

  5. Stop both the server1 and WebSphere_Portal servers:

    • ./stopServer.sh server1 -username admin_userid -password foo

    • ./stopServer.sh WebSphere_Portal -username admin_userid -password foo

  6. Change to the directory WP_PROFILE/ConfigEngine.

  7. 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.sh connect-database -Drelease.DbPassword=foo
      
      
      

      -Dcustomization.DbPassword=foo -Dcommunity.DbPassword=foo

      -Djcr.DbPassword=foo -Dfeedback.DbPassword=foo

      -Dlikeminds.DbPassword=foo

      -DWasPassword=foo

  8. Change to the directory WP_PROFILE/bin.

  9. Start the WebSphere Portal server.

      See Start and stopping servers, dmgrs, and node agents for instructions.


Parent

Solaris clustered server: Set up a remote DB2 database


Previous

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

 


+

Search Tips   |   Advanced Search