Process Integration Transports

General

When you develop your applications you must differentiate between two types of development objects:

• Design objects from the ES Repository and configuration objects from the Integration Directory.
• Objects in the different application systems. These are Java and ABAP classes, client and server proxies generated using proxy generation, ABAP programs, and other development objects that implement the actual application logic.

The functions for transporting design and configuration objects described in this section can only be used to transport ES Repository objects or Integration Directory objects. All objects that are developed in the application systems (proxy objects included) must be shipped using their infrastructure. In particular, you must ensure that the objects of your application from the ES Repository are shipped together with the objects of the application system.

More information:

• For more information about the organization and transport of ABAP development objects, see Change and Transport System - Overview (BC-CTS) .
• For more information on the organization and transport of Java development projects, see Tasks

Integration Directory content is not shipped. The export and import functions in the Integration Directory enable you to test your configuration data in a test directory before you transport this data into the productive directory.

Transport Support for PI Transports

You can perform ESR content transports and Integration Directory Transports in the following ways:

• You manually export the contents as a file from the initial system and then import this file into the target system (file system-based transport).
• Using the Change Management Service (CMS).More information: PI Transports Using the Change Management Service (CMS)