Plan for Oracle

 

+
Search Tips   |   Advanced Search

 

Overview

Before you begin review the Database topic. Also, ensure the database you plan to use is supported by this version of WebSphere Portal.

After the Oracle software has been installed, create the required databases and users and grant the proper privileges to those users.

WebSphere Portal data and Member Manager data should be stored in one database and accessed by one database user. See Member Manager in Managing Security for 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.

DB2 Content Manager Runtime Edition is a data repository that runs on Oracle 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 Database Name Function Space considerations
WebSphere Portal

Member Manager

wpsdb 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

jcrdb Used by 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 fdbkdb 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 lmdb 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 Oracle database.

Application Database user Recommended name Function
WebSphere Portal wpsdbusr <none> 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 <none> 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 <none> 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 Feedback user.

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

Likeminds lmdbusr <none> Likeminds user.

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

 

Next steps

 

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.