Websphere

®
IBM Software Group
The Business Integration Reference

Architecture
Focus on Process Integration
WebSphere Business Integration Server Foundation STEW

IBM Software Group
Today’s Business Priorities
Acquire, Keep &

Increase Operating
Grow High-value
Efficiencies
Customers
Build Stronger, More Profitable

Customer Relationships
2 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

IBM Software Group
Value Proposition of OSS/BSS Optimization Solution from a

Customers perspective
 Reduced Time to Revenue - enables rapid provisioning of new
customers with reduced costs
 Reduced Churn - Integrates Order Handling, Billing Management,
QoS, SLAs, Customer Problem Management and Fault Resolution
to reduce churn through enhancing the customer experience
 Operational Efficiency - Delivers cost savings through integration
of the provisioning process with key asset tracking applications. It
ties together the logical and physical assets in a seamless manner
 Rapid New Service Introduction - Streamlines the process for
creating and driving revenue from new products and services by
integrating CRM and Billing applications
 Number Portability (NA) - FCC requirement that wireless numbers
be portable from carrier to carrier
 Straight-Through Processing - comprehensive enterprise
integration platform

IBM Software Group
The OSS/BSS Optimisation Solutions need …

Integration of people, processes, and information
Middleware that enables service providers to

integrate processes across multiple systems in a
cost effective, flexible manner;
then continuously optimize those processes and
their IT infrastructure, ultimately integrating
Business and IT.
Representative Projects:
Billing-to-CRM Integration Process Modeling/Optimization
CRM/Contact Center integration Network Operations Portal
ERP Integration Single view of the customer
Dynamic Network Provisioning

IBM Software Group
Elements of an Effective Integration Architecture

 Well-defined Interfaces and defined set of protocols:
 Implements & enforces the “Separation of Concerns”
 Service Oriented Architecture (SOA)

 Integrate People, Process, and Information
 Applications should be treated as components
“You start with Web services and you start with good solid object-
oriented architectures. Why? Because the fundamentals of engineering
like good abstractions, good separation of concerns never go out of
style. Just because we have yet another set of protocols does not mean
those things get thrown away [Grady Booch, InfoWorld 02/04] .”

IBM Software Group
Why Service Oriented Architecture?

 A Service Oriented Architecture enables flexible connectivity of
applications or resources by
 Representing every application or resource as a service with a standardized
interface
 Enabling them to exchange structured information (messages, documents,
‘business objects’)
 Mediating the message exchange through an Enterprise Service Bus
 This flexibility enables new and existing applications to be easily and

quickly combined to address changing business needs.
 The ability to easily combine/choreograph applications allows IT
services to more readily reflect business processes
 The SOA infrastructure is also used to facilitate the management of

business performance and quality of service

IBM Software Group
SOA Concepts
 SOAs promote flexibility via clear definition and loose coupling
 What is a service?
 A service is a self-contained entity that performs a distinct business function
 How do services interact?
 May be invoked by clients inside and outside the enterprise
 May interact with each other, invoking operations and exchanging data
 Can be mediated
 What is service choreography?
 Choreography enables representations of business processes
 What is service discovery?
 A registry of services can exist allowing services to be discovered at buildtime or
runtime
 How is it enabled?
 Uses existing middleware according to SOA principles
 Exploits new, open standards and XML data definitions (Web Services)
 Combines both into fast time to market solutions

IBM Software Group
Process Integration
Challenge: Creating and managing the logic that links applications and services
together to implement a business function
Application Domain
begin
1
2
Process State 3
4
end
People Systems
Customers Customers
Partners Partners
Suppliers Suppliers
Employees
Existing Applications Existing Data

IBM Software Group
Process Integration Services

Value: Linking services together into business processes, with operating
environment support for human intervention & transactions, improves business
flexibility & reduces costs
Operating Environment
Choreography Svcs
Business Trans Svcs
Staff Services
People Process Systems
Customers Customers
Partners Partners
Suppliers Suppliers
Employees
Existing Applications Existing Data

IBM Software Group
Business Integration Reference Architecture

Comprehensive Services
Model Design Development Platform Implement Test
Process Monitoring Business Performance Management Services IT Monitoring
Interaction Services Process Services Information Services

Delivery Choreography Federation
Experience Transactions Replication
Resource Staff Transformation
Enterprise Service Bus

Event Mediation
Transport
Business App Application and Data Access Services

Partner Services
Services Event Detect On-Ramp
Community Component
Document Interface Business Application and Data Services
Protocol Core
Enterprise Applications and Data
Infrastructure Services

IBM Software Group
WebSphere Business Integration Server Foundation V5.1

Process Choreographer
 Process Choreographer
 Process Choreographer Runtime Engine
 Runtime components that support execution of processes
 Multi-style Process Support

 Non-interruptible (1-transactional) and interruptible (multi-
 transactional) Processes supported
 Compensation Support
 Runtime components that support compensation (undo of
 committed work) for processes.
 Human Interaction Support

 Runtime components that allow people to interact with processes
