What it takes to be on demand

35
e-business on demand © 2003 IBM Corporation What it takes to be on demand Business Process Integration WebSphere Business Integration Emmanuel Genard IBM Francis Geysermans IBM Dave McCarty IBM

description

What it takes to be on demand. Business Process Integration WebSphere Business Integration Emmanuel Genard IBM Francis Geysermans IBM Dave McCarty IBM. Seminar Outline. Introduction – On Demand Technical Roadmap - PowerPoint PPT Presentation

Transcript of What it takes to be on demand

Page 1: What it takes to be on demand

e-business on demand

© 2003 IBM Corporation

What it takes to be on demand

Business Process Integration WebSphere Business IntegrationEmmanuel Genard IBM Francis Geysermans IBMDave McCarty IBM

Page 2: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

2

Seminar OutlineIntroduction – On Demand Technical RoadmapIntegrate Applications and Business Processes to enable On Demand Solutions

Business Process Integration

● An Introduction to Application Integration and Process Integration● Service Oriented Architecture● WebSphere Business Integration for On Demand Process Integration

------------------- MORNING BREAK --------------------------------------------

Application Integration with WBI Adapters and Collaborations

● WBI Adapters, Business Objects and Mappings● Demo – WBI Adapters and Business Objects● WBI Collaborations, Templates, Deployment and Access● Demo – WBI Collaborations

------------------------- LUNCH ------------------------------------------------------

Application Connectivity - WebSphere Business Integration Event & Message Broker

● Multiprotocol Pub/Sub Message Routing● Message Transformation, Augmentation, and Datasource Integration● Demo – WBI Message Broker

B2B and Business Partner Integration

● WBI Connect

--------------------- AFTERNOON BREAK --------------------------------------

Workflow based Process Integration

● WBI Workflow Business Process Modelling and Monitoring

● Process Modelling in WBI Workbench ● Monitoring with WBI Monitor● Demo – WBI Workbench Modeller

Summary

● Developer Resources

Page 3: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

3

What We Will Accomplish Today

Assumption:

You are developers, programmers, architects, modelers, analysts, technical project managers or technical team leads, with some application development or IT systems background – and Java experience is also suggested

Learn about Application and Business Process Integration

Architectures and techniques available to achieve business process integration

IBM WebSphere Business Integration Products and the WBI Reference Architecture

1

2

3

Page 4: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

4

An on demand business is an enterprise

whose business processes—integrated

end-to-end across the company and with key

partners, suppliers and customers—can

respond with speed to any customer demand,

market opportunity or external threat.

On Demand Business – The “Why”

Page 5: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

5

StructuredCalculations

Data ProcessingTransactions

Open StandardsConnectivity

FlexibilitySimplicity

Modular Componentseasily defined and manipulated

Dynamic definition and operations

Traditional The Internet On Demand

Deepening Integration of IT with BusinessEmerging On Demand Computing Model

Page 6: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

6

Insights about On Demand Businesses

1.

2.

The need for flexibility and innovation forces increased componentization of the overall business and its processes

Applications evolve on a parallel path— becoming increasingly modular

3. Simplification of the underlying IT infrastructure is required to support the changes in the business

Page 7: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

7

Today’s Focus: The On Demand Operating Environment

• Integration • Infrastructure Management

Flexible Financial & Delivery Options

BusinessTransformation

On DemandOperating

Environment

Business P

rocesses

Page 8: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

8

Your Reality: Functional Automation

Historical limitations

• Monolithic applications can’t be reused

• Ad hoc integration creates connections that are difficult to change/maintain

• Lack of standards limits ability to deliver meaningful

interoperability Marketing

Partners

Web

Partners

Sales

Partners

Page 9: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

9

Marketing

Partners

Web

Partners

Sales

Partners

The Looming Reality: Horizontal Process Integration

Advances that make it possible

• Standards for creating services and enabling them to communicate are agreed upon by major vendors

• Infrastructure that supports self-defined, loosely coupled services has emerged

• Tools to incorporate existing assets are available

• Automation and virtualization of systems resources readily available

Customer/Prospect

Page 10: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

10

Horizontal Business Processes Require Next-generation Technology Infrastructure

Increased focus on business flexibility

• Use of open standards to enable communication and integration across the value net

• Partner to sharpen focus and respond to opportunities and threats

Requires an on demand IT environment

• Ability to repurpose application functionality in order to support horizontal processes

• Automation and virtualization of resources

Business Flexibility

IT Simplification

Horizontal Process

Partners Partners Partners

Page 11: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

11

Requires On Demand Operating Environment

On Demand Operating Environment

Open standards are table stakes for an on demand operating environment

Business flexibility through integration of people, processes and information within

