SAP XI Integration Repository

7/30/2019 SAP XI Integration Repository

1/35

SAP AG 2002, Title of Presentation, Speaker Name / 1

Topics

Agenda

Introduction to SAP XI 3.0

System Landscape Directory

Integration Repository

Integration Directory

Monitoring

Adapter Framework

Business Process Management

Server Administration

Security

B2B and Industry Standards


2/35


Agenda


XI 3.0 Integration Repository

Overview and concepts

Software components and namespaces

Interface objects

Proxy generation

Mapping objects

Business Process objects

Miscellaneous


3/35


Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous


4/35


Business Process in a distributed landscape

Before starting an XI Integration project, a component

view of the business process requirements must be

established


5/35


XI Integration is interface-driven. An interface represents:

The transfer of data between two components

Synchronous or asynchronous message exchange

External interfaces in a distributed landscape


6/35


Software Components, interfaces and mappings


7/35 SAP AG 2002, Title of Presentation, Speaker Name / 7

SAP Web AS

6.20

Design Time


System Landscape Directory

Software Component

Software Component Version

J2EE/ABAP

Proxies

Message Interfaces

Message Types

Integration Builder

Interface Editor

Data Types

Business Processes

Mappings

Business Scenarios

Context Objects

Scenario Editor

Process Editor

Mapping Editor

Condition Editor

BPEL

XSLT

JavaXPath

WSDL

XSD



Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous



Software component version

For each software component version, the following can be assigned: A connection to an existing SAP system

for the import of IDoc/RFC interfaces

One or more namespaces

Primary container for all

Integration Repository objects

Imported directly from the SLD

Usage dependencies from SLD

are reflected in the Repository

(Basis objects)



Namespaces

Same concept as XML namespaces

Several namespaces can be assigned to the same SWCV

Naming convention:URL http://sap.com/xi/demo

URN urn:sap-com:xi:demo

(URL without protocol assignment)

(Globally) unique identifier for related Integration Repository

objects

Usually vendor-based



Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous



Interface Objects: Data type

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



Interface Objects: Message type

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



Interface Objects: Message Interface

The Message Interface is the highest-level representation of XML

metadata.

Inbound or outbound (respective to the application), or

abstract (for BPM only)

Synchronous or asynchronous

Asynchronous refers to one message type

Synchronous refers to two message types (request andresponse)

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



Interface Objects: 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

Example: in CREMAS03 (Vendor master) IDoc:

zipcode = CREMAS03/IDOC/E1LFA1M/PSTLZ

1. Create Context Object 2. Use Context Object

in Message Interface



Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous



Application

System

Proxy Generation Overview

Separation of Business Application logicfrom XI connectivity

Outside-in development approach

Adapter-less, out-of-the-box integration

For applications based on SAP Web AS6.20 or above (ABAP and Java)

Proxy framework Hide technical detailsfrom application developer

Transform language-specific datastructures into XML and vice-versa

Ensure technical connectivity with theIntegration Engine, guaranteed delivery

Business

Function

Proxy

Integration

Engine



Proxy generation

Message interfaces are the basis for proxy generation

Proxy will have the same attributes as the message interface: Inbound, outbound

Synchronous, asynchronous

Same concept for ABAP and Java, but different procedure

J2EE proxies are generated from the IR as .JAR files

ABAP proxies are generated from the application client, based

on the WSDL representation of the message interface

Some rules and restrictions are in effect for the conversion of

XSD Data types into Java or ABAP types, respectively

See the documentation for more details


19/35


Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous


20/35


Micheal

Moore

Airline Kingdom

AK087

2001-11-22

business

22.11.2001

087

Micheal Moore

2

Happy Holiday

Mapping concepts

Mapping

Transformation from one message structure to another

Transformation rules defined by mapping program

Structure Mapping

Value

Mapping


21/35


Mapping techniques in XI

Message mapping

Graphical design and test environment

Queue-based model allows handling of very large documents

Extensible via Java user-defined functions

XSLT

Open standard

Portable

Extensible via Java user-defined functions

Memory overhead for very large documents

Java

Flexibility of Java programming language

Java mapping program is responsible for parsing/rendering XML

ABAP

Leverage existing ABAP base

ABAP mapping program is responsible for parsing/rendering XML


22/35


Mapping Objects: Message mapping

Graphical mapping tool

Graphically define mapping rules between source and targetmessage 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!


23/35


Data-Flow Editor

Structure Overview

Source Structure Target Structure

Target Field Mapping

Message Mapping: Mapping Editor

M i Obj t I t f i


24/35


Mapping Objects: Interface mapping

Representation of the mapping at the interface level

Assign mapping program(s) between source and targetmessage types:

Message mapping

XSLT mapping

Custom Java mapping

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 mappingcan be provided

