Plan for DB2 for OS/390 and z/OS

Plan for DB2 for OS/390 and z/OS

This section is designed to give the DB2 for OS/390 and z/OS administrator an overall picture of WebSphere Portal database requirements.
Before you begin:

You should have reviewed the Database topic to determine if you are going to transfer WebSphere Portal data to another supported database.
Ensure the database you plan to use is supported by this version of WebSphere Portal. Refer to Supported hardware and software for supported database that are needed for WebSphere Portal.
Ensure that the job DSNTIJSG has been executed to create the objects required for the DB2 JDBC and ODBC metadata methods.
Ensure that support for table spaces that are defined with the Unicode encoding schema is enabled.
Ensure that prepared, dynamic SQL statements are cached (DSN6SPRM CACHEDYN set to YES). See the DB2 for OS/390 and z/OS Installation Guide for details.

Plan

After the DB2 for OS/390 and z/OS software has been installed, create the required databases and users and grant the proper privileges to those users. The database names and users in this section are values to provide consistency throughout the documentation. During installation and configuration, replace these values with values in your environment.
If you plan to use a single DB2 for OS/390 and z/OS subsystem to hold data for more than one portal instance, create a unique database user for each portal instance. By default all database table names include the name of the database user used to access the data. Therefore, to prevent table name conflicts, create a unique database user for each WebSphere Portal instance on the shared DB2 for OS/390 and z/OS subsystem. Each portal instance must be in separate and distinct WebSphere Application Server cells. If the portal instances are installed in the same file system (for example, two portal instances on one Windows server box), each instance must be installed in a separate and unique directory. If the portal instances are installed in different file systems (for example, two portal instances on two Windows server boxes), the same directory name can be used.
Note the following information:

If WebSphere Portal V5.1 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal V5.1 must be different than earlier versions to avoid conflicts during installation.
WebSphere Portal data and Member Manager data should be stored in one database. See Member Manager in Managing Security for information.
DB2 Content Manager Runtime Edition is a data repository running against DB2 for OS/390 and z/OS that is used to to store data for applications such as Personalization, Document Manager, and Lotus Workplace Web Content Management .

Databases

The following table demonstrates the information each application will store in the databases.

Application Placeholder Names Function Space considerations

WebSphere Portal
Member Manager

Database: wpsdbnameonzos Used for WebSphere Portal and Member Manager (at a minimum) or to hold all data. Stores information about user customizations, such as Pages, and user profile and login information. The amount of database space that is required depends on the number of WebSphere Portal users and portal objects, such as pages and portlets.

Document Manager
Personalization
Database: jcrdbnameonzos

Used by DB2 Content Manager Runtime Edition to store Document Manager and Personalization components. Contains documents, personalization rules, personalization campaigns, and document library configuration information. The amount of database space that is required depends on the size and number of documents created and/or uploaded by the Document Manager and the number and size of Personalization rules and campaigns.

Feedback
Database: fdbkdbnameonzos
Table space: fdbkdbts
Used by Feedback components. Contains the information that is logged by your web site for generating reports for analysis of site activity. The amount of database space that is required for logging depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.

Likeminds
Database: lmdbnameonzos
Table space: lmdbts
Used for LikeMinds data. Contains the recommendations to be displayed to users when their interactions with your Web site have been analyzed and predictions generated. The amount of database space that is required depends on the amount of traffic to the site.

Users

The following table demonstrates the number of tables and types of objects owned by each user. The WebSphere Portal architecture allows each of the following users to exist in the same DB2 for OS/390 and z/OS database.

Application Database user placeholder Function

WebSphere Portal

wpsdbusr Core user.
Will own approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.

Member Manager
wmmdbusr Member Manager user.
Will own approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.

Document Manager
Personalization

icmadmin DB2 Content Manager Runtime Edition user (documents and personalization).
Will own approximately 100 tables used for document management and personalization. Tables are dynamically created based on the resources that you define for content management.

Feedback

feedback Feedback user.
Will own approximately 48 tables used for logging site and personalization usage.

Likeminds

lmdbusr Likeminds user.
Will own the tables used to hold the web site usage analysis routines and recommendation text.

DB2 for OS/390 and z/OS architecture

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

Local Machine
IP Address: 1.2.3.4

WebSphere Portal

DB2 for OS/390 and z/OS Connect:
db2inst1
Connect to server on 1.2.3.5

Remote Machine
IP Address: 1.2.3.5

DB2 for OS/390 and z/OS server:
db2inst1

Next steps

Database (Windows/UNIX)
Install DB2 for OS/390 and z/OS
Create databases and users for DB2 for OS/390 and z/OS
Configure DB2 for OS/390 and z/OS
Verifying database connections
Install DB2 for OS/390 and z/OS

Workplace Web Content Management is a trademark of the IBM Corporation in the United States, other countries, or both.

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.

Application	Placeholder Names	Function	Space considerations
WebSphere Portal Member Manager	Database: wpsdbnameonzos	Used for WebSphere Portal and Member Manager (at a minimum) or to hold all data. Stores information about user customizations, such as Pages, and user profile and login information.	The amount of database space that is required depends on the number of WebSphere Portal users and portal objects, such as pages and portlets.
Document Manager Personalization	Database: jcrdbnameonzos	Used by DB2 Content Manager Runtime Edition to store Document Manager and Personalization components. Contains documents, personalization rules, personalization campaigns, and document library configuration information.	The amount of database space that is required depends on the size and number of documents created and/or uploaded by the Document Manager and the number and size of Personalization rules and campaigns.
Feedback	Database: fdbkdbnameonzos Table space: fdbkdbts	Used by Feedback components. Contains the information that is logged by your web site for generating reports for analysis of site activity.	The amount of database space that is required for logging depends on the amount of traffic to the site. The amount of data that is logged per login-enabled page can vary.
Likeminds	Database: lmdbnameonzos Table space: lmdbts	Used for LikeMinds data. Contains the recommendations to be displayed to users when their interactions with your Web site have been analyzed and predictions generated.	The amount of database space that is required depends on the amount of traffic to the site.

Application	Database user placeholder	Function
WebSphere Portal	wpsdbusr	Core user. Will own approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
Member Manager	wmmdbusr	Member Manager user. Will own approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
Document Manager Personalization	icmadmin	DB2 Content Manager Runtime Edition user (documents and personalization). Will own approximately 100 tables used for document management and personalization. Tables are dynamically created based on the resources that you define for content management.
Feedback	feedback	Feedback user. Will own approximately 48 tables used for logging site and personalization usage.
Likeminds	lmdbusr	Likeminds user. Will own the tables used to hold the web site usage analysis routines and recommendation text.