Modify database properties

This section provides information on how to modify the,, and files to work with your database. Modify these property files before running tasks to create datbases, create users, or transfer data.


Installing DB2 for z/OS

Creating users

Creating remote databases

Creating the Java Content Repository database

The,, and are published in the WebSphere Portal wiki.

The wiki articles include examples, valid values, and descriptions to help you determine what value to provide for a given property.

The documentation team and other IBM teams will update the properties to provide more examples and clarity as needed.

For the most up-to-date information about properties, such as examples, valid values, and more, see the following wiki articles:

Working with properties files:

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.

You can locate the name of the DDF location value in the IBM DB2 Universal Database for z/OS sdsnsamp dataset, member DSNTIJUZ, or by running the following DB2 command:

db2 subsystem prefix display ddf

  1. Locate the following files and create a backup copy of each before changing any values:

    • profile_root/ConfigEngine/properties/

    • profile_root/ConfigEngine/properties/

    • profile_root/ConfigEngine/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, most properties are repeated for each domain.

  2. Edit the properties file 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 domain database.

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

    3. For dbdomain.DbSchema, type the schema name of the database domain.

      Review your target database management system documentation to define a valid schema name. Some database management systems have schema name restrictions that understand.

    4. For dbdomain.DbNameOnZos, type 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. For dbdomain.DataSourceName, type the name of the data source that WebSphere Portal 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 database with JDBC.

      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, type the user ID for the database administrator.

    8. For dbdomain.DbPassword, type the password for the database administrator.

    9. For dbdomain.DbTablespace, type the name of the DB2 for z/OS tablespace.

    10. For dbdomain.DbStorageGroup, type the name of the storage group for the database.

    11. For dbdomain.DbVolumes, type the volumes for the database.

    12. For dbdomain.DbVcat, type the VCAT for the database.

    13. For dbdomain.Db4KBufferPoolName, type the 4K bufferpool name for the database.

    14. For dbdomain.Db32KBufferPoolName, type the 32K bufferpool name for the database.

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

    16. 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 the file

    1. For db2_zos.DbDriver, type the name of the class that SqlProcessor uses to import SQL files.

    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 uses to communicate with its databases.

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

    5. For db2_zos.DbLocationName, type the DB2 location name. This value is set in the installation job DSNTIJUZ.

  5. Save and close the file.

  6. Update the following property in the file

    1. For WasPassword, type the password for the WAS security authentication used in your environment.

  7. Save and close the file.

Parent topic:

Prepare DB2 for z/OS for a stand-alone production server

Previous topic:

Assigning custom table spaces

Next topic:

Configure WebSphere Portal to use DB2 for z/OS