e.g.
 via a Web Browser based user interface to presents work items
and
 processes.
IBM Software Group
Process Choreographer – Facts

 Provides choreography for
 Web Services
 Local J2EE Components (e.g. EJB)
 Adapters
 People based steps
 Integral Module of WebSphere Application Server
 J2EE based Process Engine
 Exploiting WAS Base features, e.g. Clustering, Security, Admin
 Customizable Web-based Client
 Integrated Process Debugger & WAS Test Environment (UTE)
shipped with WebSphere Studio Application Developer Integrated
Edition
 BPEL enablement (based on BPEL 1.1 and IBM BPEL extensions)

IBM Software Group
Value Proposition
WebSphere Business
Integration Modeler v 5.1
Customers use for many objectives:

2. Model existing processes and procedures (learn about processes)
3. Analyze/simulate existing and proposed processes (focus
approach)
4. Understand technical/non-technical solutions (make decisions)
5. Move to technology solutions (implement)
Application Process
Development Orchestration
Rational XDE Rational Rose/XDE

WSAD-IE/Eclipse Tooling

IBM Software Group
WBI Modeler 5.1

IBM Software Group
WebSphere Business Integration Modeler:

Sample Workflow

IBM Software Group
WSAD-IE Process Editor

IBM Software Group
BPEL4WS – Conceptual View
BPEL
choreography,
describing BPEL (Process) extensions
behavior and
interaction
WSDL (Service) e.g.
binds
technology
EJB JMS ….…

IBM Software Group
BPEL Activities Receive
JavaSnippet
 Basic activities allow to define the Wait

Invoke
Assign
tasks that make up the business JavaSnippet Throw

Receive
Receive
process
 Structuring activities help to define Assign
the control flow of the business Invoke
process

IBM Software Group
Receive (Event) Activity– Behavior

Usage 1: Multiple Process Inputs Variable X
Receive
Output Data
Usage 2:Intra-Process Event
Inactive Waiting Finished

IBM Software Group
Types of Processes
 Non-interruptible Process (Microprocess)

 short running, fully automatic
 transient behavior, all activities within just one transaction
 Value: Reusable business functions
 Interruptible Process (Macroprocess)

 long running, automatic
 persistent state, set of separate activities, each is a single transaction
 Value: Top-level Process including asynchronous or manual activities
thereby including Microprocesses (Building blocks approach)
 Work assignment to people = Extension to Interruptible

Process
 manual activities are assigned to people based on special definitions
and the contents of an external directory

IBM Software Group
Transactions: Microflow (Short-running Process)
Microflow
Receive Invoke Invoke Reply
Reply
Invoke
Fault
T0
Transaction
boundary

IBM Software Group
Transactions: Macroflow (Long-running Process)
Transaction
JMS message boundary
“Continue Connector”
CC CC CC CC
Receive Invoke Invoke Invoke Invoke
AI AC
T0 T1 T2 T3 T4 T5
JMS message JMS message

“Activity Invoke” “Activity Complete”

IBM Software Group
Transactions: Modified Transaction Boundaries

transactionalBehavior=“participates“
CC CC CC CC
J
Receive Invoke Script Invoke Invoke
T0 T1 TT
2 2’ T3 T4
Other options: commit after, commit before, requires own

IBM Software Group
Compensation: Forward Navigation – Logging
Compensation
A2 A4 Sphere
A1 A3
Compensation
List

IBM Software Group
Compensation: Backward Navigation
P-1
Compensation
A-12 A-14 Sphere
A1-1
Compensation
List

IBM Software Group
Process Fault Handling

IBM Software Group
Deployment of the Business Process Application
ProcessApp.ear
Utility.jar
ProcessEJB.jar
Process.bpel Receive
JavaSnippet
Process-Base.java
Invoke
Wait
Assign
JavaSnippet Throw
Process
Receive
Receive
Base Class
Assign
Invoke
Process.wsdl Client.war
Process.java
Stateless
Business Process
Session Bean
Container
...
Process-Entity.java
Entity Bean
EAR file Business

Process DB
 Process deployed as EAR BI Server Foundation

 Process BPEL contained in Process Version 5.1
EJB Archive

IBM Software Group
Conclusion and Outlook

 Application model is changing towards two-level model: Flow
independence is achieved through separation of business
functions and business processes
 BPEL is becoming the standard for intra-enterprise and inter-

enterprise business processes
 WebSphere Process Choreographer provides a business

process engine that supports BPEL, people and integrates well
into J2EE
 WPC work is continuing on standardization and optimization for

various domains

IBM Software Group
Business rules support
• Powerful real-time framework for defining, executing, and managing

