Migrating rules to a new schema

Rules can be migrated to a new schema in a highly available system, which is updated on the staging system and then copied to production. To migrate the rules to a new schema, do the following:

  1. Disable saving of rules:
    1. Click Configure > System > High Availability > HA Cluster Settings.
    2. Select Cluster Upgrading - Disable saving of rules.
  2. Migrate the existing rules into a new rules schema and mark the time.
  3. If you are updating the new rules schema for a framework or application, use the prpcUtils command line tool to set the import.oop.upgrade option to true.
    Setting this option to true allows the framework or application rules to be updated and saved by ignoring the Cluster Upgrading - Disable saving of rules flag set in step 1.
  4. Perform the update on the new rules schema.
  5. Copy the new rules to the production database.
  6. Configure the Pega Platform servers to use the new rules schema and perform rolling restarts on any additional production servers.
    • During the rolling restart, users are moved from Pega Platform servers using the old rules schema to Pega Platform servers using the new rules schema.
    • The schema names to use are provided through JNDI by using the application server console.
  7. Enable saving of rules:
    1. Click Configure > System > High Availability > HA Cluster Settings.
    2. Clear Cluster Upgrading - Disable saving of rules.
  8. Migrate auto-generated rules that were created after step 1.