Planning for Oracle

This section is designed to give the Oracle database administrator an overall picture of WebSphere Portal database requirements. Sometimes approximate numbers can be used in an effort to help with space and architecture planning; however, these numbers are to be used as guides. Substitute the appropriate values for your unique environment.

After the Oracle software has been installed, create the databases, create the users, and grant the proper privileges to those users. The WebSphere Portal and content publishing architecture require six database users. Some of these Oracle users have no required naming conventions. Others, as indicated, are required to be specific names. For the purpose of making it easier to follow the documentation, they are referred to here as:

Note: If you choose to use one database to hold all WebSphere Portal, Member Manager, and content publishing information, create at least one user for the shared WebSphere Portal and Member Manager tables and another user for the content publishing tables.

The WebSphere Portal architecture allows each of these users to exist in the same Oracle database. However, for easier administration and performance reasons, it is strongly recommended that the following architecture be implemented:

Database User
wps50 wpsdbusr
wmmdbusr
wpcp50 pznadmin
EJB
wcmdbadm
fdbk50 feedback

Database functionality

The following table demonstrates what information is contained in the required databases.

Database Function
wps50 Stores information about user customizations, such as Pages, and user and login information.
wpcp50 Contains Document Manager configuration information.
fdbk50 Contains the information that is logged by your Web site for generating reports for analysis of site activity.
Note: When considering the amount of storage space that is needed for the feedback database, it is important to remember that the amount of database space that is required for logging depends on the amount of traffic to the site, and the amount of data that is logged per login-enabled page can vary.

User functionality

The following table demonstrates the number of tables and types of objects owned by each required user.

Database user Function
wpsdbusr Will own approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
wmmdbusr Will own approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
pznadmin Will own approximately 11 tables. Jointly owns tables with EJB.
EJB Will own approximately 2 tables. Jointly owns tables with With pznadmin.
wcmdbadm Will own approximately 61 tables. Tables are dynamically created based on the resources that you define for content management.
feedback Will own approximately 48 tables used for logging site usage.

Next steps

You have completed this step. Continue to the next step by choosing one of the following topics:

Related information