Import and Export

An Orchestra system configuration can be saved to a zip file and then imported into another system. The importing system must be a newly installed system, that is no configuration has been done.

Also, an exported system configuration can be sent to Qmatic for problem solving in a service assignment.

Several similar system configurations can be set up, by first creating one configuration containing most settings and then exporting it, importing it into the new systems, and then making adjustments.

The Import and Export functionality can not be used to clone a system, since that will result in severe problems with id’s in the database.

The Import/Export functionality is database agnostic. For example, it is possible to export a configuration on a system using Oracle and import it on a system using PostgreSQL.

When importing a configuration, the import will reset the state of any previously registered distributed Queue Agents, including the current profile of the Queue Agent.

For more information, see “Queue Agents” .

Note that only import/export from and to the same version of Orchestra is supported.

To export a system configuration, do the following:

Only the Central configuration is exported, i.e. no data on the Queue Agents is exported.

In the System Administration application, open the Import/Export tab:

Once the file is downloaded, you will be asked if you want to open or save the file.

The following are included in an export:

• Customer Journey Management Global configuration settings

• AAA - i.e the three security layers in an application: Authentication (the act of confirming the truth of an entity, e.g a User); Authorisation (confirming the access rights, privileges of an entity e.g a User); Audit (evaluation of a security token, e.g a User or process).

• Wookie widgets and Orchestra Wookie Widget configuration

• Queue Agent Profiles (and their connections to parameters)

• Stat job transformations, i.e. the stat-jobs.xml file.

The statistics tables and data are not included in the exported zip file. However, the user Branch Group mappings and hierarchy are included.

The exported data is saved in a nested JSON structure. Binary data is stored in binary files, referenced from the JSON structure. The exported data is finally stored in a zip file. A link to the zip file is displayed on the page. Click the file link and save the file in a suitable directory.

To import a system configuration, do the following:

When importing Users to Orchestra, using the Import/Export functionality, System administrator Users are sent to the database directly after import. However, Users with Branch privileges are not sent until the Branch is published.

By importing a system configuration, a complete Orchestra set-up can be installed in one simple operation.

Import must be performed directly after an Orchestra installation, before any configuration is done.

If any Queue Agents are connected to the system that you are performing import on, then the databases of those Queue Agents must be reset. This is done in the Queue Agent tab of the System Administration application.

For more information, see “Queue Agents” . If the databases are not reset, publishing to these Queue Agents will fail after import.