WebSphere Process Server V6

1. WebSphere Process Server V6 Technical Overview

2. What is the top focus of businesses? • 75% of CEOs place a high or very high priority on the ability to respond rapidly • Only 1 in 10 CEOs believe that their organization has the ability to be very responsive to react to changing market conditions Source: IBM Global CEO Survey, Feb 2004

3. Economics: globalization demands flexibility Business processes: changing quickly Growth is at the top of the CEO agenda Reusable assets can cut costs Greater information availability Crucial for flexibility and becoming an On Demand Business Why SOA for business flexibility and reuse? Traditional Business* Flexible business requires flexible IT Today’s World-Class Business* *Sources: CBDi

4. Deploy Assemble Model Manage Facilitates communication between services ESB Apps & Info Assets SOA Reference Architecture Business Innovation & Optimization Services Facilitates better decision-making with real-time business information Interaction Services Process Services Information Services IT ServiceManagement DevelopmentServices Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data and content in a unified manner Integrated environment for design and creation of solution assets Manage and secure services, applications & resources Partner Services Business App Services Access Services Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets Infrastructure Services Optimizes throughput, availability and performance

5. WebSphere Application Server, ESB, and Process Server WebSphere Process Server Choreography Mediation WebSphere ESB WebSphere Application Server ND Clustering WebSphere Application Server App Server

6. BusinessProcesses ServiceComponents SupportingServices InterfaceMaps BusinessObject Maps Relation-ships Service ComponentArchitecture BusinessObjects Common EventInfrastructure SOA Core WebSphere Process Server V6 – Components HumanTasks BusinessStateMachines BusinessRules Selectors Mediation(ESB) WebSphere Application Server (J2EE Runtime)

7. Integration in an SOA World • To be easy to use a solution for SOA Integration requires • Common Data Model • All Data is represented consistently • Common Invocation Model • All components are represented consistently • All components are invoked identically • Common Connectivity • Enterprise Service Bus • Service Choreography • Components can be choreographed independently of their implementation

8. Traditional Integration Programming Model

9. WebSphere Process Integration Programming Model

10. WebSphere Process Integration Programming Model

11. SDO – Service Data Objects (Data)

12. Business Object definition Business Object Metadata definition Business Graph definition Business Object Services The Common Data Model: Business Objects • Enhanced Service Data Object • Provides some function notavailable in base SDO specification(close to SDO 2.0) • Supports Inheritance and Aggregation • Enables import of ‘standard’ XSD • Business Object Framework consists of:

13. WebSphere Process Integration Programming Model

14. JavaInterface JavaInterface WSDLPort Type WSDLPort Type The Common Invocation Model: Service Components Reference:What thiscomponents calls Interface:How to callthis component Component UniformRepresentation ofencapsulatedImplementation

15. The Common Invocation Model: Imports / Exports • Adapters • J2C 1.5 • WBI Adapters • Web Services • SOAP over HTTP, SOAP over JMS • JMS (WebSphere Messaging Resources) • Point-to-Point and Publish/Subscribe • Integrate existing WebSphere MQ Solutions through MQ Link • EJB • SCA • Connect modules to each other without exposing the interface outside of WebSphere Process Server • Standalone Reference • Enables an SCA API Client to call a Module

16. get Approved Approved/ Denied If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service Composing Business Processes Java Application Sell additional services based on customer profile Human Task Human intervention on suspect applications to prevent fraud Imported EIS System Call Credit Rating service from an existing application WS-BPEL Business Process Business State Machine Adapting to business events Flexibly building business processes based on standards Business Rules Enable rapidly changing customer decision point

17. Business Process ServiceComponent ServiceImport Mapping the Implementation to the Component

18. Business Rule:Customer Status Export: doOrder Process:doOrder Human Task:Approve Order Import: Credit Check Assembling Components into Modules OtherApplicationsandModules Module: Order Reference Interface BO OtherApplicationsandModules Web BO BO BO Web BO BO Component • Encapsulate Functionality into Modules for Reuse • Components are connected by wires • Business Objects are the data flowing on wires between Components

19. Process:Order Get CustomerStatus Module: Process Order doOrder ApproveOrder Store Order Adapter forRelational DB Library: OrderLib CustomerStatus Store Order ApproveOrder Module: Update Order Database BO: DB2Order DB2 BO:Order Module: Approve Order Manually Module: Customer Status Interface MapConvert toDB2 Business Rule:Get CustomerStatus Human Task:Approve Order IF: StoreOrder IF: DB2Adapter Using Modules for Encapsulation and Reuse • Modules: Encapsulate and Reuse Functionality • Libraries: Share common definitions

