Version management in the Integration Repository permits versioning as follows:
· The Integration Builder manages multiple versions of a software component in an Integration Repository. In this way, different product versions can communicate with each other. Each design object is created in the context of a software component version that represents a unit of a product that can be shipped.
· Objects can also have new object versions when changes are made within a software component version. You also have the option of releasing changes to multiple objects simultaneously.
Versioning in the Integration Repository ensures that objects are shipped consistently, and as part of a product.
However, there are no software component versions in the Integration Directory, because the configuration content is not shipped. Nevertheless, you can also release changes to the configuration for the entire runtime environment here. When you release the objects, the Integration Server updates the directory runtime cache.
You can also export objects of an Integration Repository or an Integration Directory to import them into another repository or directory (for example, during system relocation). In doing so, versioning of the corresponding software component version is taken into account.
See also: Transporting XI Objects.
The Integration Builder supports object versioning for both the repository and for the directory using the user-specific change lists. When an object is saved for the first time, a new object version is created, which is added to the change list. When an object in the change list is activated, the object version is closed and is made visible for other users.
See also Selecting Individual Objects.
A product can have multiple versions. Each product version is a shipment unit visible for customers. The software component versions used in a product version can be called in the System Landscape Directory.
See also: Software Catalog.
In the context of SAP Exchange Infrastructure, the products and software component versions that are of interest are those that are to exchange messages with each other. When development starts they must be imported from the System Landscape Directory into the Integration Builder.
See also: Importing Software Component Versions.
In the transition from one software component version to a new software component version, you can either transfer all, or just some of the design objects from the previous version. This release transfer also enables you to transfer objects to older software component versions.
See also: Release Transfer.
Note the information contained under Compatibility of Changes when developing a new software component version.