Linux idle standby: Configuring your 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 Express®, 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. However, you cannot specify all settings through the configuration wizard. For example, regardless of the method used to transfer data, you must run a configuration task to create JMS resources as described in this topic.

1. Edit the db2cli.ini file that resides on the local system, where WebSphere Portal Express is installed, before you transfer data.
   Important: The database transfer becomes unresponsive at task action-process-constraints if you do not complete these steps.
   1. Locate the file /home/db2inst1/sqllib/cfg/db2cli.ini.
   2. Add the following lines to the end of the file:
      Editing db2cli.ini:

      • If a section named [COMMON] already exists in the file, extend that section by adding the following lines. Otherwise, add a [COMMON] section to 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_root/ConfigEngine.
3. Enter the ./ConfigEngine.sh validate-database -DWasPassword=password command to validate configuration properties.
   Tip: Add the -DTransferDomainList parameter to the validating task to specify the domains you want to validate; for example: -DTransferDomainList=jcr. If you want to validate all domains, you do not need to specify this parameter on the command line.
4. From the same command prompt as the previous steps, change to the directory wp_profile_root/bin.
5. Stop the WebSphere_Portal server:
   
   • ./stopServer.sh WebSphere_Portal -username admin_userid -password admin_password
6. Transfer the database:
   Note: 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_root/ConfigEngine.
   2. Enter the following command: ./ConfigEngine.sh database-transfer -DWasPassword=password
      Note: To select specific database domains to transfer, modify the -DTransferDomainList specified in the command to include only the domains that you want to transfer. For example, to transfer only the JCR domain you can enter the following command: ./ConfigEngine.sh database-transfer -DTransferDomainList=jcr -DWasPassword=password
   3. After running the task, a message is added to the following log file for you to verify the task ran successfully: wp_profile_root/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.
7. If a dedicated run time database user has been specified (domain.DbRuntimeUser), ensure that this user has sufficient database privileges. Refer to the appropriate template file (grantRoleToConfigUser.sql or grantRoleToRuntimeUser.sql) containing the required GRANT statements for each of the db domains.
   • Open the createRuntimeRoleForDifferentSchema.sql file when different names are used for the run time database user name and the schema name. Open the createRuntimeRoleForSameSchema.sql file when the same name is used for the run time database user name and the schema name. These files are located in PortalServer_root/base/wp.db.impl/config/templates/setupdb/db2_zos/domain and PortalServer_root/pzn/prereq.pzn/config/templates/setupdb/db2_zos/domain directories.
   • Replace all placeholders (surrounded by '@' characters) with the values defined in the wkplc_dbdomain.properties file.
   • Execute these statements in the createRuntimeRoleForDifferentSchema.sql or createRuntimeRoleForSameSchema.sql file as appropriate.
8. From the command line processor, reset the check pending status on the WebSphere Portal Express 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 Express 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.

9. 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)
   ...

10. Start the WebSphere Application Server.
11. Verify that the WebSphere Portal Express 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 Express is running and port_number is the transport port that is created by WebSphere Application Server.