Configure WebSphere Portal to use DB2



Search Tips   |   Advanced Search


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

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


  1. Installing DB2
  2. Create users
  3. Creating remote databases
  4. Modifying database properties

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

If you are transferring from Oracle, the open_cursors setting should be set to 1500 by default.

For Java Content Repository, this value might need to be increased 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.

Steps for transferring data to another supported database

  1. If you are running a type 2 connection, before transferring data edit

      C:/Program Files/IBM/SQLLIB/db2cli.ini

    ...and add the following to the end of the file. Leave an empty line after ReturnAliases=0...

        [COMMON] DYNAMIC=1 ReturnAliases=0

  2. Validate configuration properties.

      cd profile_root/ConfigEngine
      ./ConfigEngine.bat validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=wpsadmin
      ./ConfigEngine.bat validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=wpsadmin

  3. Stop both WAS and the WebSphere Portal server:

      cd profile_root/bin
      ./stopServer.bat server1 -username wpsadmin -password wpsadmin
      ./stopServer.bat WebSphere_Portal -username wpsadmin -password wpsadmin

  4. Transfer the database:

      cd profile_root/ConfigEngine
      ./ConfigEngine.bat database-transfer -DTransferDomainList=release,customization,community,jcr,feedback,likeminds -DWasPassword=wpsadmin

    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.bat database-transfer -DDbtJavaMaxMemory=1536M -DWasPassword=wpsadmin

  5. 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,, and files and then repeat this step.

  6. 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 command 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.

  7. Start the WebSphere Portal server:

      cd profile_root/bin
      ./startServer.bat WebSphere_Portal

If you have performed database transfer in a clustered environment, explicitly copy...

...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 file.

  1. Stop the portal server on the secondary node.

  2. Copy...


    ...from the primary node and replace the 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

Related information

DB2 Universal Database commands by example
SQL0443N with SYSIBM:CLI:-805 when invoking a CLI catalog function after upgrading to DB2 UDB Version 8.1 FixPak 10