Developing Business Logic Design

Purpose

The development of a collaborative process begins with its design (see: Design Time). The Integration Builder provides you with an environment with which you can describe integration scenarios, integration processes, interfaces, and mappings independently of a system landscape. These objects are stored in the Integration Repository and are associated with software component versions that belong to a product that is to be shipped (see: Software Logistics for XI Objects).

Prerequisites

Software component versions are the smallest shipment units that can be shipped using the objects of the Integration Repository. To be able to develop within a software component version, they must be maintained in the software catalog of the System Landscape Directories (SLD). SAP products and the corresponding software component versions are already maintained in the SLD. It is also possible to include external products and software component (versions) in the SLD (see: Software Catalog).

Process Flow

The following steps are usually carried out in the design phase:

...

1. To save objects in the Integration Repository, you import the software component versions in which the objects are developed (see: Importing Software Component Versions). The development manager normally has the authorization required for this.

2. To document the business process on a more abstract level, create an integration scenario. This is regardless of whether integration process, interface, or mapping objects already exist or not. If objects are available, you can reference them directly. If not, you can create the objects from the integration scenario. An Integration scenario is the key for understanding the entire process (see: Designing Integration Scenarios).

3. To define the contents of a message and the communication type, create new message interfaces in the Integration Builder or import existing interfaces or message schema from an application system (see: Designing Interfaces), or both. You can begin the interface or message description at the same time as the further design steps and development in the business systems:

¡ If a stateful message processing is required on the Integration Server, define integration processes (see: Designing Cross-System Integration Processes). You use integration processes to define a stateful message processing that is executed on the Integration Server.

¡ To map the structure of a message to another message, use a message mapping or import an XSLT or Java archive. You use an interface mapping to specify which mapping programs to execute for which exchanged message for the source and target interface (see: Designing Mappings).

¡ To create executable proxies for message interfaces, use proxy generation. You use these proxies to connect applications on the SAP Web AS to the Integration Server (see: Proxy Runtime).

Result

The objects in the Integration Repository are assigned to a product using the software component version and can therefore be shipped with this product. Before they can be implemented in a system landscape at runtime, you must first configure the contents of the Integration Repository (see: Configuration).