Object References 

The Integration Repository differentiates between the following:

·        Independent repository objects. These objects are visible in the navigation tree and are assigned to a namespace.

·        Objects assigned beneath the independent repository objects, for example a connection in a Business Scenario.

During the design phase you constantly need to reference existing repository objects, for example from a message mapping to message types. Note the following general restrictions:

·        It is only possible to reference independent repository objects.

·        Whether you can reference or not depends on the software component that the referencing repository object is located in (see below)

This is because you must be able to ensure that the repository objects of one product are delivered together.

Referencing Objects

Each referencing object is itself located in a namespace and is therefore assigned to a software component version. In turn, the software component version is assigned to a product version. It is then possible to reference other objects in the same, or in other software component versions, regardless of the object type. This restriction is reflected in the value help in the Integration Builder.

Business Scenario Objects

Object Type	Possible References
Business Scenario	Since Business Scenarios provides an overview of the communication between application components that are each assigned to a product, they can reference any products. It is recommended that the Business Scenario is part of a product itself that is referenced using an application component.
Action	An action can reference interfaces in the same product in which the action is used.

It is also possible to reference non-independent objects within a Business Scenario. See:  Business Scenario.

Interface Objects

Message interfaces reference (fault) message types and these in turn reference data types. You can only reference interface objects in the same software component version or in a sub software component version. This ensures that objects for a message interface are always in one delivery unit.

Mapping Objects

Mappings map messages from different application components to each other. Therefore, referencing cannot be as restrictive as for interfaces.The additional restrictions for interface mappings ensure that mapping programs are shipped together with the interface mapping.

Object Type	Possible References
Interface Mapping	·        You can reference interfaces from any software component version. ·        You can reference mapping programs (message mappings, XSLT or Java mappings) from the same namespace and the same software component version as the interface mapping.
Message Mapping	You can reference any message types or the request/response/fault part of an imported interface. It is also possible to reference non-independent objects. See: Message Mappings and References Between Mapping Programs.
Imported Archives	You can reference other mapping programs (see: References Between Mapping Programs) but not independent objects.