Plan for SQL Server

Plan for SQL Server

Before starting, verify system requirements.

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.

Connect at least one user to the SQL Server instance. A user can be granted permission to use several schema names, so a single user for each instance is sufficient.
The WebSphere Portal architecture allows each of the following schemata to exist in the same database. All table spaces will be approximately 2.8 GB by default. The size will increase with the use of the Java Content Repository function.

Application Database schema Recommended name Function
WebSphere Portal releaseusr
communityusr
customizationusr <none> Owns approximately 130 tables for each domain. Owns portal core objects, which includes tables that store the user customizations made to Pages.
Java Content Repository icmadmin <none> Owns at least 1130 tables; the number could be higher depending on usage.
Feedback feedback <none> Owns approximately 50 tables used for logging site and personalization usage.
Likeminds LIKEMINDS <none> 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
Progress DataDirect
Microsoft SQL Server product documentation
Registry Entries Are Required for XA Transaction Support
7391 error message in SQL Server 2000

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 schema	Recommended name	Function
WebSphere Portal	releaseusr communityusr customizationusr	<none>	Owns approximately 130 tables for each domain. Owns portal core objects, which includes tables that store the user customizations made to Pages.
Java Content Repository	icmadmin	<none>	Owns at least 1130 tables; the number could be higher depending on usage.
Feedback	feedback	<none>	Owns approximately 50 tables used for logging site and personalization usage.
Likeminds	LIKEMINDS	<none>	Owns approximately 15 tables used to hold the web site usage analysis routines and recommendation text.