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

Learn how to modify the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files to work with the database. Modify these property files before running tasks to create databases, create users, or transfer data.

Work with properties files:

• The WebSphere Portal database can be used to hold information for applications such as Personalization (Feedback) and LikeMinds. To prepare the database to hold such application information, use similar naming conventions for property values such as release.DbName. Here are some examples:
  • release.DbName=hostname/WP80REL
  • community.DbName=hostname/WP80COM
  • customization.DbName=hostname/WP80CUS
  • jcr.DbName=hostname/WP80JCR
  • feedback.DbName=hostname/WP80FBK
  • likeminds.DbName=hostname/WP80LKM

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

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

• There might be additional database properties other than those listed here. Only change the properties within this task and skip all other properties.

• Password considerations: For security reasons, you should not store passwords in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files. IBM recommends that we edit each of the properties files prior to running a configuration task, inserting the passwords needed for that task. Then, after the task has run, you should delete all passwords from each file.

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

• When creating a schema, use the following schema naming conventions on the IBM i system:

  The default schema names may be used with the product.

  • Length cannot exceed 10 characters

  • All alphanumerical characters are allowed ( "A" through "Z" and "1" through "0")

  • The following characters are invalid:

    • spaces

    • null values

    • asterisk (*)

    • quotation marks (")

    • colon (:)

    • greater than symbol (>)

    • less than symbol (<)

    • vertical bar (|)
    • plus sign (+)

    • semicolon (;)

    • single quotation mark (')

    • question mark (?)

    • Make sure you know what valid schema names are and do not use a schema name which already exists on the local or remote system. Follow the documentation of the target database management system in order to define a valid schema name as restrictions apply. Note that the Create WebSphere Portal wizard will automatically check schema names for you.

    • For more information on database and schema naming conventions, refer to the DB2 Universal Database for System i5 content in the System i5 information center.

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/ConfigEngiproperties/filename.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, type the database 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. 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.

6. Save and close the file.

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

8. Save and close the file.

Parent: Solaris stand-alone: Prepare IBM DB2 for i
Next: Solaris stand-alone: Create groups and assign users for IBM DB2 for i