LinkedIn
Copied!

Table of Contents

Preparing to package and move applications

Version:

Only available versions of this content are shown in the dropdown

Before you move your application, prepare the source and target system.

  1. Compare the source and target systems.

    1. Confirm that you have a working operator ID with a PegaRULES:SysAdm4 access role on both the source system and target system.

    2. Confirm that the Pega Platform version number of the target system is not earlier than the version number of the source system. For example, do not attempt to move a ruleset that was created in version 08-01-01 into a system that is based on version 07-03-01.

    3. Review the ruleset version rules to be included. Note the prerequisite rulesets and versions they reference. If you move more than one ruleset, note whether and how they interact.

  2. Prepare the target system for migration.

    1. On the target system, access the Records Explorer and confirm that the target system includes all the prerequisite rulesets and versions.

    2. On the source system, create a product rule or product patch rule.

    3. On the source system, examine the checked-out rules display. Confirm that none of the rules to be migrated are checked out by clicking Configure Application Development Checked Out Rules .

    4. On the source system, click Configure Case Management Tools Find Rules and use the Find by Ruleset, Version, Rule Type report to estimate a count of rules to be included in the .zip archive.

      Although the reports display up to 10,000 rules, the .zip archive might contain more than 10,000 instances.
    5. Create a restore point on the target system so that you can roll back the import if there is an error. For more information, see Using restore points to enable error recovery.

  3. Review the updated target system.

    1. Log off and then log in again with the updated access group, and then review the uploaded results.

      • If the results are satisfactory, lock the imported rulesets and versions.
      • If the results are not satisfactory, you can roll back to the restore point. For more information, see Rolling back to a restore point.
    2. Consider whether a new class group and work type structure is appropriate for deploying the application. For more information, see Working with class groups.

    3. In a multinode system, recompile the libraries and delete the lookup list cache on each of the other nodes. The lookup list cache (and in some cases the compiled libraries) might be stale on nodes other than the node on which you run the Import wizard.

Have a question? Get answers now.

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