You can export endpoint configurations, runtime instance configurations, and package bindings and reuse them either in their original form, or you can modify the files. Each of the three file types is specific to the original functionality, that is, endpoint configurations are used in Endpoint Manager, runtime instance configuration provides the configuration properties required for a runtime instance and input transports associated with the runtime instance, and package bindings provide the bindings for packages. These are not interchangeable.
Use the export functionality in Server Explorer to export your Unwired Orchestrator runtime instance configurations in the form of an XML file. Exporting runtime instance configurations allows you to use the file in the following ways:
To facilitate automated deployment using clagent deploy_instance, reconfigure_instance. See Working with Agent Server Instances from the Command Line.
To reconfigure_instance commands.
To customize runtime instance data without going to the Administration environment.
To share with others, for example, by using email or access to a shared directory.
To export configuration data:
In the Server Explorer, right-click on the runtime instance that contains the configurations you want to export:
Select Export Configuration.
A Save File dialog appears.
Specify a destination
for the runtime instance data you are exporting.
This data is saved as an XML file, which is similar to Endpoint Manager
export files.
Click Save.
Note: When naming your .xml files, use a
method that allows you to easily see the relationships of files.
For example:
..._<package name>_endpoints.xml
..._<package name>_config.xml
..._<package name>_binding.xml
Then save the files to <package name> folder.
View the format of this file in the example runtime instance configuration XML file.