Skip to main content
LinkedIn
Copied!

Table of Contents

Resolving conflicts when importing an archive by using the productMigration command-line tool

Version:

Only available versions of this content are shown in the dropdown

Importing an archive might fail if the versions of rules and data instances in the archive conflict with those on the target. If you are using the prpcUtils command-line utility, you can configure the import options in the prpcUtils.properties file to resolve these potential conflicts.

  1. From the command prompt of your Pega Platform instance, navigate to the scripts/utils directory.

  2. Open the prpcUtils.properties file. The comments in the file include information about valid values for each property.

  3. Set the import.mode property value. The following table lists the valid values and when to use them.

    Property Description
    Import This is the default behavior. Use to insert new instances and update existing instances at the same time.
    Install Use only to insert new instances and log primary key violation messages without updating existing instances.
    Hotfix Use to insert new instances and overwrite older instances in the target with the newer instances in the archive.
  4. For imports, set the import.existing.instance property to specify the behavior when an instance exists in both the target and the archive and the ruleset or ruleset version of the rule has changed. The following table lists the applicable values, and when to use them.

    If you do not specify a value for the import.existing.instance property and the ruleset or ruleset version of the rule has changed, the import operation fails with an exception.
    Value Description
    Skip The import does not update the instance in the target database.
    Override The import updates the instance in the database.
  5. To start importing, run the command-line utility for your operating system with the import option:

    • On Windows: prpcUtils.bat –import.
    • On UNIX: prpcUtils.sh –import.
  6. After you run the command-line utility, review the log file. If the log file lists any additional required actions, complete the actions and run the command-line utility again.

Did you find this content helpful?

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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us