Transfer data to DB2 from a non-default database

Learn how to modify the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_sourceDb.properties files to work with the database when transferring data to DB2 from a database other than the default 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.

This topic replaces the Modifying database properties topic in the sequence of tasks perform when configuring the database. After completing the steps in this topic, refer to the topics following the Modifying database properties topic for your configuration scenario.

Work with properties files:

• Property files are read by ConfigEngine when tasks are executed. They are not read during Portal appserver startup.

• Multiple databases can be used to hold information for applications such as Feedback and LikeMinds.

  For example:

  • release.DbName=reldb
  • jcr.DbName=jcrdb
  • feedback.DbName=fdbkdb
  • likeminds.DbName=lmdb
  • community.DbName=commdb
  • customization.DbName=custdb

• If we 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.

• Property files provide default values. These values are not correct for all databases. Enter values in accordance with the database management system that we are using.

• The recommended value listed for each property represents the specific information required to configure WebSphere Portal to the 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 we 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.

1. Make backup copies of the following files:

   • WP_PROFILE/ConfigEngine/properties/wkplc.properties

   • WP_PROFILE/ConfigEngine/properties/wkplc_dbdomain.properties

   • WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

   • If we are transferring from a database other than Derby:

     WP_PROFILE/ConfigEngine/properties/wkplc_sourceDb.properties

   Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Set the appropriate values for each instance of each property. In wkplc_dbdomain.properties, most properties are repeated for each domain.

2. Set properties in wkplc_dbdomain.properties

   1. dbdomain.DbType=db2

   2. dbdomain.DbName=domain_db_name

      DB2 database names cannot exceed eight (8) characters.

      • This value is also the database element in dbdomain.DbUrl.
      • TCP-IP alias for the database.

   3. dbdomain.DbSchema=domain_schema_name

      Some database management systems have schema name restrictions.

   4. dbdomain.DataSourceName=data_source_name

      Do not use the following reserved words:

      • releaseDS
      • communityDS
      • customizationDS
      • jcrDS
      • lmdbDS
      • feedback

   5. dbdomain.DbUrl=JDBC_DB_URL

      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, set the user ID for the database configuration user.

   7. For dbdomain.DbPassword, set the password for the database configuration user.

   8. For dbdomain.DbConfigRoleName, set 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, set 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.

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

   11. For dbdomain.DbRuntimeRoleName, set 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.

   12. Optional: For dbdomain.DBA.DbUser.

       DB administrator user ID for privileged access operations during database creation and setup. Required.if you run the create-database and setup-database ConfigEngine tasks . If you do not need this parameter, we can either accept the default value or leave blank.

   13. Optional: For dbdomain.DBA.DbPassword, set the database administrator password for privileged access operations during database creation. If you do not need this parameter, we can either accept the default value or leave blank.

   14. For dbdomain.XDbName, type the database loop back alias that needs to be set if you plan to use the create-database task.

   15. For dbdomain.DbNode, type the value for the database node name. Set this value to call create-database.

       Required only for local databases.

3. Save and close the file.

4. Edit the following properties in

   WP_PROFILE/ConfigEngine/properties/wkplc_sourceDb.properties when transferring the WebSphere Portaldatabases from any database other than the default database.

   1. For source.domain.DbType, type of the database we are currently configured to use. The value for source.domain.DbType is Derby by default.

   2. For source.domain.DbName, set the name of the database domain we are currently using.

   3. For source.domain.DbSchema, type current schema identifier for objects within the database for this domain.

   4. For source.domain.DataSourceName, set the name of the datasource that is currently used in the IBM WAS configuration.

   5. For source.domain.DbUrl, type the url currently used to access the database.

   6. For source.domain.DbUser, set the name of the user accessing this database.

   7. For source.domain.DbPassword, set the password of the source DbUser.

5. Save and close the file.

6. Update the following properties in wkplc_dbtype.properties.

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

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

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

7. Save and close the file.

8. Update the WasPassword value in wkplc.properties. This value is the password for the WAS security authentication used in the environment.

9. Save and close the file.

Parent: Transfer data from a database other than the default database.