Portal, V6.1

---

 

Modify database properties

This section provides information on 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 datbases, create users, or transfer data.

Prerequisites

Installing DB2

Create users

Creating remote databases

Working with properties files:

• The WebSphere Portal database can be used to hold information for applications such as Feedback and LikeMinds. Use similar naming conventions for property values such as release.DbName, jcr.DbName, feedback.DbName, and likeminds.DbName. For example:

  • release.DbName=release

  • jcr.DbName=jcrdb

  • feedback.DbName=fdbkdb

  • likeminds.DbName=lmddb

• If you are using a remote database, enter the values for the remote server.

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

• There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties.

• The recommended value listed for each property represents the specific information that is required to configure WebSphere Portal to your target database.

• Depending on which database domain has to be configured, replace dbdomain with:

  • release

  • customization

  • community

  • jcr

  • feedback

  • likeminds

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

  • dbdomain.DbType

  • dbdomain.DbName

  • dbdomain.DbUrl

  • dbdomain.DbSchema

  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. Locate the following files and create a backup copy of each before changing any values:

   • WP_PROFILE/ConfigEngine/properties/wkplc.properties

   • WP_PROFILE/ConfigEngine/properties/wkplc_comp.properties

   • WP_PROFILE/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 properties file wkplc_comp.properties and modify the values to correspond to your environment.

   1. For dbdomain.DbType, type db2.

   2. For dbdomain.DbName, type the name of the WebSphere Portal domain database and schema. Notes:

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

      • This value is the TCP-IP alias for the database.

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

      Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply for some database management systems.

   4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal uses to communicate with its databases.

   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. For dbdomain.XDbName, type the database loop back alias that needs to be set if you plan to use the create-database task.

      Required only for local databases using a JDBC Type 2 driver.

   9. For dbdomain.DbNode, type the value for the node database. Set this value if you want to call create-database.

      Required only for local databases.

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

Configure WebSphere Portal to use DB2

 

Previous topic:

Assigning custom table spaces

Next topic:

Configure WebSphere Portal to use DB2

---