Configure WebSphere Portal to use DB2

View the steps to manually transfer 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 described here, you can use the configuration wizard to complete the database transfer task.

Before you begin:

Ensure that the following prerequisites are met:


Prerequisites

Installing DB2

Create users

Creating remote databases

Modifying database properties
Tips:

Steps for transferring data to another supported database

  1. If you are running a type 2 connection, before transferring data edit the db2cli.ini file. Failure to follow these steps will cause the database transfer to hang at the task action-process-constraints.

    1. Locate the file /home/db2inst1/sqllib/cfg/db2cli.ini.

    2. Add the following to the end of the file. Leave an empty line after ReturnAliases=0.

      [COMMON] DYNAMIC=1 ReturnAliases=0
      
      

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

  3. Using a JDBC Type 2 driver only, export the DB2 user profile that created when installing DB2 onto the administrative user using the following command. This command gives that administrative user rights over DB2.

    . /home/db2inst1/sqllib/db2profile
    
    where db2inst1 represents your database instance

    You must complete this step before running database tasks and before enabling security to create a suitable JDBC driver.

  4. Enter the following commands to validate configuration properties.

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

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

  5. From the same command prompt as the previous steps, change to the directory profile_root/bin.

  6. Stop both WAS and the WebSphere Portal server:

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

  7. Transfer the database:

    1. cd profile_root/ConfigEngine.

    2. Enter the following command:

      ./ConfigEngine.sh database-transfer -DTransferDomainList=release,customization,community,jcr, feedback,likeminds -DWasPassword=password 
      

      If you have been storing data in IBM Derby for a long time, database transfer could fail with OutOfMemory exceptions. If database transfer fails, add the following property to the command in this step: ./ConfigEngine.sh database-transfer -DDbtJavaMaxMemory=1536M -DWasPassword=password

    3. After running this task, a message is added to the log files to verify that this task was successful. Check the log files. If the configuration fails, verify the values in the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files and then repeat this step.

  8. After transferring the database tables, perform a reorg check to improve performance. Perform this step for each database alias in the property file.

    1. Connect to a database with the following command:

      db2 connect to database_alias user
      db2admin_userid
       using password
      

      Additional options might be required if additional security has been installed. Refer to DB2 Universal Database commands by example for links to the command reference.

    2. After it is connected, run the following commands 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. For each line with a *, note the tablename and run the following command for each tablename:

      db2 reorg table tablename
      db2 terminate
      db2rbind database_name -l
      db2rbind.out -u
      db2_admin
       -p password
      

    4. The output file db2rbind.out is only created when there is an error for the db2rbind command.

  9. Change to the directory profile_root/bin.

  10. Enter the following command to start the WebSphere Portal server: ./startServer.sh WebSphere_Portal

If you have performed database transfer in a clustered environment, explicitly copy the profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties file from the primary node on which the database-transfer task was processed to all secondary nodes. This ensures that the secondary nodes have the new JCR database values specified in the icm.properties file.

  1. Stop the portal server on the secondary node.

  2. Copy the profile_root/PortalServer/jcr/lib/com/ibm/icm/icm.properties file from the primary node and replace the icm.properties file on the secondary node with the new file from the primary node.

  3. Start the portal server on the secondary node.


Parent topic:

Configure WebSphere Portal to use DB2


Previous topic:

Configure JCR collation support


Next topic:

Configure DB2 for large file handling in Web Content Management