sap ecc6.0 ccbpm in xi

SAP AG 2004, BPM@BSGs / Volmering / 1

Agenda

Architecture

Process Design with the Graphical Process Editor

Basics: Overview Step Types, Correlations, Container

Step Types in Detail

BPEL4WS Import and Export


Objectives

After completing this unit, you will be able to:

Understand the basic design principles of cross-component BPM

Define integration processes

Import/export integration processes to/from non-SAP systems


Integration Server

Business Process Engine

ccBPM Architecture - Overview

IntegrationRepository

AbstractInterfaces

IntegrationDirectory

Integration Process(Configuration)

Routing Rules

Integration Builder

Integration Process(Definition)

(References)M

es

sa

ge

Me

ss

ag

e

23

1

4

Process / Message Store

ProcessExecution

CorrelationHandling

Routing MappingChannel

Det.

Adapter Engine

Pro

cess

Ed

ito

r

Integration Engine


Directory

ScenarioScenario

Party

RepositorySWCV

Architecture – Definition

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

**

Integration ProcessIntegration Process

Flow

If

**

Mapping RelationMapping Relation

ProcessProcessProcess

Process

MessageMappingsMessageMappings

IdocIdoc

RFCRFC


Agenda

Architecture







Output Area Object Area

Header

Overview Area

Edit AreaProperties

Area


Process Editor Settings

Personal Settings• Default Editor • Horizontal/Vertical Display of Process Definiton• Hide Output Area• Error Level for Processing Log• Automatic refresh for BPEL4WS

Detach, thenmaximize window


Agenda

Architecture


Basics: Step Types, Correlations, Container




ccBPM - Process Step Types

Receiver Determination

Receive

Transformation

Process Flow Control Relevant:

Send

Container Operation

Messaging Relevant:

Control

Loop

Undefined

Fork Switch

Wait

Block


Block-oriented Design

Nested blocks Deadline branch

Exception branch


Container – Process Data

Container Consists of an unlimited number of container elements

Carries the overall state of the process at runtime – references to messages, loop counters, …

Allows to access data by a name relevant within the process

Container element (Variable declaration) Consists of a name to address data in the process

Can be typed to Simple XSD types: XSD:date, XSD:time, XSD:integer, XSD:string Abstract Interface Receiver

Can be Multiline (a vector of the types above)


Process Container and Local Containers

Container elements of inner block SendParallel are not

visible in outer block

In inner block CheckResult

container elements of outer block

SendParallel and Process container

are visible


Correlations

Correlation Handling Routing of messages (Business

Documents) to process instances

Dependencies rely on business data (e.g. Message ID, Order ID, Business Partner ID, Company Code)

Correlations define these dependencies


Correlation

Enter name of correlation

Define elements to be used to correlate

the messages

Specify messages that satisfy the correlation at

runtime

Specify which element is to fill the corresponding element in the correlation container (use

context objects or XPath)


Receive Step – Starting a Process

Several start messages: Receive steps in a Fork

Each Receive activates / uses correlation

One start message: Receive step is 1st step

Message to be received

Indicator Start Process

Mode Asynchronous

Can activate correlations


Receive Step – Sync/Async-Bridge

Communication between a synchronous and an asynchronous business system:


Send – Send Message (Asynchronous)

Acknowledgement:• None• Transport• Application

Receiver Determination:

• Send context• Receiver List• Response to Message

Exception:Enter Exception to be triggered when a system

error occurs (permanent

error)

Activate Correlation for send step in a ParForEach

block


Send – Send Message (Synchronous)


Send – Send Acknowledgement

Send positive Acknowledgment – usually used in a

branch that defines normal processing

Send negative Acknowledgment – usually used in an exception handler

(exception branch of a block)

Receiver of the acknowledgment is automatically determined from the header of the

message


Send – Sync/Async-Bridge

Closing a Sync/Async-Bridge: send step sends the response from the asynchronous business system to the synchronous business system


Agenda

Architecture






Transformation Step

Displays Source and Target Messages defined in the interface mapping.- Specify the container elements that contain the message reference or that the message reference is to be written to


Receiver Determination – List of Receivers for Send

Multiline container element for receiver

list, Category Receiver

Receiver Determination step used to get a list of

receivers

Send step uses list of receivers


Switch – Defining Processing Branches

Otherwise branch(created automatically)

Executed if no other branch returns TRUE


Container Operation – Assigning a Value


Container Operation – Appending a Value

Multiline Element


Block – Exception Handling

Define exception

Assign exception to exception handler

Throws exception – process continues in

exception branch


Block

Basic design element

Blocks can be nested Block hierarchy defines scope/visibility of container elements (local

variables)

Also: local correlations

Modes Default

DynamicParallel For Each (ParForEach) – Dynamic parallelFor Each – Dynamic sequential

Basis for deadline monitoring and exception handling


Block – ParForEach (Dynamic Parallel Processing)


Block – For Each (Dynamic Sequential Processing)


Control – Trigger Exception


Control – Trigger Alert

Alert Message will be displayed

in Alert Inbox


Control – Cancel Process


Fork – Independent Processing Branches


Loop – Repeat Execution of Steps


Wait – Specifying Start Time for Next Step


Agenda

Architecture


Basics: Step Types, Correlations, Container




Standards Support

Support for open standards BPEL4WS 1.1

(BPM in SAP XI 3.0)

Active participation in standards, e.g.:

Advance BPEL4WS 1.1 together with IBM, BEA and Microsoft

Graphical Process Editor Supports process design

adhering to standards Import/ export of standard

process descriptions

Cross-Component BPM adheres to evolving future standards via a pluggable import/export-interface concept .


BPEL4WS

Business Process Execution Language for Web Services

Language for the formal specification of business processes and business interaction protocols

Extends Web Services interaction model enabling it to support business transactions:

Temporal and logical dependencies between activities, especially Web service interactions Association between a message received by the Web service and a particular process instance Error handling and compensation behavior Binary relationships between process roles


BPEL4WS 1.1

BPEL4WS as exchange format for exporting / importing integration processes to/from non-SAP systems

BPEL4WS not intended for importing or exporting integration processes between Integration Repositories (use import function instead)

WSDL View

BPEL4WS View


BPEL4WS Export


BPEL4WS Import Select .zip file containing (.bpel

and .wsdl file)

Select Message Interface (should be

created before starting the import)

sap ecc6.0 ccbpm in xi

Documents

container step types

overview step types

step message

process mode asynchronous

types aboveprocess container

xpathreceive step

simple xsd types

exportprocess design