WebSphere Integration Developer v6.0 - Component Implementation for Business Processes

1. WebSphere Integration Developer v6.0Component Implementation

2. 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)

3. A s s e m b l y D i a g r a m Mapping Components Component types that are wired together in Assembly Editor Business Processes Human Tasks Selectors Exports Imports BusinessStateMachines BusinessRules Web Services EJBs Resource Adaptors Java J2EE Artifacts Reuse Business Objects Component Interfaces Visual Snippets Business Event Monitoring WebSphere Integration Developer – Key Features Used in Component Creation

4. Agenda • How new components are created in WID? • A Tour of Component Development Tools

5. Define and Implement Components • Two ways to define components • From the Assembly Diagram • From the Component Tree

6. New Components – From Assembly Editor 3 1 • Add Interface/References and generate implementation • Open Module in Assembly Diagram Editor • Double click on the Module 2 • Drag and drop Component from the palette 4 • Component Editor opens and Component appears in the Component tree

7. New Components – From Navigator 1 3 • Lunch a New Component Wizard from the Navigator • A Component Editor is launched 4 • Component appears in the Navigator 2 • New Module Wizard is launched • Asks if new or exiting interface

8. Components from Existing Assets • Java Objects • Enterprise Java Beans • Web Services • And anything else you can get to via Java,EJBs or Web Services…

9. Drag and drop Java class on Assembly Diagram Component from Java • Creates a Java Component in Navigator • Creates a Java Component in Assembly Diagram

10. Drag and drop Session EJB on Assembly Diagram Component from EJB • Creates an Import with Session EJB binding in Navigator • Creates a EJB Import in Assembly Diagram

11. Demo Next Component from Web Service • Import Web Service or drag/drop WSDL file from file system (i.e. Windows Explorer drag-drop into workbench) • Creates Web Service (port) in Navigator • Creates a EJB Import in Assembly Diagram

12. Demo Next Define New Components • Selector • BPEL Process • Business State Machine • Human Task • Business Rule • Visual Snippets

13. Agenda • How new components are created in WID? • A Tour of Component Development Tools

14. Traditional Integration Programming Model

15. WebSphere Process Integration Programming Model

16. WebSphere Process Integration Programming Model

17. WebSphere Process Integration Programming Model

18. get Approved Approved/ Denied If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service Composite 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

19. Used in Component Creation Business Objects Component Interfaces Visual Snippets Business Event Monitoring Web Services EJBs Resource Adaptors Java J2EE Artifacts WebSphere Integration Developer – Components A s s e m b l y D i a g r a m Artifacts* Assembled in Assembly Editor *Java Component not shown Business Processes Human Tasks Selectors Mapping Components Exports BusinessRules BusinessStateMachines Imports

