Configure WebSphere Portal to use DB2 for z/OS

View information on manually transferring data to theDB2 for z/OS you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository to DB2 for z/OS. 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:


Installing DB2 for z/OS

Creating users

Creating remote databases

Creating the Java Content Repository database

Modifying database properties

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. Enter the following commands to validate configuration properties.

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

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

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

  5. Stop both WAS and the WebSphere Portal server:

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

  6. Transfer the database:

    1. cd profile_root/ConfigEngine.

    2. Enter the following command:

      ./ database-transfer -DTransferDomainList=release,customization,community,jcr, feedback,likeminds

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

  7. From the command line processor, reset the check pending status on the WebSphere Portal table spaces listed here. CHECK DATA is a DB2 batch utility that is invoked through JCL or through the DB2 utility panels. Type the following utility commands to check pending status:

    check data tablespace releasenameonzos.TS320A check data tablespace releasenameonzos.TS280A check data tablespace releasenameonzos.TS300A check data tablespace releasenameonzos.TS2110A check data tablespace releasenameonzos.TS830A check data tablespace communitynameonzos.TS8000B check data tablespace communitynameonzos.TS8011B check data tablespace communitynameonzos.TS280B check data tablespace customizationnameonzos.TS2110C check data tablespace jcrdbnameonzos.ICMSFQ04 check data tablespace jcrdbnameonzos.TS2110D

    where releasenameonzos, communitynameonzos, and customizationnameonzos are the names of your WebSphere Portal databases, and jcrdbnameonzos is the name of your JCR database. Refer to the Utility Guide and Reference for DB2 for z/OS for additional details.

  8. Run the RUNSTATS utility as shown in the following example:


  9. Start the WAS.

  10. Verify that the WebSphere Portal appserver is running by opening the following URL in a browser:, where is the fully qualified host name of the machine where WebSphere Portal is running and port_number is the transport port that is created by WAS.

If you have performed database transfer in a clustered environment, explicitly copy the profile_root/PortalServer/jcr/lib/com/ibm/icm/ 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 file.

  1. Stop the portal server on the secondary node.

  2. Copy the profile_root/PortalServer/jcr/lib/com/ibm/icm/ file 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:

Prepare DB2 for z/OS for a stand-alone production server

Previous topic:

Modifying database properties

Next topic:

Verify database connections