Tbit40 en Coll44 Show

© SAP AG <Course Number> Course Overview - 1

© SAP AG 2004

TADMBO Implementation&Operation II

THE BEST-RUN BUSINESSES RUN SAP

© SAP AG 2004

TBIT40Implementation & Operation II

2004/Q4

Material number: 50069569

SAP Exchange Infrastructure 3.0

TBIT40 XI Foundations

© SAP AG 2003, PM Process Integration 2

Lecture topics

Topics

XI Overview

System Landscape Directory

Integration Repository

Integration Directory

Runtime

Runtime Workbench

Adapter Framework

Business Process Management

Server Administration

Security

B2B and Industry Standards

© SAP AG 2003, PM Process Integration 3

Exercise topics

Topics

Exercise 1: File to IDoc

Exercise 2: File to JDBC

Exercise 3: HTTP to (t)RFC

Exercise 4: ABAP Proxy to RFC

Exercise 5: BPM Async-Sync

SAP Exchange Infrastructure – Process Centric Integration

XI Overview

SAP NetWeaverTM

Process Integration

© SAP AG 2004, TBIT40 01 XI Overview 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Exchange Infrastructure Overview: Unit Objectives

After completing this unit, you will be able to:

Explain need for and the benefits of the SAP Exchange Infrastructure.

Describe the components of the SAP Exchange Infrastructure.

Detail the key functionality of SAP XI.


SAP Exchange Infrastructure

Agenda

Positioning

Architecture Overview

Key Functionality

Summary


Mission

SAP XI is an integration technology and platform……for SAP and non-SAP applications.

…for A2A and B2B scenarios.

…for asynchronous and synchronous communication.

…for cross-component Business Process Management.

BUILDER

SERVER


SAP NetWeaver™

SAP NetWeaverSAP NetWeaver™™SAP NetWeaver™

Com

posi

te A

pplic

atio

n Fr

amew

ork

PEOPLE INTEGRATION

Multi channel access

Portal Collaboration

INFORMATION INTEGRATION

Bus. Intelligence

Master Data Mgmt

Knowledge Mgmt

PROCESS INTEGRATION

Integration Broker

BusinessProcess Mgmt

APPLICATION PLATFORM

J2EE

DB and OS Abstraction

ABAP

Life Cycle M

gmt

Unifies and aligns people, information and business processes

Integrates across technologies and organizational boundariesA safe choice with full .NET and J2EE interoperability

The business foundation for SAP and partners

Powers business-ready solutions that reduce custom integrationIts Enterprise Services Architecture increases business process flexibility


One Customer’s Complex Integration Landscape

SAPMarketsEnterprise Buyer

(Professional Edition)

CollaborativeEngineering

SAP R/3: ~30 systems,

versions 3.1I – 4.6B

e-Procurement: in 10 units

ERP legacy: ~15 systems

e-Sales

Technical Systems

Trading

ERP non-SAP: ~25 systems,

different versions


Exchange Infrastructure for Collaboration

Integration Engine &Bus Infrastructure

Shared central knowledge,

Small number of peer-to-peer connections

Direct Connections

Integration challengeQuadratically

growing complexity

Database Integration

Integration by single centralized data

model

Enterprise ResourcePlanning

Inter-/Intra-EnterpriseCo-operation

CollaborativeBusiness


The Solution – Shared Business Semantics

Shared Integration KnowledgeIntegration scenarios, business processes, Web services,

interfaces, mappings, routing rules, ... For a common understanding how collaborative business

processes workEnabling distributed executionShared classification and discovery of businesses and services

Support for UDDI (Universal Description, Discovery and Integration)

Loose coupling via XML messagingAsynchronous communication as far as possibleSynchronous communication where required

EvolutionAllow easy and non-disruptive addition of new services and

processesIntegration of existing and new SAP componentsIntegration of existing customer and 3rd party components


Advantage: Pre-delivered Integration Content

SUS

EBP

3rd PartyCatalog

DataSAP solutions bring their integration meta-data (CRM, SRM, SCM, xAppslike xRPM, etc.)

Delivered with the Integration Repository of SAP XI

BenefitsOut-of-the-box integration of SAP solutions

Simplified upgrade of SAP Solutions

Versioning and modification management of integration meta-data


Advantage: Openness and Interoperability

3rd PartyApplication

SAPApplication

3rd PartyMiddlewareComponent


Connect to existing integration solutionsThrough JMS messaging (e.g. MQSeries)Through SOAP

Use open, XML based standards for integration

Incorporate existing functionality into new processes

Adapters (JCA)Web Services (WSDL)

BenefitsLeverage existing investments

Arrive at new integration landscape in an evolutionary manner

Allow easy and non-disruptive addition of new services and processes



Agenda

Positioning


Key Functionality

Summary


SAP Applications Using XI

More and more SAP applications are making use of SAP Exchange Infrastructure and introducing XI to a customer landscape

The following applications now use XI:xApps (such as xRPM, Resource and Program Management)MDM (SAP Master Data Management)SRM (SAP Supplier Relationship Management)ICH (SAP Inventory Collaboration Hub within SAP SCM)BI (SAP Business Intelligence, for Global Spending Reporting)R/3 Enterprise (for Industry Standard Support)CRM (SAP Customer Relationship Management, for Extended Order

Management)SBO (SAP Business One)


Component Overview

Execution of Collaborative Business Processes

Shared Collaboration Knowledge

Integration Builder

IntegrationDirectory

(ID)

IntegrationRepository

(IR)

IntegrationServer

(IS)

System Landscape Directory (SLD)

Central Monitoring

SAPSystems

3rd PartySystems


Marketplace/BusinessPartner


Capturing Shared Knowledge at Design/Config Time

Integration Engine

Integration RepositoryProduct to be used at design/development timeAt SAP, partner, and customer siteShipped along with content

Integration DirectoryProduct to be used at configuration timeAt customer siteContent partially derivable from Integration Repository by configuration tools

Integration EngineProduct to be used at runtimeAt customer siteRelies on content of Integration Directory


Exchange Infrastructure – Integration Landscape

SAP3.x

SAP3.x

SAP4.x

SAP4.x

ThirdParty

System

ThirdParty

System

SAPAdapter

3rd Party Adapter

mySAPSolution*mySAP

Solution*

FirewallBusinessPartner

BusinessPartner

BusinessPartner

BusinessPartner

BusinessPartner

BusinessPartner

Market-place

Market-place



Integration Server connects to different SAP and Non-SAP Systems, to Business Partners and Public Marketplaces

* based on SAP Web Application Server 6.20+



Agenda

Positioning


Key Functionality

Summary


Integration Builder – Common tool framework

DB

UI C

lientServer



Integration Builder Server Framework

Query Service & Cross ReferencesImport/Export & CMS interfaceInternationalizationChange list ManagementVersioningLockingAuthorization & Authentication

Integration Builder Client Framework

Layout Building BlocksPersonalizationNavigation

Client-server frameworkConsistent look and feelBased on Java Web Start


Design

SystemLandscapeDirectory Software Component

Software Component Version

SAP

Web A

S

J2EE/ABAP

Proxies


BPEL

XSLTJava

XPath

WSDL

Integration Builder

Data Type Editor

MessageInterfaces

Message TypesData Types (XSD)

BusinessProcesses

Mappings

BusinessScenarios

ContextObjects

Scenario Editor

Process Editor

Mapping Editor

Condition Editor

Pre-delivered Integration Content for mySAP solutions

Open for collaboration knowledge of non-SAP systems, using open standards (e.g. WSDL)

Provision to enhance XI design time objects by customers / partners

Java based graphical tools


Configuration

Integration Builder


Business Processes

Routing Rules

Business Scenarios

Receiver Determination Rules

Interface Determination Rules(including Mapping Assignment)

ConfigurationEditors

ConfigurationWizards

Collaboration Profiles

Parties & ServicesChannels

Collaboration AgreementsSecurity

Adapt integration content to specific configuration

Derive integration content from Integration Repository

Open for Customer to add collaboration knowledge relevant to non-SAP components

Java based graphical tools

Central configuration for B2B processes and BPM

Centralized adapter configuration



Describes concrete system landscape of customer installation

What component is actively available on which machine/instance/client, etc.

Information about domain contained, i.e. in which network environment (local / remote) are components accessible

Any number of different landscapesAny type of component (SAP, partner

products, other packages, legacy systems ..)

Open architecture, based on CIM

Base for structuring design objects in the repository, and for configuring routing rules in the directory


Runtime

Central Monitoring

SAP Web AS ≥ 6.20SAP

System


SystemLandscapeDirectory

XIProtocol RosettaNet, …

XIProtocol

Business Process Engine

Integration Engine

Adapter Engine

IDocsRFCs

Proxy

3rd PartyApps

FileDB

JMS

Apps of BusinessPartner Apps of

(small)BusinessPartner

Local Integration Engine

Proxy Runtime

PartnerConnectivity

Kit


Decoupling Of Integrated Applications

3rd Party Adapter

Firewall


IntegrationServer

SAPR/3 3.1i

SAP R/3Enterprise

3rd PartyApp

Marketplace

BusinessPartner

BusinessPartner

BusinessPartner

SAPAdapter

ReceiverDetermination

ChannelDetermination

Mapping

Routing Rules

Mappings


A sample message flow from one application to another is depicted

Logical decoupling of senders and receivers

Decoupling of sender and receiver interface formats


XI Runtime Environment

FunctionalityCommunication

Synchronous: always “best effort”

Asynchronous: exactly-once or exactly-once-in-orderRetry mechanism

Acknowledgment is supported

Including error handlingSynchronous: error messages sent back to sender

Asynchronous: errors made persistent

Transport of (XML) messages based on HTTP or HTTPS“SOAP Messages with Attachments” as wire format

Messaging protocol based on SOAP envelope with header extensions


Connectivity / Adapters

Execute Collaborative Business ProcessesExecute Collaborative Business Processes

Central Monitoring –ensures collaboration reliabilityCentral Monitoring –

ensures collaboration reliability

SAPSystems

SAPSystems

Partner Connectivity Kit

Partner Connectivity Kit




Integration Server

Integration Engine

Central Adapter Engine

Adapter FrameworkMessagingQueuing

Security Handling

Resource

Adapter

ApplicationTechn. System

File/DB/JMS

Adapter framework based on Java Connector Architecture (JCA)

Adapters work as plug-ins to the Adapter Framework

Adapter Development Kit - customers and partners can develop adapters

SAP NetWeaver certification of 3rd party adapters based on JCA adapter framework

Reselling of JCA adapters from selected partners (iWay, Seeburger)


Adapter Architecture

Integration Server

J2SEAdapter Engine

Partner ConnectivityKitOptional Decentral

Adapter EngineCentral Adapter Engine

Integration Repository / Integration Directory / System Landscape Directory


Integration Engine


Security Handling

Resource

Adapter

Resource

Adapter

Resource

Adapter

Adapter FWMessagingQueuing

Security Handling


Security Handling

PCK Configurationand Monitoring

RFC

/IDoc

Adapter

Adapter



ApplicationTechn. System

File/DB/JMS

FileDB

JMSSAP

System


Cross-Component Business Process Management

BusinessSystem

1

Integration Server

BusinessSystem

3

BusinessSystem

21 2 3

Messages

Message

4

Orchestrates message choreography based on stateful interactions

Design, execute and monitor automated processes across applications and systems

Provides process control in the central technology layer

Contains a Graphical Modeler

Integral part of XIModeling enables linkage to XI design

objects: interfaces, mappings …BPM runtime is embedded in the Integration

Server runtime

Adheres to standardsIndustry Standard support (BPEL4WS)Import/ export of process definitions

BusinessSystem

4


SAP XI and B2B enablement (1)Industry B2B

Protocols



(IR)


(ID)

IntegrationServer

(IS)Partner

ConnectivityKit

Apps of(small)

