PI FastTrackCourse ESR

7/30/2019 PI FastTrackCourse ESR

1/22

USIPI- Accelerated PI Traning course

Fed 2010

SAP NetWeaver- Process Integration

Enterprise Service Repository


2/22

2009 Deloitte Touche Tohmatsu2

Objectives of the Session

Describes Software Components and namespace

Describes the Integration Repository and Objects.

Understand Various Interfaces Objects and roles .

Describes types of message mapping.

Use of Web Standards .

Import of Various objects into Integration Repository.


3/22


ESREnterprise Service Repository

Integration repository is now referred as ESR - Enterprise Service

Repository.

The global data types, interfaces and business processes maintained in

Enterprise service repository are reusable

WSDL-based editors for the specification of service interfaces, message

types and data types. Fulfills UDDI 3.0 (UDDI: Universal Description, Discovery, and

Integration).

Enabling Application-to-Application Processes

Enabling Business-to-Business Processes


4/22


Software Components Version

Primary container for all Integration Repository objects.

Imported directly from the SLD.

For each software component version, can be assigned a connection to anexisting SAP system for the import of IDoc/RFC interfaces.

Each software component version can be assigned one or more namespaces.


5/22


Import SWCAs from SLD into ESR

Import Steps

In the Enterprise Services Repository menu bar,

Choose Object New.

In the create dialog, expand the Work Areas node.

Select Software Component Version. Select the Import from SLD radio button. After List of Software Component Versions, choose

Display.

The system displays all software component versions from the SLD.

Select one or more software component versions to import select the corresponding

checkboxes.

Choose Import


6/22


Namespaces

Unique identifier for related Integration Repository objects. Development objects in the Integration Repository are organized by namespace.

Several namespaces can be assigned to the same SWCV.

Naming convention:

http://sap.com/xi/demo -URI(Uniform Resource Indicator)

urn:sap-com:xi:demo -URN(Uniform Resource Name )


7/22 2009 Deloitte Touche Tohmatsu7

Design Objects in the Enterprise Services Builder

Process Integration scenario enables to

define the message exchange and process

flow for collaborative processes.

An integration process is an executable

cross-system process for processing

messages.

Mapping is supported by a graphical

mapping editor. The editor enables to design

a structure mapping between any two XML

structures and connect to a value mapping(Transformation Rules Defined by Mapping

Program).

Context objects mask access to elements or

attributes in the payload.

Data types and message types describe the

structure of messages that are to be

exchanged using service interfaces .


8/22 2009 Deloitte Touche Tohmatsu8

Interface Object Data Types

Data types are the most basic entity to define the structure of XML elements

Equivalent to XML Schema (XSD)

Data type editor provides all XSD basic data types.

Nesting of data types possible

Export of data type in XSD format possible

Structures can be created in the Data Type editor and reused in other

structures


9/22


Interface Object Message Types

The Message type corresponds to the root of the XML message

Name and namespace must match exactly the root of XML Business

documents.

The Message type references one single data type

XSD representation available for export

The message type describes what the actual payload message of an PI

interface


10/22


Interface Object Message Interface

The Message Interface is the highest-level representation of XML metadata.

Inbound or outbound (respective to the application), or abstract (forBPM only)

Synchronous or asynchronouso Asynchronous refers to one message typeo Synchronous refers to two message types (request and response)

References fault message types for exception handling WSDL representation available for export Starting point for proxy generation (ABAP and Java) Context objects can be assigned


11/22


Message Interfaces based on RFC/IDoc

Impor ts mu st be

al lowed

as part of the

conf igu rat ion of theSWCV.

Connect ion informat ion

for the target system ismainta ined as part of the

SWCV.


12/22


Message Interfaces based on RFC/Idoc

The connection parameters for the back-end SAP system must be specified in the

Software Component version. Must log on with a user that has the authorizations required to import interfaces. For an IDOC, the definition of the IDOC, the segments, records, and data elements of the

IDOC will be imported. For an RFC, the Input, Output, and Fault types for the interface will be imported

Namespaces are preset:

o urn:sap-com:document:sap:idoc:messages

o urn:sap-com:document:sap:rfc:functions


13/22


Interface Objects And WSDL

Message types in the Integration Repository translate to message elements in the WSDL

standard. Data Types in the Integration Repository map to type elements in WSDL. Message/Service Interfaces are portType elements in WSDL .


14/22


Context Objects

Context Object

Pointer to a specific element (field) within the message, for future

reference.

Encapsulate access to data that is contained in the payload or in the

header (technical context objects) of a message


15/22


Mapping Techniques In PI

Message mapping

o Graphical design and test environment

o Queue-based model allows handling of very large documentso Extensible via Java user-defined functions

XSLT

o Open standard

o Portable

o Extensible via Java user-defined functionso Memory overhead for very large documents

Java

o Flexibility of Java programming language

o Java mapping program is responsible for parsing/rendering XML

ABAPo Leverage existing ABAP base

o ABAP mapping program is responsible for parsing/rendering XML


16/22


Mapping Objects: Message Mapping

Graphical mapping tool

Graphically define mapping rules between source and target

Message types

Queue-based model allows for handling of extremely large

documents

Drag-and-drop

Generates internal Java code Built-in and user-defined functions (in Java)

Integrated testing tool

N: M mapping possible for use with BPM only!


17/22


Mapping Objects: Mapping Editor

The source message appears on the left-hand side of the screen, and the target message

appears on the right.

Functional transformations can be made using a library of built-in functions. The graphical editor includes a Test tab to load an instance of the source document and test

the mapping.


18/22


Mapping Objects: Operational Mapping

Representation of the mapping at the interface level

Assign mapping program(s) between source and target message

types:o Message mapping

o XSLT mapping

o Custom Java mapping

o ABAP mapping

Mapping programs can be combined in a sequence N: M interface mapping possible (for use with BPM only!)

For synchronous interfaces, a request and response mapping can

be Provided


19/22


Import/ Export Functions

XSLT: eXtensible Style sheet Language Transformation;

WSDL: Web Service Description Language;

XSD: XML Schema Definition;

DTD: Document Type Definition;

BPEL: Business Process Execution Language Objects in the Integration Repository are based on open

standards

The import function for WSDL,XSD and DTD filesenables you to upload message definitions from external

sources. The object type External Definition is a container which

is used to make external Message definitions available

in the Integration Repository.


20/22


Proxy Generation

Proxies separate Business

Application Logic from the

Integration logic of the PI

Proxies are generated from the

WSDL description of the interface

objects

SPROXY Transaction used for

generating Proxies Proxy will have the same attributes

as the message interface:

o Inbound, outbound

o Synchronous, asynchronous

Outside-in development approach

o Adapter-less, out-of-the-boxintegration

o For applications based on SAP

Web AS 6.20 or above (ABAP

and Java)


21/22


Create Proxy -SPROXY

The counterparts to outbound message interfaces in application systems are client proxies. The counterparts to inbound message interfaces in application systems are server proxies. In the case of synchronous interfaces, the method is called EXECUTE_SYNCHRONOUS. In the case of asynchronous interfaces, the method is called EXECUTE_ASYNCHRONOUS. Proxy generation saves a reusable data type in the ABAP Dictionary for global XSD data types,

for example data elements or structures.


22/22

2009 Deloitte Touche Tohmatsu

PI FastTrackCourse ESR

Documents

Transcript of PI FastTrackCourse ESR