|
Use this option on a target Process Commander system, the destination system of a migration operation.
This option lets you import into a Process Commander system 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.
Rules 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 Archive tool, select
> Application > Import & Export > Import.
2. Completing
the Form — Local ZIP file
In the File Name field, type in the full path and name of the ZIP file to be uploaded, or click Browse . B-16465B-19047 underscoreB-21958 backs out B-21089 malformed file name
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. B-16850 and FROHR 6/4/07
Using this facility, by default, you can't
upload a ZIP file using this facility that is larger than 25 MB. 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. CLINIC 8/29/06 See Limits and
maximums.
You can also import Pegasystems engine changes contained in a JAR file, or third-party JAR files directly into the pr_engineclasses table using this method. 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. V6.1 (By default, the JAR file is loaded into the Customer codeset identified in the prbootstrap.properties file.)
3. Completing
the form — Zip File On Server
| Option | Description |
| Compile Libraries |
Select to force Java compilation of the libraries affected by the rules in the ZIP file following upload. SR-1180 B-16579 SR-7298 not working SR-6738 B-15945 This option is meaningful when the ZIP archive contains a library rule (Rule-Utility-Library rule type) or function rule (Rule-Utility-Function rule type). You can also compile any library later from a button on the Library form. SR-1289 (This checkbox compiles the libraries on the current node during the import operation. On each other node of a multinode cluster, the Pega-RULES agent compiles these libraries later, ensuring consistency in compiled code across all nodes.) Proj-388 |
| Update Only If Newer |
Select this option to only import instances of rules that have a more recent update time then the instances of those rules already present in the system. This is particularly valuable when importing hot fixes, because the user can import hot fixes in any order, without having to worry about whether the new import might conflict with or cancel out a previously-imported hot fix.55sp2, TASK-8276 |
| Overwrite Existing Rules |
Select this option to overwrite any rule instances with the same RuleSet name, RuleSet version and visible keys that are already present in the destination PegaRULES database with the rule from the archive ZIP file. If not selected, when you click Import, the tool scans the rules in the ZIP archive and compares them with existing rules in the system, noting any matches. If matches are found, you cannot import the ZIP archive. You can:
Technically, a "match" means identical values for four properties:
If this checkbox is selected, rules in the ZIP archive overwrite rules in the current system if they match on pzInsKey, pyRuleSet, and pyRuleSetVersion. (If the pxUpdateDateTime also matches, the rule is skipped; there is no need to overwrite, as the rule in the ZIP archive and the rule in the system are identical.)
|
| Overwrite Existing Data |
Select this option to overwrite any existing data instances with the same key that are already present in this destination PegaRULES database the database with the data instance in the archive ZIP file.BUG-3971 BUG-4107 If matches are found, you cannot import the ZIP file. You can:
Technically, a "match" means identical values for two properties:
If the checkbox is selected, data instances in the ZIP archive overwrite data instances in the current system if they match on pzInsKey. (If the pxUpdateDateTime matches, there data instance is skipped; there is no need to overwrite, as the data instance in the ZIP archive and the one in the system are identical.) |
4. Optional.
Select Specified Instances For Load
To import specific rules or data from the ZIP archive, rather than the entire contents, select the checkbox Show Contents. The Import gadget display expands to list all the rules in the archive by Key name and RuleSet Version. Proj-1293
Select the checkbox next to each rule you want to import. The Import Options you have selected are applied to each rule individually as they would be for the entire archive.
When you have completed your selection, continue with the Import.
Individual rules must validate
normally when imported.The Import tool does not update the
rule's RuleSet references or the class list on the Pages and Classes tab. All components required by
the rule must be present in the target system or imported along with
it. See Pega Developer Network article 
PRKB-24183 Troubleshooting: "Class...does not
exist" error when importing a ZIP archive for more
information on these types of errors.
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. CLINIC 3/05 also
B-12115
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 pulse. KIESE 6/4/07 changes
from LINIC 2/24/07
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 Process Commander 05-03-01 system into a Process Commander 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.) PALAV 7/11/06
|
library, lookup list |
|
Troubleshooting Import Archive: Duplicate record found |
Import gadget
About Archive tools