Migration using the Distribution landing page

The Pega Platform provides several tools to archive rules, data instances, and work items into .zip files and move them from one Pega Platform system to another.

• Application Package wizard — A guided process that creates a product rule containing relevant data instances as well as rulesets.
• Export gadget — Creates a ZIP archive from a product rule.
• Import wizard landing page — Imports a ZIP archive
• Product Migration wizard — Creates a ZIP archive from a product or product patch rule, migrates the archive, and imports it to one or more destination systems.

You can use these tools to copy a product or ruleset from one Pega Platform system to another. Also known as migrating or moving, this procedure does not alter or delete the source rules.

For example, you can move a product from a development Pega Platform system into a test Pega Platform system. The source and target systems might have different servers, operating systems, database vendors, web server software vendors, and so on. Information inside the .zip file consists entirely of XML documents in Unicode characters.

Stage 1 - Review criteria

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 less than the version number of the source system. For example, do not attempt to move a ruleset created in version 05-01-06 into a system based on version 04-02-01.
3. Review the ruleset version rules to be included. Note the prerequisite rulesets and versions they reference. If moving more than one ruleset, note whether and how they are interdependent.

Stage 2 - Prepare

1. On the target system, access the Records Explorer. Confirm that the target system includes all the prerequisite rulesets and versions needed.
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 Designer Studio >Application > Development > Checked Out Rules.
4. On the source system, click Designer Studio > Process and Rules > 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. Note that although the reports display up to 10,000 rules, the .zip archive might contain more than 10,000 instances.

Stage 3 - Export/Import

1. Export the .zip archive.
2. On the target system, import the .zip archive.
3. Adjust your access group as necessary to provide access to the uploaded rulesets and versions.

Stage 4 - Review results

1. Log off then log in again with the updated access group, and then review the uploaded results. If they are satisfactory, lock the imported rulesets and versions.
2. Consider whether a new class group and work type structure is appropriate for deployment of the application. See Data Model category — Classes and Properties page.
3. In a multinode system, 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. As a best practice, recompile the libraries and delete the lookup list cache on each of the other nodes.

Open topic with navigation