websphere process integration introductionw4.uqo.ca/iglewski/ens/inf6033/extra/2008/bi1115g02.pdf©...

© Copyright IBM Corporation 2005Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 3.3.1

WebSphere Process Integration Introduction

Unit 2

© Copyright IBM Corporation 2005

Objectives

Discuss Service Oriented Architecture (SOA)

Lay Groundwork to Understand Process Integration– Business needs for Process Integration– Vision and Reference Architecture– Complementary products– A New Programming Model– What are the Components – User Roles

Understand Product Heritage


Packaging business functions from applications in a simple and standardized way creates services that are available for use Services are used directly to get the right information to the right people at the right timeServices can be reused and combined to deploy composite applications to address new opportunities or changing business priorities.Increasing use of web services based on open standards complements existing services technology

The Key to Business Flexibility

The flexibility to treat elements of business processes and the underlying IT infrastructure as standardized components (services) that can be reused and combined to address changing business priorities

Service Oriented IT Architecture (SOA)

Services are the “building blocks” for business processes


Service-Oriented Architecture (SOA)

What is a service?– A self-contained entity that performs a distinct business function– A service is defined with explicit interfaces, independent of any specific

implementations– The service interfaces provide the contract between service requestors

and service providers

How do services interact?– May be invoked by clients inside and outside the enterprise– May interact with each other, invoking operations, exchanging data– Multiple services can be composed into larger services– Can be mediated


WSDL – Web Services Description Language

Web Services Description Language (WSDL) provides an industry-standard way of describing services in a Service-Oriented Architecture

Defines the public interface to an available service– PortType (type or class)– Operation (method)– Message (method signature)– Part (method parameter)

Defined in XML– Industry standard language– Recognizable and compatible across divergent technologies– Service definitions are flexible and extensible– Capable of describing a wide range of services


Separation of Concerns

Operating Environment

Business Need Necessary Functions & Services Composite Application(s)

1. Decompose the Business Need into its necessary function and services (Separation of Concerns)

2. Reuse/Create Business Application Specific function and services (Create/reuse services)

3. Utilize common services provided by the Operating Environment (Leverage Infrastructure)

1 2

3

By decomposing business needs into necessary services and composing combinations of existing and newly created services that represent business processes …

RESULT: Implemented Composite Application representing a business process


A Typical Manual System: Loan Application

CustomereXtendBank

Loan Officer

1. Fill in Loan Application at Loan Dept

2. Loan Officer enters loan information (3270 emulator)

CICS

3. Requests FAX Credit Report

5. Makes a decision on Loan Application

4. Makes decision as to whether this Loan application needs approval.

6. Loan Officer reserves Funds

7.Sends email to Assess Business Risk –(Government Watch List)

8. Notifies customer

Business Analyst(Rules change frequently)

Developer

Loan Officer

Loan Officer Loan Officer Loan Officer Loan OfficerBank Manager

Application Server


Challenges with the Old System

Takes too long to process loan applications

Paper-based human interaction in loan processing is error prone

Many different technologies are involved (legacy, app servers, email apps …)

Integrating people, processes, and information is difficult

Manual work is needed to “undo” work performed if there is a process failure

Difficult to propagate and react to business rule changes


Loan Application as an Automated Business Process

Pre-Approved?

YES

NO

Reserve Funds

Loan Officer Approval

Assess Loan Risk

Approve?

Send Rejection Email

YESNO

Too Risky?

YES

NOSend

Confirmation Email

End

Service (CICS)

LegendServices

Business Rules

Service (Web)

Service (J2EE)

Service (Web)Service (JavaMail)

Service (JavaMail)

Service (Staff)(Human interaction)

Create Loan App

Start

Credit Check


IBM WebSphere Integration Reference Architecture

IT Service Management

Business Innovation & Optimization Services

Business Application

Services

ProcessServices

Information Services

Development Services

Interaction Services

Partner Services

Applicationand

InformationAssets

Connectivity Services

Modular product portfolio built on open

standards

Ability to develop, deploy and manage

Integrated role based tools for development

& administration

…utilizing common install, administration,