BusinessPartner

Apps of (small)BusinessPartner

XIProtocol

Enable business partners to conduct B2B processes with XI

Security enrichments for B2BDigital Signature and Encryption

Partner Connectivity KitEnable partners of XI customers to conduct XML document

exchange with XI


SAP XI and B2B enablement (2)


(ID)

Collaboration ProfileCollaboration Agreement Industry B2B

Protocols



(IR)

IntegrationServer

(IS)Partner

ConnectivityKit

Apps of(small)

BusinessPartner

Apps of (small)BusinessPartner

XIProtocol

Industry StandardsContent

Industry Standards Content (e.g. RosettaNet PIPs, specific mappings)

Collaboration Profile and Collaboration Agreement in IntegrationDirectory

Manages technical characteristics of partners to facilitate document exchange, such as

Party identificationMessage formats and versions supportedSecurity requirements


Value-added Web Services Through XI

Web ServiceClient

(SAP/non-SAP)

Proxy


Proxy Runtime

Web ServicesFramework

SOAP

IDocsRFCs

Web ServiceClient

(SAP/non-SAP)

‘Managed’ Web Service

‘Basic’ Web Service

MappingRouting

Business Processes

Adapter

SOAP

XI Protocol or

SOAP

Adapter

Integration Server

3rd PartyApp

SAP Web AS ≥ 6.40

SAPSystem


Runtime Workbench

Central monitoring tool for the complete XI landscape

Component monitoringMessage monitoringGraphical end-to-end

monitoringPerformance monitoring

Smooth integration with CCMS

Easy ConfigurationExploiting System Landscape

DirectoryWeb-based user interface


Summary

SAP XI addresses integration challengesIs a A2A and B2B integration solutionIndustry standard supportSupports the whole process integration lifecycleComes with pre-delivered contentIs suited for heterogeneous integration landscapesIs interoperable based on open standards

SAP XI is SAP’s strategic process integration platformmySAP SRM, mySAP SCM, SAP for Retail, …Synergetic use inside SAP NetWeaver with SAP MDM, BPM, CAF, …

SAP XI is more than just an Integration BrokerCross-Component BPM


Exchange Infrastructure Overview: Unit Summary

You should now be able to:

Explain need for and the benefits of the SAP Exchange Infrastructure.

Describe the components of the SAP Exchange Infrastructure.

Detail the key functionality of SAP XI.



© SAP AG 2004, TBIT40 02 SLD 2

Topics

Lecture topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security




Explain the purpose of the System Landscape Directory and its role as an information provider.

Describe the content types in the System Landscape Directory.

Create Software Component descriptions in the System Landscape Directory.

Define Technical Systems in the System Landscape Directory.

Define Business Systems in the System Landscape Directory.

System Landscape Directory: Unit Objectives


System Landscape Directory Overview

Central information provider for NetWeaver system landscapes

Manage software components and platform dependencies

Facilitate Installations, upgrades and transports

Based on Common Information Model (CIM) of the Distributed Management Task Force (DMTF)

Basis for SAP Solution Manager

Information provider for SAP XI


Aspects of system landscapes


SLD content type

Component InformationDescribes building blocks of solutions Describes possible combinations and dependenciesDelivered by SAP, extensible by customer

Landscape DescriptionInformation on installed landscape elementsCustomer-specific

SAP XI utilizes both types of content:

Integration Repository: Component Information

Integration Directory: Landscape Description



Synchronize, XML

PPMS

MasterComponentRepository

MasterComponentRepository

SAP

ComponentTypes

LandscapePatterns

PossibleCombinations

Customer

Update



ComponentinformationComponentinformation

CIMCIM

3rd-Party / CustomerComponent Types

3rd-Party / CustomerComponent Types

LandscapedescriptionLandscapedescription

CIMCIM

Any Landscape Element

Any Landscape Element

Customer LandscapeCustomer Landscape

Applications and ToolsApplications and Tools

GraphicalDesign Tool

.. ....

Software LogisticsSoftware Logistics

.. ....1 21

Technical Configuration

Technical Configuration

..

ValidationValidation

....

Registration

WBEM,XML

WBEM,XML


SLD: Products and Software Components

Software ComponentProduct

Product Version Software Component Version

Software Feature

1

* *

*

* *

0..1 0..1


Example: SAP APO

© SAP AG 2004, TBIT40 02 SLD 10

Example: workshop exercise

Product

Product Version

Software Component

Software ComponentVersion

1 1

nn

Software Feature:Associations

TBIT40_WORKSHOP ##, 1.0of SAP

TBIT40_WORKSHOP, 1.0of SAP

TBIT40_WORKSHOP of SAP

TBIT40_WORKSHOP ## of SAP

© SAP AG 2004, TBIT40 02 SLD 11

Defining the Software Component

Select the Product from the drop-down

Enter the software vendor

Enter the Software Component Name

Enter the Software Component version (SWCV)

Choose “Create”

To define a Software Component:

From the main screen of the SLD, choose “Software Catalog.”

Use the drop-down to select the Software Components type, and then select “New Component” to start the wizard.

© SAP AG 2004, TBIT40 02 SLD 12

SLD: Technical System

Technical SystemWebAS ABAP

Standalone JAVA

Third Party

Name; host name; system number; ReleaseInstalled clientsMessage Server Installed Products

Installed Products

Business System

Business Systems

Business Systems

Technical System ID

WebAS Java

Name; host name; SID; System Home

© SAP AG 2004, TBIT40 02 SLD 13

Defining the Technical System

From the Technical System browser choose “New Technical System…”

… select (and add) the products and components that are installed on the technical system...

… click “Finish.”

… specify the Technical System Type…

© SAP AG 2004, TBIT40 02 SLD 14

SLD: Business System

Business SystemWebAS ABAP

WebAS Java

Third Party Systems

Related Integration ServerclientInstalled Products

Installed Products

Technical System

Technical System

Technical System

Name

Standalone Java

Related Integration Server

Related Integration Server

Name Technical System

© SAP AG 2004, TBIT40 02 SLD 15

Defining the Business System

Give the system a unique name…

… specify the associated Technical System (and Logical System, if necesary)…

… select the installed products (from the technical system

definition)…

… and the Related Integration Server

… click “Finish.”

© SAP AG 2004, TBIT40 02 SLD 16

SLD and XI Integration Repository


Product Version

Product

Software Component


Integration Repository (Design)

Application Component

Role

Product Version

Software ComponentVersion

Business Scenario

Interface Objects

Mapping Objects

© SAP AG 2004, TBIT40 02 SLD 17

SLD and Repository: usage dependencies


Software Component Version A

SAP Integration BuilderRepository (Design)

Software ComponentVersion A

Basis objects

...

Software Component Version B

Usage Dependency

Software ComponentVersion B

X

X

A dependency can be defined in the SLDThis dependency will be automaticallydetected in the Integration Repository

© SAP AG 2004, TBIT40 02 SLD 18

SLD and Directory

SAP Integration Directory (Configuration)

Routing Relations

Sender Service:

Receiver Service:

Business System

Business System

Business System

Technical System


A service object in the Integration Directory can be derived from the SLD.

© SAP AG 2004, TBIT40 02 SLD 19

Summary: object structure in SLD

© SAP AG 2004, TBIT40 02 SLD 20


Explain the purpose of the System Landscape Directory and its role as an information provider.

Describe the content types in the System Landscape Directory.

Create Software Component descriptions in the System Landscape Directory.

Define Technical Systems in the System Landscape Directory.

Define Business Systems in the System Landscape Directory.

System Landscape Directory: Unit Summary



© SAP AG 2004, TBIT40 03 Integration Repository 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Integration Repository: Unit Objectives


Describe the Integration Repository and the objects that are created in it.

Understand various Interface Objects and their roles in integration scenarios.

Detail the use of web standards in the descriptions of interface objects in the Integration Repository.

Explain the Proxy functionality in XI.

Describe message mappings and list the different types of mappings available in XI.

Explain Business Processes and their role in integration scenarios.

Describe how to import various objects into the Integration Repository.


Integration Repository: Business Scenario

You need to implement and Integration Scenario.

You must first create the appropriate objects and processes in the 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




Interface objects

Proxy generation

Mapping objects


Miscellaneous


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 componentsSynchronous or asynchronous message exchange


Software Components, Interfaces And Mappings


Design Time

SAP Web AS≥ 6.20



Software ComponentSoftware Component Version

J2EE/ABAP

ProxiesMessage Interfaces

Message Types

Integration Builder

Interface EditorData Types

Business Processes

Mappings

Business Scenarios

Context Objects

Scenario Editor

Process Editor

Mapping Editor

Condition Editor

BPEL

XSLTJava

XPath

WSDL

XSD



Agenda




Interface objects

Proxy generation

Mapping objects


Miscellaneous



Primary container for all Integration Repository objects

Imported directly from the SLDUsage 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 interfacesOne or more namespaces


Namespaces

(Globally) unique identifier for related Integration Repository objects

Usually vendor-based

Same concept as XML namespacesSeveral namespaces can be assigned to the same SWCVNaming convention:

URI http://sap.com/xi/demo

URN urn:sap-com:xi:demo(URI without protocol assignment)



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 possibleExport of data type in XSD format possible


Interface Objects: Message Type

The Message type corresponds to the root of the XML messageName and namespace must match exactly the root of XML

Business documentsThe Message type references one single data typeXSD 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), orabstract (for BPM only)

Synchronous or asynchronousAsynchronous refers to one message typeSynchronous refers to two message types (request and

response)References fault message types for exception handlingWSDL representation available for exportStarting point for proxy generation (ABAP and Java)Context objects can be assigned


Message Interfaces based on RFC/IDoc

Imports must be allowed as part of the configuration of the SWCV.

Connection information for the target system is maintained as part of the SWCV.

A wizard interface walks you through the process of importing RFC’s/IDOC’s


Interface Objects And WSDL


Message InterfaceFlightBooking_Confirm_Out

Output Message Type:FlightBooking_Confirm_Out_Req

Message TypeFlightBooking_Confirm_Out_Req

Data Type:FlightBookingID

Data TypeFlightBookingID

XML Schema (XSD)

<?xml version=“1.0“><wsdl:definitions ...>

<wsdl:portType name=“FlightBooking_Confirm_Out“><wsdl:operation name=“FlightBooking_Confirm_Out“>

<wsdl:input message=“FlightBooking_Confirm_Out_Req“></wsdl:operation>

</wsdl:portType>

</wsdl:definitions>

<wsdl:message name =“FlightBooking_Confirm_Out_Req“><wsdl:part name=“FlightBookingID“

type=“FlightBookingID“></wsdl:message>

<wsdl: types><xsd:schema><xsd:simpleType name=“FlightBookingID“

type=“xsd:nonNegativeInteger“ ></xsd:schema></wsdl: types>


Interface Objects: Context Objects

Context ObjectPointer to a specific element (field) within the message, for

future referenceEncapsulate access to data that is contained in the payload

or in the header (technical context objects) of a messageExample: in CREMAS03 (Vendor master) IDoc:

zipcode = CREMAS03/IDOC/E1LFA1M/PSTLZ2. Use Context Objectin Message Interface

1. Create Context Object



Agenda




Interface objects

Proxy generation

Mapping objects


Miscellaneous


Proxy Generation – Overview

Separation of Business Application logic from XI connectivity

Outside-in development approachAdapter-less, out-of-the-box integrationFor applications based on SAP Web AS

6.20 or above (ABAP and Java)

The Proxy Framework hides technical details from application developer

Transform language-specific data structures into XML and vice-versa

Ensure technical connectivity with the Integration Engine, guaranteed delivery

ApplicationSystem

ApplicationSystem

BusinessFunction

Proxy

IntegrationEngine


Proxy Generation

Message interfaces are the basis for proxy generation

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

Same concept for ABAP and Java, but different procedureJ2EE proxies are generated from the IR as .JAR filesABAP 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


