Windows stand-alone: Modify properties for IBM DB2 for i

Modify wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties before running tasks to create databases, create users, or transfer data.

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

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

      EDTF 'WP_PROFILE/ConfigEngine/properties/property filename.properties'

      where property filename is wkplc_dbdomain, wkplc, or wkplc_dbtype. You must have a user profile on the IBM i server and must have at least *USE special authority to edit the properties file.

      Instead of performing the following steps, you can use the configuration wizard, which is a graphical user interface, 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. Edit wkplc_dbdomain.properties

    1. dbdomain.DbType=db2_iseries

    2. dbdomain.DbName=domain_db_name

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

    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 connection property metadata source=1 must be specified for databases running on systems older than IBM i V7R1.

      • 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"

      • 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"

      • WebSphere Portal is installed on a UNIX platform, and you 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.

        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.

  4. Save and close the file.

  5. Update the following properties in wkplc_dbtype.properties.

      You must download the jt400.jar file prior to database transfer.

      1. db2_iseries.DbDriver = name of the JDBC driver class

      2. db2_iseries.DbLibrary = path to JDBC .zip or .jar file

      3. db2_iseries.JdbcProviderName = JDBC provider

      4. db2_iseries.DbDriverType = driver type for the database

  6. Save and close the file.

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

  8. Save and close the file.


Parent

Prepare IBM DB2 for i


Next topic

Create user profiles for IBM DB2 for i

 


+

Search Tips   |   Advanced Search