Plan for DB2 on UNIX or Linux

Plan for DB2 on UNIX or Linux

Before starting review database considerations. Ensure the database to use is supported by this version of WebSphere Portal.
The database name cannot exceed eight characters and can only contain letters and numbers. When using the same database user ID, the value for the database name, database server node, or schema name must be unique.
Accessing a local DB2 database can cause shared memory problems. To correct these problems, treat the local database as a remote database on the local system.
WebSphere Portal supports DB2 JDBC Type 2 (CLI-based) and Type 4 (JCC) drivers. When the DB2 Universal JDBC driver (type 4 mode) is used, connect to the database directly. Do not connect to an alias database (gateway), instead specify the real database name in the JDBC connection URL (dbdomain.DbUrl) and in the database name property (dbdomain.DbName). When a JDBC type 2 connections is used, WebSphere Portal and DB2 Connect are installed on one system (the local system). The DB2 server is installed on a separate system (the remote system). For JDBC type 4 connections, no DB2 Connect installation is required on the system that runs WebSphere Portal. The DB2 Universal JDBC driver supplied with DB2 is copied to the portal system, and is used within the JVM of WebSphere Portal, connecting directly to the remote DB2 server.
The recommended architecture uses the default instance (db2inst1) created by the installation program.

Application Description DB name Space required
WebSphere Portal. 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
Web Content Manager 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 Recommendations 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.

Review the tables and types of objects 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 DB 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 LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.

Parent: Database considerations
Related:
Which distributed edition of DB2 Universal Database v8 is correct for you?
Which distributed edition of DB2 Universal Database Version 9 is correct for you?
Related:
System requirements

Application	Description	DB name	Space required
WebSphere Portal.	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 Web Content Manager	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	Recommendations 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	DB 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	LikeMinds user who owns approximately 15 tables used to hold the Web site usage analysis routines and recommendation text.