Create ABAP Proxies (Transaction SPROXY)

1

2

3


Generated ABAP ObjectsMessage interfaces can have the mode synchronous or asynchronous.

Furthermore, the type of the message interface determines what type of proxy is generated.

The counterparts to outbound message interfaces in application systems are client proxies. They are called to send a message to an inbound interface. An outbound message interface is mapped to an ABAP object class (prefix CO_).

The counterparts to inbound message interfaces in application systems are server proxies. The proxy generation functions generate an ABAP object interface (prefix II_) for an inbound message interface; you must implement this interface using an ABAP object class to make this service available.

Example: Client proxy (class) generated from Outbound Message Interface


Java Proxy Wizard



Agenda




Interface objects

Proxy generation

Mapping objects


Miscellaneous


Mapping Concepts

MappingTransformation From One Message Structure To AnotherTransformation 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>

<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

Value Mapping


Mapping Techniques In XI

Message mappingGraphical design and test environmentQueue-based model allows handling of very large documentsExtensible via Java user-defined functions

XSLTOpen standardPortableExtensible via Java user-defined functionsMemory overhead for very large documents

JavaFlexibility of Java programming languageJava mapping program is responsible for parsing/rendering XML

ABAPLeverage existing ABAP baseABAP 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

Data-Flow Editor

Structure Overview

Source StructureSource Structure Target StructureTarget Structure

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 mappingXSLT mappingCustom Java mappingABAP 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 stylesheetsJava mappingsJava extensions to XSLT mappingsJava classes to be imported in a user-defined function for message

mapping

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

The archive is uploaded from user workstation.

Integration Repository can serve as central maintenance locationfor imported objects

XSLT and text files can be edited directly from IR.Java CLASS files must be edited and recompiled locally, then re-

imported.



Agenda




Interface objects

Proxy generation

Mapping objects


Miscellaneous


Business Scenario Objects

A Business Scenariodescribes a complete collaborative

process from the XI point of viewmain focus on the complete message

exchangedescribes only the public part of the

process

An Actiondescribes a function (a process) within

one component that is involved in themessage exchange

refers to the interfaces that can be usedto perform that function

may be used by one or more businessscenarios

Check Seat Availability

Send FlightBooking Order

Determine Seat Availability

Book Flight

Travel AgencyAirline

Web AS 6.20Web AS 6.20


What Are XI Business Scenarios Used For?

Business Scenario = Plan of IntegrationBusiness Scenario driven modelling and visualization of integrated business processesCollects all XI objects of an integration scenarioEnables single entry point and access to all objectsProvides structured documentation

Input for XI configurationBusiness Scenario guided configurationGeneration of configuration objectsProducts, FunctionsConnections (Interfaces, Mapping)

Input for implementationInvolved functions and servicesProducts and system requirements


Business Process Objects

You can design new objects for executable business processesby using the graphical Process Editor.

You can use different modeling elements and patterns to designa stateful, cross-component business process.

The following modeling patterns and elements are supported:Receive messages and trigger processSend, transform (merge or split) messagesCollect messagesMulticastSerializationProcess control elements such as switch, assign, fork,

wait, block, loop, controlDeadlines, 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 SystemNavigation from Scenario to Process


Concept: Integration Of Scenario And ProcessVisualisation In XI Integration Builder

ProductA

IFabs1

IFabs

ProductA

Scenario – Component ViewProduct

BProductTemplate

IFabs2

Process Send

W ait for response Alert

[tim eout]

Send responseback to initiator

W ait for NegativeAcknowledgement

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 collaborativebusiness process

Process is assigned to a swimlane – visualization of the public parts of the processprocess 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




Interface objects

Proxy generation

Mapping objects


Miscellaneous


Import / Export Functions


Business Processes

Mappings

Interfaces

SAP SystemIDocs, RFCs

WSDLXSD

BPEL

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.

BPEL

XSLTJava

WSDLXSDDTD


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 repositoryobjects 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.


Integration Repository: Unit Summary


Describe the Integration Repository and the objects that are created in it.

Understand various Interface Objects and their roles in integration scenarios.

Detail the use of web standards in the descriptions of interface objects in the Integration Repository.

Explain the Proxy functionality in XI.

Describe message mappings and list the different types of mappings available in XI.

Explain Business Processes and their role in integration scenarios.

Describe how to import various objects into the Integration Repository.



© SAP AG 2004, TBIT40 04 Integration Directory 2

Topics

Lecture topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security




Describe the Configuration Time Activities of the Exchange Infrastructure

Detail the task areas and configuration objects of the Integration Directory

Create and work with Collaboration Profiles

Design Logical Routings

Work with Collaboration Agreements

Completely and correctly configure Integration Scenarios within the Integration Directory

Integration Directory: Unit Objectives


The Development Consultants on your project have designed and developed Integration Scenarios and the related objects to enable A2A and B2B communication.

You are tasked with configuring these scenarios in the Integration Directory so they can be successfully executed at runtime.

Integration Directory: Business Scenario


Agenda

Integration Directory XI 3.0

XI 3.0 Integration Directory

Overview and Concepts

Business Scenarios


Routing Rules

Collaboration Agreements

Facilities

Cache updates


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


XI Configuration Concept

The goal of the Integration Directory is for the customer to configure the sender-receiver relationships which will be used at runtime.

Service B

Service A


XI 3.0 Integration Directory: Overview


Adapt integration content to specific configuration

Delivered empty, without predefined content

all content is customer-specific

Integration content derived from Integration Repository

Open for Customer to add collaboration knowledge relevant to non-SAP components

Home for centralized adapter configuration

Data provider for IS runtime

Integration Builder


Business Processes

Routing Rules

Business Scenarios

Receiver Determination Rules

Interface Determination Rules(including Mapping Assignment)

ConfigurationEditors

ConfigurationWizards


Parties , Services& Channels

Collaboration AgreementsSender & Receiver Agreements


Task Areas At Configuration Time

Area in the Integration Directory

Tasks

Collaboration Profile(Objects: Communication Party, Service,Communication Channel)

In the collaboration profile, you document the technical options available to the communication parties for exchanging messages. Specify the potential senders and receivers of messages and the technical communication paths.

Logical Routing(Objects: Receiver Determination,Interface Determination)

In logical routing, you define the flow of messages in a system landscape.

Collaboration Agreement(Objects: Sender Agreement, Receiver Agreement)

In collaboration agreements, you define the technical details for message processing (for example, adapter configuration) and the security settings for specific sender/receiver pairs.


Collaboration Profile Objects

A communication partyrepresents a larger unit which is involved in a cross-system process (for example a company).

Services are used to:

• Represent a technical or business unit, which is to be addressed as the sender or receiver of messages.

• Group interfaces to exchange messages according to particular task areas.

• Address business systems and business processes as senders or receivers of messages.

A Communication Channel defines how an adapter transforms a message so that it can be processed by the Integration Engine


Logical Routing Objects

A Receiver Determination defines one or more receivers

for a sender and an outbound interface

An Interface Determination specifies which interface is to be

used for the inbound processing of a

message


Collaboration Agreement Objects

In the receiver agreement, you define how the message is to be transformed so that it can be processed by a receiver.

In the sender agreement, you define how the message is to be transformed so that it can be processed by the Integration Engine


Collaboration Profile

Logical Routing Collaboration Agreement

...

Sender Agreement

...

Receiver Agreement

Configuration Model: Overview

SenderPartySenderServiceSenderInterfaceNamespaceSenderInterfaceNameReceiverPartyInboundChannelCertificates

Sender Agreement

SenderPartyReceiverPartyReceiverServiceReceiverInterfaceNamespaceReceiverInterfaceNameOutboundCannelCertificates

Receiver Agreement

...

Interface Determination

...

Receiver Determination

SenderPartySenderServiceSenderInterfaceNamespaceSenderInterfaceNameReceiverPartyReceiverServiceConditions

Receiver Determination

SenderPartySenderServiceSenderInterfaceNamespaceSenderInterfaceNameReceiverPartyReceiverServiceReceiverInterfaceNamespaceReceiverInterfaceNameMappingProgramName

Interface Determination

... ...

...

Party Service

1

0..*

Channel

0..1 0..*

ServiceNameAlternativeIdentifiersInterfaces

Service

PartyNameAlternativeIdentifiers

Party

Service may be:• a B2B service• a Business System• a Process

ChannelNameAdapterEngineTransportProtocolBusinessProtocolBusinessProtocolVersionURLLogonData

Channel


Ford JBL

…

POCreate

POConfirm

XI

CP

CA

Configuration Model: Terminology

Ford JBL

What must XI do, so

that Ford is able to send a

POCreate

What must XI do, so that XI is able to

forward a POCreate to

JBL

SenderAgreement ReceiverAgreement

XI must decrypt

XI must encrypt

Sender ChannelsSender InterfacesSender Agreements

Receiver ChannelsReceiver InterfacesReceiver Agreements

Attention: the notion of Role may be misleading In the purchasing scenario, Ford is a buyer and may be a technical sender (POCreate) and a technical receiver (POConfirm) – and vice versaRNIF and the Repository scenario knows Roles in the sense of Business Roles


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


Business Scenario objects (optional):Serve as grouping for related configuration objects Can be derived from the Integration Repository via a wizardCan serve as the basis of the Configuration wizard (Business Scenario

Configurator).

XI 3.0 Configuration: Business Scenario


Creating Business Scenarios

Add Collaboration Profile objects (Partners, Services, and Communication Channels)

Add Logical Routing objects (Receiver Determination, Interface Determination) and Collaboration Agreement objects (Sender Agreements, Receiver Agreements) – or use the Configuration Wizard.

Configuration Wizard


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


XI 3.0 Collaboration Profile: Partner (Party)

The optional object party facilitates the B2B functions of SAP Exchange Infrastructure and contains the following information:

A Name and a DescriptionAdditional identifiers (DUNS, DUNS+4, GLN)Assigned Services


XI 3.0 Collaboration Profile: Service

Service Objects:Address business systems and business processes as senders or receivers of messages Serve as grouping of interfaces for message exchange according to particular task areas

Contain the following information:Interfaces (inbound/outbound)Communication channels (sender/receiver)

3 Types Of Service:Business ServiceBusiness SystemBusiness Process


XI 3.0 Service Object : Business Service

A Business Service represents an abstract entity for addressing the senders and receivers of messages A Business Service can be used in cross-company processes, for example, if the parties involved have only published their interfaces and not their system landscape, or it is only partly known. With a Business Service, you can define the technical or business subunits of the companies (parties) involved and then assign the relevant interfacesCan be used to group interfaces


XI 3.0 Service Object : Business System

Business System objects are derived directly from existing XI Business Systems in the System Landscape Directory. As such, they contain information about Software Components assigned to the Business System, and which inbound/outbound interfaces are exposed. Can be addressed as a sender or receiver of messages


XI 3.0 Service Object : Business Process

A Business Process can send or receive messages by using Abstract Interfaces At configuration time, Business Processes are handled as senders and receivers or messagesDerived from the Integration Repository where the process is defined


XI 3.0 Collaboration Profile: Channel

Communication ChannelContains specific information for the message protocol, transport protocol, URL, logon data and adapter-specificconfigurationFor configuring specific adapters, pre-delivered communication channels, called channel templates, are available in the Integration Repository

Sender or Receiver channel


Adapter Types

Abbreviation Description

XIFor communicating using the proxy runtime. You can also use thisadapter type to communicate with an Adapter Engine at the receiver that is based on XI 2.0

IDoc For communicating with an SAP System by using the IDoc adapter

RFC For communicating with an SAP System by using the RFC adapter

http For communicating with http server by using the http adapter

JDBC For communicating with a database system by using the JDBC adapter

JMS For communicating with a messaging system by using the JMS adapter

Marketplace For communicating with marketplaces (see: Marketplace Adapter)

