Configuration Export is the way that applications and miscellaneous configuration components are exported from PhixFlow. You may want to export your configuration for a number of reasons - e.g. to back up an application, or set of configuration components, you are working on; or so that you can import it somewhere else.
...
- the download area
- the header.xml file in the configuration export zip file
- log file messages generated by the export process and when the file is imported.
| Excerpt | ||
|---|---|---|
PasswordsPasswords Saved in PhixFlowExported files do not include any passwords from the PhixFlow system, such as passwords for:
Providing a Password to Encrypt the Exported FileBy default, when you download an exported file, it is encrypted. You must provide a password that you can then use when you import the file into another instance. |
Using the Export Pane to Copy
In addition to being able to export items ready for import to another instance, you can also copy items into the same instance using the copy option.
In PhixFlow, items are often associated with other items. For example a stream is run by an analysis task or a style is used by a layout component. When making a copy, PhixFlow does not update associated items. The following table provides some examples:
| Item copied | Associated items | What happens to associated items |
|---|---|---|
| StreamA is copied to streamB. | An analysis task runs streamA. | The analysis task is not changed and only runs streamA. |
| Shared-style1 is copied to shared-style2. | There are 10 layout components that use shared-style1. | Shared-style2 has no components. The 10 layout components that use shared-style1 are not changed. |