Plan for DB2 for z/OS

When planning to transfer data to IBM DB2 Universal Database™ for z/OS®, you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Some fix packs require steps prior to the transfer task to complete successfully.

When planning to install DB2 for z/OS to use as the database for WebSphere Portal, consider the following:

The database names and users on this page are suggested values and provide consistency throughout the documentation. Replace these values with values in environment. The database name cannot exceed eight characters and can only contain letters and numbers.

If you plan to use a single DB2 for z/OS subsystem to hold data for more than one portal installation, use the same user name but a separate schema name for each database domain. For Member Manager, the user name must match the schema; the same database user cannot be used for the Member Manager databases of two distinct portal installations.

Each portal installation must be in separate and distinct WAS cells. If the portals are installed in the same file system, each must be installed in a separate and unique directory. If the portals are installed in different file systems, the same directory name can be used.

In a remote database environment, WebSphere Portal and DB2 Connect are installed on one machine (the local machine) and the DB2 for z/OS server is installed on a separate machine (the remote machine).

  1. Review the different databases shown in the following table and replace these values with the values in environment; schema names must be different when the database subsystem is shared.

      You can configure WebSphere Portal to use one database. However, using separate databases will improve scalability and performance.

      Application Database name Space required
      WebSphere Portal

      Used for WebSphere Portal (at a minimum) or to hold all data. Stores information about user customizations, such as pages, and user profile and login information.

        relzos

        commzos

        custzos

      		Depends on the number of WebSphere Portal users and portal objects, such as pages and portlets.
      Personalization, Web Content Manager

      Contains documents and other content, personalization rules, personalization campaigns, and document library configuration information.

      		jcrdbzos Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Manager.
      Feedback

      Contains the information that is logged by Web site for generating reports for analysis of site activity.

        Database: fdbkzos

        Table space: fdbkdbts

      		Depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
      LikeMinds

      Contains the recommendations to be displayed to users when their interactions with Web site have been analyzed and predictions generated.

        Database: lmdbzos

        Table space: lmdbts

      		Depends on the amount of traffic to the site.

  2. Review the tables and types of objects owned by each user.

      The architecture allows each of the following users to exist in the same database. All table spaces are approximately 2.8 GB by default. The size increases with the use of Java™ Content Repository. Table 2. Tables and objects owned by database users


      Application
      Database user placeholder
      Function
      WebSphere Portal

        releaseusr

        communityusr

        customizationusr

      		Core user who owns approximately 230 tables, used for WebSphere Portal core objects, which includes tables that store the user customizations made to pages.
      Java Content Repository

        jcr
      		Java Content Repository user who owns at least 1130 tables. The number could be higher depending on usage.
      Feedback

        feedback
      		Feedback user who owns approximately 50 tables used for logging site and personalization usage.
      LikeMinds

        likeminds
      		LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.

  3. If Java Content Repository is using declared global temporary tables (DGTT), have the appropriate TEMP database and TEMP tablespaces configured prior to use. The TEMP database may also require additional allocated space. Use the following information as a guideline to create a TEMP database and a TEMP tablespace to contain the declared temporary tables:

    Examples on how to create a TEMP database and a TEMP tablespace by database version

    Database version Example
    DB2 for z/OS Version 8 Create a TEMP database and tablespace if it does not already exist. The following is a representative example of a TEMP database definition: 

      CREATE DATABASE TEMP AS TEMP STOGROUP SYSDEFLT;
CREATE TABLESPACE TEMP IN TEMP  
USING STOGROUP SYSDEFLT  
BUFFERPOOL BP8  
SEGSIZE 32;

    This version also requires work file database storage for SQL statements that require working storage, such as sorts. This requires the addition of a table space to support sorting operations in addition to the TEMP database.
    DB2 for z/OS Version 9 in a non-data sharing environment The TEMP database is DSNDB07 and is created during database installation. Temporary table spaces are added to the existing TEMP database. The following is a representative example of a temporary table space: 

      CREATE TABLESPACE ICMTEMP IN DSNDB07  
USING STOGROUP SYSDEFLT  
BUFFERPOOL BP8  
SEGSIZE 32;

    In this version the work file database and TEMP databases are combined. See the DB2 for z/OS information center for the procedures and sizing recommendations for creating work file databases.
    DB2 for z/OS Version 9 in a data sharing environment Create a WORKFILE database. Only one WORKFILE database can be created per subsystem. The following is a representative example for creating a WORKFILE database and temporary table space: 

      CREATE DATABASE WORKTEMP AS WORKFILE STOGROUP SYSDEFLT;  
CREATE TABLESPACE ICMTEMP IN WORKTEMP  
USING STOGROUP SYSDEFLT  
BUFFERPOOL BP8  
SEGSIZE 32;

    In this version the work file database and TEMP databases are combined. See the DB2 for z/OS information center for the procedures and sizing recommendations for creating work file databases.

    Refer to the DB2 for z/OS documentation for additional information on setting up the TEMP database and TEMP tablespaces.


Parent

Database considerations


Related tasks

WebSphere Portal detailed system requirements

http://www.ibm.com/software/data/pubs/

DB2 for z/OS

DB2 Installation Guide

  changed Redbook to Redbooks publication


+

Search Tips   |   Advanced Search