e-business on demand Business Process Integration with WBI

e-business on demand Seminar Outline Introduction – On Demand Technical Roadmap §Integrate Applications and Business Processes to enable On Demand Solutions §Business Process Integration ● ● ● An Introduction to Application Integration and Process Integration Service Oriented Architecture Web. Sphere Business Integration for On Demand Process Integration ---------- MORNING BREAK ---------------------- §Application Integration and Process 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 - Web. Sphere Business Integration Event & Message Broker Multiprotocol Pub/Sub Message Routing Message Transformation, Augmentation, and Datasource Integration ● Demo – WBI Message Broker §B 2 B and Business Partner Integration ● WBI Connect ● ● ----------- AFTERNOON BREAK ------------------- §Workflow based Process Integration WBI Workflow Demo – Workflow JSPs §Business Process Modelling and Monitoring ● Process Modelling in WBI Workbench ● Monitoring with WBI Monitor ● Demo – WBI Workbench Modeller §Summary ● Developer Resources ● ● 2 © 2004 IBM Corporation

e-business on demand Agenda § Business Integration Workflow Processes § Workflow Process Modeling § WBI Workflow Buildtime Process Modeling § Worklists and workitems § External Program & Application Integration § Web Services § User Interfaces to Workflow Processes. Process Monitoring § WBI Workflow Process Formats and Architecture 3 © 2004 IBM Corporation

e-business on demand Web. Sphere Business Integration Reference Architecture Business Activity Monitoring Web. Sphere Business Integration Web. Sphere Portal Web. Sphere Business Integration - Connect Process Integration Services Browser User Interaction Services Partner Services Common Business Entity Model WAP Business Protocol Staff Audit State Management Personalization Human Activity Transaction / Compensation Presentation Cross. Reference Process Choreography Process Automation Business Partner Application Exchange Hubs Business Partner Events Application Connectivity Services Routing Pub/Sub Transformation Mediation Web. Sphere Business Integration Adaptors HR 4 Legacy Finance ERP CRM . . . © 2004 IBM Corporation

e-business on demand Example: Software Order Process Manager of Starter Accept="NO" NOTIFY APPROVE Price>1000 Financial Application Accept="YES" Starter WHAT Price<=1000 CHECK BUDGET AND SYNC SEND WAIT INSTALL _RC=1 Approve Order Analyst 5 © 2004 IBM Corporation

e-business on demand Business Process Requirements § Long running (e. g. , several business days or months) ● ● Interruptible Persistent state § Distributed across the enterprise ● ● ● A 2 Multiple people and organizational units A 1 Diverse types of activity implementations ► Individual steps in the workflow process ► Could be a message sent to a person in an appropriate role A 3 ► Could be a message sent to a configured application for execution Federated system A 4 § Process Flow determined by business rules § Resource assignments (people and resources) determined by business rules § Reliable – transacted execution § Monitoring, auditing of running processes § Easy Process Modeling and deployment - changing business rules 6 © 2004 IBM Corporation

e-business on demand Business Integration Workflow Business Process Model Staff Assignment (roles, people, organization, level, process history) Workflow activities - human - automated Reports Monitors Transactional XML messages, MQ client/server, Web services Application Integration Applications -Front-end GUIs -Back-end apps 7 Web&Portal Server Farms, JSP forms Java, RMI, JMS, XML, Web services CRM ERP SCM B 2 B CICS IMS Databases TXSeries Lotus Notes Active. X, COM (Visual. Basic) other app's client/server local © 2004 IBM Corporation

e-business on demand Modeling a Workflow Business process: Series of work activities Application functions customer: _____ Loan request: __ § A workflow model is a complete representation of one or more business processes and its associated resources, for the purpose of managing workflow execution. Roles, Users, Organization, Responsibilities, Capabilities ● ● ● A process is a series of activities, with input and output data, rules for start and exit conditions, and control and data flows between them. Activities are assigned to users or applications, based on rules. Programs are registered to activities, detailing application functions, needed to perform a process function Amount: _____ 8 © 2004 IBM Corporation

e-business on demand Modeling a Workflow § Graphical process design and documentation ● ● ● Transit condition rules Time control, events, notifications Audit points ● ● ● Input and output variables (process, activities) ► Meeting need-to-know, ability-to-understand constraints Data mapping Data flows ● ● ● Built-in, customizable Staff model (roles, users, organizations, levels) Work assignment rules Work distribution at runtime ● ● Message Queues Program/application registrations § Data structure definitions § Role-based work assignments § Application integration Coordinator People Substitute 9 Manager Roles Organizations Belongs To Levels © 2004 IBM Corporation

