+

Search Tips   |   Advanced Search

Transfer data to IBM DB2 for i 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.

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:

  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. Edit properties files and enter values appropriate for your environment. We can modify each properties file locally on the System i5 system by typing the following on an OS/400 command line in a 5250 session:

      EDTF 'wp_profile_root/ConfigEngifilename.properties'

    ...where filename is wkplc_dbdomain, wkplc, or wkplc_dbtype.

    This step only applies when WebSphere Portal is installed on IBM i, and we are transferring to IBM DB2 for i.

    You must have a user profile on the IBM i server and must have at least *USE special authority to edit the properties file.

    The steps for transferring data to another supported database section provide instructions for manually transferring data. Instead of performing the following steps, we can use the configuration wizard, which is a GUI, to transfer data to another supported database.

    Properties must be changed before creating a database name and schema on a local or remote IBM i server.

  3. Set properties in wkplc_dbdomain.properties

    1. dbdomain.DbType=db2_iseries

    2. dbdomain.DbName=domain_db_name

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

    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.

      For databases running on systems older than IBM i V7R1, set metadata source=1...

      • When WebSphere Portal is installed on IBM i and you transferring data remotely or locally to IBM DB2 for i:

          dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1"

      • When WebSphere Portal is installed on Windows and you transferring data remotely to IBM DB2 for i:

          dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1"

      • When WebSphere Portal is installed on a UNIX platform, and we are transferring data to IBM DB2 for i:

          dbdomain.DbUrl="jdbc:as400:daisy.mycorp.com/WPDBREL;metadata source=1;prompt=false"

        If the X11 DISPLAY is set and active, do not add the ;prompt=false to the URL.

    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.

  4. Save and close the file.

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

  6. Save and close the file.

  7. Update the following properties in wkplc_dbtype.properties.

    You must download the jt400.jar file prior to database transfer. Refer to wkplc_dbtype.properties for more information on downloading the jt400.jar file.

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

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

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

    4. For db2_iseries.DbDriverType, type the number representing the driver type for the database.

  8. Save and close the file.

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

  10. Save and close the file.


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