Windows stand-alone: Configure the portal to use DB2

View information on manually transferring data to the DB2 database you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to DB2. As an alternative to the manual database transfer procedure that this topic describes, we can use the configuration wizard to complete the database transfer task. However, we cannot specify all settings through the configuration wizard. For this reason, specify the required settings in the appropriate property files before transferring the database with the configuration wizard.

Before beginning:
Ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are set up.

• For JDBC Type 2 drivers, perform additional steps.

  See the Type 2 configuration section for more instructions.

Prerequisites

Windows stand-alone: Install DB2

Windows stand-alone: Modify DB2 database properties

Windows stand-alone: Create groups and assign users

Windows stand-alone: Create DB2 databases

Windows stand-alone: Set up DB2 automatically or manually

Tips:

• To run these tasks as a non-root user, first run the task...
  chown -R non-root_user WebSphereDir

• By default, open_cursors is set to 1500. You may need to increase this value based on the table count in the Java Content Repository schema.

• Be sure that DB2 is started by checking the service. If attempts to restart result in a logon failure message, then go to the DB2 properties and reenter the password.

To validate configuration properties.

cd WP_PROFILE\ConfigEngine.
ConfigEngine.bat validate-database -DWasPassword=foo

To specify the domains to validate; for example...

ConfigEngine.bat validate-database -DWasPassword=foo -DTransferDomainList=jcr

To validate all domains, do not specify this parameter.

1. From the same command prompt as the previous steps, change to the directory WP_PROFILE\bin.

2. Stop the WebSphere_Portal server:

   • stopServer.bat WebSphere_Portal -username wpadmin -password foo

3. Transfer the database:

   Important: Do not execute the database-transfer task as a background process. This might cause the task to stall.

   1. Change to the directory WP_PROFILE\ConfigEngine.

      • Set -DTransferDomainList to include only the domains to transfer.

        For example, to transfer only the JCR domain we can enter the following command: ConfigEngine.bat database-transfer -DTransferDomainList=jcr -DWasPassword=foo

      • If you have been storing data in Apache Derby for a long time, database transfer could fail with OutOfMemory exceptions. To fix:
        ConfigEngine.bat database-transfer -DDbtJavaMaxMemory=1536M -DWasPassword=foo

   2. Log output is written to: WP_PROFILE\ConfigEngine\log\ConfigTrace.log If the configuration fails, verify the values in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files and then repeat this step.

4. If dbdomain.DbRuntimeUser is set that user must have sufficient database user privileges:

   1. To manually grant database user privileges:

      1. Copy the appropriate template files to a work directory:

         • createRuntimeRoleForDifferentSchema.sql

           If the name of the database user and the schema name are not the same.

         • createRuntimeRoleForSameSchema.sql

           If the name of the database user and the schema name are the same.

         Files are in the following directories, where dbms is the database management system, and domain represents the database domains we are configuring (release, customization, community, jcr, feedback, and likeminds).

         • PORTAL_HOME\base\wp.db.impl\config\templates\setupdb\dbms\domain

         • PORTAL_HOME\pzn\prereq.pzn\config\templates\setupdb\dbms\domain

         JCR database domain: For the JCR database domain, copy grantPermissionsToRuntimeRoleStatic.sql from the following directory:

         PORTAL_HOME/jcr/wp.content.repository.install/config/templates/setupdb/dbms/jcr/grantPermissionsToRuntimeRoleStatic.sql .

      2. Replace all placeholder values with the values as defined in wkplc_dbdomain.properties. Placeholder values are surrounded by the character @.

      3. Execute the SQL statements.

   2. Grant database user privileges:

      1. Ensure the database administrator user ID is specified for domain.DBA.DbUser in WP_PROFILE/ConfigEngine/properties\wkplc_dbdomain.properties.

         For example, domain.DBA.DbUser=dbadmin.

      2. ConfigEngine.bat grant-runtime-db-user-privileges -DTransferDomainList=release,customization,community,etc...

         You only need to add -DTransferDomainList when granting privileges across specific domains.

5. Perform a reorg check to improve performance. Perform this step for each database in the property file.

   1. Connect to a database:
      db2 connect to dbName user db2wpadmin using password

      Additional options might be required if additional security has been installed. Refer to DB2 Universal Database™ commands by example .

   2. After it is connected from the DB2 prompt:

      db2 reorgchk update statistics on table all > xyz.out

   3. Look in the reorg column for entries marked with a star or asterisk * in the file xyz.out.

      1. For each line with *, note the tablename and run the following command for each tablename:

         db2 reorg table tablename

      2. After you have run the reorg command for each tablenames:

         db2 terminate

         db2rbind database_name -l db2rbind.out -u db2_admin -p password

   4. The file db2rbind.out is created when there is an error.

6. Change to the directory WP_PROFILE\bin.

7. Start the WebSphere Portal server.

If you have additional nodes already configured, compare the following file on all nodes with the file from the primary node. Ensure all instances of the file are identical: WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm\icm.properties. If the files are not identical, copy icm.properties from the primary node on which you ran the database-transfer task to the node.

1. Stop the portal server on the secondary nodes.

2. Copy WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm\icm.properties from the primary node and replace icm.properties on the secondary nodes.

3. Start the portal server on the secondary nodes.

Parent: Windows stand-alone: Set up a DB2 database
Previous: Windows stand-alone: Configure JCR collation support
Next: Windows stand-alone: Enable DB2 pureScale load balancing feature