e-business on demand Process Modelling with WBI Workflow 10 © 2004 IBM Corporation

e-business on demand An Activity – a Step in the Business Process Org DB Input Data f Sta pjoin Act pexit Output Data y er f Qu Description Documentation Support Tool Priority Notification § Activity Implementation • as a workitem message for a human activity • as an automated task via Program Registration/Association/Execution § Elementary step – Application command execution or worklist item § Complex (sub-process implemented by another workflow) 11 © 2004 IBM Corporation

e-business on demand Control Flow and Data Flow in Workflow Processes § Data Flow ● ● Each discrete step in a workflow has some set of input data Output data that it can send to the next steps in the process May need to transform, subset, manipulate, augment data Data fields and Dataflow specifications graphically defined and available to be used across processes START: §automatic | manual §incoming connectors wall TRUE wat least one TRUE EXIT: §automatic | manual §condition TRUE (otherwise REPEAT) § Control Flow ● ● 12 May need to apply business logic in determining which actions and steps to take in the process Alternate Paths, Parallel Paths, Joins Conditional logic, Loops Computational/Numeric, String operations © 2004 IBM Corporation

e-business on demand 13 Workflow XML IF HTTP JMS/MQ Workflow Web Client Workflow API Process Models Organization Workflow Engine Process State Workflow JSPs Call Applications and Human Interfaces that can interact with the Workflow Process Workflow Runtime Execution Architecture Business Applications Invocation Engine Systems © 2004 IBM Corporation

e-business on demand Trigger Workflow Processes from External Applications § Trigger processes via messages, using any message format desired/required ● ● Format conversion Request/reply correlation Persistent, transacted solution Pub/Sub, XML, SOAP WBI Message Broker 14 © 2004 IBM Corporation

e-business on demand Workflow Processes and Web Services HTTP SOAP Client MQSeries Web. Sphere App. Srv WA 07 SOAP proxy Wf XML Input Queue process start MQ Workflow Server Wf XML Output Queue Data Flow a<=b Control Flow a>b a, b, c Service Requester Service Provider People Systems § Publish, deploy Business Processes as Web Services § Consume Web Services as Business Process activity implementations § Automated process deployment and WSDL mapping § www. ibm. com/software/integration/supportpacs/wmqwf. html, supportpac WA 07 15 © 2004 IBM Corporation

e-business on demand Deploying Workflows as a Web Service § Shipped as a Web Application ● ● ● Simply deployed into any J 2 EE compliant application server IBM Web. Sphere and Tomcat tested Built on top of Apache Axis § Automatic Process Deployment ● ● ● 16 Browse Templates Pick a template Java Façade class is generated Web Service is deployed in the gateway WSDL available on request © 2004 IBM Corporation

e-business on demand Invoking a Web Service within a Workflow § Call out to a Web Service to implement an activity in a Workflow process § Orchestrate existing Web Services in a workflow process ● ● ● add control flow logic to Web Services integrate Web Services with "in-house" applications being agile through changing the business logic (control flow) fast § Late binding of Web Services through dynamic find ● ● 17 attach business rules to an "Web Service" activity, e. g. deliver at least xxx, until mm/dd/yy; lowest price find & bind Web Service through UDDI when the activity is started © 2004 IBM Corporation

e-business on demand Work Lists – A Launch Pad for Business Functions § Filtered lists of work items per user in authorized role § Automatic prioritization of work § Associates tools to pieces of work § Automatic data provision § User gains focus on business aspects of work instead of computer aspects § Workitem due dates, time out ranges and automatic notification of overdue items 18 © 2004 IBM Corporation

e-business on demand Web Client - Work List 19 © 2004 IBM Corporation

e-business on demand Web-based User Clients and Java - Architecture Serve r Client 20

e-business on demand Workflow Description Formats § Allow import export of process flows with external tools and systems § FDL – A standard Flow Definition Language format § BPEL 4 WS - An XML-based flow language that defines how business processes interact within or between enterprises ● Allows companies to describe complex business processes that can span multiple companies, such as order processing, lead management and claims handling ● Helps enable business processes to interoperate within and between companies that use different underlying technologies ● Replaces the existing IBM WSFL and Microsoft® XLANG efforts by combining and extending the functions of these previous foundation technologies. Extensions to BPEL for specifying human activities in a workflow ● 21 © 2004 IBM Corporation