Migrating auto-generated rules in a highly available system after an upgrade or patch

Some Pega Platform applications have auto-generated rules. These rules are created at runtime during the normal use of a production system. If you have a highly available system, migrate the auto-generated rules after the upgrade or patch completes.

Note: Auto-generated rules created after the initial rule migration are not present in the upgraded rule base and must be migrated manually after the upgrade completes.

Create an XML file containing the following classes to export:
```
<?xml version="1.0" encoding="UTF-8" ?>
<ExportClassList>
<Database dbname="PegaRULES">
<Class name="Rule-Obj-Property" column="PXUPDATEDATETIME"/>
<Class name="Rule-Obj-When" column="PXUPDATEDATETIME"/>
<Class name="Rule-Obj-FlowAction" column="PXUPDATEDATETIME"/>
</Database>
</ExportClassList>
```
- Class name represents either:
  - The name of the class for a rule type that you want to export
  - A wild-card pattern, such as parent class name (for example, Rule-), used to export all the rules belonging to the Rule- hierarchy, including its descendants.
- PXUPDATEDATETIME represents the exposed column, which could be used to match the time stamp in the export.migration.date property in the prpcUtils.properties file in step 2.
Edit the prpcUtils.properties file:
1. Open the coreBuildDistributionImage/scripts/utils directory/prpcUtils.properties file.
2. Enter the database connection information by setting the following properties in the Settings for Export Tool section:
  - export.archive.full.path
  - export.migration.date
  - export.migration.xml – the full-path to the XML file containing the classes to export that was created in step 1.
3. Save and close the prpcUtils.properties file.
Run the prpcUtils.bat script or the prpcUtils.sh script with the export option. For example:
```
prpcUtils.bat export
```