Portal, V6.1

---

 

Configure WebSphere Portal to use DB2 for z/OS

This section provides information on how to manually transfer data to theDB2 for z/OS you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to DB2 for z/OS

Before you begin:
Ensure that the following prerequisites are met:

• Supported database software is installed.

• Databases and users are set up.

Prerequisites

Installing DB2 for z/OS

Creating users

Creating remote databases

Tips:

• The steps for transferring data to another supported database section provides instructions for manually transferring data. Instead of performing the following steps, use the configuration wizard, which is a graphical user interface, to transfer data to another supported database.

• If you are transferring from Oracle, the open_cursors setting should be set to 1500 by default. If you are using Java Content Repository, this value might need to be increased based on the table count in the Java Content Repository schema.

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 C:\Program Files\ibm\SQLLIB\db2cli

   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 WP_PROFILE/ConfigEngine.

3. Validate configuration properties.

   • ConfigEngine.bat validate-database-driver -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

   • ConfigEngine.bat validate-database-connection -DTransferDomainList=release,customization,community,jcr,feedback,likeminds

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

5. Stop both WAS and the WebSphere Portal server:

   Option	Description
   WAS	stopServer.bat server1 -username adminid -password passwd
   WebSphere Portal	stopServer.bat WebSphere_Portal -username adminid -password passwd

6. Transfer the database:

   1. Change to the directory WP_PROFILE/ConfigEngine.

   2. Enter the following commands:

      ConfigEngine.bat 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 wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties 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:

   LISTDEF JCRDBZOS INCLUDE TABLESPACE JCRDBZOS.* BASE RUNSTATS TABLESPACE LIST JCRDBZOS INDEX(ALL) KEYCARD TABLE(ALL) LISTDEF JCRDB01 INCLUDE TABLESPACE JCRDB01.* BASE RUNSTATS TABLESPACE LIST JCRDB01 INDEX(ALL) KEYCARD TABLE(ALL)
   ...
   

9. Start the WAS.

10. Verify that the WebSphere Portal application server is running by opening the following URL in a browser: http://hostname.companyname.com:port_number/wps/portal, where hostname.companyname.com 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.

 

Parent topic

Configure WebSphere Portal to use DB2 for z/OS

 

Previous topic:

Assigning custom table spaces

---