About the Product Migration wizard |
Application migration can be done using a command line utility or wizard.
The Product migration command line utility is an enhancement to the existing UI based migration from within PRPC. This utility is intended to give ability to users to perform migration of multiple products (RAPs) to multiple targets and also get a more granular status of the migration process.
This is a standalone utility and doesn’t require engine to start up. Instead it uses services exposed from PRPC to communicate with both source and target ends of migration. This utility is available from release PRPC v7.1.
Product Migration Command Line Utility for details on how to use the command line utility.
The Product Migration Wizard simplifies the management of rule assets across PRPC systems. After specifying the appropriate packaging information through a Rule-Admin-Product instance, this wizard eliminates the need to:
This wizard creates a work item with prefix pxMigReq-
. To find open and resolved wizard work items, select > Application > Tools > All Wizards. There is also a command line tool that you can use to perform these actions.
Before using the wizard, do the following:
PegaDiagnosticUser
security role is defined for your PRPC server node. Also confirm that an instance of the Data-Admin-System-Security class exists with this security role as the key. The user and password information must match the ones specified by the Web server console for this security role. Normally, this security role is configured during installation of your PRPC server. For more information, see the Installation Guide for your platform.Select> System > Tools > Migrate Product to start the Product Migration wizard and create a Migration Request cover work item; the resulting work item ID has the prefix pxMigReq
. The Step 1: Products and Targets form appears.
If your system contains unresolved migration requests, select one from the worklist that appears (see Managing requests below).
In the Step 1 form, specify the product and version. Then identify one or more target systems.
MyProd-Classgroup_01-01.zip
or MyProd-Classgroup_01-01-99.zip.
pzMigDest
.When you submit the request, the source system creates a ZIP archive file. It also creates a covered work item for each target system. The process then attempts to make a connection to each target system and place the ZIP file on its ServiceExport
directory.
Rather than having to re-enter the host name, context root, and port number each time you submit a migration request, you can create a list of saved target systems. This allows you to select the systems you want to export to.
You add the target systems to the list by creating instances of the Data-Admin-System-Targets rule. To create a new System Target instance:
The information displays in the Specify Target Systems list in the Step 1. Product and Targets form.
If you created a new target system rule instance after the original request was created, the system does not appear in the Specify Target Systems list.
You can also perform these actions and more using the Product Migration Command Line tool. This is also useful for scripting commonly used actions.
About Product rules
About the Application Packaging wizard Import Archive — Completing the Import Zip file option About the Package Work wizard |