Prepare DB2 on AIX for a stand-alone production server

You can install DB2 on the same server as WebSphere Portal, also referred to as local, or on a different server, referred to as remote. If you plan to use a local DB2 database, scripts are provided to simplify the database creation and transfer. More information about the local database is provide in the single server installation instructions. For a remote database complete the transfer manually.

  1. Installing DB2

    View information on installing DB2 for use with WebSphere Portal.

  2. Create users

    View the steps to set up users for DB2 to work with WebSphere Portal.

  3. Creating remote databases

    A remote database resides on a different system than WebSphere Portal. When you use a remote server, manually create the databases that are required by WebSphere Portal.

  4. Optional: 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.

  5. 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.

  6. 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.

  7. Set up DB2

    View information on how to manually transfer 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.

  8. 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.

  9. Changing driver types

    WebSphere Portal requires either JDBC Type 2 or Type 4 drivers. View the steps to switch from one driver type to the other.


Parent topic:

Configure databases