Plan for DB2 for iSeries

Plan for DB2 for iSeries

+
Search Tips | Advanced Search

You are here

Planning for DB2 for iSeries (Current task)
Create schemas and users for DB2 for iSeries
Transfer between databases manually
Verify database connections for iSeries

Overview

WebSphere Portal uses IBM Cloudscape during installation, and supports configuration of DB2 for an iSeries system. The IBM Cloudscape database is ideal for a test environment. For a production environment, you may move from the installed IBM Cloudscape database to DB2 for iSeries, but note that there is no option to transfer back to Cloudscape.
The database and user names referenced below are suggested values. During implementation, we can replace with the values.
Before configuring portal with DB2 for iSeries, verify the CCSID is valid.
The DB2 database enables us to access and manage server data through an application or a user interface. In addition to providing access to and protection for the data, IBM DB2 Universal Database for iSeries provides advanced functions such as referential integrity and parallel database processing.
DB2 is bundled with, and fully integrated on each iSeries system. DB2 provides features such as...

triggers
stored procedures
dynamic bitmapped indexing

These applications range from traditional host-based applications to client/server solutions to business intelligence applications.
As an interface to DB2, the DB2 Query Manager and SQL Development Kit for iSeries add an interactive query and report writing interface, and precompilers and tools to assist in writing SQL application programs in high-level programming languages.
The SQL implementation for OS/400 allows us to...

define
manipulate
query
control access

...to iSeries data. It works equally well with iSeries files and SQL tables.
WebSphere Portal can create the databases for you.
If you choose to use one database to hold all WebSphere Portal, Member Manager, and content publishing information, only one user profile is required. Additional user profiles are necessary only if using multiple iSeries machines or separate databases are required.
Portal creates databases using database names specified in...
/QIBM/UserData/portal_server_root/config/wpconfig_dbdomain.properties

To use a single shared database, replace each database and user variable with the name of the database and database user, respectively.
For scalability and performance reasons, it is possible to create up to six different databases.
The format for database names is *LOCAL for a local database, or a fully qualified server name such as myserver.mycompany.com for a remote database.
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.

Databases

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

Application Database Name DB2 user profile Function Space considerations
WebSphere Portal

release
community
customization

db2inst1 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. The 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 db2inst1
The database name should be the same as Member Manager 's DB2 User profile
db2inst1 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 The amount of this database depends on the number of Users and groups you are storing within the database repository. If the user repository is an LDAP this database is not used.
Document Manager Personalization jcrdb db2inst1 Used by Document Manager and Personalization components. Contains documents, personalization rules, personalization campaigns, and document library configuration information. The 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 db2inst1 Used by Feedback components. Contains the information that is logged by the web site for generating reports for analysis of site activity. The 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 db2inst1 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. The 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 DB2 database.

Application Database user profile Function
WebSphere Portal releaseusr
communityusr
customizationusr Core user.
Owns approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
Member Manager wmmdbusr Member Manager user.
Owns approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
Document Manager Personalization icmadmin DB2 Content Manager Runtime Edition user
Documents and personalization
Owns approximately 100 tables used for document management and personalization. Tables are dynamically created based on the resources that you define for content management.
Feedback feedback Feedback user.
Owns approximately 48 tables used for logging site and personalization usage.
Likeminds lmdbusr Likeminds user.
Owns the tables used to hold the web site usage analysis routines and recommendation text.

DB2 architecture

In a local database environment, WebSphere Portal and DB2 are installed on the same machine.
Figure 1. Local Database Environment

IP Address: 1.2.3.4
WebSphere Portal
Integrated DB2 Connect and server
Local Host: 127.0.0.1

In a remote database environment, WebSphere Portal and a DB2 Connect are installed on one machine (the local machine). The DB2 server is installed on a separate machine (the remote machine).
Figure 2. Remote Database Environment

Local Machine IP Address: 1.2.3.4 Remote Machine IP Address: 1.2.3.5
WebSphere Portal --
DB2
Connect: db2inst1
Connect to server on 1.2.3.5
Integrated DB2
Connect on iSeries server 1.2.3.5 DB2 server: db2inst1
Integrated DB2

Next steps

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

Creating schemas and users for DB2 for iSeries

.

Parent Topic
Planning for databases

Application	Database Name	DB2 user profile	Function	Space considerations
WebSphere Portal	release community customization	db2inst1	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.	The 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	db2inst1 The database name should be the same as Member Manager 's DB2 User profile	db2inst1	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	The amount of this database depends on the number of Users and groups you are storing within the database repository. If the user repository is an LDAP this database is not used.
Document Manager Personalization	jcrdb	db2inst1	Used by Document Manager and Personalization components. Contains documents, personalization rules, personalization campaigns, and document library configuration information.	The 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	db2inst1	Used by Feedback components. Contains the information that is logged by the web site for generating reports for analysis of site activity.	The 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	db2inst1	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.	The amount of database space that is required depends on the amount of traffic to the site.

Application	Database user profile	Function
WebSphere Portal	releaseusr communityusr customizationusr	Core user. Owns approximately 76 tables. Owns WebSphere Portal core objects, which includes tables that store the user customizations made to Pages.
Member Manager	wmmdbusr	Member Manager user. Owns approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal users.
Document Manager Personalization	icmadmin	DB2 Content Manager Runtime Edition user Documents and personalization Owns approximately 100 tables used for document management and personalization. Tables are dynamically created based on the resources that you define for content management.
Feedback	feedback	Feedback user. Owns approximately 48 tables used for logging site and personalization usage.
Likeminds	lmdbusr	Likeminds user. Owns the tables used to hold the web site usage analysis routines and recommendation text.

Local Machine IP Address: 1.2.3.4	Remote Machine IP Address: 1.2.3.5
WebSphere Portal	--
DB2 Connect: db2inst1 Connect to server on 1.2.3.5 Integrated DB2 Connect on iSeries server 1.2.3.5	DB2 server: db2inst1 Integrated DB2