Plan for DB2 for z/OS

Portal, V6.1

Plan for DB2 for z/OS

When planning to transfer data to DB2 for z/OS you should consider the databases and user information, such as database names, what data is stored, and the database space needed. Before you begin:

Review the "Database considerations" topic.
Ensure the database that you plan to use is supported by this version of WebSphere Portal.
Refer to Supported hardware and software for the list of supported databases.

Guidelines:
If the current version of WebSphere Portal and an earlier version coexist using the same DB2 for z/OS subsystem the database user IDs for the current version of WebSphere Portal must be different than the earlier version to avoid conflicts during installation. If the two versions of WebSphere Portal connect to two different DB2 for z/OS subsystems using the same user ID will not cause conflict.
Check the bufferpool allocations for your system, and define the bufferpools as appropriate for your installation and define a large enough size. For example:
-db2 display bufferpool(bp2) 
-db2 alter bufferpool(bp2) vpsize(15000)
Repeat for additional bufferpools as needed, ex: bp3, bp4, bp5, bp32k1, bp32k2.
Java Content Repository is a data repository that runs on DB2 to store data for applications such as Personalization and Web Content Management.
During database transfer from Derby to DB2 for z/OS, a supporting low order byte table space is created for the database tables storing documents. The PRIQTY and SECQTY for the table space are assigned using the default values. If you plan to store a large number of documents, you should use an automatic class selection (ACS) routine to allocate the DB2 for z/OS data sets with a primary and secondary space allocation of at least 10 cylinders, or specify a large enough value for PRIQTY and SEQTY in the DB2 DSNTIJUZ member. The table spaces can be identified by their name, having a structure like JCRDB.Sxxxxxxx, where xxxxxxx is a system-assigned combination of seven numbers and characters.
Also in member DSNTIJUZ, update the following parameters and then verify DSNTIJUZ runs successfully:
edmdbdc = 204800  edmpool=409600  edmstmtc=204800  rrulock=yes cachedyn=yes   (prepared, dynamic SQL statements are cached)
Ensure that the job DSNTIJSG has been executed to create the objects required for the DB2 JDBC and ODBC metadata methods. See the DB2 Installation Guide Enabling stored procedures and tables for JDBC and ODBC support.
Ensure that job DSNTIJMS runs successfully (re-execute binds)
Ensure that job DSNTIJEX runs successfully
Cycle DB2 to pick up the zparm changes
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 WAS cells. If the portals are installed in the same file system, each must be installed in a separate and unique. 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).

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. While configuring WebSphere Portal to use one database is technically possible, using separate databases can 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, WCM
Contains documents, 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 WCM .
Feedback
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.
LikeMinds
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.

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

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

lmdbusr

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

Parent topic
Planning for databases

Related tasks

http://www.ibm.com/support/docview.wss?rs=688&uid=swg27007791
http://www.ibm.com/software/data/pubs/

Related information

http://www.ibm.com/software/data/db2/os390/
DB2 Installation Guide

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, WCM Contains documents, 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 WCM .
Feedback 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.
LikeMinds 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.

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	lmdbusr	LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.