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


Prerequisites

Installing DB2

Create users

Creating remote databases

The wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties are published in the WebSphere Portal wiki.

The wiki articles include examples, valid values, and descriptions to help you determine what value to provide for a given property.

The documentation team and other IBM teams will update the properties to provide more examples and clarity as needed.

For the most up-to-date information about properties, such as examples, valid values, and more, see the following wiki articles:

Working with properties files:

  1. Locate the following files and create a backup copy of each before changing any values:

    • profile_root/ConfigEngine/properties/wkplc.properties

    • profile_root/ConfigEngine/properties/wkplc_comp.properties

    • profile_root/ConfigEngine/properties/wkplc_dbtype.properties

    Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out the steps below for reference before modifying the properties files. Make sure to enter the appropriate values for each instance of each property. In wkplc_comp.properties, most properties are repeated for each domain.

  2. Edit the properties file wkplc_comp.properties and modify the values to correspond to your environment.

    The wkplc_comp.properties file by default has the properties populated for the Apache Derby database.

    The source.dbdomain.properties represent the properties for the source database. These values should not be modified unless you are transferring from a supported database other than Apache Derby.

    1. For dbdomain.DbType, type db2.

    2. For dbdomain.DbName, type the name of the WebSphere Portal domain database.

      This value is also the database element in the dbdomain.DbUrl property.

    3. For dbdomain.DbSchema, type the schema name of the database domain.

      Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that understand.

    4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal uses to communicate with its databases. Do not use the following reserved words:

      • releaseDS

      • communityDS

      • customizationDS

      • jcrDS

      • lmdbDS

      • feedback

    5. For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal database with JDBC.

      The value must conform to the JDBC URL syntax specified by the database.

      The database element of this value should match the value of DbName.

    6. For dbdomain.DbUser, type the user ID for the database administrator.

    7. For dbdomain.DbPassword, type the password for the database administrator.

    8. Optional: For dbdomain.DbRuntimeUser, type the user ID of the database user that should be used by WebSphere Portal to connect to the database at runtime.

    9. If dbdomain.DbRuntimeUser is specified, set dbdomain.DbRuntimePassword to be the password of the runtime database user.

  3. Save and close the file.

  4. Update the following properties in the file wkplc_dbtype.properties.

    1. For db2.DbDriver, type the name of the JDBC driver class.

    2. For db2.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class.

    3. For db2.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal uses to communicate with its databases.

  5. Save and close the file.

  6. Update the following property in the file wkplc.properties.

    1. For WasPassword, type the password for the WAS security authentication used in your environment.

  7. Save and close the file.


Parent topic:

Set up a remote DB2 database


Previous topic:

Assigning custom table spaces


Next topic:

Configure JCR collation support