security and programming model

Functionally rich adopted incrementally

IBM WebSphere Integration Reference Architecture


Process Integration Is Enabled by Business Driven Development

Service Oriented Architecture – Focus on Flexibility and Reuse– An approach for designing and implementing distributed systems that

allows a tight correlation between the business model and the ITimplementation

Model Driven Development – Focus on Efficiency and Quality– A style of enterprise application development and integration based on

using automated tools to build system independent models and transform them into efficient implementations

Business Performance Management – Focus on Responsiveness and Optimization– A monitoring and management approach that leverages integrated

resources to achieve aligned, accountable, and action-oriented business operations


Business Driven Development – Scenario Flow and Products

Discover– WebSphere Business Modeler (WBM or Modeler)

is used to create the business process, model the tasks and forward- engineer to BPEL.

Develop– Rational Software Architect (RSA) opens the Model

as UML and is used to create Session EJBs that implement the Modeler tasks. In addition, RSA is used to create the necessary JSPs for the manual tasks that are part of the Model. The main component of RSA creating this code is theRational Application Developer (RAD).

– The BPEL is imported into WID. This maps Modeler process to the BPEL language in WebSphere Integration Developer (WID). The various Modeler tasks are mapped as Services (Automated Tasks) or Staff Activities (Manual Tasks) in WID. WID is also used to create additional Services from the WSDL services definition file imported from Modeler. Next implementation code is added to call/invoke the Session EJBs created in RSA. Choreography of the process is done through BPEL.

Deploy– The deployment of the Business Process is

accomplished using WebSphere Process Serverruntime engine.

– WebSphere Business Monitor is used to gather metrics used to optimize the process

Prioritize Plan Manage Measure

Monitor Optimize Iterate


Process Integration Vision and Related Products

Process Execution/Choreography

Services

InteractionGlue

Process Modeling

Monitor Analysis

Optimize

Existing Components

Process Requirements

Manage Execution

Participate

Tool: Rational Application Developer

Tool: WebSphere Integration Developer

Tool: WebSphere Business Modeler

Tool: WebSphere Business Monitor

Run Time: WebSphere

Process Server

Web & Portal Clients

This Course(plus

Adapters)


User Roles Defined

A user role is not a real person

“A user role is an abstract collection of needs, interests, expectations, behaviors and responsibilities characterizing a relationship between a class or kind of user and a system.”[Constantine and Lockwood, 1998]

Individuals assume a user role– One person may assume many roles– Defined by activity and phase


User Roles and Process IntegrationLine Of Business Manager– No programming experience; focus is on business strategy & performance

Business Analyst– No programming experience; focus is on business performance & process design and

optimization

Integration Developer– Focus is on SOA/EAI solutions, business process automation– Some basic programming experience (loops, conditions, string manipulation)– Expects tools to simplify and abstract advanced IT implementation details

Application Developers– Focus is on development of application specific business logic (e.g. EJBs, POJOs,

COBOL) for components and services used by a business integration solution

Server Administrators– Focus is on Server management and maintenance

Solution Administrators– Focus is on management and maintenance of deployed business integration solution


Roles Applied to an End-to-End Taskflow

Strategy &Initiation

Analysis &Planning

Build & Test

Deploy toProduction

Monitor & React

Green-light from business and IT decision

makers

Solution meets design specifications

N Y N Y

Roles InvolvedLOB Manager

Roles InvolvedBusiness AnalystIntegration Dev’rLOB Manager

Roles InvolvedIntegration Dev’rApplication Dev’r

Roles InvolvedServer Admin’rIntegration Dev’rApplication Dev’r

Roles InvolvedSolution Admin’rServer Admin’rBusiness AnalystLOB Manager

Modify business rulesto adapt quickly to

market

WebSphere Business Modeler

WebSphere Integration Developer

WebSphere Business Monitor

(transform)WebSphere Process Server


Integration Developer

The Integration Developer– The key target Role for WebSphere Integration Developer