and beyond the enterprise

Integration

Infrastructure Management

IT simplification through automation and virtualization, enables access to

and creates a consolidated, logical view of resources across a network

Business Flexibility

IT Simplification

Horizontal Process

Partners Partners Partners

Page 12: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

12

Business Flexibility

IT Simplification

Horizontal Process

Partners Partners Partners

The Capabilities You’ll Need

Automation/Virtualization • Availability• Security• Optimization• Provisioning• Policy-based Orchestration• Business Service Management• Resource Virtualization of Servers,

Storage, Distributed Systems/Grid and the Network

• Business Modeling • Process Transformation• Application & Information Integration• Access• Collaboration• Business Process Management

Integration

Infrastructure Management

Page 13: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

13

A Services-oriented Architecture (SOA) is Key

What is SOA? SOA enables flexible connectivity of applications or resources by:

• Representing every application or resource as a service with a standard interface

• Enabling them to exchange structured information.

Why do you care?SOA helps introduce flexibility in a technology environment. There is growing acceptance of SOA as an approach to integration and to structure collections of interacting applications.

IT Simplification

The flexibility to treat business processes and the underlying infrastructure

as defined components that can be mixed and matched at will

Partner

Partner

Business Flexibility

Horizontal Process

Page 14: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

14

Packaged Apps

Current Systems

New Systems

Build

ExtendModernize

DeployInte

grate Integrate

Integrate

Software Development

Software Development is Key

HorizontalProcess

Business Flexibility

IT Simplification

Partners Partners Partners

Integrating & automating horizontal business processes:• Unique to each business• Competitive advantage

Page 15: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

15

IBM’s On Demand Operating Environment Roadmap for ISVs

Enable applications for back-end business process management,

automation & integration

WebSphere Business Integration

Adopt an open, cross platform application foundation to support IT consolidation

WebSphere, DB2 & Linux

Open server in

frastru

ctureEnsure apps can be customized & integrated at the user improving

people productivity

WebSphere Portal & Lotus Workplace

Certify apps to a secure, provisioned & orchestrated platform lowering

TCO by optimizing system utilization

Tivoli Intelligent Management Software

Page 16: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

16

Integration: Technical Capabilities Required

Enterprise Service Bus

Process ChoreographyPortal Information

Integration

Pub/Sub Queuing Mediation point-to-point

CompensationFlow State Behavior

Business ConnectionsAdapters Web ServicesGateways

PersonalizationPresentation Federation

ReplicationPlacement

Web Services and J2EE Standards

Programming Model Extensions QoSDB

CollaborationFront-endIntegration

People Processes Information

Page 17: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

17

Today Tomorrow Future

People People

Process Process

Information Information

Lotus Domino/Notes Lotus Instant Messaging Lotus Team Workplace WebSphere Portal Lotus Workplace Messaging

Role-based dynamic adaptive workplaces:

•Messaging•Real time & collaboration•Learning•Document management

DB2 Information Integrator DB2 Information Integrator

for Content DB2 Data Propagator IBM DiscoveryLink

Free-form access to data & content

Transaction oriented replication for reference data

Grid standards exploitation

Policy-based, dynamic data placement

WebSphere Business Integration

•43 adapters•57 collaborations• 7 cross-industry solutions•12 industry solutions

WebSphere MQ Family

Integration Technology Roadmap

Enhanced J2EE services

Common event infrastructure for monitoring

WebSphere Business Integration

• B2B hub with onboarding and monitoring

• DashboardExpress offerings

Page 18: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

18

Business Integration Is the Basis of the on demand Business Transformation

•Product Lifecycle Management•Collaborative Product Design•Business Transformation•Total Asset Visibility

•ERP Integration•Order Management•Merger & Acquisitions•Government

•e-Procurement•Market Places•Exchanges

•Supply Chain Management•e-Logistics

•Customer Relationship Management•Human Resources

•Financials•Insurance•Healthcare

•Manufacturing•Telecom•Energy & Utilities•Retail

Page 19: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

19

Separate Business Function and ProcessesCore business application logic should remain in the packaged and legacy applications being integrated.Logic specific to routing and transformation in an application connectivity layer.Cross-application business process logic in a process integration layer.Separating business process logic from business process implementationDefines what needs to be done, when and why, and how it is done, by whom or by which application.Enables the concept of business flow to be separated from underlying organizational and IT resources that support it

Page 20: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

20

Business Process Integration Example: Sales Order Processing

InterChange ServerOrder Management

Application(SAP)

CRMApplication

(Siebel)

Product MasterApplication

(SAP)

Step 1: Sales Order is created in CRM Application

Step 4: SOP validates Customer details (via Customer Manager) & creates or updates Customer as required

