SAP XI Integration Repository

Agenda
Topics
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
SAP AG 2002, Title of Presentation, Speaker Name / 1
Integration Repository
Agenda
XI 3.0 Integration Repository Overview and concepts Software components and namespaces Interface objects Proxy generation Mapping objects Business Process objects Miscellaneous
Agenda
Business Process in a distributed landscape
Before starting an XI Integration project, a component view of the business process requirements must be established
External interfaces in a distributed landscape
XI Integration is interface-driven. An interface represents: The transfer of data between two components Synchronous or asynchronous message exchange
Software Components, interfaces and mappings
Design Time
Integration Builder Integration Repository
Scenario Editor
Process Editor
Business Scenarios
Business Processes Mappings Context Objects Message Interfaces
BPEL XSLT Java XPath WSDL
Mapping Editor Condition Editor
J2EE/ABAP
Proxies
Interface Editor
Message Types Data Types
XSD
SAP Web AS 6.20
Software Component Version
Software Component
System Landscape Directory

Agenda
Software component version

Primary container for all Integration Repository objects Imported directly from the SLD Usage dependencies from SLD are reflected in the Repository (Basis objects)
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
Namespaces
(Globally) unique identifier for related Integration Repository objects Usually vendor-based
Same concept as XML namespaces Several namespaces can be assigned to the same SWCV Naming convention:
URL URN
http://sap.com/xi/demo urn:sap-com:xi:demo
(URL without protocol assignment)
Agenda
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 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
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
Proxy Generation Overview

Separation of Business Application logic from XI connectivity
Outside-in development approach

Adapter-less, out-of-the-box integration For applications based on SAP Web AS 6.20 or above (ABAP and Java)
Integration Engine
Proxy framework Hide technical details from application developer

Transform language-specific data structures into XML and vice-versa Ensure technical connectivity with the Integration Engine, guaranteed delivery
Proxy
Business Function Application System
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
Agenda
Mapping concepts
Mapping
Transformation from one message structure to another Transformation rules defined by mapping program
<hh:book-flight xmlns:hh="..."> <hh:customer> <hh:first-name>Micheal</hh:first-name> <hh:surname>Moore</hh:surname> </hh:customer> <hh:booking-data> <hh:airline>Airline Kingdom</hh:airline> <hh:connection>AK087</hh:connection> <hh:date>2001-11-22</hh:date> <hh:class>business</hh:class> </hh:booking-data> </hh:book-flight>
Value Mapping
<ak:BookFlight xmlns:ak="..."> <ak:Date>22.11.2001</ak:Date> <ak:Flight>087</ak:Flight> <ak:Passenger>Micheal Moore</ak:Passenger> <ak:Class>2</ak:Class> <ak:Agency>Happy Holiday</ak:Agency> </ak:BookFlight>
Structure Mapping
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
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!
Message Mapping: Mapping Editor
Structure Overview
Source Structure
Target Structure
Data-Flow Editor
Target Field Mapping
Mapping Objects: Interface mapping

Representation of the mapping at the interface level Assign mapping program(s) between source and target message 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 mapping can be provided
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 reimported.
Agenda
Business Scenario Objects

A Business Scenario
describes a complete collaborative process from the XI point of view
main
focus on the complete message exchange only the public part of the process
describes
An Action
describes a function (a process) within one component that is involved in the message exchange refers to the interfaces that can be used to perform that function may be used by one or more business scenarios
Travel Agency Web AS 6.20 Airline Web AS 6.20
Check Seat Availability
Determine Seat Availability
Send Flight Booking Order
Book Flight
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
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
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 Visualisation in XI Integration Builder

Scenario Component View
Product A
Process - Flow
Product Template
Send Receive
Process
Product A
Product B
IFabs1 IFabs2
IFabs1 IFabs2
Wait for response
Wait for Negative Acknowledgement
[timeout]
Alert Alert
Send response back to initiator
Send
[continue]
IFabs
IFabs
[one out of three]
Scenario: integration view of an abstract collaborative business process
BPM process: executable collaborative business process
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

*the process interface requires XI interfaces of type abstract in integration repository
Agenda
Import / Export Functions

Objects in the Integration Repository are based on open standards

BPEL
BPEL
Business Processes
XSLT Java
The import function for WSDL, XSD and DTD files enables you to upload message definitions from external sources.
Mappings
WSDL XSD DTD
Interfaces
After conversion to WSDL they can be used to define message mappings and message WSDL interfaces. XSD The object type External Definition is a container which is used to make external message definitions available in the Integration Repository.
IDocs, RFCs
SAP System
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
The Integration Repository supports versioning of all repository objects at software component level. Support Packages of a software component version are also supported. Message interfaces can 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.

SAP XI Integration Repository

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP XI Integration Repository

Uploaded by

Copyright:

Available Formats

Agenda

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

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

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

Business Process in a distributed landscape

External interfaces in a distributed landscape

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

Software Components, interfaces and mappings

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

Mapping Editor Condition Editor

Message Types Data Types

SAP Web AS 6.20

Software Component Version

System Landscape Directory

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

Software component version

the import of IDoc/RFC interfaces

One or more namespaces

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

(URL without protocol assignment)

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

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

Interface Objects: Data type

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

Interface Objects: Message type

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

Interface Objects: Message Interface

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

Interface Objects: Context Objects

2. Use Context Object in Message Interface

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

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

Proxy Generation Overview

Outside-in development approach

Proxy framework Hide technical details from application developer

Business Function Application System

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

Same concept for ABAP and Java, but different procedure

See the documentation for more details

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

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

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

Memory overhead for very large documents

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

Mapping Objects: Message mapping

Queue-based model allows for handling of extremely large documents

Generates internal Java code

N:M mapping possible for use with BPM only!

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

Message Mapping: Mapping Editor

Target Field Mapping

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

Mapping Objects: Interface mapping

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

Mapping objects: imported archives

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

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

Business Scenario Objects

Check Seat Availability

Determine Seat Availability

Send Flight Booking Order

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

What are XI Business Scenarios used for?