Transfer data to DB2 from a non-default database

Modify the wkplc.properties, wkplc_dbdomain.properties, wkplc_dbtype.properties, and wkplc_sourceDb.properties files to work with database when transferring data to DB2from 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 you need to perform when configuring database. After completing the steps in this topic, refer to the topics following the Modifying database properties topic for configuration scenario.

• 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 OS, 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 you are using.

• Some values, shown here in italics, might need to be modified to specific environment.

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

1. Create backups:
   • WP_PROFILE/ConfigEngine/properties/wkplc.properties
   • WP_PROFILE/ConfigEngine/properties/wkplc_dbdomain.properties
   • WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

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

2. Edit wkplc_dbdomain.properties

   1. For dbdomain.DbType, type db2.

   2. dbdomain.DbName=domain_db_name DB2 database names cannot exceed eight (8) characters.

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

      • TCP-IP alias for the database.

   3. dbdomain.DbSchema=domain_schema_name

   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 database element of this value should match the value of DbName.

   6. dbdomain.DbUser = database configuration user.

   7. dbdomain.DbPassword = password for database configuration user.

   8. dbdomain.DbConfigRoleName = 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.

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

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

   12. Optional. For dbdomain.DBA.DbUser, type the database administrator user ID for privileged access operations during database creation. If not required, you can accept the default value or leave blank.

   13. Optional. For dbdomain.DBA.DbPassword, database administrator password for privileged access operations during database creation. If not required, you can accept the default value or leave blank.

   14. For dbdomain.XDbName, type the database loop back alias that needs to be set to use the create-database task.
       Required only for local databases using a JDBC Type 2 driver.

   15. For dbdomain.DbNode, type the value for the database node name.
       Set this value if you want 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 you are currently configured to use. The value for source.domain.DbType is Derby by default.

   2. For source.domain.DbName, type the name of the database domain you 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, type the name of the datasource that is currently used in IBM WebSphere Application Server configuration.

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

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

   7. For source.domain.DbPassword, type 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, 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.

7. Save and close the file.

8. Update the WasPassword value in wkplc.properties. Password for the WAS security authentication used in environment.

9. Save and close the file.

Parent

Transfer data from a database other than the default database. January 4, 2012

  2012/01/04 v7. Edition 2: Second edition includes corrections a... 2011/12/15 documentation refresh

+

Search Tips   |   Advanced Search