Step 5: SOP validates Product details (via Item Manager) & creates or updates Product as required

Step 6: Order is created in OM application with “Answer Back” for final XRef

Step 7: As order status changes in OM, it is automatically updated in CRM

ItemManager

CustomerManager

Step 4a/5a: XRef tables are accessed / updated for Customer / Product as required

Step 2: Adapter detects event & delivers Order BO to Integration BrokerStep 3: Order BO is transformed, Xref’d

& SOP is triggered

OrderStatus

Sales OrderProcessing

Customer MasterApplication(PeopleSoft)

Page 21: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

21

Manage

Interact Integrate

Transform

Model

Accelerate

ServiceOriented

Architecture

ProvenExperience

StandardsLeadership

Secure &Scaleable

SimpleIntegrated

Development

Integration in IBM’s On-Demand Operating Environment

Model business functions and processes

Transform applications, processes & data

Integrate islands of applications and information

Connect & Interact with people and resources anytime, anywhere, with any device

Manage & Monitor performance against business objectives

Accelerate the implementation of intelligent processes

Page 22: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

22

Technical Criteria for Superior Business Process Integration Approach

Logical, distributed hub-and-spoke architecture that provides rapidly scalable, "plug and play" integration

Data and messaging format independence that provides integration flexibility and reduces system implementation and management costs

Integrate both human resources and applications into coherent real world business processes

Single common view of critical business objects across diverse application environments

Business process definitions, procedures and policies captured and stored in a central repository for documentation, ongoing improvements, accessible throughout value chain

Transactions management and long-running transaction supportStandards based runtime, data and modelling environmentDevelopment tools environment for data mapping, relationship management and

process design that provides highly flexible integration managementEnterprise scalability, reliability, availability and performance to meet mission

critical requirements

Page 23: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

23

Service Oriented Architecture

The flexibility to treat business processes and the underlying infrastructure

as defined components that can be mixed and matched at will

Architecture that leverages open standards to

represent software assets as services Individual software assets become building

blocks that can be reused in developing other applications

Shifts focus to application assembly rather than implementation details

Create and integrate new applications out of existing components and applications

• Achieve flexibility to enable “processes built to change”

• Isolate cross application process control flow from participating applications, centralizing it for enhanced flexibility and ability to manage change at business process levels

• Every application and resource is represented as a service with a standard interface which simplifies its activation and the exchange of structured information

• Open standard interfaces to connect services

Bus

ines

s

Tran

sfor

mat

ion

Flexible Financial &

Delivery M

odels

OperatingEnvironment

Business FlexibilityIntegration

IT SimplificationInfrastructure Mgmt

Page 24: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

24

Service Oriented Architecture

Services are typically course (large grained) in granularity, representing complete self-contained functions

● checkOrderAvailability, createBillingRecord, calculateDollarValueFromYen, getStockPrice, auditEvent, checkUserAuthorisation

Service Choreography● Business processes define a set of activities carried out in a sequence to realize a business objective● Each step specifies an invokable action and business rules that define the transition to the next step● Services define interfaces to activity implementations● In SOA the process defining the choreography of services is itself defined as a service (e.g. createSalesOrder)

Component Models● Standards based interfaces (XML, Java, WSDL)● Composite applications assembled together from components into a flow that instantiates a complete business

process● Applications components (EJBs, BPEL flows, Application Adaptors) and People Facing Components● Mediation and transformation of data (business objects) between components performed by the enterprise service

bus

Page 25: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

25

The idea behind the vision

Business Analysts Level Global

Process Design and Modeling

Define Process Automation

Map and relate data

Generate linkages to applications or

services

Islands of Processing

Business Analysts describe , model and simulate the business solution. Show ROI.

Refine the business flows and process steps.

Design the detail of the process automation.

Select, customize and map data, services, rules, and measurements in the process.

Build or customize the inter operation with selected applications and services.

Deploy processes. Monitor, analyse and report on process execution cost.

Technical ProgrammingSkills

Business AnalystsSkills

Feedback

Page 26: What it takes to be on demand

e-business on demand

© 2003 IBM Corporation

IBM WebSphere Business Integration

Page 27: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

27

Business Integration Reference ArchitectureComprehensive Services

Community Integ’n Services

Enterprise Applications

Enterprise Service Bus

Application Services

Monitoring Services

Data/Information Services

Enterprise Data

Application Connectivity Services

User Interaction Services

Process Services

J2EE Extensions

J2EE Container Services

J2EE Base Services

Transaction/ Compensation

Process State Management

Staff Services

Community Management

Document Management

Protocol Services

Transport Services Mediation Services

Process Choreography Services

Common Runtime Infrastructure

Development Tools, ServicesModel, Design, Development, Test Tools

