Modify database properties



Search Tips   |   Advanced Search



Modify,, and before running tasks to create databases, create users, or transfer data.

Common naming naming conventions...

For a remote database, enter the values for the remote server.

Use a forward slash (/) instead of a backslash (\).

Only change the properties within this task and skip all other properties.

The values for at least one of the following properties must be unique for the release, customization, community, and jcr domains:

If you use the same values for all four properties across the release, customization, community, and JCR domains, the database-transfer task fails because of ambiguous database object names. If DbUser, DbUrl, and DbPassword are not the same across domains, the value for DataSourceName must differ from the DataSourceName of the other domains. In other words, this value must be unique for the database domain.


  1. Install DB2

  2. Create users

  3. Create remote databases

  4. Make backup copies of...

    • profile_root/ConfigEngine/properties/
    • profile_root/ConfigEngine/properties/
    • profile_root/ConfigEngine/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, most properties are repeated for each domain.

  5. Edit and modify the values to correspond to your environment.

    The file by default has the properties populated for the Apache Derby database. The 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.

    dbdomain.DbType db2
    dbdomain.DbName Name of the WebSphere Portal domain database.

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

    dbdomain.DbSchema Schema name of the database domain.
    dbdomain.DataSourceName Data source that WebSphere Portal uses to communicate with its databases.

    Do not use the following reserved words:

    • releaseDS
    • communityDS
    • customizationDS
    • jcrDS
    • lmdbDS
    • feedback
    dbdomain.DbUrl 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.

    dbdomain.DbUser User ID for the database administrator.
    dbdomain.DbPassword Password for the database administrator.
    dbdomain.DbRuntimeUser User ID of the database user that should be used by WebSphere Portal to connect to the database at runtime. Optional:

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

  6. Save and close the file.

  7. Set following properties in

    db2.DbDriver JDBC driver class.
    db2.DbLibrary Directory and name of the .zip or .jar file that contains the JDBC driver class.
    db2.JdbcProviderName JDBC provider that WebSphere Portal uses to communicate with its databases.

  8. Save and close the file.

  9. In, for WasPassword, type the password for the WAS security authentication used in your environment.

  10. Save and close the file.

Parent topic:

Configure WebSphere Portal to use DB2

Previous topic:

Assigning custom table spaces

Next topic:

Configure JCR collation support