Skip to main content

 –

For Pega Platform version 8.3 and earlier: Migrating rules and objects to the new rules schema

Suggest edit Updated on September 29, 2021

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 migrateSystem.properties file in the scripts directory of your distribution image:
    Pega-image\scripts\migrateSystem.properties
  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.jdbc.password=password
    pega.source.rules.schema=existing rules schema name
    pega.source.data.schema=existing data schema name
  3. Configure the target properties. Leave the target data schema name blank:
    pega.target.jdbc.driver.jar=full path/DRIVER.JAR
    pega.target.jdbc.driver.class=database driver class
    pega.target.database.type=database vendor type
    pega.target.jdbc.url=database URL
    pega.target.jdbc.username=Deployment user name
    pega.target.jdbc.password=password
    pega.target.rules.schema=new rules schema
    Note: If pega.target.data.schema is blank, the rules schema is used by default.
  4. Configure the bulkmover directory:
    pega.bulkmover.directory=full path to output directory
  5. Configure a temporary directory:
    pega.migrate.temp.directory=full path to temporary directory
  6. Configure the operations to be performed by the utility as shown below:
    pega.move.admin.table=true
    pega.clone.generate.xml=true
    pega.clone.create.ddl=true
    pega.clone.apply.ddl=true
    pega.bulkmover.unload.db=true
    pega.bulkmover.load.db=true
    pega.rules.objects.generate=false
    pega.rule.objects.apply=false
  7. Save the properties file.
  8. Open a command prompt, and navigate to the scripts directory.
  9. Type migrate.bat or ./migrate.sh to run the script.
Result:

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

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us