Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Plan for DB2 for i5/OS
Overview
WebSphere Portal Express uses IBM DB2 for i5/OS during installation.
Tools to interface with DB2 for i5/OS...
- DB2 Query Manager
- SQL Development Kit for System i5
DB2 works works with both System i5 files and SQL tables.
Note that the CCSID default of 65535 is not supported.
DB2 is integrated with System i5 and does not require a separate installation.
Required databases, users, and user privileges are created by WebSphere Portal Express utilities.
If you choose to use one database to hold all information for...
- WebSphere Portal Express
- Member Manager
- Content publishing
...only one user profile is required. Additional user profiles are necessary only if using multiple System i5 machines or separate databases are required.
When WebSphere Portal Express creates databases, it uses the database names that are specified in...
portal_server_root/config/wpconfig_dbdomain.properties
It is possible to create up to six different databases by setting different values in the wpconfig_dbdomain.properties file.
The following sections provide an overview of the different databases and database user names you should consider in your planning. While configuring Portal to use one database is technically possible, IBM recommends using separate databases for scalability and performance tuning reasons. To use a single shared database, replace each database and user variable with the name of your database and database user, respectively.
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 enabled 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 Express |
| db2inst1 | Used for WebSphere Portal Express (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 Express 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 Express 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 your database repository. If your 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 your 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 your 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 Express architecture allows each of the following users to exist in the same DB2 database.
| Application | Database user profile | Function |
| WebSphere Portal Express |
| Core user. Will own approximately 76 tables. Owns WebSphere Portal Express core objects, which includes tables that store the user customizations made to Pages. |
| Member Manager | wmmdbusr | Member Manager user. Will own approximately 17 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal Express users. |
| Document Manager Personalization | icmadmin | DB2 Content Manager Runtime Edition user (documents and personalization). Will own 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. Will own approximately 48 tables used for logging site and personalization usage. |
| Likeminds | lmdbusr | Likeminds user. Will own the tables used to hold the web site usage analysis routines and recommendation text. |
DB2 architecture
In a local database environment, WebSphere Portal Express and DB2 are installed on the same machine.
Figure 1. Local Database Environment
| IP Address: 1.2.3.4 |
| WebSphere Portal Express |
| Integrated DB2 Connect and server |
| Local Host: 127.0.0.1 |
In a remote database environment, WebSphere Portal Express 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 Express | -- |
|
DB2
Connect: db2inst1
Connect to server on 1.2.3.5
Integrated DB2
Connect on System i5 server 1.2.3.5
|
DB2 server: db2inst1
Integrated DB2
|
Parent topic:
Configuring DB2 for i5/OS