Import landing page

Select a local file to load and import

Use this option on a target Pega 7 Platform system that is the target or destination system of a migration operation.

This option lets you import the contents of an archive ZIP file produced by the Export Rules/Data tool, the Purge/Archive wizard, the Product Package wizard, or the Product or Product Patch rule forms into a Pega 7 Platform system.

Basics

Rules, data, and other Pega 7 Platform instances contained in the ZIP file are added to the rules already present in this system, optionally overwriting some existing rules. Data instances (if any) in the ZIP file are added to the data instances already present, optionally overwriting some existing ones.

To start the Import gadget, click Designer Studio> Application > Distribution > Import.You can also import Pegasystems engine changes contained in a JAR file, or third-party JAR files directly into the pr_engine classes database table using this gadget. Upon restarting the server, code contained within the JAR file will be available and can be called from Java steps in activities. Using this approach, you do not need to undeploy and redeploy the prweb application, nor make any changes to the prconfig.xml file. (By default, the JAR file is loaded into the Customer CodeSet identified in the prbootstrap.properties file.)

 1. Completing the Form — Local archive file

In the File Name field, enter the full path and name of the ZIP or JAR file to be uploaded, or click Browse.

Navigate to the local directory that contains the ZIP file, select it, and click Upload file.

If you attempt to upload a ZIP file when the ServiceExport directory already contains a file of that name, a prompt appears. Click to confirm that you want to overwrite the existing file.

Using this facility, by default, you cannot use this form to upload a ZIP file larger than 1GB. This is an intentional design restriction on the HTTP file copy facility, not a limit on the rule import processing. For larger files, use File Transfer Protocol (FTP) or another means to place the file into the ServiceExport directory. Alternatively, you can set a higher (or lower) upload limit on your system by changing the value for the Initialization/MaximumFileUploadSizeMB parameter in the prconfig.xml file.

 2. Begin Import

Click Import. The import operation starts. Importing may take several minutes or more.

The system attempts to upload the rules in an order that minimizes processing. After processing completes, adjust access groups or application rules to provide access to the new RuleSets, versions, and class groups as needed. Other users must log off and log in again to access the uploaded application RuleSets.

Click Close to close this form.

Notes:

If you upload rules in a ruleset version that users already can access, they may begin executing them immediately, possibly before other rules in the same ZIP archive are present. This may be desirable and intended, or not desirable. Similarly, declarative rules begin executing for such users immediately. Declarative rules may fail if not all the elements or properties they reference are uploaded yet.

In a multinode system, the lookup list cache on nodes other than the node on which you run the Import Archive tool may be stale temporarily. The Pega-RULES agent on each other node clears the lookup list cache during the next system pulse.

If you import rules in a ruleset version that some users already can access, they may begin executing them immediately, possibly before other rules in the same ZIP archive are present. This may be desirable and intended, or not intended. Similarly, declarative rules begin executing for such users immediately; declarative rules may fail if not all the elements or properties they reference are uploaded yet.

By default, you can't upload a ZIP file larger than 1GB to the server from your desktop with the Import Archive tool. This is a limitation on the upload operation, not on the import itself. Use FTP or another means to place the ZIP archive into the ServiceExport directory on the server, or change the limit through an entry in the prconfig.xml file or Dynamic System Setting.

If a ZIP archive contains instances of classes with encrypted Storage Stream values, the ZIP archive can only be imported to another system that uses the identical site-specific cipher.

The property @baseclass.pxMoveImportDateTime records the date and time that a rule (or other instance) was imported from a ZIP archive. You can report on this property (for one rule type such as properties or flows) on when the rules moved into a system.

During the ZIP import operation, the system confirms, for each ruleset version imported, that other ruleset versions (or higher versions) identified as prerequisites are present. For example, you can't import a product ZIP archive exported from a Pega 7 Platform 05-03-01 system into a Pega 7 Platform 04-02-60 system. The converse — from 04-02-60 to 05-03-01 — is allowed, however. (This check is not performed for a ZIP archive that contains only RuleSets and was created directly in the Export Archive tool.)

Resolving missing dependency error messages

If your application has any missing product dependencies, the system lists the missing product name and version.

• For production systems, correct the missing dependency.
• For testing or development systems, you can either correct the missing dependency or select Allow import with missing dependencies. If you continue to import with missing dependencies, the rules you import may not work correctly.

Click Next to continue importing the application.

Related information

Open topic with navigation