Linux stand-alone: Modifying properties for IBM DB2 for i

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

Working with properties files:
  • The WebSphere® Portal Express® database can be used to hold information for applications such as Personalization (Feedback) and LikeMinds. To prepare the database to hold such application information, you should 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 you 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 you are using. Enter values in accordance with the database management system that you 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.
  • Some values, shown here in italics, might need to be modified to your specific environment.
  • Password considerations: For security reasons, you should not store passwords in the wkplc.properties, wkplc_dbdomain.properties, and wkplc_dbtype.properties files. It is recommended that you 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 Express to your 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.
  • When you create a schema, you must use the following schema naming conventions on the IBM® i system:
    Note: 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 (?)
      Notes:
      • 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 Express 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. Locate the following files and create a back up copy of each before changing any values:

    Default values are listed in these files. Unless otherwise noted, all values are of type alphanumeric text string. Print out this topic 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. Use a text editor to open the properties files and enter the values that are appropriate for your environment. You can also modify each properties file locally on your System i5 system by typing the following on an OS/400 command line in a 5250 session:
    Note: This step only applies when WebSphere Portal Express is installed on IBM i, and you are transferring to IBM DB2 for i. 
    EDTF 'wp_profile_root/ConfigEngine/properties/property filename.properties'

    where property filename is wkplc_dbdomain, wkplc, or wkplc_dbtype.

    Note: You must have a user profile on the IBM i server and must have at least *USE special authority to edit the properties file.
    Tip: The steps for transferring data to another supported database section provide instructions for manually transferring data. 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. Use a text editor to open the properties file wkplc_dbdomain.properties and modify the values to correspond to your environment.
    1. For dbdomain.DbType, type db2_iseries.
    2. For dbdomain.DbName, type the name of the WebSphere Portal Express domain database.
      Note: This value is also the database element in the dbdomain.DbUrl property.
    3. For dbdomain.DbSchema, type the schema name of the database domain.
      Note: Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that you need to understand.
    4. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal Express uses to communicate with its databases. Do not use the following reserved words:
      • releaseDS
      • communityDS
      • customizationDS
      • jcrDS
      • lmdbDS
      • feedback
    5. For dbdomain.DbUrl, type the database URL used to access the WebSphere Portal Express database with JDBC. The value must conform to the JDBC URL syntax specified by the database. The connection property metadata source=1 must be specified for databases running on systems older than IBM i V7R1. Refer to the following example when WebSphere Portal Express 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" Refer to the following example when WebSphere Portal Express 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" Refer to the following example when WebSphere Portal Express 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.
      Note: The database element of this value should match the value of DbName.
    6. For dbdomain.DbUser, type the user ID for the database configuration user.
    7. For dbdomain.DbPassword, type the password for the database configuration user.
    8. For dbdomain.DbConfigRoleName, type 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, type the user ID of the database user that should be used by WebSphere Portal Express 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, you must 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 and setup. This property is required if you run the create-database and setup-database ConfigEngine tasks referenced later in this section. If you do not need this parameter, you can either accept the default value or leave blank.
    13. Optional: For dbdomain.DBA.DbPassword, type the database administrator password for privileged access operations during database creation. If you do not need this parameter, you can either accept the default value or leave blank.
  4. Save and close the file.
  5. Update the following properties in the file wkplc_dbtype.properties.
    Note: 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, type the name of the JDBC driver class.
    2. For db2_iseries.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class.
    3. For db2_iseries.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal Express 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 the wkplc.properties file. This value is the password for the WebSphere Application Server security authentication used in your environment.
  8. Save and close the file.
  9. Use a text editor to open the wkplc_sourceDb.properties file and modify the source.domain.DbPassword parameter across all domains to correspond to your environment. This value is the password for the configuration user.
  10. Save and close the file.
Parent topic: Linux stand-aloneserver: Preparing IBM DB2 for i
Next topic: Linux stand-alone: Creating groups and assigning users for IBM DB2 for i