Linux clustered server: Modify 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 the database. Modify these property files before running tasks to create databases, create users, or transfer data.

Prerequisites

Linux clustered server: Install DB2 for z/OS

Work with properties files:

• Property files are read by ConfigEngine when tasks are executed. They are not read during Portal appserver startup.

• Multiple databases can be used to hold information for applications such as Feedback and LikeMinds.

  For example:

  • release.DbName=reldb
  • jcr.DbName=jcrdb
  • feedback.DbName=fdbkdb
  • likeminds.DbName=lmdb
  • community.DbName=commdb
  • customization.DbName=custdb

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

• 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 we are using.

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

To successfully transfer data from the JCR domain, use the DDF location value for the value of jcr.DbName field when setting up IBM DB2 Universal Database™ for z/OS . We 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

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. Set properties in wkplc_dbdomain.properties

   1. dbdomain.DbType=db2zos.

   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. For dbdomain.DbNameOnZos, set the name of the WebSphere Portal database on DB2 for z/OS.

      • 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 is running on z/OS with DB2 for z/OS, set the value equal to the value of DbName.

   5. dbdomain.DataSourceName=data_source_name

      Do not use the following reserved words:

      • releaseDS
      • communityDS
      • customizationDS
      • jcrDS
      • lmdbDS
      • feedback

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

   7. For dbdomain.DbUser, set the user ID for the database configuration user.

   8. For dbdomain.DbPassword, set the password for the database configuration user.

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

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

   11. If dbdomain.DbRuntimeUser is specified, set dbdomain.DbRuntimePassword to be the password of the runtime database user.

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

   13. For dbdomain.DbTablespace, set the name of the DB2 for z/OS tablespace.

   14. For dbdomain.DbStorageGroup, set 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. T 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.

3. Save and close the file.

4. Update the following properties in wkplc_dbtype.properties.

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

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

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

   4. For db2_zos.DbDriverType, type the number of the driver type for the database.

5. Save and close the file.

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

7. Save and close the file.

Parent: Linux clustered server: Set up a remote DB2 for z/OS database
Previous: Linux clustered server: Install DB2 for z/OS
Next: Linux clustered server: Use JCL templates to set up DB2 for z/OS