By default, IBM® Lotus® Quickr™ for WebSphere Portal installs and uses IBM DB2 Universal Database™ Enterprise Server Edition. Installing with DB2® lets you quickly get Lotus Quickr installed and running in a production-level environment. Before using the product extensively, learn the benefits and limitations of using DB2.
When you choose to transfer data to another supported database, perform the database transfer before you use the portal extensively. Large amounts of data in the databases can cause the database transfer to fail if your Java heap size is not large enough. Because information is added to the databases as you use the portal, perform the database transfer as soon as it is practical to avoid problems in a production environment.
If you are transferring from a database other than the default database, you will need to edit the wpconfig_sourceDb.properties
file to update it with the source database information. This file is a copy of the wpconfig_dbdomain.properties
file that is created during installation, so the default values are for DB2.
You can install the database server on the same system as Lotus Quickr, or you can install the database server on a different, also referred to as a remote, system.
Using a remote database can have performance benefits. When you are deploying in a large scale environment, you can dedicate a server specifically to your database. As more users are accessing the portal, the portal application becomes database intensive. Database activity can take up CPU utilization and disk I/O time. Separating the database from the server that the portal is running on increases capacity. Local
Using a local database can make administering your environment easier.
Parent topic: Database considerations: qp85