Working with Properties Files

You must modify the appropriate properties files before transferring your data from the default database to the Oracle or Oracle RAC database.

Multiple databases can be used to hold information for applications such as Feedback and LikeMinds. For example, you could use the following property values:
- release.DbName=reldb
- jcr.DbName=jcrdb
- feedback.DbName=fdbkdb
- likeminds.DbName=lmdb
- community.DbName=commdb
- customization.DbName=custdb
If you are using a remote database, enter the values for the remote server.
Regardless of the operating system, use a forward slash (/) instead of a backslash (\) in the property files for file system paths.
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.DbName
- dbdomain.DbUrl
- dbdomain.DbSchema
If you use the same values for all three properties across the release, customization, community, and JCR domains, the database-transfer task fails due to 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.
When doing a single database, single user, and multi schema database transfer, there can be only one user for each domain (release, community, customization, JCR, Feedback, and LikeMinds), and the schema for each database must be different. The user must be a superuser or DBA and must have authority over all other schemas for the transfer to work.

Locate the following files and create a backup copy of each before changing any values:
- wp_profile_root/ConfigEngine/properties/wkplc.properties
- wp_profile_root/ConfigEngine/properties/wkplc_dbdomain.properties
- wp_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_dbdomain.properties, most properties are repeated for each domain.
Use a text editor to open the properties file wkplc_dbdomain.properties and modify the values to correspond to your environment.
1. For dbdomain.DbType, type oracle.
2. For dbdomain.DbName, type the name of the WebSphere Portal domain database.
  Note: This value is also the database element in the dbdomain.DbUrl property.
3. For dbdomain.DbSchema, type the schema name of the database domain.
  Note: Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that you need to 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.
  Note: The database element of this value should match the value of DbName.
6. For dbdomain.DbUser, type the user ID for the database configuration user.
7. For dbdomain.DbPassword, type the password for the database configuration user.
8. For dbdomain.DbConfigRoleName, type the name of the group for database configuration users. Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbUser must be assigned to this group.
9. 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. If no value is specified for this setting, the database configuration user will be used to connect to the databases at runtime.
  If dbdomain.DbRuntimeUser is specified, you must set dbdomain.DbRuntimePassword to be the password of the runtime database user.
10. For dbdomain.DbRuntimeRoleName, type the name of the group for database runtime users. Database rights are granted to this group instead of individuals. The user specified for dbdomain.DbRuntimeUser must be assigned to this group.
11. Optional: For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank.
12. Optional: For dbdomain.DBA.DbPassword, type the database administrator password for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank.
13. For dbdomain.DbHome, type the root location for the database.
  Note: This value is used to specify the location to create the tablespaces.
Save and close the file.
Update the following properties in the file wkplc_dbtype.properties.
- For oracle.DbDriver, type the name of the Oracle JDBC driver class.
- For oracle.DbLibrary, type the directory and name of the .jar file that contains the JDBC driver class.
- For oracle.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal uses to communicate with its databases.
Save and close the file.
Update the WasPassword value in the wkplc.properties file. This value is the password for the WebSphere Application Server security authentication used in your environment.
Save and close the file.