File For communicating with a file system by using the File/FTP adapter

RNIF For connecting to the RNIF protocol (RosettaNet Implementation Framework) by using the RNIF adapter


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


Routing Rule: Receiver Determination

Use the condition editor to enter conditions for

routing

Assign one or more receivers to a sender/outbound interface pair.Content-based receiver determination is possible (via XPath/context objects)Receiver should be an existing service (with or without Party).


Routing Rule: Interface Determination

Assign one or more inbound interfaces to be used for the inboundprocessing of a message (after the receiver determination).Assign an Interface Mapping for each outbound-inbound interface pair


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


XI 3.0 Collaboration Agreement

The objects Sender Agreement and Receiver AgreementSpecify a binding between an interface and a communicationchannelContain additional security settings, such as certificates. The sender agreement is used on the Integration Server for inboundprocessing, the receiver agreement for outbound processing


Use casesOverwrite party/service information based on IDoc control recordAdd payload information to the XI message headerNormalization/de-normalization of alternative party identifiers

Header mapping

The header mapping is a part of the collaboration agreement and allows you to overwrite specific fields of the header

Content can be provided from Constant valueMessage PayloadContext object


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


Facilities: Configuration Assistant


Configuration Assistant: Internal Communication

Configuration Steps:

• Specify Inbound Message

• Specify Outbound Message

• Define Message Processing

• Confirm Configuration Data


Configuration Assistant: Communication with Partners


Facilities: Business Scenario Configurator

From the Business Scenario Editor, click this icon to start the configuration wizard…

All of the configuration objects that are needed for a given scenario can be created manually; Alternately, you can use the Business Scenario Configuration Wizard to generate all of the objects that are necessary to implement the scenario.


Step 1: Select Component View

You assign a Business Scenario From the Integration Repository to use as the basis of the configuration.

Each Role in the Business Scenario is assigned to a Service

Each Connection in the Business Scenario is assigned to an Interface Mapping (if necessary)


Step 2: Assign Services

Use the Left and Right arrows to navigate through all Roles (“swim lanes”) of the scenario and assign the appropriate service

Assign a service for each Role in the Integration Scenario


Step3: Configure Connections

Use the Left and Right arrows to navigate through the connections

Use the Mapping tab to assign Mappings (where necessary) between interfaces


Step 4: Generate

Specify whether you will simulate or generate the configuration objects

Set the objects to generate

Specify a change list (for generation only)

Start generation


Step 5: Review Generation Log

Review the Generation Log to insure that all objects were created correctly. You have the option of saving the log. When you close the wizard, you will be asked if you want to keep the changes; if you are satisfied with the results of the wizard, save the assignments.


Value Mapping

The Value mapping function provides a specific value transformation.

1. Use the standard function Conversions -> Value mapping to link source and target element

2. Double click to define properties3. Define access keys for table entries:

Value Mapping Context stores information on the origin of the data. If data is maintained in the Integration Directory, use http://sap.com/xi/XI

Agency and Schema for sender and receiver messages. Any arbitrary string value can be used.


Integration DirectoryIntegration Directory

Value Mapping


Value MappingTool

Value MappingTool

Value MappingTool

Value MappingTool

Value MappingTool

3rd party component

Integration Server

Value Mapping API

Display UIValueMapping Server

Value Mapping Cache

Value Mapping API

Mapping Runtime

Mapping Program


Preliminary Receiver Determination

Find out at the application level whether a receiver exists for a given outbound interface

Routing rule must be maintained in directory (virtual receiver)

This is done before generating and sending the message at runtimeAvoid unnecessary construction of messageAvoid unnecessary parsing of message by runtime engine


Agenda




Business Scenarios


Routing Rules


Facilities

Cache updates


Cache updates

When Integration Directory objects are activated, the changes are replicated

In the Integration Server runtime cache (accessed via SXI_CACHE)In the CPA cache of each adapter engine (central and de-central)



Integration Engine

Bus. Process Engine

Decentral Adapter Engine

Decentral Adapter Engine

SXI_CACHE

CPA CACHE

Information about the adapter engines is obtained from the SLD


Cache Notifications


IS Runtime cache

Goto AE Cacheto list the connections from the IS to the adapter engines



Describe the Configuration Time Activities of the Exchange Infrastructure

Detail the task areas and configuration objects of the Integration Directory

Create and work with Collaboration Profiles

Design Logical Routings

Work with Collaboration Agreements

Completely and correctly configure Integration Scenarios within the Integration Directory

Integration Directory: Unit Summary


Runtime

© SAP AG 2004 TBIT40 05 Runtime

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Runtime Overview : Unit Objectives


Explain basic concepts of XI message processing.

Describe the concept of the Integration Engine and the Pipeline, and detail the difference.

Use the message monitoring capability of the XI.

Explain the XI-SOAP message format.

Describe the caching capabilities of the Integration Server


XI 3.0 Runtime

Agenda

XI 3.0 Runtime


Pipeline steps

IS Runtime Cache


XI Message Processing

Application System A

SOAP-XML

Integration Server

Application System B

SOAP-XML

XI connects various application systems via XML messaging.

XI uses an SAP-specific implementation of the SOAP protocol.

Messages received at the Integration Server are processed through a defined series of steps called Pipeline Services.

When a message is received at the Integration Server, the message is examined and all valid configurations (as maintained in the Integration Directory) for that message are executed.


Example of basic SOAP document over HTTP


XI Message format: SOAP with attachments


Sample XI Message


Technical Structure of an XI Message


The XI Pipeline

TargetMessage

TargetMessage

CallAdapter

CallAdapterTechnical

Routing

TechnicalRoutingMessage

Mapping

MessageMappingMessage

Split

MessageSplitInterface

Determination

InterfaceDeterminationReceiver

Identification

ReceiverIdentification

SourceMessage

SourceMessage


Pipeline Entry Point

transactionSICF


Important Pipeline Steps

Receiver IdentificationReceiver IdentificationDetermine which Determine which system(ssystem(s) should participate in an exchange with the ) should participate in an exchange with the incoming message.incoming message.

Interface DeterminationInterface DeterminationFor each receiver system determine which For each receiver system determine which interface(sinterface(s) should receive a ) should receive a message.message.

Message BranchMessage BranchIf multiple receivers are found, XI will instantiate a new messaIf multiple receivers are found, XI will instantiate a new message for each ge for each receiver.receiver.

Request Message MappingRequest Message MappingCall the mapping program to transform the message structure to tCall the mapping program to transform the message structure to the receiver he receiver format.format.

Outbound BindingOutbound BindingBind a specific destination and protocol to the message.Bind a specific destination and protocol to the message.

Call AdapterCall AdapterSend the transformed message to the adapter or proxy.Send the transformed message to the adapter or proxy.


Adapter Engine

Configurationcache

ISRuntime

AdapterSender

AdapterReceiver

Adapter Engine in SAP J2EE

Q

Administration

Security

Monitoring

Adapter-Specific

ComponentServices

TracingLogging

Module ProcessorEIS

Channel

´Messaging

Config.cache

End-to-End MonitoringMessage flow over all XI components / applications

Runtime Workbench• Uis for adminstration,

monitoring

Integration Builder / Directory:

... Receiver determination• Party->Service->Action

... Channel Definition:• Adapter Engine• Adapter Type• Message Protocol• Transport Protocol• Security• Channel Configuration