20. Process:Order Get CustomerStatus Module: Process Order doOrder ApproveOrder Store Order Adapter forSAP Library: OrderLib CustomerStatus Store Order ApproveOrder Module: Update Order SAP BO: SAPOrder SAP BO:Order Module: Approve Order Automatic Module: Customer Status Interface MapConvert toSAP Business Rule:Get CustomerStatus Business Rule:Approve Order IF: StoreOrder IF: SAPAdapter Using Modules for Encapsulation and Reuse • Change Approval to Business Rule • Store Order in SAP instead of DB2 • All without affecting common objects or consumers

21. Shape = Protocol Color = Data type An ESB performs the following between requestor and service Common Connectivity: Enterprise Service Bus An Enterprise Service Bus (ESB) is a flexible connectivity infrastructure for integrating applications and services. An ESB powers your SOA by reducing the number, size, and complexity of interfaces. • ROUTINGmessages between services • CONVERTINGtransport protocols between requestor and service • TRANSFORMINGmessage formats between requestor and service • HANDLINGbusiness events from disparate sources

22. Mediation Primitive Request Flow Mediation Primitive Mediation Primitive Response Flow ESB Mediation Component • Provide the Implementation of mediation “logic” • “flows” that operate on messages/events as they are processed by the system • Operate on both One-Way and Request-Response interactions • Pre-Supplied primitives allow flows to be visually composed • XSLT Transformation • Message Logger • Message Filter • Fail • Stop • Database Lookup • Custom (Java) Component • CEI Emitter (Post GA)

23. Service Choreography: WS-BPEL • WS-BPEL provides portable, interoperable process models • WS-BPEL enables … • Defining business processes as coordinated sets of service interactions, recursively into new aggregated services • WSDL abstract interfaces alone used to define composition • Defining both abstract and executable processes • Abstract processes for e-commerce specifications • Executable processes provide a model to integrating enterprise applications • Creating compositions of services • Composition based on abstract descriptions

24. WS-BPEL 2.0 Elements Process x Variables Partner Links/Partners Event Handlers Fault Handlers Correlation Sets Compensation Handler at scope level * Assign Compensate Sequence Scope Receive ! Flow Reply (Re) Throw Empty Switch Invoke Terminate Wait While Pick

25. Business Processes Traditional Business Processes Full support for WS-BPEL Import from WebSphere Business Modeler Business State Machines Event-driven Business Processes Full support for State Machine programming model States, Events, Transitions, Actions, Guards, … State Machine Authoring / Debugging / Logging Two Styles of Service Choreography

26. Business Process • WS-BPEL compliant business process engine • Simplified Process Editor • Optional simplification ofterms • Generic Business Process • Operations / Parameters • Service Implementation Details hidden • Transactions / Compensation • Full XPath 1.0 Support

27. Business State Machines • State MachineImplementation • Based on UML 2.0State Machine Models • Event driven businessprocesses • Creates WS-BPELunder the covers • Simple/Complex States • Entry/Exit • Transitions • Events • Actions (invokes) • Guards • Timeout

28. Human Task Manager – Human Tasks • Three kinds of Human Tasks • „Invoke humans as services“ • The ‘classical‘ staff activity scenario • Allow humans to invoke services • Services implemented by business processes or arbitrary service components • Control which users are allowed to invoke a service • Allow humans to „invoke“ humans • Services „implemented“ by humans (Ad-hoc)

29. Human Task Features • Different, rich assignment rules for Editors, Readers, Administrators and Potential Owners • Multiple Clients • Web Client • Portal Client • Multi-level Escalation Mechanisms • e-Mail • Staff Assignment -> Notification Work Item • Priority Aging

30. Business Rules • Externalize Business Logic from an application (business process) • Easy change of logic that may change • Dynamically Update Rules in Runtime on the fly through Web Interface • NLS enabled free text representation for rules • Most-requested Business Rule Functionality • Decision Tables • Rule Sets (If/Then Rules) • Rule Templates • Action Rules • Ease of Use • Rule Group: detailed implementation encapsulated in a component with a well defined interface

31. Business Rules Rule Group Rule Set Decision Table

32. Client 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 Selector

33. Export: doOrder Interface Map Data Map Import: submitOrderSAP SAPOrder Order Relationship OrderID SAPID Transformation Components Interface:doOrder(Order) Interface:submitOrder(SAPOrder) BO (Order) BO(SAPOrder)

34. Common Event Infrastructure Event Source Distribute Submit Event Consumer Complete Event Consumer Event Consumer Event Consumer • An event occurs whensomething significant happensin 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 calledthe Common Base Event (CBE) • The application supplies the business data and WebSphere fillsin the details from the runtime environment such as the server name, J2EE component details and business context. • 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 Query Store Event Data

35. Common Base Event Selection • Select which events to emit • Select detail of events • Full, Digest, Empty

