Modeling Unbounded Processes
Purpose
In this IT process, you define an integration model from a business perspective, for example, for the integration of third-party or legacy systems. You then use this integration model to derive the required unbounded processes and to model the relevant integration scenarios and integration processes.
You can use ARIS for SAP NetWeaver as the modeling environment for the business perspective. For the modeling of integration scenarios and integration processes you use the Integration Repository of the Integration Builder.
You can use process patterns shipped by SAP and adapt and enhance them as required.
Use of the Process
This process is part of the following IT scenarios:
IT Scenario |
Scenario Variant |
Prerequisites
You want to describe the integration scenario for your company in a model and implement it in integration processes.
Process Flow
1. Describe integration strategy in a model (ARIS for SAP NetWeaver).
You analyze and document the business requirements of the integration strategy in a model. From a business perspective, you describe which systems are to be integrated.
2. Import BPEL scenario and process model for documentation of the integration strategy from the Integration Builder (ARIS for SAP NetWeaver).
3. Create integration scenario based on the project scope (PI).
You can define the message exchange for collaborative processes in an integration scenario. This generally involves processes between various business partners that are loosely linked with each other by the exchange of messages. The integration scenario provides you with a central point of access for all objects that you require for semantic and technical integration, such as interfaces and mappings.
4. Create metadata (PI).
You define the required objects, such as data types, message interfaces, and mappings, in the Integration Repository of the Integration Builder. You can create your own objects or adapt and enhance objects shipped by SAP.
5. Model integration process (PI).
The Integration Directory of the Integration Builder provides a graphical process editor for defining integration processes. You define the required processing steps and control structures, such as loops and forks. You also define the data to be processed by the process. In doing so, you can use the process patterns shipped by SAP.
Result
You have used the integration strategy as a basis to define the necessary integration scenarios and integration processes.