Delivery Services

Experience Services

Resource Services

Event Services

IT Monitoring Process Monitoring

WebSphere BI Modeler WebSphere Studio

WebSphere BI Monitor

WebSphere BI ConnectWebSphere BI ServerWebSphere Application

ServerWebSphere Portal Server

WebSphere MQ

WebSphere BI Adapters

DB2 Information Integrator

WebSphere BI Event/Message Broker

WebSphere BI Workflow

Page 28: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

28

Process Integration – Event Broker Model

● Message-based, reliable, transaction based, multi-protocol, scalable event processing● Use business events – from external as well as internal systems - as Publish/Subscribe messages to deliver information to many

systems at the same time● Messages between senders and receivers mediated, routed, and transformed by a centalized event broker ● Message represent realtime events - market data feeds, airport flight information, purchase order, account transfer or news tickers ● Define business events separately from the applications in which they occur● Specific information about any event can be distributed or received based on specified conditions – content of the message, topic,

conditional processing and other filtering attributes ● Participating applications continue to work independently, so the way the information flows can be changed without making

changes to the applications

Page 29: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

29

WebSphere Business Integration Server

Full range of application and process integration services

Business application synchronization

Process choreography and compensation

Application connectivity

Process Integration – process automation and interaction with people

Application Connectivity – pub/sub and intelligent routing of messages

Numerous application and technology connectors

Prebuilt collaborations – process templates for common business processes composed of generalized business objects and flows

Industry specific connectors and collaborations

Process Modelling, Integration, and Monitoring tools

WebSphere Business Integration Server

Process Integration Services

Pro

cess

Ch

ore

og

rap

hy

Cro

ss-

Ref

eren

ce

Tra

nsa

ctio

n /

Co

mp

ensa

tio

n

Sta

teM

anag

emen

t

Au

dit

Sta

ff

Application Connectivity Services

CommonBusiness

ObjectModel

Process Automation Human Activity

Events

HR Legacy Finance ERP CRM

Routing Pub/Sub Transformation Mediation

InformationIntegration

WebSphere MQ

Page 30: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

30

WebSphere Business Integration Modeler and Monitor

Modeling Monitoring

Managing

Graphically build business processes including their associated business metrics, requiring no Java coding

Simulate processes and determine ROI prior to deployment

Enhance flexibility and ability to manage change at business levels

Use role based dashboards to see process execution and to handle out-of-line conditions

Track and manage business events through to completion

Analyze trends and metrics for continuous process improvement

Page 31: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

31

Business Processes: WebSphere MQ Workflow

Integrate People-based activities and tasks with applications/systems into the business processes Manual tasks executed in sequence with other automated tasks—or parallel to them Activities assigned and tracked based on roles rather than individuals Electronic work task assignments, reminders Manage long-running business transactions for efficient use of system resources Any person in the proper role can execute an action when needed Staff & Role selection, definition Manage long-running business transactions for efficient use of system resources Interoperate with WBI Server Collaborations

Applications

Message FlowHuman Interaction

Web Device

WebSphere MQ Workflow

User Presentation IntegrationJavaBeans, Servlets, JSP forms, Portlet based rapid

development

Information Manipulation & Routing

Tightly-coupled Process IntegrationFor tasks executed by applications

Loosely-coupled Process Integration

Web Services& Message based

ApplicationConnections

Page 32: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

32

WebSphere Business Integration Connect

Exception Management/Alert Notification

Community Manager Console Community Participant Console

Management Console

Communication

HTTP

Document Handling and Validation

Message Protocol

EDIINT AS1/AS2

Communication

HTTP/SHTTP/S

FTP

SMTP

XML

SOAP

RNIF 1.1/2.0

FILE SYSTEM

EDI

XML

SOAP BODY (RPC/DOCUMENT)

RNSC

BINARY/FLAT FILE

Ext

erna

l P

artn

er

Inte

grat

ion

Inte

rnal

In

tegr

atio

n to

WB

I an

d ex

istin

g bu

sine

sss

app

lica

tions

JMS

HTTP

B2B Gateway Hub providing document exchange services with a rich set of operational tools to manage the trading community

Page 33: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

33

Business Process Model

Implementation Model

Doing the Work

Measuring the

Outcomes

Redesign

Integration Model

Business Analyst Model

Completed without the need of a Java

programmerProcess Actual Data

Compare& Adjust

Process Simulation

Data Role Based Dashboard

Business Operations Data

Getting to on-demand

Page 34: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

34

Questions

Any questions on:

Introduction – On Demand Technical Roadmap

Page 35: What it takes to be on demand

© 2004 IBM Corporation

e-business on demand

35

Break

15 Minute Break