Transporting a Change Set

A released change set can be automatically transported by selecting a target system to which the change set will be transported. This utilizes the web services feature provided by the application. For more details, refer to the Target System chapter in System Configuration guide for further details on how to setup or maintain the web services feature.

Released change sets can also be manually transported to a target system. Manual transport is used when it is not possible to create a connection between two systems over a network. For example, there may be network issues or security policies may mandate that the production systems need to be hosted on networks isolated from development systems. To manually transport a change set, three steps are required: export, copy and import. The change set is first exported from the source system. This downloads the change set, including the business objects, to the source system local drive from CTM. Then, the exported file is manually copied to the target system, for example, by e-mail, USB key, shared directory, etc. The file is then imported into the target system. The CTM import function reads the change set and all of its contents from the external file into the target system and creates it on that system in a released state. The change set is then ready and available to be applied on the target system.

Note: With a manual transport, there is an option to encrypt the change set. The method used is Base64 which provides an obfuscation mechanism rather than encryption.