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 to run the 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 package bindings in the form of an XML file. Exporting bindings allows you to use the file in the following ways:
To facilitate automated deployment using the clagent deploy_instance command. See Working with Agent Server Instances from the Command Line.
To customize package bindings without going back to the Design environment.
To share with others, for example, by using email or access to a shared directory.
To export the bindings used in a package:
In the Server Explorer, right-click on the runtime instance that contains the bindings to export.
Select Export Bindings.
A Save File dialog appears.
In Save File, specify
the destination for a copy of the binding document for the package.
This data is saved as an XML file.
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 package bindings XML file.