(Sender / Receiver Agreement:• Party/Service/Action <-> Channel

ConfigurationMaster

System Landscape Directory• Holds component description

including address data

AdapterFramework

Integration Repository• Holds Adapter metadataIntegration Repository• Holds Adapter metadata

http://<IntegrationServerURL>

XI Message

http://<AdapterEngineURL>

OK / Error


XI 3.0 Runtime

Agenda

XI 3.0 Runtime


Pipeline steps

IS Runtime Cache


Pipeline Definition

Sender

Central

Receiver


Pipeline Services


Pipeline Processing

Message After Receiver Identification

Message Received in the Pipeline


Transaction SXI_Monitor

Two selection screens(Standard/Advanced)

Selection on:Status GroupStatusExecution FromExecution ToParty/Scheme/Agency/Service (S/R)Interface Name/Namespace (S/R)PipelineTechnical Inbound ChannelOutbound StatusErrorClient


XML Message List

FlexibleALV Views Legend


Changing the Layout

tecview

bizview

Messages are displayed in an ALV Grid Control.Different layouts are possible:

•Default: All attributes of a message are displayed•Technical View: Only the technical attributes are displayed•Business View: Business-oriented attributes are displayed•Acknowledgment View: Attributes important for acknowledgmentsare displayed


Display Message Contents

Compareversions

Step

sin

Pip

elin

e

Display and download of the content


Message Handling: Synchronous Processing

Synchronous Processing (QoS = BestEffort)

Sending System XI Integration Server

Sending Application

Outbound Proxy

CentralCentral Integration Engine

ReceiverLocal Integration Engine

Receiving System

SenderLocal Integration Engine

Receiving Application

Inbound Proxy

HTTP HTTP

Blocking call of sending application (incl. DB commit)

No message persistance (logging needs to be swiched on)


Message Handling: Asynchronous Processing

Asynchronous Processing(QoS = Exactly Once/Exactly Once In Order)

XIqRFCSender

qRFC qRFCReceiver


Sending System XI Integration Server

Sending Application

Outbound Proxy

CentralCentral Integration

Engine

HTTP

Receiving System

Receiving Application

Inbound Proxy

HTTP

XI XI


•XI processing is asynchronously decoupled (scheduled in qRFC)•Hop-to-Hop exactly once protocol -> messages are persisted in database•EOIO serialization by qRFC queues (no serialization number!)


XI 3.0 Runtime

Agenda

XI 3.0 Runtime


Pipeline steps

IS Runtime Cache


XI Runtime Cache

Configuration Settings are cached at the Integration Server to improve performance. Cached objects include:

PartiesServicesReceiver Determination

Interface DeterminationSender/Receiver AgreementCommunication ChannelMappingsSoftware ComponentsBusiness Process


Transaction SXI_Cache


Manual Cache Refresh


Adapter Engine Cache

To view the cached addresses of all Adapter Engines that are registered at the Integration Server, choose

Goto AE Cache

from the main menu in transaction SXI_CACHE.


IDOC Adapter Cache

TransactionIDX2


XI Runtime 3.0: Unit Summary


Explain basic concepts of XI message processing.

Describe the concept of the Integration Engine and the Pipeline, and detail the difference.

Use the message monitoring capability of the XI.

Explain the XI-SOAP message format.

Describe the caching capabilities of the Integration Server


Runtime Workbench

© SAP AG 2004, TBIT40 06 Runtime Workbench 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Runtime Workbench: Unit Objectives


Explain the purpose of the Runtime Workbench.

Describe the capabilities of the Runtime Workbench.

Monitor messages, performance, and components in the Runtime Workbench.

Describe the capabilities of End-to-End monitoring.

Detail the alert capabilities of the Runtime Workbench.


Runtime Workbench overview

Central point of access: XI Runtime Workbench

Smooth integration with CCMS

Easy ConfigurationExploiting System Landscape DirectoryConsistent look-and-feel in UI

Improved Error HandlingErrors classified by error cause


Monitoring – Message Monitoring

Based on SAP standard monitoring solutions

Used by End-to-End monitoring to construct instanceview

Available for XI component with persistence

Central Monitoring

RuntimeWorkbench(RWB)

Syst

em L

ands

cape

Dire

ctor

y

MessageMonitoring

PerformanceAnalysis

ComponentMonitoring CCMS

Alerting Framework

PMI

MessageAlerting

Integration Server(SAP Web AS ≥ 6.40)


Integration Engine

Adapter Engine

SAP Application

SAP Web AS ≥ 6.40,using XI proxies

(decentral)AdapterEngine

J2SEAdapterEngine


Monitoring – Component Monitoring

Smooth integration with CCMS (easier, leaner)

Monitoring of ABAP and Java components

Improved error handling

Central Monitoring


Syst

em L

ands

cape

Dire

ctor

y

MessageMonitoring

PerformanceAnalysis


Alerting Framework

PMI

MessageAlerting



Integration Engine

Adapter Engine

SAP Application



J2SEAdapterEngine


Monitoring – Performance Analysis

Central Monitoring


Syst

em L

ands

cape

Dire

ctor

y

MessageMonitoring

PerformanceAnalysis


Alerting Framework

PMI

MessageAlerting

Enhanced performance statistics

Measuring of throughput and latency (‘processing time’)

Selection andaggregation of performance data by- XI component- Time range- Message attributes



Integration Engine

Adapter Engine

SAP Application



J2SEAdapterEngine


Monitoring - Alerting

Central Monitoring


Syst

em L

ands

cape

Dire

ctor

y

MessageMonitoring

PerformanceAnalysis


Alerting Framework

PMI

MessageAlerting Based on Central

Alerting Framework

Active Monitoring (alerts being sent by e-Mail, SMS,…)



Integration Engine

Adapter Engine

SAP Application



J2SEAdapterEngine


XI 3.0 RWB – Component Monitoring

Component Monitoring:

Monitoring of ABAP and Java components

Central viewing of component‘s connection status in a specific domain.

Ping of system and sending of messages to components via a self-test area.


Component Monitoring features

Selecting associated information: For ABAP components, specific configuration parameters are displayed as defined in TC SXMB_ADM. For Java components, system settings as well as Aii-Properties are displayed as defined in the exchange profile

Two different views: XI components can be displayed either

in Table or Tree format.


Sending Test Messages


XI 3.0 RWB – Message Monitoring

Message Monitoring

Harmonization of different message monitorsIntegration EngineAdapter Framework (J2EE)

All message monitoring centrally accessible through RWB

Monitoring locally available as wellat least for partner connectivity kit


Message Monitoring – Message Details

•To see the detailed information about a message, select the radio button for the message and choose Details.

•To view the individual versions of the message (as in transaction SXI_MONITOR), choose Message Content.

•You can also view referencing and referenced messages.


XI 3.0 RWB – End-to-End Monitoring/Configuration

Configure

Monitor


End-To-End Monitoring at a glance

Status of monitoringtool itself

Statistics

Overall process status

Graphical representation of process or instance flow


End-To-End Monitoring – Prerequisites

Activate the Process Monitoring Infrastructure Monitoring by setting respective configuration parameter in TC SXMB_ADM


End-To-End Monitoring - Configuration

After configuration, choose button “Save Configuration” to activate the End-To-End Monitoring

Select business system to be involved

Select level of monitoring

Configure as sendingor receiving system


End-To-End Monitoring – Monitoring Status

Displays internal error messages derived from self-monitoring in CCMS

Deletes error messages;corresponding alerts in CCMS are completedFrequency of updating

process monitoring data

Starts update immediately


End-To-End Monitoring – Process Overview

Choose status symbol or attributes (e.g. warning, error, success) to display corresponding process instances


End-To-End Monitoring – Instance View

Choose message to switch to instance view providing tracking information

Duration of message

Componentsinvolved


XI 3.0 Performance Monitoring

Measured data:ThroughputLatency (“processing time”)

Selection and Aggregation by:XI component (Integration Server, Adapter Engine)Time rangeMessage attributes: Sender, receiver, message type

Performance MonitoringPerformance measurement during operation


Performance Statistics --- Example


XI 3.0 Alert Configuration

| Alert-Configuration

Alert-Configuration

Objective: Active Monitoring

CCMS Alerts + message-oriented alerts

Based on SAP’s Basis Alert Framework

Alerts propagated through E-Mail, SMS, …


Creating A New Alert Rule (2)


XI 3.0 RWB – Cache Monitoring


XI 3.0 RWB - Summary

Central access to monitoring

Component Monitoring

End-to-end Message Monitoring

Performance Measurement across distributed XI landscape

Integration with Basis Monitoring solutions:

•CCMS

•PMI

•Alert Framework

Unified User Interface (UI)

Easy monitor configuration


Runtime Workbench: Unit Summary


Explain the purpose of the Runtime Workbench.

Describe the capabilities of the Runtime Workbench.

Monitor messages, performance, and components in the Runtime Workbench.

Describe the capabilities of End-to-End monitoring.

Detail the alert capabilities of the Runtime Workbench.


Adapter Framework

© SAP AG 2004, TBIT40 07 Adapter Framework 2

Topics

Lecture topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



XI 3.0 Adapter Framework : Unit Objectives


Describe the Architecture of the SAP XI Adapter Framework.

Detail the functionality of the Adapter Engine.

Explain central and local Adapter Installations.

Distinguish between the various adapter types.

Describe the Partner Connectivity Kit.

Configure different adapters to send messages to and receive messages from the Integration Server.


Agenda

XI 3.0 Adapter Framework

SAP XI 3.0 Adapter Framework Overview

SAP XI 3.0 Adapter Strategy

Technical adapters in detail

Summary


SAP XI 3.0 Architecture

PlainJ2SE

Adapter Engine

Adapter

Integration Repository / Integration Directory / System Landscape DirectoryIntegration Repository / Integration Directory / System Landscape Directory

Integration ServerIntegration Server

SAPSystem

SAPSystem

IDoc

Adapter


Integration Engine



Security Handling

Optional local Adapter Engine


Security Handling

Resource

Adapter

Partner ConnectivityKit


Security Handling

FileDB

JMS

FileDB

JMS

Resource

Adapter

Resource

Adapter


File/DB/JMSMarketplace 3rd Party Sys.




File/DB/JMSSAP SystemFile/DB/JMSSAP System

Content (e. g. Mapping, Adapter Metadata)


Adapter Framework based on SAP J2EE Engine

The Adapter Framework provides common functionality for both the Adapter Engine and SAP Partner Connectivity Kit

Adapter Framework is based on SAP J2EE Engine as part of SAP Web ASAdapter Framework inherits properties and features such as

scalability, clustering, high availability, thread management, etc.

Adapter Framework provides its own queuing and logging services

Temporary stand-alone operation without connection to an Integration Server is possible, while still providing e. g. guaranteed exactly once messaging to and

from connected application system


JCA enabled Adapter Framework

Adapter Framework supports J2EE Connector Architecture (JCA)

JCA is standard architecture for connecting the J2EE platform to Enterprise Information Systems (EIS) - e. g. ERP, DBMS, etc.

A Resource Adapter plugs into an application server, providing connectivity between the EIS and a Java application

JCA enabled Adapter Framework provides definedinterfaces to which both our adapters and 3rd party adapters can conform

JCA is a widely accepted standard that 3rd party adapter providers are already familiar with


Central configuration, administration, monitoring

Additionally Adapter Framework provides comprehensive integration for central configuration,

administration, monitoring of deployed adapters

One single point of access, only one common UI, enhancedtransparency

Capability to move or copy configuration from one Adapter Framework to another (transportable configuration):

To transport configuration from test landscape to productive landscape

For high availability/failoverAvoid redundant maintenance, ensure consistencyEnd-to-end monitoring of the message flow over all SAP XI

components and processes





Security Handling

Resource

Adapter


PlainJ2SE

Adapter Engine

Adapter



SAPSystem

SAPSystem

IDoc

Adapter


Integration Engine

Central Adapter EngineAdapter Framework

MessagingQueuing

Security Handling



Security Handling

Resource

Adapter

FileDB

JMS

FileDB

JMS

Resource

Adapter








Adapter Engine

ISRuntime

EIS

Config.cache

End-to-End MonitoringMessage flow over all XI components / applications

Runtime Workbench• UIs for administration,

monitoring

Configurationcache

AdapterSender

AdapterReceiver

Adapter Engine in SAP J2EE

Q

Administration

Security

Monitoring

Adapter-Specific

ComponentServices

TracingLogging

Module ProcessorChannel

´MessagingIntegration Builder / Directory:

... Receiver determination• Party->Service->Action

... Channel Definition:• Adapter Engine• Adapter Type• Message Protocol• Transport Protocol• Security• Channel Configuration

(Sender / Receiver Agreement:• Party/Service/Action <-> Channel

ConfigurationMaster

System Landscape Directory• Holds component description

including address data

AdapterFramework

Integration Repository• Holds Adapter metadataIntegration Repository• Holds Adapter metadata

http://<IntegrationServerURL>

XI Message

http://<AdapterEngineURL>

OK / Error


Full integration of Adapter Engine in SAP XI landscape

Adapter Engine is based on Adapter Framework

Adapter Engine fully integrated with the SAP XI landscape

Central configuration of connections to application systems (through appropriate adapters) in Integration Directory

Reuse of Integration Directory’s existing versioning and transport capabilities

Central administration and monitoring over adapters, Integration Server, Integration Engine through Runtime Workbench


Central and Local Adapter Engine

Adapter Engine is open for adapter development by partners and customers

JCA based adapter development as ‘state-of-the-art’ Java technology

Additional services for configuration, monitoring, security etc.SAP XI Adapter Framework (as PCK), Adapter Framework

Interface Specification, JCA sample adapter (incl. source code) available via SAP Integration and Certification Center

The Adapter Engine can be deployed centrally as part of Integration Server, or as optional local Adapter Engine on its own SAP J2EE Server

Use of local Adapter Engine e. g. to be close to business system


Adapters hosted in Adapter Engine

In addition to Adapter Framework, the Adapter Engine hosts a set of adapters:

SAP AdaptersFile / FTPJDBC (Database)JMS (MQSeries, SonicMQ, …)RFCSOAPSMTPSAP BC (header extension for support of Quality of Service)SAP Marketplace AdapterRosettaNet (RNIF 2.0) AdapterCDIX (RNIF 1.1) Adapter

3rd Party AdaptersiWay: UCCnet, more to come …Optional: Adapters developed by partners, certificated by SAP


SAP XI Adapter Partner System

SAP relies on a system of partners to provide adapters for otherapplications and certain industry standards

Adapter Reseller AgreementiWay Software

UCCnet AdapterOracle, Siebel, PeopleSoft

SEEBURGER AGEDI Adapters

WebMethodsApplications (Oracle, Siebel, PeopleSoft, Baan, …)Industry Standards (RosettaNet, CDIX) SAP XI 3.0

Partner adapters are sold and delivered through SAP

Technical SupportSAP provides 1st level support via CSN, 24x7Partners provide 2nd and 3rd level support via CSN, 24x7


Adapter Info on SAP Service Marketplace

SAP Service Marketplace:SAP XI in Detail Connectivityhttp://service.sap.com/xi


Adapter Configuration

Adapter independent parameters

Adapter specific parameters


Remark: Future of SAP XI 2.0 Adapter Engine

SAP XI 2.0 Adapter Engine is available in SAP XI 3.0 as “Plain J2SE Adapter Engine”

Functional scope as in SAP XI 2.0:Adopted to the SAP XI 3.0 message protocolMinor maintenance issues, bug fixes

Recommendation:Use where platform requirements or limitations (hardware,

operating system, JVM support) demand it

SAP XI 2.0 Adapter Engine works with SAP XI 3.0 landscapes, too



PlainJ2SE

Adapter Engine

Adapter



SAPSystem

SAPSystem

IDoc

Adapter


Integration Engine



Security Handling



Security Handling

Resource

Adapter



Security Handling

FileDB

JMS

FileDB

JMS

Resource

Adapter

Resource

Adapter









SAP Partner Connectivity Kit (PCK) Overview (1)

SAP Partner Connectivity Kit is based on the Adapter FrameworkThe PCK enables XML document exchange between SAP XI and

business partners not using SAP XIPCK provides connectivity options to access SAP Adapters:

SAP Web AS (J2EE only)



Security Handling

Resource

Adapter


Integration Server

XI PIPELINEXI-SOAP/HTTP(S)

File/FTPJDBC (Database)JMS SOAPRFC

Communication between SAP XI and PCK is via SAP XI messaging protocol


SAP Partner Connectivity Kit Overview (2)

The PCK is deployed on a standalone SAP J2EE Engine (part of SAP Web AS) within business partner’s landscape

SAP Web AS (J2EE only)



Security Handling

Resource

Adapter


Configuration, administration, and monitoring are done locally on the PCK itself without the need for an Integration Directory

Configuration UI provides same “look and feel” as configuration UI of Adapter Engine


Agenda





Summary


SAP Exchange Infrastructure - Openness

Integration of SAP and non-SAP applicationsAdapter Framework for comprehensive integration of adaptersAdapters are used for technical connectivityAdapter metadata and mappings are stored in Integration Repository


Dual Strategy

Dual connectivity strategyAdapter Framework for comprehensive integration of adapters

to provide technical connectivity, including central configuration, administration, monitoring of adapters

Interoperability based on open standards (SOAP, JMS, HTTP(S)) to interoperate with EAI providers

Value propositionStandardized interfaces allow easy integration of adapters from

different partnersMinimum knowledge of SAP XI requiredComprehensive integration avoids redundant maintenance,

ensures consistency, enhances transparancyOpenness to integrate non-SAP applications, 3rd party systems,

etc.Reduced TCO


Certification

CertificationSAP NetWeaver Certification of 3rd party adapters based on

the adapter framework

Value propositionCertification helps customers to find right solutionFaster implementation time and lower integration costs

through the use of tested 3rd party integrationQuality (stability, HA aspects, performance, etc.) of adapters

is controlledQuick and convenient search for a variety of certified

products with the online partner and product directory (http://www.sap.com/partners/icc)

Reduced TCO


Adapter Mappings, Metadata in Integration Repository

Adapter mappings and adapter metadata are stored in the Integration Repository

Centralized Integration Repository contains all relevant information for collaborative and integrative processesAll content adheres to open standards Adapters provide technical connectivity

Value propositionUse largest content catalogReduce costs in integration projectsReduce maintenance costsReduced TCO


Agenda





Summary


Technical Adapters in Detail

This section will give an overview of the functionality and usage of each technical adapter delivered with XI 3.0

RFCIDocFileJDBCJMSPlain HTTPMailSOAP

Other adapters are covered in advanced or specialized workshops:RosettaNetCIDXSAP BCMarketplacePartner adapters (SEEBURGER, iWay, etc.)


RFC Adapter

IntegrationServer

RFC-Client/Server

Adapter module: Localeejbs/RFCAFBean

Messaging System

J2EE AF (AE/PCK)

ModuleProcessor

XI RFCAdapter

M1

M...

Mn

JRFC/JCo-lib

RFC

RFC

XI-SOAP/http

XI-SOAP/http

Channelcache


IDOC Adapter

SubsystemIDoc

Metadata

SAP System

RFC

FM EDI_OUTPUT_NEW

FMIDocTYPE_READ_COMPLETE

... RFC dest

RFC dest

Metadata

IDX1

tRFC

Port

IDocXML

XI-PipelineInbound IDoc

Adapter

Integration Server

IDX2


File Adapter


JDBC/JMS Adapter

QXTJ10005MSG0000001MSG0000002MSG0000003MSG0000004MSG0000005

…

JDBC Driver

JMS Driver

ADAPTERENGINE

XI-SOAP/HTTP


Plain HTTP Adapter

The Plain HTTP Adapter is used to receive (send) arbitrary XML in the body of an HTTP-Post request...

The Sender HTTP-adapter is an ICF service on the Integration Server (path /sap/xi/adapter_plain).

The Receiver HTTP adapter is configured as a communicationchannel in the Integration Directory.

Supports QoS BE, EO, and EOIO (specified in the query string of the URL).

The HTTP adapter uses HTTP version 1.0, and does not supportreturning fault messages to the sender.


Plain SOAP Adapter

Sender

Receiver


Example: Configure the JDBC Receiver Adapter


XI 3.0 Adapter Framework : Unit Summary


Describe the Architecture of the SAP XI Adapter Framework.

Detail the functionality of the Adapter Engine.

Explain central and local Adapter Installations.

Distinguish between the various adapter types.

Describe the Partner Connectivity Kit.

Configuration different adapters to send messages to and receive messages from the Integration Server.


Integration Process (Business Process) Management

© SAP AG 2004, TBIT40 08 BPM 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Business Process Management : Unit Objectives


Understand the need for Business Process Management in the Integration Scenario

Create an Integration Process (Business Process) in the Integration Repository.

Use a Integration Process (Business Process) in configuring a scenario.

Describe runtime aspects of Integration Processes (Business Processes).


Today’s Home-Grown Integration Landscapes …

Business Partners

hard codedhard coded

EAIToolEAITool

3rdParty

3rdParty3rd

Party

B2BToolB2BTool

SAP

SAP

mainframeapplication

SAP

SAP

SAP

Marketplace

Business Partner Application

3rdparty

SAP

other IntegrationSolution

B2B Tool

Adapter


Process Driven Integration Solution …

Business Partners

3rdParty

3rdParty

SAP

SAP


SAP

Marketplace


3rdparty

SAP

RosettaNetMiddleware

MessageOriented

Middleware

SAP

SAP

SAP XIother IntegrationSolution

3rdParty

3rd party WfMS

3rd party BPMS

SAP BusinessWorkflow

ProgrammedWorkflow

BPMS: Business Process Management SystemWfMS: Workflow Management System


Integration with SAP Exchange Infrastructure (SAP XI)

Business Partners

3rdParty

3rdParty3rd

Party

SAP

SAP


SAP

Marketplace


3rdparty

SAP

RosettaNetMiddleware

SAP

SAP


SAP NetWeaver

SAP XI


ccBPM

ccBPM

SAP BusinessWorkflow

ProgrammedWorkflow


Business Process Management (BPM)

Ad-hoc WorkflowTeam-driven processesSpontaneous eventsCollaboration

Cross-Component BPMDesign, execute and monitor

automated processes across applications and systems

Stateful interaction modelCross application execution

Business WorkflowDesign, execute and monitor

processes within applicationsApply standard business rulesBusiness eventsHuman interaction


Cross-Component BPM in a Nutshell

BusinessSystem

4

BusinessSystem

1

Integration Server

BusinessSystem

3

BusinessSystem

21 2 3

Messages

Message

4

Design, execute and monitor automated processes across applicationsProvides process control in the central technology layerContains a Graphical Process EditorContains a Business Process EngineIntegral part of XI

Integration Repository (Design)Integration Directory (Configuration)Integration Server (Runtime)

Adheres to open modeling standardsBPEL4WS 1.1

Industry standard supportRosettaNet (RNIF adapter, PIP, …)

Technical Process Monitoring Integrated with technical Monitoring of XI Graphical Process Monitoring

BusinessProcessEngine

IntegrationEngine


Cross-Component BPM Architecture – Overview

Integration Server

Integration Engine

Process / Message Store


AbstractInterfaces


Business Process(Configuration)

Routing Rules


Adapter Engine

Routing

CorrelationHandling

Integration Builder

Proc

ess

Edito

r

Business Process(Definition)

(References)M

essa

ge

Mes

sage

23

1

4Mapping ChannelDet.

ProcessExecution

© SAP AG 2004, TBIT40 08 BPM 10

Business Processes at Design Time

Business Process as a Repository ObjectGraphical Process Editor“Native” access to all process relevant XI design objects: interfaces, mappingsAdheres to standards

Open standards support (BPEL4WS)Import/ export of process definitions

Abstract InterfacesBi-directional (inbound & outbound)Used by BPM & RNIF adapter

Business Process ModelingMessage relevant process elements

Trigger and receive, send, receiver determination, transformation (merge & split)

Process flow elementsSwitch, container operation, control (terminate, throw exception, throw alert), block (exceptions & deadlines), fork (parallel sections), loop, wait, “undefined” (empty)

Process data (for data declaration)


AbstractInterfaces


Conditions

© SAP AG 2004, TBIT40 08 BPM 11

Architecture – Definition

DirectoryScenarioScenario

Party

Repository SWCV

Cache/Runtime

ProcessProcess

Flow

If**

Interf. MappingsInterf. Mappings

AbstractInterfacesAbstractInterfaces

Context objectsContext objects

MessageTypeMessageType

XML-objectsXML-objects

CorrelationsCorrelations

Business ScenarioBusiness Scenario

*

*

Routing RelationRouting Relation

ProcessProcess

Flow

If**

Business ProcessBusiness Process

Flow

If**

Mapping RelationMapping Relation

ProcessProcessProcessProcess

MessageMappingsMessageMappings

IdocIdoc

RFCRFC

© SAP AG 2004, TBIT40 08 BPM 12

Big Picture – Components

Client J2EE

Directory

Repository

IS

ProcessEngineProcessEngine

DesignDesign

Flow

If

**

Definition

Process definition

*

* *

*

Runtime

5

Configuration

RoutingsMappings

...

Configuration

RoutingsMappings

...

XI objectsXI objects

XI objectsXI objects

3

Business Process

2

1

Import

DeploymentRules

XML-Objects Correlations

Changelist

4 Cache-Refresh

Monitoring

6

© SAP AG 2004, TBIT40 08 BPM 13

Business Processes & Business Scenarios

Business Process can be incorporated in a Business Scenario

Representation in a swim lane Treated as a Business SystemNavigation from Scenario to Process

© SAP AG 2004, TBIT40 08 BPM 14

Business Process Editor

Output area Object area

Header

Processoverview

Propertyarea

Edit area

© SAP AG 2004, TBIT40 08 BPM 15

Edit area in detail

Drag and drop

Message relatedstep types

Process controlrelated step types Other commands

Process overview as navigation help for large

process definitions

Horizontal and vertical modelling

Printing capabilities

© SAP AG 2004, TBIT40 08 BPM 16

Object area in detail

The container holds the datadeclaration of the process

The correlation list holds all correlations used by this process

The process signature shows all the abstract interfaces received

and sent by the process

© SAP AG 2004, TBIT40 08 BPM 17

Property area in detail

Container-operation step

Receive step

Transformation step

Property sheet as unified mediumfor step setting

© SAP AG 2004, TBIT40 08 BPM 18

Output area in detail

Tasks show the result of the syntax check (filtering on severity

level possible)

Search Result shows all objects that match the search ciriteria.

Messages show immediate consequences of user-

interactions (filtering on severity level possible)

© SAP AG 2004, TBIT40 08 BPM 19

Process Step-Types

MESSAGING RELEVANT

RECEIVER DETERMINATION

RECEIVE

TRANSFORMATION

SEND

Block

BLOCK

EXAMPLE

PROCESS FLOW CONTROL RELEVANT

CONTAINER-OPERATION

CONTROL (deadlines, exceptions, alerts)

EMPTYWHILE LOOP

FORK WAIT

BLOCK SWITCH

© SAP AG 2004, TBIT40 08 BPM 20

Message Relevant Steps

RECEIVER DETERMINATION

RECEIVE

TRANSFORMATION

SEND

You use a receive step to receive a message.

You use a send step to send either an asynchronous or synchronous message or an acknowledgment.

You use a transformation step to change a message inside the process.

You use a receiver determination step to get a list of receivers for a subsequent send step.

© SAP AG 2004, TBIT40 08 BPM 21

Flow Control Steps (1)

CONTAINER-OPERATION

CONTROL (deadlines, exceptions, alerts)

BLOCK

SWITCH

You use a switch to define different processing branches for a process.

You use a container operation to set a value for a target container element at runtime.

You use a control step to do the following to execute process controls (e.g, terminate a process).

You use a block to combine steps that you want to execute one after the other and which are to access the same local data.

© SAP AG 2004, TBIT40 08 BPM 22

Flow Control Steps (2)

You use a fork when you want to continue a process in branches that are independent of each other.

You use a while loop to repeat the execution of steps within the loop.

You use a wait step to incorporate a delay in a process.

You use an empty (undefined) step as a placeholder.

FORK

WHILE LOOP

WAIT

EMPTY

© SAP AG 2004, TBIT40 08 BPM 23

Process Data

Messaging Relevant Process DataVariables typed by abstract interfacesVariables typed as receiverRead access to message-payload via

XPathContext objects

Process Flow Relevant DataVariables typed by XSD simple types (e.g. used for loop-counter, ...)

Process TriggerVia messages (trigger receive)Scheduling (batch jobs)

© SAP AG 2004, TBIT40 08 BPM 24

Correlations

Correlation HandlingRouting of messages (Business Documents) to process instancesDependencies rely on business data (e.g. Message ID, Order ID, Business Partner ID, Company Code)Correlations define these dependencies

© SAP AG 2004, TBIT40 08 BPM 25

SAP NetWeaver: Business Process Content



Proc

ess

Edito

r

Integration Builder



References

SAP Business Process ContentXI scenario & process pattern templates (XI 3.0)SAP solution process content (delivered with SAP solutions)Industry standard content(as e.g. RosettaNet)

IndustryStandards

SAPSolutions

Patterns

XI ProcessPatterns

WorkflowTemplates

© SAP AG 2004, TBIT40 08 BPM 26

Business Process Patterns

ProcessProcess

Loop

Receive message on A

Add 1 to C

Append A to AT

While C <> A.number

Container

A type AIF1AT type AIF1*B type AIF2C type int

Correlations

MyCorrelationID type int

Transformation Merge AT into B

Send message on B

ProcessInterface

AIF1 inAIF2 out

SerializationS_FL1: single message triggerS_FL2: multi message trigger

Transformations/Merge/Split(N:1)(1:N)

Collect (same IF type/ different IF type)C_FL1.1: payload-triggered endC_FL1.2: time-triggered endC_FL1.3: message triggered endC_FL2.1: collect all C_FL2.2: collect some (condition

based)

MulticastM_FL1: send in a sequenceM_FL2: send in parallel

© SAP AG 2004, TBIT40 08 BPM 27

Configuration Time: Integration Directory



Routing Rules

A Business ProcessIs identified by a name and belongs to a Party analogous to a Business SystemsContains a reference (link) to its originating repository process

Can only be deployed not created in the directory

Business Process Wizard to import Process reference from the Integration Repository

Routing and Mapping RelationsBusiness processes can act as source or target (sender/receiver) as Business Systems

Process Wizard

© SAP AG 2004, TBIT40 08 BPM 28

Runtime

RuntimeProcesses participate in the common cache-mechanismExecutable process-definition and depending objects are createdBusiness Process Engine

Enhancement of SAP WebAS Workflow EngineStable, proven and robust technology

Monitoring = Technical MonitoringEntry from message view (XI runtime)Entry from process view (Process runtime)Seamless navigation between the monitoring tools

© SAP AG 2004, TBIT40 08 BPM 29

Runtime cache in detail (SXI_CACHE)

Runtime cache viewer knows Business Processes

Business Workflow tools in a special profile

Workflow Builder uses same look and feel as the Process Builder in

IB (tiles and other concepts)

© SAP AG 2004, TBIT40 08 BPM 30

Business Process Monitoring

BPE MonitoringProcess InstancesProcesses with missed deadlineError DiagnosisRestart processesRFC Monitor

© SAP AG 2004, TBIT40 08 BPM 31

Technical Monitoring of Business Processes

Technical monitoringEntry from message view (Integration Engine)Entry from process view (Business Process Engine)Navigation between the monitoring tools

Integration in Monitoring Infrastructure

Process Engine Component Test (Runtime Workbench)Technical Process Monitoring(end-to-end)SAP Alert Framework

Business AlertsSAP CCMS integration

System failures

© SAP AG 2004, TBIT40 08 BPM 32

Current Process Modeling Approaches

Business ViewBusiness blueprintingProject planningHigh-level executive model

Cost advantage via online salesReduced days supply inventoryCustomer Self-InformationInteractive configurationSpeed up buyingConsistent Dealer DatabaseOnline informa-tion to customer reduces time of communicationPooled data on cars availableVisibility of tracking statusSpeed up handing overof vehicleIncreased customer satisfaction

OEM DealerImporter

ProductionProduction

ReservationPlanning

Goods ReceiptProcessing

Vehicle Specification/Search Request

via Internet

ShipmentTracking

Transport Control

Vehicle Locating and

Allocation

Order Processing

Order TrackingOrder Tracking

ValuePotential

ValuePotential

$ 800 per vehicle**From 75 to35 days**

5.1%***

27.2%***

7.5%***

12.6%***

5.5%***

Up to 50%2 months- 2 weeks*$ 250 per vehicle**Up to14%**

Business Benefits Business Benefits

Reduced delivery times

Cost advantage via online salesReduction in Supply Chain CostsReduced inventoriesCollect information about customer requirements and preferencesImproved market intelligenceFaster reaction to market trendsIncreased customer satisfactionIncreased planning security and quality

Management/Business Analyst

Scenario Maps/ Solution Maps

IT Specialist/Developer

Dynamic Implementation ViewExecutable processesState engineProcess execution model

Business Processes

Business Analyst/Developer

Static Implementation ViewImplementation informationComponent viewProcess configuration model

Business Scenarios

© SAP AG 2004, TBIT40 08 BPM 33

Unified Business Process Management

One Architecture for workflow and automated processes

Process logic decoupled from applications

Flexible process design & configuration

Integrated inSAP NetWeaver

Unified approach for A2A and B2B Integration

Open StandardsSupport

Unified Modeling Environment

Model drivenImplementation as far as possible

One common Repository

SAP ExecutionApplications& Composites,

SAP XI & WorkflowBusiness Objects

MonitoringTechnical Process Monitoring

Business ActivityMonitoring

ProcessConfiguration

ModelingDesign

ProcessMonitoring

ProcessExecution

BusinessActivity Monitoring BPM

Business Events

Business Objects

Enterprise Services

Business Activities

© SAP AG 2004, TBIT40 08 BPM 34

Unified BPM: High Level Architecture

Process Models& Abstractions

Co-Development with IDS Scheer AGbased on:

ARIS Modeling UIUnified Look & FeelModeling Views & Roles

SAP NetWeaver RepositoryVersioningSoftware Logistics

SAP ExecutionSAP Applications & CompositesccBPM (SAP XI)WorkflowBusiness Objects & Services

Complementary Monitoring TechnologyTechnical MonitoringService InfrastructureBusiness Activity Monitoring (BAM)

Process Efficiency MonitoringEvent Resolution

UI Framework

BAMTechnical

Unified Modeling UI

MONITORING

MODELING

Workflow

Composite Application

Process Engine

Monitoring Data Collection

Application

EXECUTION

REPOSITORY

© SAP AG 2004, TBIT40 08 BPM 35

Business Process Management : Unit Summary


Understand the need for Business Process Management in the Integration Scenario

Create an Integration Process (Business Process) in the Integration Repository.

Use a Integration Process (Business Process) in configuring a scenario.

Describe runtime aspects of Integration Processes (Business Processes).



© SAP AG 2004, TBIT40 09 Server Administration 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Server Administration: Unit Objectives


Explain which XI components reside in the Java and ABAP parts of the Web Application Server

Manage Logs in the J2EE stack.

Use Tracing and Logging of the XI ABAP components.

Define conditions and actions for troubleshooting.


XI 3.0 components in SAP Web AS 6.40

ABAP

ICMCentral Monitoring


JRFC

J2EE

Adapter Engine

HTTP(s)

HTTP(s)

OpenSQLfor Java

OpenSQLfor ABAP

SLD

Integration Builder (IR, ID)

Runtime workbench

XI Tools

Mapping runtimeIntegration Engine


Web AS 6.40 - key architecture points

J2EE stackSQLJ layer for database connectivityAll objects stored in databaseSLD is delivered with the J2EE EngineUME for user management

MiddlewareJRFC replaces JCo for J2EE to ABAP connectivity

ABAP stackIntegration Engine is part of BASIS (and corresponding support

packages)


Integration Engine Administration

SXMB_ADMAdministration:•Tuning capabilities for queues:

• Special queue for large messages• Balancing between parallel queues

•Schedule Jobs

Configuration:•Time-controlled message processing•“Switch procedure“ for message deletion•Pipeline Definition/Settings


J2EE Engine – Administration overview

J2EE Engine Administrator Configuration tool

Offline configuration editor


Tracing and Logging

J2EE-based components of XI use standard logging of J2EE EngineSetup via Log Configurator Service in Visual Administrator tool


Standalone Log Viewer UI

Connect to any number of WebAS servers (ABAP/J2EE)


Integrated Log Viewer UI

Accessible via J2EE Visual Administrator tool


Trace and Log Files for the XI J2EE components

Under <J2EE_dir>/cluster/server0/log/applications/com.sap.xi

repository.logdirectory.logmapruntime.logrwb.logxi.log

repository.trcdirectory.trcmapruntime.trcrwb.trcxi.trc

Default trace file for entire J2EE Engine:<J2EE_dir>/cluster/server0/log/defaultTrace.trc


Trace and Log Files in the ABAP Part

Usage of logging parameter:You set this parameter when you want to analyze message processing as it enables you to document either individual steps, or all steps in a pipeline.


Trace and Log Files in the ABAP Part

The parameter TRACE_LEVEL enables you to locally set the trace level for all pipelines in an Integration Engine.


Defining Conditions and Actions for Troubleshooting

In the Integration Engine, you can specify conditions for troubleshooting in inbound messages that trigger particular actions (Example: Writing trace and log information to a file).

The procedure for creating a conditioned action is divided into the creation of one or more conditions and one or more actions.


Integration Builder – Administration page

System informationAdministration of locksMigration tool


BPE trace

In case of any problems or error situations it is recommended toturn on tracing by using transaction SWELS


Summary

SAP introduced significant changes in the SAP Web AS architecture for version 6.40.

In particular, improved J2EE Engine architecture allows better performance, system administration, and monitoring

There are also better performance tuning capabilities for Integration Engine


Server Administration: Unit Summary


Explain which XI components reside in the Java and ABAP parts of the Web Application Server

Manage Logs in the J2EE stack.

Use Tracing and Logging of the XI ABAP components.

Define conditions and actions for troubleshooting.


Security

© SAP AG 2004, TBIT40 10 Security 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



Security : Unit Objectives


Understand User Management and security for the Exchange Infrastructure.

Describe the built-in users and roles in XI.

Implement message-level security.

Implement channel-level security.

Place the Exchange Infrastructure in the network landscape securely.

Manage the J2EE key store.


Why Is Security Necessary?

Business processes executed using XI have to be done in a secure manner. XML messages which contain confidential business data need to be transported over a secure connection

Security requirements also apply to communicating XI components- securing information like user names and passwords

The messaging system has to be sited securely in the network environment.


Security Topics

User Management, Authentication & Authorization

Message level security

Network and Communication Security

Recommended setup for inter-enterprise connectivity

Certificate management in the J2EE key store


User Administration And Authentication

All components of XI 3.0 that run on the SAP Web AS use the underlying infrastructureprovided by the Web AS for the following:

User managementAdministrationAuthorizationsAuthentication

(The only exception is for the J2SE adapters)


User Administration And Authentication

User StoreStandard: Users are maintained in the ABAP user storeCan also be integrated with LDAP based user administration

Certificate StoreXI and RNIF protocols support message level security based

on digital signatureRNIF protocol also supports encryptionThe required certificates to be used need to be entered into

the key store of the J2EE engineIn the Integration Directory these certificates are referred by

the name of the key store view and the certificate nameRecommended to store CA certificates in the TrustedCAs view


Users

With respect to authentication and authorization, we distinguish two major scenarios:

During design and configuration, dialog users communicate through the Integration Builder with XI.

At runtime the actors are computer systems rather than humans!

1. At design and configuration time(Integration Repository/Directory)

2. At runtime

Computer systemsReal User


Dialog Users

Dialog users represent human users that log on through the various UIs of the Integration Builder

Dialog users are generally maintained in the ABAP part of the SAP Web AS

The roles for the different dialog users are predefined and shipped with the installation


Service Users

Service users provide dialog free access to XI components

Service users have the SAP user roles on the ABAP part of the Web Application Server

They are made available on the J2EE part as user groups

Service users have the required authorizations to access the required services on the addressed XI components

Service users are created during installation

Names and passwords can be assigned during installation


Service Users During Design And Configuration

XIREPUSER – Access the XI Repository for Design

XIDIRUSER – Access the XI Directory for Configuration

XIISUSER - Get Cache-updates from XI Directory to RuntimeCache

XILDUSER - Get Business System Name from System Landscape Directory

Integration Builder


(ID)


(IR)

IntegrationServer

(IS)


Central Monitoring

SAPSystems

3rd PartySystems



XIISUSER

XIREPUSER XIDIRUSER

<YOUR XI USER> <YOUR XI USER>


XI Service Users In Use During Runtime

XILDUSER – Get Business System Name from System Landscape DirectoryXIRWBUSER – Get monitoring information to Runtime WorkbenchXIISUSER – Get Cache-updates from XI Directory to Runtime CacheXIAPPLUSER – Access XI Engines for message processing (SAP template)XIAFUSER – Access Adapter Framework

Central MonitoringXIRWBUSER

SAPSystem

IDocsRFCs

SAP Web AS ≥ 6.20Proxy

3rd PartyApps

FileDB

JMS

Apps of BusinessPartner


Proxy Runtime

PartnerConnectivity Kit

Apps/Systemsof (small)

Business Partner

IntegrationServer


SystemLandscapeDirectory


Integration Engine

Adapter Engine

XILDUSER

customer specific copyof XIAPPLUSER XIAFUSER

XIISUSER

XILDUSER

<User from Directory Configuration>


Default Service Users In XI Systems And Their Roles

Created automatically at installation time.

Referenced in the Exchange Profile.

In the future it will be possible to create custom UserIDs at installation time

<Your XIREPUSER> must have the role: SAP_XI_IR_SERV_USER

<Your XIDIRUSER> must have the role: SAP_XI_ID_SERV_USER

<Your XIAPPLUSER> must have the role: SAP_XI_APPL_SERV_USER

<Your XIISUSER> must have the role: SAP_XI_IS_SERV_USER

<Your XIRWBUSER> must have the role: SAP_XI_RWB_SERV_USER

<Your XIAFUSER> must have the role: SAP_XI_AF_SERV_USER_MAIN

<Your XILDUSER> must have the role: SAP_BC_AI_LANDSCAPE_DB_RFC


User Maintenance

Users and roles are maintained via the standard Web AS ABAP user management (SU01)

After a short delay, the updated users are automatically replicated to the J2EE engine

J2EE User maintenance

in Visual Administrator tool Security provider service

UME (User Management Engine) available as part of J2EE engine


J2EE User Maintenance

Visual Admin tool

UME frontend


Security Topics







Security – Availability With XI 3.0

Availability

Levels of Security

XI 1.0 /

XI 2.0

XI 3.0

XI protocol

XI 3.0

RNIF

Connection Level Security(HTTPS)

Message Level Security (for B2B)

Signature

Data Integrity

Non-Repudiation of origin

Non-Repudiation of receipt

Encryption

Technology WS-Security (XML-Signature) S/MIME


Security – Outlook

Availability

Levels of Security

XI 1.0 /

XI 2.0

XI 3.0

XI protocol

XI 3.0

RNIF

Connection Level Security


Signature

Data Integrity



Encryption

Focus of future security enhancements for XI


Message Exchange

In general, the message exchange between business systems can beseparated into two communication segments that are treated differently from an authentication and authorization point of view:

1. Sending System to Integration Server

2. Integration Server to Receiving System

Business System XI 3.0 Business System

HTTP(S) HTTP(S)Configuration done in the Integration Directory

Technical communication configured only once


Message Level Security

Message level security enabled through the use of digital signatures in XI 3.0

Digital signatures authenticate sending partner and ensure data integrity

Adds security qualities to communication level security that arerequired for B2B communication

Message level security for XI 3.0 protocol is based on the Web Service security standard

RosettaNet employs the S/MIME standard

Encryption ensures that the message content is confidential Only supported by the RNIF protocol


Archiving Secured Messages

For non-repudiation, secured messages are archived in the non-repudiation store

For each secured message the following data is stored:

The raw messageSecurity policy as configured in the

directoryReferences to certificates in the key storeIdentification of the certification used

The archive can be monitored using the Runtime Workbench

The non-repudiation archive is only available for the RNIF protocol


Security Topics







Network And Communication Security

HTTP and SSLXI runtime components support encryption of the HTTP data stream using SSLA certificate must be installed on the server component based on X.509 to enable HTTPsConfiguring SSL for message exchange for ABAP and Java are differentSSL can also be configured for technical communication like cache updates and respository access in the directory

RFC and SNCConnections between SAP components can be secured by SNCSNC supports three levels of security protection

•Authentication only•Integrity protection•Confidentiality protection

WebAS security guide explains how to set up SNC


SSL And SNC For Secure Connections

Secure connection possible between the following

Between adapters and Integration ServerBetween business systems and Integration ServerBetween PCK and Integration ServerBetween business systems and adaptersCache updates


Security Topics







B2B Communication – Recommended Setup

ExternalPartners

Inte

rnet

Fire

wal

l

Fire

wal

l

Fire

wal

l

Fire

wal

l

Inner DMZ

Outer DMZ

ServerLAN

ApplicationGateway

ISBusiness Systems

Proxy

Proxies and application gateways are placed in the outer DMZ providing access control between Internet and internal networks


Security Topics







The J2EE Key Store

Trusted certification authorities on J2EE key store


Requesting A Server Certificate

Creation of server certificate


Importing the Server Certificate

Import the certificate signing response file into your key store


Import The Partner Public Key

Import the public key of your partner


Viewing The Public Key

Partners public key in the J2EE key store


User Autentication

User authentication for the different views created


Further Documentation

XI 3.0 Security Guide

SAP Web As Network and Communication Security:This section describes the network and communication security for the SAP Web AS.

SAP Web AS Security Guide for ABAP Technology:This section describes the security aspects involved with the SAP WebAS when using ABAP technology.

SAP Web AS Security Guide for J2EE Technology:This section describes the security aspects involved with the SAP WebAS when using Java or J2EE technology.


Security : Unit Summary


Understand User Management and security for the Exchange Infrastructure.

Describe the built-in users and roles in XI.

Implement message-level security.

Implement channel-level security.

Place the Exchange Infrastructure in the network landscape securely.

Manage the J2EE key store.



© SAP AG 2004, TBIT40 11 B2B Industry standards / 2

Lecture topics

Topics

XI Overview




Runtime

Runtime Workbench

Adapter Framework



Security



B2B and Industry Standards : Unit Objectives


Explain the XI Infrastructure for supporting B2B scenarios and Industry Standards.

Describe the configuration objects to use for implementing B2B scenarios.

Describe SAP Business Packages for Industry.


B2B And Industry Standards Support – ChallengesBusiness Partners

BusinessPartner

Application

SAPApplication

Marketplaces

OtherIntegration

Solution

B2B Tool

B2B Tool


SAPApplication

Hard-codedIntegration

WorkflowTool

Industry standardAdapter

EAITool

MainframeApplication

Secu

rity

Industry Standard Protocols

• Different solutions for A2A and B2B scenarios

• Custom solutions to connect to Industry Standards compliant business partners

• Substantial effort to develop and support mappings to standard interfaces

• Small business partners have to invest heavily to be industry standards compliant

• Different solutions used to connect to Marketplaces

• Use of proprietary technologies for security handling in B2B scenarios


B2B In XI 3.0 Overview


B2BMessaging

Secu

rity

Small Trading Partners


BusinessPartners

BusinessPartners

AnyApplication

SAPApplication

SAP XI

Marketplaces


B2B In XI 3.0


B2BMessaging

Secu

rity


Message Interfaces

Business ProcessesMappings

Business Scenarios





BusinessPartners

BusinessPartners

Integration Server

BPE

IntegrationEngine

Adapter Engine



Security Handling

AnyApplication

SAPApplication


B2B Related Configuration In The Directory

Creation of PartyThe new object party facilitates the B2B functions of SAP Exchange

Infrastructure and contains the following information:Name, description, and additional identifiers (DUNS, GLN or SCAC) of

the party


B2B Related Configuration In The DirectoryCreation of Service

The new object service generalizes business systems.

A service can represent:A business system (in A2A scenarios)Semantical units (grouping of interfaces), which are used mainly forrouting purposes in the communication between multiple B2B parties. An example would be a specific PIP® (RosettaNet).A business process



Creation of a Channel

Communication channels can be used in twodirections

Sender communication channel-Receiver communication channel

For configuring specific adapters you can use the predelivered communication channels called channel templates

Channel templates also contain the security policies

Contains specific information for the messageprotocol, transport protocol, URL, logon data and adapter specific configuration

This also helps in the central configuration of adapters in the Integration directory



Creation of Sender and Receiver Agreements

The new objects sender agreement and receiver agreementdescribe which channel to use and specify the party related security settings like certificates

The sender agreement is used on the Integration Server for inbound processing, the receiver agreement for outbound processing.

Sender agreement and receiver agreement can be subsumed under the term „collaboration agreement“.


B2B Security Details

Availability

Levels of Security

XI 1.0 /

XI 2.0

XI 3.0

XI protocol

XI 3.0

RNIF

Connection Level Security(HTTPS)


Signature

Data Integrity



Encryption

Technology WS-Security (XML-Signature) S/MIME


B2B In XI 3.0

Collaboration Partner Data in the Integration Directory

Manages technical characteristics of partners to facilitate document exchange such as

Party identificationMessage formats and versions supportedSecurity requirementsCollaboration Agreements

Partner Connectivity Kit For small business partnersEnable business partners of XI customers to conduct XML

document exchange with XISmall scale easy to use client

B2B security (Signature/Encryption)

XI as marketplace messaging infrastructure


SAP XI Provides Industry Standards Technology


Secu

rity

B2BMessaging

Integration Repository & Integration Directory



BusinessPartners

BusinessPartners

Integration Server

BPE

IntegrationEngine

Adapter Engine

SAPApplication

Any Application


Industry Standards Support


Message Interfaces

Business ProcessesMappings

Business Scenarios



Integration Server

BPE

IntegrationEngine

Adapter EngineCollaboration Profiles

Adapter Framework

SAP CRM

SAP Industry SolutionIDOC/Proxy

Business Partner

Application↔Standard

Business Doc Schema

Industry StandardProtocol


SAP Business Packages For Industry Standards

Provides Solution Kits for specific industries and delivers mappings for RosettaNet and CIDX

Application adoptionEnhance business applications like mySAP CRM or mySAP SCM to

support SAP Business Packages for high priority processes

MappingIncluding message sets for the industries according their prioritySupport mappings: versions, upgrade, maintenance

Process IntegrationSAP Business Packages’ message protocol implementation (such as

RNIF 2.0 and RNIF 1.1 for CIDX)Provision of Collaboration AgreementsBusiness Process Management support


B2B and Industry Standards : Unit Summary


Explain the XI Infrastructure for supporting B2B scenarios and Industry Standards.

Describe the configuration objects to use for implementing B2B scenarios.

Describe SAP Business Packages for Industry.