This section provides information to give the database administrator an overall picture of Lotus® Quickr™ database requirements.
See the following links if you need help determining which DB2® version to use.
Before you begin:
- DB2 is installed during Lotus Quickr installation. This section is only required if you want to change the configuration and transfer to another local DB2 database.
- You should have reviewed the Planning for databases topic to determine if you are going to transfer Lotus Quickr data to another supported database.
- Ensure the database you plan to use is supported by this version of Lotus Quickr. Refer to Supported hardware and software for supported databases that are needed for Lotus Quickr.
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.
- After the database software has been installed, you must create the required databases and users and grant the proper privileges to those users.
- The database name cannot exceed eight characters and can only contain letters and numbers.
- DB2 Content Manager Runtime Edition is a data repository that runs on DB2 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 Lotus Quickr 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.
The following table demonstrates the information each application will store in the databases.
Table 1. Databases
|Application||Database Name||Instance*||Function||Space considerations|
|Lotus Quickr ||
||db2inst1||Used for Lotus Quickr (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 Lotus Quickr users and objects, such as pages and portlets.|
|Document Manager, Personalization, Web Content Management||jcrdb||db2inst1||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 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||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.|
|Place Center||placecntr||db2inst1||Used for Place Center configuration tables and favorites tables.||The amount of database space that is required depends on the number of favorites, which usually correlates to the number of users.|
|Search Center||searchcntr||db2inst1||Used for Search Center configuration tables.||The space is fixed and quite small.|
|Quickr Admin||qkradmin||db2inst1||Used for Admin Console statistic data. Store daily system and place level statistic data, such as total number of places or documents.||The amount of database space that is required depends on number of places and number of days statistics task agent has run.|
- The Lotus Quickr architecture allows each of these databases to exist in one or many instances. However, the recommended architecture uses the default instance (shown above as db2inst1) that is created by the DB2 installation program.
The following table demonstrates the number of tables and types of objects owned by each user. The Lotus Quickr 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|
|Lotus Quickr ||
|<none>||Core user. Will own approximately 130 tables for each domain. Owns Lotus Quickr 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.|
|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. |
|Place Center||placecntr||<none>||Place Center user. Will own 4 tables used for storing crawler collections, configurations and favorites.|
|Search Center||searchcntr||<none>||Search Center user. Will own 3 tables; 1 used - search rcss configuration.|
|Quickr Admin||qkradmin||<none>||Admin Console user. Will own 5 tables used to hold statistical data for system level and each team place.|
In a local database environment, Lotus Quickr and DB2 are installed on the same machine.
For JDBC type 4 connections no DB2 Connect installation is required on the machine that runs Lotus Quickr. The DB2 Universal JDBC driver that is supplied with DB2 is copied to this machine. It is used within the Java Virtual Machine of Lotus Quickr and connects directly to the remote DB2 server.
You have completed this step. Continue to the next step.
Parent topic: Database considerations: qp85