M i bj t i t d hi


25/35


Mapping objects: imported archives

The object type imported archive is for importing externally

defined programs into the Integration Repository:

XSLT stylesheets

Java mappings

Java extensions to XSLT mappings

Java classes to be imported in a user-defined function for message

mapping

All files to be imported must be archived (ZIP or JAR format)

The archive is uploaded from user workstation.

Integration Repository can serve as central maintenance

location for imported objects

XSLT and text files can be edited directly from IR.

Java CLASS files must be edited and recompiled locally, then re-

imported.

I t ti R it


26/35


Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous

B i S i Obj t


27/35


Business Scenario Objects

A Business Scenario

describes a complete collaborative process from the XI point of

viewmain focus on the complete message exchange

describes only the public part of the process

An Action

describes a function (a process) within one component that isinvolved in the message exchange

refers to the interfaces that can be used to

perform that function

may be used by one or more business scenariosCheck Seat

Availability

Send Flight

Booking Order

Determine Seat

Availability

Book Flight

Travel Agency AirlineWeb AS 6.20Web AS 6.20

Wh t XI B i S i d f ?


28/35


What are XI Business Scenarios used for?

Business Scenario = Plan of Integration

Business Scenario driven modelling and

visualization of integrated business processes Collects all XI objects of an integration scenario

Enables single entry point and access to all objects

Provides structured documentation

Input for XI configuration Business Scenario guided configuration

Generation of configuration objects

Products, Functions

Connections (Interfaces, Mapping)

Input for implementation

Involved functions and services

Products and system requirements

B i P Obj t


29/35


Business Process Objects

You can design new objects for executable business processes

by using the graphical Process Editor.

You can use different modeling elements and patterns to design a

stateful, cross-component business process.

The following modeling patterns and elements are supported:

Receive messages and trigger process

Send, transform (merge or split) messages

Collect messages

Multicast

Serialization

Process control elements such as switch, assign, fork, wait, block,loop, control

Deadlines, exception handling, conditions

B siness Processes & B siness Scenarios


30/35


Business Processes & Business Scenarios

Business Process can be incorporated

in a Business Scenario

Representation in a swim lane

Treated as a Business System

Navigation from Scenario to Process

Concept: Integration of Scenario and Process


31/35


Concept: Integration of Scenario and ProcessVisualisation in XI Integration Builder

Process is assigned to a swimlane visualization of the public parts of the process- process is part of a software component of the product- navigation from swimlane in scenario to process object

One action and connection per abstract interface* of the process- checked consistency between process interface and connections in scenario

Executable process (behind the swimlane) for Business Process Engine

Product

A

IFabs1

IFabs

Product

A

Scenario Component ViewProduct

B

Product

Template

IFabs2

Process Send

Wait for response Alert

[timeout]

Send response

back to initiator

Wait for Negative

Acknowledgement

Alert

[one out of three]

[continue]

Process - Flow

Receive

Send

IFabs1

IFabs2

IFabs

Scenario: integration view of an

abstract collaborative business process

BPM process: executable collaborative

business process

*the process interface requires XI interfaces of type abstract in integration repository



32/35


Agenda





Interface objects

Proxy generation

Mapping objects


Miscellaneous

Import / Export Functions


33/35


Import / Export Functions

Objects in the Integration

Repository are based on open

standards

The import function for WSDL,

XSD and DTD files enables you to

upload message definitions from

external sources.

After conversion to WSDL they

can be used to define message

mappings and message

interfaces.

The object type External

Definition is a container which is

used to make external message

definitions available in the

Integration Repository.

Integration

Repository

Business Processes

Mappings

Interfaces

SAP System

IDocs, RFCs

XSLT

Java

WSDL

XSD

DTD

BPEL

WSDL

XSD

BPEL

Import of RFC / IDoc interfaces


34/35


Import of RFC / IDoc interfaces

Import of RFC / IDoc metadata

from existing SAP system

Based on connection parameters

specified in the SW Component

RFC and IDoc metadata cannot

be modified within XI

Namespaces are preset:

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

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

XSD and WSDL representation

available for export

Procedure: right-click on

imported objects and follow the

wizard

Miscellaneous


35/35

Miscellaneous

The Integration Repository supports versioning of all repository

objects at software component level. Support Packages of a

software component version are also supported.

Message interfacescan be marked as abstract (instead of

inbound or outbound). This applies to interfaces which are

used in BPM or which are handled by adapters.

Advantage: There is no need to define two interfaces (inbound

and outbound) if their structure is identical.

It is possible to enhance data types shipped by SAP with

customer-specific fields. These enhancements will not be lost in

the event of a release upgrade.

The information modeled in business scenarios can be used to

describe product release combinations. A separate component

view can be defined for each release.

Documents

SAP XI Integration Repository