business rules that encapsulate business policies that vary based on
changes in the business environment.
 For example, a simple business rule might be, "If a customer's shopping cart
is greater than $X, then offer a Y% discount."
• Support for business rules includes:
 Easy to use tools for defining, executing, and managing business rules
 Cheat sheets to walk the user
through the process of
defining business rules
 Ability to update business
rules at runtime using a
straightforward user interface
without the need to bring
the application or server down
 Ability to organize business
rules into logical categories
 Support for defining a start
and end date for when the
rule is effect

IBM Software Group
Application adapters
• WebSphere Studio Application Developer Integration Edition provides

integrated, open standards-based support for building Web applications and
BPEL4WS business processes that integrate with back-end systems including:
 Integrated tool support for using J2EE Connector Architecture 1.0 (JCA) 1.0
resource adapters to access back-end systems
 Enhanced tool integration for JCA adapters with tool plug-in extensions (available
from IBM and business partners) including sophisticated wizards to manage the
low-level data handling requirements
 Easy to use tools for creating services out of JCA resource adapters and
including those services as part of a BPEL4WS business process
 Enhanced JCA 1.0 resource adapters
included for CICS, IBM Host On-Demand
and IBM IMS® (for development use only)
 Ability to import definitions from COBOL, C
structures, CICS basic mapping support
(BMS), and IMS Message Format Service
(MFS) definitions
 Support for the entire suite of WebSphere
Business Integration Adapters

IBM Software Group
WebSphere Business Integration Adapters

Adapters
• Ariba Buyer • MetaSolv Applications • Telcordia Applications
Application
• Clarify CRM • mySAP.com • WebSphere Commerce
• eMatrix • NightFire Applications • Centricity Gateway
• i2 • Oracle Applications • ESRI Spatial Databases
• i2 Active Data Warehouse • PeopleSoft • JD Edwards OneWorld
• IndusConnect Framework • Portal Infranet • Manugistics Demand and
• Maximo MEA • QAD MFG/PRO Fulfillment Management
Technology / • Siebel eBusiness Applications • Spirent Applications • SAP Exchange Infrastructure
Data
Handlers • Adapter for e-mail • JDBC • WebSphere MQ Integrator
• COM • JMS • WebSphere MQ Workflow
• CORBA • JText • Data Handler for XML
• Exchange • Lotus Domino • Data Handler for EDI
• FIX Protocol • SWIFT • ACORD XML
• Healthcare Data Protocols • XML • HTTP
• iSeries • Web Services • Enterprise Java Bean
Mainframe
• JCA • WebSphere MQ
• CICS • ADABAS • IMS Database Manager

• IMS Transaction • Adapter for VSAM • Natural
Manager • DB2 Databases • IDMS Database
31 WBI Server Foundation STEW | Presentation Subtitle December

© 2004 IBM 2003
Corporation
IBM Software Group
Thank you!
Questions?

Websphere

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Websphere

Uploaded by

Copyright:

Available Formats

®

IBM Software Group

The Business Integration Reference

Focus on Process Integration

WebSphere Business Integration Server Foundation STEW

Today’s Business Priorities

Acquire, Keep &

Build Stronger, More Profitable

2 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Value Proposition of OSS/BSS Optimization Solution from a

3 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

The OSS/BSS Optimisation Solutions need …

Middleware that enables service providers to

4 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Elements of an Effective Integration Architecture

 Service Oriented Architecture (SOA)

5 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Why Service Oriented Architecture?

 This flexibility enables new and existing applications to be easily and

 The SOA infrastructure is also used to facilitate the management of

6 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

7 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Existing Applications Existing Data

Process Integration Services

Business Trans Svcs

Existing Applications Existing Data

Business Integration Reference Architecture

Model Design Development Platform Implement Test

Process Monitoring Business Performance Management Services IT Monitoring

Interaction Services Process Services Information Services

Enterprise Service Bus

Business App Application and Data Access Services

Enterprise Applications and Data

10 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

WebSphere Business Integration Server Foundation V5.1

 Multi-style Process Support

 transactional) Processes supported

 Human Interaction Support

Process Choreographer – Facts

12 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Customers use for many objectives:

Rational XDE Rational Rose/XDE

13 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

WBI Modeler 5.1

14 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

WebSphere Business Integration Modeler:

15 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

WSAD-IE Process Editor

16 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

BPEL4WS – Conceptual View

EJB JMS ….…

17 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

BPEL Activities Receive

 Basic activities allow to define the Wait

tasks that make up the business JavaSnippet Throw

the control flow of the business Invoke

18 WBI Server Foundation STEW | Presentation Subtitle © 2004 IBM Corporation

Receive (Event) Activity– Behavior

Usage 2:Intra-Process Event

Inactive Waiting Finished

 Non-interruptible Process (Microprocess)

 Interruptible Process (Macroprocess)

 Work assignment to people = Extension to Interruptible