Linux idle standby: Modifying DB2 for z/OS database properties

This section provides information on 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.

Prerequisites: Linux idle standby: Installing DB2 for z/OS

Working with properties files:

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 operating system, 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 your specific environment.
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.

Note: To successfully transfer data from the JCR domain, you must use the DDF location value for the value of jcr.DbName field when setting up IBM® DB2 Universal Database™ for z/OS®. You can locate the name of the DDF location value in the IBM DB2 Universal Database for z/OS sdsnsamp data set, member DSNTIJUZ, or by running the following DB2® command:

db2 subsystem prefix display ddf

Locate the following files and create a back up copy of each before changing any values:
- wp_profile_root/ConfigEngine/properties/wkplc.properties
- wp_profile_root/ConfigEngine/properties/wkplc_dbdomain.properties
- wp_profile_root/ConfigEngine/properties/wkplc_dbtype.properties
- wp_profile_root/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 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.
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_zos.
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.DbNameOnZos, type the name of the WebSphere Portal Express database on DB2 for z/OS.
  Note:
  - If running DB2 for z/OS as a remote database, set the value to the name of the remote database for the domain.
  - If WebSphere Portal Express is running on z/OS with DB2 for z/OS, set the value equal to the value of DbName.
5. 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
6. 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.
  Note: The database element of this value should match the value of DbName.
7. For dbdomain.DbUser, type the user ID for the database configuration user.
8. For dbdomain.DbPassword, type the password for the database configuration user.
9. 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.
10. 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.
11. If dbdomain.DbRuntimeUser is specified, you must set dbdomain.DbRuntimePassword to be the password of the runtime database user.
12. 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.
13. For dbdomain.DbTablespace, type the name of the DB2 for z/OS tablespace.
14. For dbdomain.DbStorageGroup, type the name of the storage group for the database.
15. For dbdomain.DbVolumes, type the volumes for the database.
16. For dbdomain.DbVcat, type the VCAT for the database.
17. For dbdomain.Db4KBufferPoolName, type the 4K bufferpool name for the database.
18. For dbdomain.Db32KBufferPoolName, type the 32K bufferpool name for the database.
19. For dbdomain.DbIndex4KBufferPoolName, type the 4K bufferpool name for the database. If you choose to use the default bufferpool value BP3, verify that this bufferpool is active.
20. For dbdomain.TablespaceTrackMod , set the value to determine TRACKMOD attribute of all tablespaces to use the specified value. Refer to the DB2 for z/OS documentation before changing this value.
Save and close the file.
Update the following properties in the file wkplc_dbtype.properties.
1. For db2_zos.DbDriver, type the name of the JDBC driver class.
2. For db2_zos.DbLibrary, type the directory and name of the .zip or .jar file that contains the JDBC driver class.
3. For db2_zos.JdbcProviderName, type the name of the JDBC provider that WebSphere Portal Express uses to communicate with its databases.
4. For db2_zos.DbDriverType, type the number of the driver type for the database.
Save and close the file.
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.
Save and close the file.
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.
Save and close the file.