Integration Developer Responsibilities and Tasks• Creates interfaces and interface maps• Creates business objects, data maps and models data relationships• Creates business rules• Models & creates automated business processes (aka: workflows, process

flows)• Creates points for human interaction• Models & creates service-oriented view of a solution• Builds solutions either top-down, bottom-up or meet-in-the-middle

Of course, Application Developers needed too!– Consideration of integration during application design


Programming Model – Today

Data

Invocation

Composition

JDBC Row Set

Java Bean, JAXB ObjectJMS Message, JCA Data

EJB Transfer Bean

JAX-RPC POJO, EMF Data, XML DOM

EJB StatelessSession Bean

JAX-RPC, JDBC

JCA, JMS

EJB Stateless Session Bean Composition

Java Bean Composition

WebSphere InterChange Server Collaborations

Flow Definition Language (FDL)BPEL4WS


Programming Model – Simplification

Composition

Invocation

Data Service Data Objects (SDO)(Plus extensions)

Service Components (SCA)(Plus extensions)

WS-BPEL(Plus extensions)


Programming Model: Triangle of Truth

Service Component Architecture (SCA)

Business Objects(SDO-based technology)

BPEL + Extensions


WebSphere Process Server andWebSphere Integration Developer Components

SOA Core

ServiceComponents

WebSphere Application Server (J2EE Runtime)

SupportingServices

BusinessRules

BusinessRules

Human TaskManager

Human TaskManager

BusinessProcessesBusiness

Processes

Business State

Machines

Business State

Machines

SelectorsSelectorsRelationshipsRelationshipsBusiness Object MapsBusiness

Object MapsInterface

MapsInterface

Maps

Service Component Architecture

BusinessObjects

Common EventInfrastructure


SCA – Conceptual View – Key ConceptSCA – Component, Interface, Implementation, and Reference

Interface

Component = “Service A”

Service CReference

Service BReference

Implementation

Business ProcessBusiness

ProcessJava

JavaState

MachineStateMachine

BusinessRuleBusiness

Rule

HumanTaskHuman

TaskSelector

SelectorInterface

MapInterfaceMap

Java InterfaceJava

Interface

WSDLPort TypeWSDL

Port Type

Java InterfaceJava

Interface

WSDLPort TypeWSDL

Port Type


Module: Order

SCA and Business Objects – Conceptual View

Service Component Architecture (SCA) is the component modelComponents may be wired togetherBusiness Objects are the data flowing on wires between Components

Business Rule:Customer Status

Human Task:Approve Order

Process:doOrder

Import:Credit Check

Web

Web

BOBO

BO

BO

BO

BO

OtherApplications

andModules

OtherApplications

andModules Interface

Reference

Component

Export:doOrder


Component Assembly Editor

ImportReference

Export

Module

Interface


Business ProcessWS-BPEL compliant business process engine

Simplified Process Editor– Optional

Generic Business Process– Operations / Parameters– Service Implementation Details

hidden

Transactions / Compensation


Human Task Manager – Human TasksInvoke work items for humans as human task services– The ‘classical‘ staff activity scenario

Allow humans to invoke services– Any SCA component, e.g. a

business process– Arbitrary Web services – Services performed by humans (ad-

hoc)


Business State MachinesState MachineImplementation– Based on UML 2.0

State Machine– Event driven business processes– Creates WS-BPEL

under the covers

Simple/Complex States– Entry/Exit

Transitions– Guards– Actions (invokes)– Timeout


Business Rules

Externalize Business Logic from an application (business process)– Easily modify logic that may change– Dynamically Update Rules in Runtime on the fly through Web Interface

• Natural Language Presentation (NLS Enabled)

Most-requested Business Rule functionality– Decision Tables– Rule Sets (If/Then Rules)– Rule Templates

Ease of Use– Rule Group: all artifacts needed for business rule developer are

contained within one component


Transformation Components

InterfaceMap

Import:submitOrderSAP

BO (Order)

BO(SAPOrder)

Interface:doOrder(Order)

Interface:submitOrder(SAPOrder)

BusinessObjectMap

Order SAPOrder

RelationshipOrderID SAPID

Export:doOrder


SelectorClient– Makes a call to the Selector

