Solaris stand-alone: Configure the portal to use DB2 for z/OS

View information on manually transferring data to theDB2 for z/OSyou 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. However, you cannot specify all settings through the configuration wizard. For example, regardless of the method used to transfer data, run a configuration task to create JMS resources as described in this topic.

Before you begin:

Ensure that the following prerequisites are met:


Prerequisites


Install DB2 for z/OS
Modify properties for DB2 for z/OS
Create users for DB2 for z/OS
Create a remote database on DB2 for z/OS
Grant privileges to DB2 for z/OS users
Create the Java content repository database on DB2 for z/OS

  1. If you are running a type 2 connection, edit the db2cli.ini file that resides on the local system, where WebSphere Portal is installed, before you transfer data.

    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:

        Edit 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

      cd WP_PROFILE/ConfigEngine

  3. Enter the ./ConfigEngine.sh validate-database -DWasPassword=foo command to validate configuration properties.

      Add -DTransferDomainList to specify the domains to validate; for example: -DTransferDomainList=jcr.

  4. From the same command prompt as the previous steps, cd WP_PROFILE/bin.

  5. Stop both the server1 and WebSphere_Portal servers:

    • ./stopServer.sh server1 -username admin_userid -password foo

    • ./stopServer.sh WebSphere_Portal -username admin_userid -password foo

  6. Transfer the database:

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

      2. Enter the following command:

          ./ConfigEngine.sh database-transfer -DWasPassword=foo
          To select specific database domains to transfer, set -DTransferDomainList to include only the domains that you want to transfer. For example, to transfer only the JCR domain:

            ./ConfigEngine.sh database-transfer -DTransferDomainList=jcr -DWasPassword=foo

      3. After running the task, a message is added to the following log file for you to verify the task ran successfully:

          WP_PROFILE/ConfigEngine/log/ConfigTrace.log

          If the configuration fails, verify the values in wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties and then repeat this step.

  7. If a dedicated runtime 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 runtime database user name and the schema name. Open the createRuntimeRoleForSameSchema.sql file when the same name is used for the runtime database user name and the schema name. These files are located in $PORTAL_HOME/base/wp.db.impl/config/templates/setupdb/db2_zos/domain and $PORTAL_HOME/pzn/prereq.pzn/config/templates/setupdb/db2_zos/domain directories.

    • Replace all placeholders (surrounded by '@' characters) with the values defined in wkplc_dbdomain.properties.

    • 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 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 WebSphere Portal databases, and jcrdbnameonzos is the name of 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. Run the ./ConfigEngine.sh create-jcr-jms-resources-post-dbxfer -DWasPassword=foo command to create JMS resources in the new database.

      Regardless of the method used to transfer data (configuration wizard or the steps in this topic), run this task to create JMS resources.

  11. Start the WAS.

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

If you have additional nodes already configured, compare the following file on all nodes with the file from the primary node. Ensure all instances of the file are identical:

If the files are not identical, copy icm.properties from the primary node on which you ran the database-transfer task to the node.

  1. Stop the portal server on the secondary node.

  2. Copy

      WP_PROFILE/PortalServer/jcr/lib/com/ibm/icm/icm.properties

    from the primary node and replace icm.properties on the secondary node.

  3. Start the portal server on the secondary node.


Parent

Prepare DB2 for z/OS


Previous

Assign custom tablespaces for DB2 on z/OS

 


+

Search Tips   |   Advanced Search