Database
IBM WebSphere Portal includes an Apache Derby database configured and ready for immediate use. As a result, we have a running portal that is ready for exploration or portlet and theme development. But for a production environment or any environment for WCM, use one of the other supported database management systems.
Derby is a built-in Java database that provides a small footprint, is self-tuning, and is ideal for solutions where the database must be hidden. Derby works in a non-clustered environment with a few users, such as a portlet or theme development environments. Derby does not support clustered environments, enabling security in a database-only mode, or vertical cloned environments in which multiple application servers are configured on a single server. The Derby database installed by default is not intended for use in a production environment.
Use one of the other supported databases in a production environment or when developing presentation templates or authoring web content. The Derby database can be sufficient for non-production installations of WebSphere Portal, the performance of Derby with WCM is poor. A typical cause of performance issues is transaction timeouts. Although we can increase these timeouts, the resulting performance is prohibitively slow. Use one of the other supported database management systems. They are better able to handle large amounts of data and can be tuned for performance.
Database transfer
Transfer data to another supported database before using 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. Do not postpone transferring data to another database management system. Waiting to transfer the database can cause errors to occur during the transfer process, such as not having adequate Java heap size.
Configuration Wizard
Use the wizard to either create scripts that you or the database administrator can use to create databases, create database user IDs, and configure database user ID privileges. The wizard collects information about the database management system, the database topology we want, the user IDs we require, and more. Then, it generated custom scripts and instructions.
See
- Database users
- Database topologies
- Portal database domains
- JDBC type 2 and type 4 drivers
- Shared database domains