36. WebSphere Software Platform – Development Roles Role Description Benefits & Skill Requirements Business Analyst Modeling business processes for optimization or to reengineer existing business processes or define new business processes • No programming experience required • Can focus on business performance & process Integration Developer / Specialist Visual tools to configure integration logicwith existing and new applications and humans in the network • Some basic programming experience (loops, conditions, string manipulation) • No J2EE skill required • Expect tools to simplify and abstract advanced IT implementation details Software Architect Model-driven development environment that automates the translation from design to implementation. Includes requirements and business modeling integrations with RequisitePro and WBI Modeler • Focused specifically on UML modeling and J2EE implementation J2EE / Java Application Developer Comprehensive integrated development environment, for Web, Java, Web services, Portal, and EJB development with visual tools that accelerate application development. • Focused specifically on J2EE implementation

37. WebSphere Software Platform – Development Roles Role Description Development Tool Business Analyst Modeling business processes for optimization or to reengineer existing business processes or define new business processes • No programming experience required • Can focus on business performance & process WebSphere Business Modeler Integration Developer / Specialist WebSphere Integration Developer Visual tools to configure integration logicwith existing and new applications and humans in the network • Some basic programming experience (loops, conditions, string manipulation) • No J2EE skill required • Expect tools to simplify and abstract advanced IT implementation details Software Architect Model-driven development environment that automates the translation from design to implementation. Includes requirements and business modeling integrations with RequisitePro and WBI Modeler • Focused specifically on UML modeling and J2EE implementation Rational Software Architect J2EE / Java Application Developer Comprehensive integrated development environment, for Web, Java, Web services, Portal, and EJB development with visual tools that accelerate application development. • Focused specifically on J2EE implementation Rational Application Developer

38. WebSphere Software Platform – Tools Portfolio Rational Developer for iSeries / WebSphere Developer for zSeries Extensible Platform WebSphere Message BrokerToolkit Rational Software Architect WebSphere Integration Developer WebSphere BusinessModeler Rational Application Developer ‘IBM / 3rd Party’ Products … Eclipse 3.0 • All IBM Software Development platform products install in a consistent and extendable way within the ‘platform’ • First Product installs the ‘platform’ as well as it’s own product-specific ‘installable units’ • User of multiple tools, experiences a single integrated “desktop” IDE • Reuse of RAD and Eclipse components (‘installable units’) is baked into the design

39. WebSphere Integration Developer 6.0 • Reduce cost of skills • Default = Little to no Java • Roles / progressive disclosure • Accelerate skills • Tutorials • Out of Box Experience • Samples • Reduce time to deployment • Business Objects, Relationships • Wiring / Components • End-to-end test framework • Simplify the authoring metaphor • Interface / Data transformation • Business Process • Business Rules • Business State Machines • Business Events Point Click Integrate

40. WebSphere Integration Developer – Welcome

41. Development Tool Navigation Outline Browser Graphical Outline References Browser

42. WebSphere for Process Integration Process Integration which changes the competitive landscape What’s new • Best In Class Business Modeling and Simulation • Simplified Integration – Easy To Learn And Use • Revolutionizes Business Flexibility • Broadest Reaching Integration • Real Time Visibility into Business Performance • Closed Loop for Continuous Improvement • IBM WebSphere Business Modeler • IBM WebSphere Integration Developer • IBM WebSphere Process Server • IBM WebSphere ESB • IBM WebSphere Business Monitor • IBM WebSphere Jump Start in Process Integration

43. BACKUP CHARTS

44. IBM WebSphere Integration Evolution Today Version 6 Message Broker WebSphere Message Broker Beta 2Q05, GA 3Q05 WebSphere Business Integration Server v4.x MQ Workflow InterChange Server WebSphere Business Integration Tools WebSphere Process Server V6 Tech Preview 4Q04, Beta 3Q05, GA 3Q05 WebSphere Business Integration Server Foundation v5.x WebSphere Integration Developer v6 WebSphere Studio Application Developer – Integration Edition (WSAD-IE)

45. Connector Connector Claims Connector Connector Loan Invest Employee CustomerCase CustomerHistory Customer Connector Connector Policy Statement Credit Card SalesOrder Connector Connector The Value of a Common Business Object Model Item Home Assesment Risk Item Claims Contract Customer Auto CustomerCase Score Customer PurchaseOrder Customer Contract Back OfficeWorkflow Financials Check Image SalesOrder Invoice Customer SignitureCard Segments Customer Customer Case CustomerCare OperationalData Store Vendor SalesOrder SalesOrder Customer Customer Persing Household Vendor Customer Check Commercial Statement Insurance Household Time DepositAccount Trust Item Deposit Account

46. Thai Traditional Chinese Gracias Russian Spanish Thank You English Merci Obrigado French Brazilian Portuguese Arabic Danke Grazie Italian German Simplified Chinese Japanese