Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Plan for SQL Server
This section provides information to give the database administrator an overall picture of WebSphere Portal Express database requirements.
Before you begin:
- You should have reviewed the Planning for databases topic to determine if you are going to transfer WebSphere Portal Express data to another supported database.
- Ensure the database you plan to use is supported by this version of WebSphere Portal Express. Refer to Supported hardware and software for supported database that are needed for WebSphere Portal Express.
Plan
The following areas provide an overview of the database and user names used in the documentation as well as some information about each database and user you should consider in your planning. The database names and users on this page are suggested values and provide consistency throughout the documentation. During your implementation, replace these values with values in your environment.
Notes:
- After the database software has been installed, create the required databases and users and grant the proper privileges to those users.
- If WebSphere Portal Express Version 6.0 and an earlier version of WebSphere Portal Express coexist, the database user IDs for WebSphere Portal Express Version 6.0 must be different than earlier versions to avoid conflicts during installation.
If the two versions of WebSphere Portal Express coexist on different databases, using the same user ID will not cause conflict.
- The Feedback function is not configured by default. It must first be turned on by following the steps in Enable logging, otherwise the Feedback tables will not be created in the new database.
- DB2 Content Manager Runtime Edition is a data repository that runs on SQL Server to store data for applications such as Personalization, Document Manager, and Web Content Management.
The following sections provide an overview of the different databases and database user names you should consider in your planning. While configuring WebSphere Portal Express to use one database is technically possible, we strongly recommend 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; schema names must be different when the database is shared.
Databases
The following table demonstrates the information each application will store in the databases.
| Application | Database Name | Function | Space considerations |
|---|---|---|---|
| WebSphere Portal Express |
| 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 | wmmdb | 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,Web Content Management | jcrdb | Used by Document Manager, Personalization, and Web Content Management 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 , the number and size of Personalization rules and campaigns, and the number and size of items and elements created in Web Content Management. |
| Feedback | fdbkdb | 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 | 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 database.
All tablespaces will be approximately 2.8 GB by default. The size will increase with the use of the DB2 Content Manager Runtime Edition function.
| Application | Database user placeholder | Recommended name | Function |
| WebSphere Portal Express |
| <none> | Core user. Will own approximately 130 tables for each domain. Owns WebSphere Portal Express core objects, which includes tables that store the user customizations made to Pages. |
| DB2 Content Manager Runtime Edition | icmadmin | <none> | DB2 Content Manager Runtime Edition user. Will own at least 1130 tables; the number could be higher depending on usage. |
| Member Manager | wmmdbusr | <none> | Member Manager user. Will own approximately 35 tables. Owns the Member Manager objects, which includes the tables that store login information about WebSphere Portal Express users. |
| Feedback | feedback | <none> | Feedback user. Will own approximately 50 tables used for logging site and personalization usage. |
| Likeminds | lmdbusr | <none> | LikeMinds user. Will own approximately 15 tables used to hold the web site usage analysis routines and recommendation text. |
Next steps
You have completed this step. Continue to the next step.
Parent topic:
Configuring SQL Server