SAP NetWeaver PI 7.1: Process Integration Modeling a Challenge? ES Repository Simplifies with a Top-Down Approach

  • by Peter Gutsche, SAP AG
  • October 29, 2009
Software architects and developers involved in service-oriented architecture projects can use the Enterprise Services Repository to design integration content following a top-down approach. This approach facilitates your design work because you have an overview of the content objects that belong to your integration scenarios as well as how these objects are related to each other. Keeping your design work and the created content transparent and interlinked saves you time and effort.
Key Concept

Enterprise Services Repository, included in SAP NetWeaver Process Integration 7.1 (SAP NetWeaver PI 7.1), provides an enhanced modeling environment that improves the top-down design capabilities available in releases prior to SAP NetWeaver PI 7.1. The integrated modeling environment enables users to design integration content starting with a model and then they can add the relevant interfaces and data types.

Today’s business processes span several departments and can even involve external business partners. In addition to that, the speed of change has increased considerably: Companies have to be able to quickly adapt their business processes to new business requirements. As a result, modeling and design challenges arise. Furthermore, as large business processes typically are implemented on extensive and complex system landscapes, there’s a demand for a modeling environment that allows you to concentrate on the business process without the need to care for the technical implementation level.

The Enterprise Services Repository (ES Repository) provides a modeling and design environment that allows you to design collaborative processes — particularly the integration-relevant aspects , such as mappings of data structures — on an abstract level first. This is independent from the technical level of the system landscape in which you plan to implement the process.

The decoupling of the business level from the technical implementation level provides the flexibility for the solution architect to change a business process according to new business requirements (e.g., adding a new field to a data type) without having to worry about the implications the change might have on the technical implementation level, such as the individual connections between the involved systems.

The ES Repository allows you to design integration content top-down. In this process, you start with a model and then, based on the model, specify the other integration content types, such as service interfaces and mappings. I will introduce the basic concepts that establish the ES Repository as an environment for the top-down design of integration content. SAP NetWeaver PI 7.1 has two new model types available that you can use as a starting point to design integration content: the process integration scenario model and the process components interaction model. The modeling environment is interlinked with editors for other integration content types, such as service interfaces and mappings. To perform the steps I describe, you need SAP NetWeaver PI 7.1 or SAP enhancement package 1 for SAP NetWeaver PI 7.1.

Peter Gutsche

Peter Gutsche joined SAP in 1999 with a university degree in physics. As an expert in the topic area of SOA middleware, he is responsible for writing product documentation about SAP NetWeaver Process Integration.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.