Component

Selector Component– Chooses which target destination to

invoke using a declared selection implementation

Destination(s)– For each operation on the Selector

Component are associated with the Selector Component

Web-based Administration

Dynamic Links


Common Event InfrastructureAn event occurs when something significant happens in the IT system. – E.g., whenever an application processes a new order or a failure occurs in a

critical part of the system Based on CEI (Common Event Infrastructure)Data about the event are captured in an event object.– The event object has a standardized format called the Common Base Event

(CBE)– The application supplies the business data and WebSphere fills in the details

from the runtime environment such as the server name, J2EE component details and business context.

Event Data

Event ConsumerEvent Consumer

Event ConsumerEvent Consumer

Submit

Event Source Distribute

StoreQuery

Complete

All event objects are passed to the event infrastructure to enable:– Tracking the progress of a business process– Audit trails– Coordinating work between independent

business processes– Monitoring for exceptions in a business process

For example, if the process does not complete within a time limit


Adapters in Process IntegrationAdapters provide– Enterprise Information System (EIS) integration – Encapsulation of functions and events as Services– Common data model called Business Objects.– A consistent framework for access to back-end systems for extracting and placing

data on behalf of the integration broker– Consistent configuration, deployment, and administration

Adapters can be categorized as:– Application adapters (PeopleSoft, SAP) – Technology adapters (JDBC, Flat File)– Custom adapters

Two major types– WBI Adapters (Existing adapters as used with InterChange Server, Message

Broker)– WebSphere Adapters (New adapter architecture based on JCA 1.5)


Adapters and Relationship to SCA

EnterpriseInformation

System


SystemWBIAdapter

NativeAPIs

WebSphere Process Server 6.0MQ JMS

(XML)

Service AImpl = “BPEL”

ServiceImport

ServiceExport Service

Import



ServiceImport

ServiceExportServiceExport Service

ImportServiceImport


System


SystemWebSphereAdapter

NativeAPIs

WebSphere Process Server 6.0

JCA CCIinterface


ServiceImport

ServiceExport Service

Import



ServiceImport

ServiceExportServiceExport Service

ImportServiceImport

WebSphere Adapter

WBI Adapter


WebSphere Process Server – Heritage

WebSphere BusinessIntegration ServerFoundation 5.1.1

WebSphereInterChangeServer 4.3

WebSphereMQ Workflow 3.5/3.6

WebSphereProcess

Server 6.0

Evolution

Capabilities

Capabilities

Leveraged for business process choreography and building open standards based composite applications within a service oriented architecture

Leveraged for advanced human task workflow within WMQ based infrastructure

Leveraged for application synchronization and process driven automation with industry templates

Comprehensive, fully integrated integration server, built on the platform runtime and leveraging WebSphere Platform Messaging for connectivity services


Course Business Scenario: What You Will Build

---------------------------------

TwineBallTwineBall

DB2DB2

CaesarCaesarDB2DB2

HumanTask

Manager

TwineBall Module

CustomerSyncModule

CaesarModule

WebModule

BPCExplorer

Client

FlatFileModule

CustomerTaskModule

WPSDBWPSDBCloudscapeCloudscape

Delivery

Request

Response

AgentDelivery HubRequest

HubOneWay

C:\...\flatfile\outdir

BusinessRules

Manager

WebModule

BRManager

Client

WID / WebSphere Process ServerWID / WebSphere Process Server


Summary

Discuss Service Oriented ArchitectureBuild an understanding of WebSphere Process IntegrationUnder user roles Looked at the new programming modelSurveyed the componentsLooked at the heritage productsUnderstand the course scenario


Exercise

Run script to install software needed for class– User Ids used in class– DB2– WebSphere MQ Client– WBI Adapter Framework– WBI Adapter for JDBC

• Other adapters will be installed later in the course– WebSphere Adapter for Flat Files– WebSphere Integration Developer– WebSphere Process ServerCopy the support files from the instructor machine to your localmachine

websphere process integration introductionw4.uqo.ca/iglewski/ens/inf6033/extra/2008/bi1115g02.pdf©...

Documents