Show all
The Product Migration wizard enables
you to automatically archive, migrate, and import a product
rule (Rule-Admin-Product rule type) or a product
patch rule (Rule-Admin-Product-Patch rule type) to
one or more destination systems.
The wizard eliminates the need to:
- Create the ZIP file using the Export Rule/Data tool, or
the product or product patch rule forms.
- Upload the ZIP file into the other Process
Commander’s temporary file directory.
- Log into each destination system and manually import the
rules from the ZIP file using the Import Archive wizard.
This wizard creates a work object with prefix
pxMigReq-
. To find open
and resolved wizard work objects, select the
Developer portal menu option Open > Wizards in
Progress > All Wizards.
Using the
wizard
To use the wizard you do the following:
- Start the wizard, which creates a migration request (a
cover work object).
- Define a product and a version and optionally, a
product patch. Then specify one or more target
systems.
- Authenticate your login credentials for the target
server system(s) and submit the request. The system creates
a ZIP product archive. The ZIP file is ported to each
target specified.
Prerequisites
Before using the wizard, do the following:
- In your source system, verify that the
PegaDiagnosticUser
security role is defined
for your Process Commander 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 Process Commander server. For more information, see
the Installation Guide for your platform.
- Verify that v5.4 or later is installed on your target
systems.
- Validate the connections between the source system and
target systems.
- Refer to How to
create a product ZIP file for information on how to
prepare a product rule for archiving to a ZIP file. Do not
use the Product rule form to create the ZIP file.
Starting
the wizard
Select File > Migrate Product to start the
Product Migration wizard and create a Migration Request cover
work object; the resulting work object ID has the prefix
pxMigReq
. The Step 1: Products and Targets
form appears.
If your system contains unresolved migration requests, a
worklist appears (see Managing requests below).
Creating
and submitting a migration request
In the Step 1 form, specify the product and version, and
optionally, a product patch. Then select one or more target
systems.
- Click Next>> to move to
the Step 2:
Authentication wizard form. Enter the ID and
password needed to authenticate access to each of the
target systems.
- Click Finish to submit the
request and begin the migration process, which includes:
- Creating the product ZIP file, which uses the
following naming convention:<product name _version
number[-patch number] >. For example:
MyProd-Classgroup_01-01.zip
or
MyProd-Classgroup_01-01-99.zip.
- Creating work object IDs for each of the
destination systems, using a prefix of
pzMigDest
.
When you submit the request, the source system creates a
ZIP archive file. It also creates a covered work object 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.
- If the connection succeeds and the file is successfully
loaded onto the server, the work object is resolved.
- If the connection fails or the file is not loaded due
to system error, the work object status is Pending. You can
either retry the connection or cancel the connection
attempt, which withdraws and resolves the work object.
Saving
target systems
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 simply 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:
- Using the Class Explorer, navigate to the Data-Admin-System-Targets class.
- Click the new instances icon on the toolbar.
- In the New form, enter a name for the target system and
click Create.
- In the rule form, enter:
- Process Commander server name (machine name or IP
address)
- Server port number such as 8080
- Server context root name such as prweb or
prweb.war
- Save the rule.
The information displays in the Specify Target
Systems list in the Step 1. Product and Targets
form.
Managing
requests
Tools, accelerators, and wizards