IBM DB2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name

If you plan to import an application with schema changes and a separate DB-Admin-DB-Name and you are using IBM DB2 for z/OS, follow these instructions to configure the import parameters before you import the application, or the import fails.

If you are not using IBM DB2 for z/OS, or if your application does not have a separate DB-Admin-DB-Name, skip this procedure. For more information about your application, contact your database administrator.

When you import an application, Pega Platform creates a DDL file of schema changes. In IBM DB2 for z/OS only, the DDL file is populated by the DB2SiteDependent.properties file that you configured when you deployed Pega Platform. The DB2SiteDependent.properties file includes settings for the DB-Admin-DB-Name that is associated with the database schema. If your application has a separate DB-Admin-DB-Name, you must provide similar property values for your application and then run the prpcUtils tool to import the properties. For more information about the DB2SiteDependent.properties file, see your installation guide.

To provide the properties follow these steps:

1. Create your application properties file:

   1. Copy the Pega-image/scripts/config/db2zos/DB2SiteDependent.properties file for your application properties. As a best practice, include the application name in your application properties file name.

   2. Have your database administrator edit your application properties file for this application.

   3. Save and close your application properties file.

2. Use the prpcUtils tool to import your application properties:

   1. Open the prpcUtils.properties file.

   2. At a minimum, update the following values:

      pega.zos.properties – The path and file name of the file that contains the IBM DB2 for z/OS site-specific propertiespega.zos.database.names – A comma-delimited list of all database names

   3. Save and close the prpcUtils.properties file.

   4. Run the prpcUtils.bat or prpcUtils.sh script with the importZosConfig option, for example:

      prpcUtils.bat importZosConfig

3. Use one of the following methods to import the application:

   • Importing rules and data by using a direct connection to the database
   • Importing rules and data by submitting a request to an active instance
   • Importing a file by using the Import wizard
   • Migrating products from the user interface

Open topic with navigation