...
The export can contain your system's data, configurations, and runtime data. You can send this export data to another system, using the System Importer to import it and embed its contents locally.
| Info |
|---|
Example - How System Exporter can be used You can import a tested and exported ZIP or MZP file of configurations from a test system and use it safely in production. |
...
When exporting a Workflow Template with Dynamic Workflow Configuration enabled, the Dynamic Workflows will also be exported. You can specify in the System Importer if they should be imported or not. See Workflows(4.0)
The following sections explain the following:
| Table of Contents |
|---|
Export Types
There are two export types. They result in different behaviors when imported later. Select the one that suits your requirements:
Configuration: The configurations must be compatible with the software packages of the system to which you import the configurations This is normally not a problem as long as you are using the same release. The export will be downloaded as a ZIP file. See Configuration Export Type.
Workflow Package: Export in Workflow Packages(4.0) format. A Workflow Package is read-only and self-contained, with the same binaries as in the exporting system. A Workflow Package is not affected by, nor will it affect, any existing configurations when imported, since the used binaries are not replaced. When selecting Workflow Package Export Type, you compile a Workflow Package by selecting workflows in the Available Entries table. All dependent configurations will also be selected. See Workflow Package Export.
| Note |
|---|
Note! See File System (4.0) to learn how to configure a File System Profile when exporting to Git or AWS S3 Bucket. |
| Anchor | ||||
|---|---|---|---|---|
|
You can export a configuration to your local browser or remote with a File System Profile of type Git or AWS S3.
...
Option | Description |
|---|---|
File Name | The file name of the export. It will automatically become a Zip file. |
Select Target | A table showing the folders in AWS S3 Bucket. Select a folder to export to, when no folder or file is selected the export will be uploaded to the top level of the Bucket. |
| Anchor | ||||
|---|---|---|---|---|
|
...
When this type is selected, Workflow Packages(4.0) can be created and exported as a MZP file. A Workflow Package is read-only and self-contained, with the same binaries as in the exporting system. A Workflow Package is not affected by, nor will it affect, any existing configurations when imported, since the used binaries are not replaced. When the Export Type is Workflow Package you can select data from the following types:
Configuration: Workflow configurations, agent profiles, workflow groups, Ultra formats, or alarm detectors.
System: Other customized parts such as; Data Veracity, Event Category, Folder (structure), Pico Host, Ultra, User, or Workflow Alarm Value.
...
When one configuration is selected all dependent configurations will also be selected.
...
How To Perform an Export
| Note |
|---|
Note! Since no workflow state, i.e. File Sequence Number, is included in the exported data and only the initial value is exported, you need to take note of information such as file sequence numbers in Collector agents. |
...