Plan for Oracle

Plan for Oracle

Before starting, verify system requirements.
The database names and users in this topic are suggested values and provide consistency throughout the documentation. Replace these values with values in the environment.

Application Description DB name Space required
WebSphere Portal Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information. reldb
commdb
custdb Depends on the number of users and portal objects, such as pages and portlets.
Personalization, WCM Contains documents, personalization rules, personalization campaigns, and document library configuration information. jcrdb Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Manager.
Feedback Information logged by the Web site for analysis of site activity and generating reports. fdbkdb Depends on the amount of traffic to the site. The amount of data logged per login-enabled page can vary.
LikeMinds Contains the recommendations to be displayed to users when their interactions with the Web site have been analyzed and predictions generated. lmdb Depends on the amount of traffic to the site.

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 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 Owns at least 1130 tables. The number could be higher depending on usage.
Feedback feedback Owns approximately 50 tables used for logging site and personalization usage.
LikeMinds likeminds Owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.

Parent: Database considerations
Related:

WebSphere Portal V8.5 and V8.0 detailed system requirements
Oracle product documentation

Application	Description	DB name	Space required
WebSphere Portal	Used for the portal (at a minimum) or to hold all data. Stores information about user customization, such as pages, and user profile and login information.	reldb commdb custdb	Depends on the number of users and portal objects, such as pages and portlets.
Personalization, WCM	Contains documents, personalization rules, personalization campaigns, and document library configuration information.	jcrdb	Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Manager.
Feedback	Information logged by the Web site for analysis of site activity and generating reports.	fdbkdb	Depends on the amount of traffic to the site. The amount of data logged per login-enabled page can vary.
LikeMinds	Contains the recommendations to be displayed to users when their interactions with the Web site have been analyzed and predictions generated.	lmdb	Depends on the amount of traffic to the site.

Application	Database user placeholder	Function
WebSphere Portal	releaseusr communityusr customizationusr	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	Owns at least 1130 tables. The number could be higher depending on usage.
Feedback	feedback	Owns approximately 50 tables used for logging site and personalization usage.
LikeMinds	likeminds	Owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.