Portal database domains

Portal database domains

Domain categories portal data into the following categories...

Data Domains Description
Release release
jcr Release data includes two separate database domains: Release and JCR. Typically not modified during production. Administrators typically create release data on an integration server, then stage it to a production system. The Release domain contains portal static site configuration, including access control, pages, and portlets. The JCR database domain contains authored content, Personalization rules, and theme policy definitions.
Customization customization Data scoped with a particular user only. Cannot be shared across users or user groups. Includes portlet data and customized pages (implicitly derived pages).
Community community Resources can be modified during production. Typically, users and groups are allowed to modify or delete shared resources. Community resources are protected by access control.
Configuration
Not stored in a database domain. Typically kept in property files that are either protected by file system security, or application server administration rights. This data defines the portal server setup, such as database connection, object factories, and deployment descriptors. Typically is constant during the time a server node is running.
Feedback feedback Stores data exclusively for the Feedback application.
Likeminds likeminds Stores data exclusively for the LikeMinds application.

Database schema names

The table below includes the default schema names used in by the Configuration Wizard. Replace these values with the values for our environment. Schema names must be different when the database is shared with another portal. All table spaces will be approximately 2.8 GB by default. The size will increase with the use of the Java Content Repository function. For some database software, such as DB2, the database name cannot exceed 8 characters and can contain letters and numbers only.

Applications DB names Description Space required
WebSphere Portal reldb commdb custdb Depends on the number of users and portal objects, such as pages and portlets. 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.
Personalization
Web Content Manager jcrdb Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in WCM. Contains documents, personalization rules, personalization campaigns, and document library configuration information.
Feedback fdbkdb Contains the information logged by the website for analysis of site activity and generating reports. Depends on the amount of traffic to the site. The amount of data logged per login-enabled page can vary.
LikeMinds lmdb Contains the recommendations displayed to users. The LikeMinds application analyzes the visitor's interactions with the website are and generates predictions. Depends on the amount of traffic to the site.

Database users

The table indicates types of objects that are owned by each user. 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 Function
WebSphere Portal releaseusr communityusr customizationusr Owns approximately 230 tables used for WebSphere Portal core objects, including tables that store user customizations to pages.
Java Content Repository jcr Owns approximately 100 tables. The number might 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 website usage analysis routines and recommendation text.

db2 connect to

With DB2, if you get error similar to...

db2-01$ db2 connect to fdbkdb
SQL0930N There is not enough storage available to process the statement.
SQLSTATE=57011

...debug...

Confirm memory use using the db2mtrk command.
Run either db2 snapshots or db2pd commands to determine what agents are consuming available memory.

Parent Database

Data	Domains	Description
Release	release jcr	Release data includes two separate database domains: Release and JCR. Typically not modified during production. Administrators typically create release data on an integration server, then stage it to a production system. The Release domain contains portal static site configuration, including access control, pages, and portlets. The JCR database domain contains authored content, Personalization rules, and theme policy definitions.
Customization	customization	Data scoped with a particular user only. Cannot be shared across users or user groups. Includes portlet data and customized pages (implicitly derived pages).
Community	community	Resources can be modified during production. Typically, users and groups are allowed to modify or delete shared resources. Community resources are protected by access control.
Configuration		Not stored in a database domain. Typically kept in property files that are either protected by file system security, or application server administration rights. This data defines the portal server setup, such as database connection, object factories, and deployment descriptors. Typically is constant during the time a server node is running.
Feedback	feedback	Stores data exclusively for the Feedback application.
Likeminds	likeminds	Stores data exclusively for the LikeMinds application.

Applications	DB names	Description	Space required
WebSphere Portal	reldb commdb custdb	Depends on the number of users and portal objects, such as pages and portlets.	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.
Personalization Web Content Manager	jcrdb	Depends on the number and size of Personalization rules and campaigns, and the number and size of items and elements created in WCM.	Contains documents, personalization rules, personalization campaigns, and document library configuration information.
Feedback	fdbkdb	Contains the information logged by the website for analysis of site activity and generating reports.	Depends on the amount of traffic to the site. The amount of data logged per login-enabled page can vary.
LikeMinds	lmdb	Contains the recommendations displayed to users. The LikeMinds application analyzes the visitor's interactions with the website are and generates predictions.	Depends on the amount of traffic to the site.

Application	Database user	Function
WebSphere Portal	releaseusr communityusr customizationusr	Owns approximately 230 tables used for WebSphere Portal core objects, including tables that store user customizations to pages.
Java Content Repository	jcr	Owns approximately 100 tables. The number might 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 website usage analysis routines and recommendation text.