20. Short-runningProcess Process Component Business Processes • Process is a directed graph of BPEL Activity Nodes that represents a single business activity • There are two types of Processes • Short-running • Single transaction per Process • Basic Process Choreography • Long-running • Transaction scope at Activity level • Persistent - therefore interruptible • Advanced Process Choreography (such as asynchronous and Human Activities • Compensation Activities undo executed Activities Long-runningProcess DB Maintains execution state in database DB

21. Palette - Contains activity icons which can be dragged-and-dropped on the canvas Variables Area - Contains process variables. Activities Area - The area process where the process is assembled Action-bar - Contains actions that are relevant to an activity Partners Area - Contains the Interface Partners and Reference Partners Details Area - Displays properties that are relevant to the object that is selected on the canvas Correlation Sets Area - Contains the correlation sets are listed. Activities Interface Partners Action-bar Reference Partners Palette Variables Correlation Sets Details Process Editor Business Processes

22. BPEL standard: BPEL4WS 1.1 and a draft version of the WS-BPEL 2.0 Compensation standard Full XPath 1.0 support (i.e. for expressions) Variables XSD type and elements Scoped New Activities: Scopes Re-throw Compensate Removed Activities: Transform New Handlers: Event, Compensation Based on a Scope or Activity Links crossing activity boundaries Assign activity improved Scope Event Handler Compensation Handler Process Component – What’s New? Business Processes

23. WS-BPEL 2.0 Elements Business Processes 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

24. 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 Business Processes

25. Business Process Business Processes • 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

26. Business State Machines 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

27. Transition Events (Partner Link) Action (Logic) Guard (Condition) State Entry (Logic) Exit (Logic) Composite States Time-out Based on UML 2.0 State Machine Logic embedded in Transitions Guards Outbound Partner Links or inline Events are BPEL Partner Inbound Links Business State Machines Business State Machine Editor

28. Human Tasks Human Tasks Component • A stand-alone Component not restricted to invocation form a BPEL Process • *Machine to Human • Component creates a work item for Human interaction (WS-BPEL) • Human to Machine • Human interaction invokes a Component (i.e. Business State Machine) • Human to Human • Human interaction invokes a Component which creates a work item for another Human * classic, typical “staff” workflow activities.

29. Human Tasks Human Task Editor General Properties • General Properties • Staff Plug-in Provider, Calendar, etc.. • Permission Settings • Specify Verb and Parameters for Roles • Client Settings • Web, Portal interface • Escalations Settings • Defines escalation actions and notification • e-Mail • Staff Assignment -> Notification Work Item • Priority Aging Permission Settings Client Interface Escalation Settings

30. Business Rules Component – Rule Group BusinessRules • Rule Group aggregates rules (Rule Sets or Decision Tables) with the same interface • Rule Sets and Decision Tables is where the rules are implemented • For each rule we define a date/time range for when a business rule is going to be invoked • Date\time may be specified • As the Current Date, • Supplied by Java snippet • “Mined” from the input parameters via Xpath • Rule implementations can be “scheduled” for a point in the past, present, or future • i.e. Able to process a claim from the past Rule Set Editor Decision Table Editor

31. Business Rules – Rule Set and Decision Table BusinessRules Rule Set Editor • Rule Set • Consists of a set of if/then rule statements • Templates • Conditions and actions • Which aspects of the rule can be modified at runtime • User interface to modify rules • Rule Sets are created from the templates • Decision Table • Rule Set in a table format Decision Table Editor

32. Selector determines dynamically which implementation of a target destination to invoke Selection is based on a Selector Algorithm Framework for custom selector algorithms The default Selection is date based Allows new implementations of target destinations to be added dynamically Selector Editor For each operation on the interface add a sequence of time slots Each time slot is associate with a Destination which must be a SCA destination Assembly Diagram No wiring is required to the destination components Selector is pointing at its components using “dynamic wires” Selector Component Selectors Selector Editor Selector Component

33. Selector Administration Console Selectors Selector Editor Selector Administration Console

34. Used in Component Creation Business Objects Component Interfaces Visual Snippets Business Event Monitoring Web Services EJBs Resource Adaptors Java J2EE Artifacts WebSphere Integration Developer – Components A s s e m b l y D i a g r a m Artifacts* Assembled in Assembly Editor *Java Component not shown Business Processes Human Tasks Selectors Mapping Components Exports BusinessRules BusinessStateMachines Imports

35. BACKUP CHARTS

36. A ‘State Machine’ model is a way to describe the dynamic behavior of an application or business process by focusing on the events that cause a transition from one state to another A ‘Business State Machine’ is an implementation of a business model that ‘executes’, moves from state to state, based on real-time events Use a Business State Machine when: Business process is heavily event-driven Reaction to these events is dependent on the process state Process may revert to prior states Business State Machines Business State Machine Component

37. Traditional Integration Programming Model

38. WebSphere Process Integration Programming Model

39. WebSphere Process Integration Programming Model

40. WebSphere Process Integration Programming Model

41. get Approved Approved/ Denied If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service BPEL – Business Process Execution Language 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

42. SDO – Service Data Objects (Data)

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