Plan for Oracle

 

+
Search Tips   |   Advanced Search

 

Contents

  1. Before you begin
  2. Databases
  3. Users
  4. Next steps

You are here

  1. Planning for Oracle (Current task)
  2. Installing Oracle
  3. Creating databases and users for Oracle
  4. Transferring Oracle manually or Transferring between databases manually
  5. Verifying database connections

 

Before you begin

  1. Review the Configuring databases topic.

  2. Ensure the database you plan to use is supported by WebSphere Portal v6.0.

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

  4. If WebSphere Portal Version 6.0 and an earlier version of WebSphere Portal coexist, the database user IDs for WebSphere Portal Version 6.0 must be different than earlier versions to avoid conflicts during installation.

    If the two versions of WebSphere Portal coexist on different databases, using the same user ID will not cause conflict.

  5. The Feedback function is not configured by default. It must first be turned it on by following the steps in Enable logging, otherwise the Feedback tables will not be created in the new database.

  6. DB2 Content Manager Runtime Edition is a data repository that runs on Oracle to store data for applications such as...

The following sections provide an overview of the different databases and database user names you should consider in the planning.

While configuring Portal to use one database is technically possible, IBM recommends using separate databases for scalability and performance tuning reasons. To use a single shared database, replace each database and user variable with the name of the database and database user, respectively.

 

Databases

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

Application Database Name Function Space considerations
WebSphere Portal release
community
customization
Used for WebSphere Portal (at a minimum) or to hold all data. Stores information about user customization, such as Pages, and user profile and login information. Amount of database space that is required depends on the number of WebSphere Portal users and portal objects, such as pages and portlets.
Member Manager wmmdb Used for Member Manager if the data is not stored on the WebSphere Portal database. Stores information about users and groups. Dependent on the configuration of users, groups and their relationship, or only additional attributes are stored. Amount of this database depends on the number of Users and groups you are storing within the database repository. If your user repository is an LDAP this database is not used.
Document Manager, Personalization, Web Content Management jcrdb Used by Document Manager and Personalization components. Contains documents, personalization rules, personalization campaigns, and document library configuration information. 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 the web site for generating reports for analysis of site activity. 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 the Web site have been analyzed and predictions generated. 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 database.

All tablespaces will be approximately 2.8 GB by default. The size will increase with the use of the DB2 Content Manager Runtime Edition function.

Application Database user placeholder Recommended name Function
WebSphere Portal releaseusr
communityusr
customizationusr
<none> Core user. Will own approximately 130 tables for each domain. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
DB2 Content Manager Runtime Edition icmadmin <none> DB2 Content Manager Runtime Edition user. Will own at least 1130 tables; the number could be higher depending on usage.
Member Manager wmmdbusr <none> Member Manager user. Will own approximately 35 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
Feedback feedback <none> Feedback user. Will own approximately 50 tables used for logging site and personalization usage.
Likeminds lmdbusr <none> Likeminds user. Will own approximately 15 tables used to hold the web site usage analysis routines and recommendation text.

 

Next steps

You have completed this step. Continue to the next step:

 

Parent topic:

Planning for databases