Planning 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, and the database space needed.

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

    Table 1. Applications, database names, and space required. Applications, database names, and required space

    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 Management

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

    Contains the information that is logged by your 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.


    Contains the recommendations to be displayed to users when their interactions with your 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.

    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 user who owns approximately 50 tables used for logging site and personalization usage.

    • likeminds

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

Parent topic:


Related information

Manage LOB logging in DB2 for z/OS
WebSphere Portal detailed system requirements
DB2 for z/OS
DB2 Installation Guide