Sdata tool Patch Archives
Sdata tool Patch Archives
Archive
Should you experience any difficulty in accessing this document, please don’t hesitate to contact us. We will work to provide information to you in an alternative format. The Agency of Education created this Excel spreadsheet to provide you with a fiscal snapshot of each school district in Vermont. Specifically, information regarding various pupil counts, education spending, per-pupil spending, tax rates, and staff numbers are used to generate a five-year picture of each district. As these data influence each other (equalized pupils and education spending generate per-pupil spending which determines tax rates, for instance), we compiled these items into a three-page, printable report, with locked data cells so the data does not get inadvertently altered by the user. The first page of the tool allows you to choose which district you are interested in viewing and which school. You can then run the report to view that school’s change in enrollment over time, tax rate calculations, student: staff ratios, staffing patterns, and per pupil spending, both in data form and graphs. Also included are data for the state as a whole over the same time period.
Help: Import Archive wizard
Completing the Import Zip file option
Show all
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.
Basics
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 .
1. Select an Import mode
Complete the Select Import Mode field. Select:
- if the ZIP file has already been placed in the ServiceExport directory.
- if the ZIP file is on your local area network only.
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 .
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 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 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 parameter in the file. See Limits and maximums.
3. Completing the form — Zip File On Server
- Click to select one file in the boxed text area.
- Set options as desired:
| Option | Description |
| Compile Libraries | Select to force Java compilation of the libraries affected by the rules in the ZIP file following upload. 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. (This check box 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.) |
| 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 check box 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. If matches are found, you cannot import the ZIP file. You can:
Technically, a "match" means identical values for two properties:
If the check box 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 check box Show Contents. The Import Archive display expands to list all the rules in the archive by Key name and RuleSet Version.
Select the check box 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.
. 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.
5. 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 pulse.
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.)
About Archive tools
Import gadget
Select a File from the Server to Import
Use this option on a target Pega 7 Platform system, the 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.
1. Select File from Server
Click the name of the file you want to import..
Review the File Information details that display to confirm that this is the file you want and that it is appropriate for your system.
The File Information available for a specific archive may vary, but can include the following:
Label | Description |
| Type | Indicates whether the ZIP archive contains only RuleSets, is derived from a product rule, or contains Java classes. |
| Operator | Full name of the user who exporting this ZIP on the source system, from the General tab of the Operator ID data instance. |
| PRPC Engine | Version of the source system. |
| Pega-Build-Date | For an application bundle, the date the bundle was created. |
| Pega-CodeSet-Name | For an application bundle, the name of the CodeSet from which any Java JAR files were extracted. |
| Pega-CodeSet-Version | For an application bundle, the version number of the CodeSet from which any Java JAR files were extracted. |
| Manifest-Version | If available, a version number extracted from the application bundle manifest file. |
| Pega-CodeSet-Patch | Not used. |
| Name | If the Type is , the Product Name key part of the product rule in the source system. |
| Version | If the Type is , the Product Version key part of the product rule in the source system. |
| Instance Count | Count of all records in the ZIP archive. |
| Label | If the Type is , the Short Description of the product rule in the source system. |
| Creation Date | Date and time the ZIP archive was exported from the source system. |
| Archive Type | One of: for a product rule or RuleSet export, for a Java Archive, or , for a collection of multiple ZIP archives with a manifest. |
| Synchronizable | Not used. |
| RuleSet Name | If the archive contains only some or all versions of a single RuleSet, the name of the RuleSet. |
2. Optional. Show Content Details
To review the content of the archive, click Show Content Details.
The content displays in a separate window in the following sections:
- Rules
Displays each RuleSet in the import. Within each RuleSet you can drill down to expand each RuleSet Version and then each class. For each class you can click the number in the Instances column to display a list of the individual instances in the import. - Application/Framework Data
Custom Data classes associated with the application, for example. PegaAES-Data- - System Data
Data- classes included in the archive. - Schema
Database Schema ChangesClass — Table
- Code Items
CodeSet — Version — Jar File
3. Optional. Enable advanced mode
Check Enable advanced mode to see all the import wizard pages. By default, only import screens that require your input are shown, for example, when there is a conflict between the content in the import archive and the content in the target system.
In advanced mode, the wizard displays a page for each type of content in the archive allowing you to review each step and modify the content before submitting the import.
4. Begin Import
Click Next to begin the import. The import operation starts immediately. Importing may take several minutes or more.
If you do not want to complete the import, select << Back to return to Select a local file or << Cancel to exit from the wizard.
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.
Notes
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.
Caution: 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 directory on the server, or change the limit through a file setting. See Limits and maximums.
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.)
About Archive tools
Open topic with navigation
What’s New in the Sdata tool Patch Archives?
Screen Shot
System Requirements for Sdata tool Patch Archives
- First, download the Sdata tool Patch Archives
-
You can download its setup from given links:
Sdata tool Patch Archives & Free Download
Sdata tool Patch Archives& Free Download
Sdata tool Patch Archives
About Author
