Skip to main content

Migrating to the new rules schema

Suggest edit
Updated on April 12, 2022

Use the migrate script to migrate the rules tables and other required database objects from the existing rules schema to the new rules schema. To minimize the time required, run the migration scripts from the same data center as the database server.

Note: Pega strongly recommends that you use the Pega-provided migration script. The use of vendor tools to manage this step is not recommended, since there are additional manual steps required to migrate the schema, not documented here, if you do not use the migrate script.
  1. Use a text editor to edit the file in the scripts directory of your distribution image:
  2. Configure the source properties.
    # Connection Information
    pega.source.jdbc.driver.jar=full path/DRIVER.jar
    pega.source.jdbc.driver.class=database driver class
    pega.source.database.type=database vendor type
    pega.source.jdbc.url=URL of database
    pega.source.jdbc.username=Deployment user name
    pega.source.rules.schema=existing rules schema data schema
  3. Configure the target properties. path/DRIVER.JAR driver class vendor type URL user name rules schema data schema
  4. Configure the bulkmover directory. path to output directory
  5. Configure a temporary directory: path to temporary directory
  6. Configure the operations to be performed by the utility as shown below:
  7. Save the properties file.
  8. Open a command prompt, and navigate to the scripts directory.
  9. Type migrate.bat (for Windows) or ./ (for Linux) to run the script.

Pega Platform writes command-line output to a file in the Pega-image\scripts\logs directory.

  • Previous topic For High Availability systems: Preparing the cluster for patching
  • Next topic Patch methods for the migrated rules schema
Did you find this content helpful? YesNo

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us