Configure a local database

The database can be installed on the same server as WebSphere Portal. Having the database on the same server has advantages and disadvantages. This is a common scenario for a proof-of-concept installation where you want to test out the capabilities and features. Another scenario that may use this configuration is a stand-alone server installation. Installing the database on another server has the advantage of distributing the processing and workload.

• Installing DB2 on the same server as WebSphere Portal

  View information on installing DB2 for use with WebSphere Portal.

• Configure JCR collation support

  View the steps to set up JCR collation to work with your IBM DB2 Universal Database™ Enterprise Server Edition database. JCR collation is recommended when the language locales of your users do not natively collate correctly in the DB2 database and when language locale correct ordering is important.

• Modifying database properties

  Learn how to modify the wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties files to work with your database. Modify these property files before running tasks to create databases, create users, or transfer data. Create a backup copy of each properties file before modifying it.

• Set up databases

  This section provides information on using ConfigEngine tasks to create databases and users.

• Assigning custom table spaces

  The repository of WebSphere Portal consists of many tables and indices that are created in default table spaces. When using an existing set of table spaces for the objects of the repository, specify this when executing the database transfer to the target database system.

• Configure WebSphere Portal to use DB2

  View information on manually transferring data to the DB2 database you have installed and set up. Follow these steps to transfer WebSphere Portal, and Java Content Repository databases to DB2. As an alternative to the manual database transfer procedure described here, you can use the configuration wizard to complete the database transfer task.

• Configure DB2 for large file handling in Web Content Management

  For Web Content Management, update the database configuration to support large files. Do this by setting the fullyMaterializeLobData property in the administrative console.

• Verify databases

  After you configure WebSphere Portal to work with your database, test the database connection to ensure that it operates correctly. Then verify that all database transactions work properly within the WebSphere Portal environment.

  For example, all portal pages should display without HTTP 404 errors, and there should be no database layer-related exceptions in the SystemOut.log and SystemErr.log files.

Parent topic:

Set up a database

---