WID and WPS V Marco Dragoni IBM Software Group Technical Sales Specialist IBM Italia S.p.A. Agenda

Transcription

1 IBM Italia SpA WID and WPS V6.1.2 Marco Dragoni IBM Software Group Technical Sales Specialist IBM Italia S.p.A. Milan, 28 November IBM Corporation Agenda BPM and SOA WebSphere Software for SOA and interaction WebSphere Process Server components SOA Programming Model Service components and implementation concepts Objects and SDO Creating a Integrated Solution Tour of key feature 2

2 Today applications Different software Different systems Data island Different network 3 requirement Time reduction to build new business process Support for a flexible business model Cost reduction Integrate different available solution at enterprise level 4

3 SOA concept introduction SOA is a business concept, not only technology: it is an approach and an architectural style that let to plan, project ICT solutions as modular services to build an organization with the following requirements: agile, flexible and business aligned to be more competitive, profitable, effective and efficient. Evolution to add value (see chart below) process value Single process Single problem 1980s 1990s 2000s 5 Process definition The term process means: an organized set of activities and decisions, with the objective to create an output required by the customer. The output have a value for the customer itself and the company Process start / Input Process Step 1 Step 2 Step 3 Possible Interaction Step Process Output Step N 6

4 Two Styles of Service Choreography Processes Traditional Processes focused on process activities Import from WebSphere Modeler Parallelism, advanced BPEL concepts State Machines Event-Driven Processes focused on business states Full Support for State Machine Programming Model States, Events, Actions, Guards, State Machine Authoring / Debugging / Logging 7 Long Running vs Short Running Suspendable vs non-interruptible Recoverable vs complete restart Human tasks, asynchronous calls and waits vs not allowed 8

5 Runtime aspect of BPEL BPEL is defined to be independent of any software vendor s run-time implementation Several aspects of a BPEL program s behavior depend on how the run-time is implemented Process Type Transactions Uninterruptible (Short running) One transaction for the entire process Interruptible (Long running) Transaction boundaries can be set between each activity Persistence None Processes can be quiesced to a database and restarted Crash Recovery None, execution is completely transient. If the server crashes, process state is lost. Process can resume from the last checkpoint Parallelism Interruptible Asynchronous Correlation None, strictly single-threaded NO NO NO Flow activities may execute in parallel YES YES YES 9 Process Integrity in BPM Advanced Event handling Process waits for event to arrive arbitrary event handler flows can be assigned based on the event type received Synchronize processes with external partners Process Compensation Logical undo of already committed process steps allows to roll-back multi-transactional processes consistently Keeps your process environment consistent Effective error handling Assign different fault handler flows based on type of error received Either stop/cancel process or handle fault as part of the process based on business requirements Flexible way to handle any type of error in your business processes 10

6 Flexible User Interface Support Generate & customize the user clients you need Users Clean hand-off to IT with Models, Metrics Modeling and Simulation WebSphere Modeler Collaborative Development WebSphere Integration Developer Govern services through the SOA lifecycle, find and reuse services WebSphere Service Registry & Repository Integrated deployment of policies, rules, and services based on an SOA platform Workflow and Choreography WebSphere Process Server JSP-based IBM User Workplace Forms- based Client User Client WebSphere Portal Server- based User Client Space Feedback for continuous improvement and optimization Monitoring, Dashboards, Analytics WebSphere Monitor Real time collaboration and management of business processes BPC Explorer Operations 11 What is Process Management? BPM is a discipline combining software capabilities and business expertise through people, systems, and information to accelerate time between process improvements, facilitating business innovation What does BPM with SOA provide? Processes BPM with SOA provides process flexibility by improving how you design, manage, and optimize your business processes and reuse existing assets. Services (Application & Information) External Operational Systems Application (Application & Information Assets) Application Content Data Registry 12

7 IBM WebSphere Software for BPM WebSphere Integration Developer Assemble existing and new assets to execute and manage business processes WebSphere Modeler Capture, simulate, analyze, and optimize business models to reduce risk and increase flexibility WebSphere Process Server, WebSphere ESB, WebSphere Portal Deploy process EARs. Run process instances. Monitor the running process instances WebSphere Monitor Real-time visibility and analysis of business information for timely and coordinated action WebSphere Services Registry & Repository Registry and Repository function to provide a real SOA registry. 13 WebSphere BPM Tooling Overview Rational Tool Set (RAD, RSA) Development WebSphere Modeler Process Models Process Process Modules Modules WebSphere Integration Developer Real-time Data WebSphere Service Registry & Repository Process Application (EAR) WebSphere Monitor Common Event Infrastructure CEI Events WebSphere Process Server WESB WebSphere Portal Message Broker /Adapters/EIS Runtime 14

8 Base Tools and Runtimes Development Tools Runtime WebSphere Integration Developer V6.1.2 RAD Eclipse V Eclipse V3.2 Deploy WebSphere Process Server V6.1.2 WebSphere ND V WID is based on a subset of Rational Application Developer (RAD) v7 (WID 7 = RAD7 some Portal tools - Crystal reports - RUP EGL WAS Test environment) WPS is based on WebSphere Application Server ND v What is WebSphere Process Server? Processes Interface Maps Human Tasks WebSphere Process Server Relationships V6.1.2 Mediation Object Maps (ESB) WebSphere V Service Component Architecture Objects State Machines Rules Selectors Common Event Infrastructure WebSphere Application Server (J2EE Runtime) 16

9 WebSphere Process Server The infrastructure of Process Server is built on the infrastructure of Application Server. As an analogy, consider the home in which you live, which provides you with shelter and the amenities for living. Your house provides basic services that are essential for day-to-day living, such as electricity, water (well pump, septic system, and so forth), heating/cooling, and shelter from the elements. Each of these services is necessary for you to function on a daily basis. At any point in time, you can take advantage of any service and build upon it. For example, you may want to build an addition to your home. In order to accomplish this, the electrical and water services are utilized and possibly extended. A major difference between an Application Server and Process Server is Process Server's ability to manage orchestration of business processes. process orchestration is the capability to bring together individual services to accomplish a larger piece of work. 17 Process Container WebSphere Process Server provides an environment in which business processes can run. The engine that supports the runtime is called the business process container. It is similar in concept to the Web container and EJB containers in WebSphere Application Server that provide an environment in which to run servlets and EJBs, respectively. The business process container provides an environment to manage the execution and flow of business processes, and to manage the interaction of people with business processes. 18

10 Process Container components The business process container is deployed as an enterprise application. The business process container is deployed as a set of EJBs that leverage the EJB container and its services. The container is deployed either upon installation of the product or at a later point in time via scripts or the WebSphere Application Server administrative console. During the deployment of the container, the necessary data source and Java Message Service (JMS) resources are created. This is an example of WebSphere Process Server leveraging the underlying architecture of WebSphere Application Server. The business process container is comprised of components (the business flow manager and human task manager), plug-ins, and APIs. 19 SOA Programming Model In many programming models, the focus is on technology where the developer has to deal with several different technologies to represent application composition, invocation and data models. The SOA programming model simplifies the model by providing a common composition, invocation and data model through the use of BPEL, SCA and SDO. This allows the application developer to focus on business services and let the underlying middleware focus on the technology needed to implement the business services. Current Programming Model Focus is on technology SOA Programming Model Focus is on Service Composition EJB stateless Session Bean, JavaBean, Flow Definition Language, BPEL BPEL Invocation EJB stateless Session Bean, JAX-RPC, JCA, JDBC, JMS SCA Data JDBC Row Set, JMS Message, JCA Data, XML, DOM. SDO 20

11 SCA - Service component SCA let you to differentiate between business logic and technical detail so you can concentrate in solving business problem process implementation is contained in the SCA component. SCA give you the programming model to build business process and mediation module Interface: How the component can be called Component Uniform representation for an encapsulated element Reference: How can I call another component 21 Interface definition An Interface: describe input/output messages used by a services Implementation: describes the behaviour of the service 22

12 Service Component Architecture - Interface Through the interface you define the possible operation that can be called on a component and the message data that need to be used A component expose interface so that it can be invoked and utilized from other component Two are the possibile interface Java interface or WSDL Port Type A component can be called in synchronous or asynchronous way Interface: How the component can be called Component Uniform representation for an encapsulated element Reference: How can I call another component 23 Service Component Architecture - Implementation A component can represent different type of implementation, for example Java, BPEL, state machine, Rule, etc Interface: How the component can be called Component Uniform representation for an encapsulated element Reference: How can I call another component 24

13 Service Component Architecture - Reference When a component need to call another component you need a reference Reference definition use the same procedure to define and interface Interface: How the component can be called Component Uniform representation for an encapsulated element Reference: How can I call another component 25 SCA - Service Key Concepts Invocation static or dynamic, synchronous or asynchronous Interfaces define how to invoke Service (can be WSDL or Java Interfaces) References specify how other Component are called from my Component Policies define quality of service Implementation Types can be BPEL, Java, Mediation, etc Wires define how a Reference connect to an Interfaces Wire Service Component Reference Interface Policies Implementation Types 26

14 Sample Invocation Model Java Application Human Task BPEL Process Value All the component can be reused Rules If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service State Machine Native support for: - EIS Systems via WebSphere Adapters - Web Services SOAP over HTTP SOAP over JMS -JMS -MQ (native, MQ/JMS) -EJB - HTTP -WebSphere Transformation Extender (WTX) All the component (es. process, rules, human interactions) are represented and called in the same way with the final objectives to reduce development cost 27 BO - Service Data Object (SDO) SDO enables unified data access and representation across heterogeneous data stores (JSR 235) SDOs provide a common, self-describing data abstraction that map onto a specific underlying infrastructure and data type. SDOs let programmers retrieve, update and write back data, unaware of the underlying data access technology (JDBC, RMI/IIOP, JAX-RPC, JMS, etc.), and they can process and manipulate messages without knowing the message transport technology (java.io.serializable, DOM Objects and Simple Object Access Protocol (SOAP) encoding, JMS message passing styles, etc.) Recognizing that some programmers prefer to view data as Java objects while others prefer XML documents, SDOs support both models equally. 28

15 BO - Service Data Object SDO Core APIs Custom Mediator Access APIs Data APIs Metadata Access APIs File Metadata APIs Client Access APIs JDBC Mediator Data APIs Metadata Access APIs Data Base Unified data representation & retrieval across heterogeneous data sources DMS or DAS EJB Mediator Metadata APIs Access APIs Data APIs Metadata Access APIs Metadata APIs Data Base 29 BO - Core SDO At the core of SDO are DataGraphs and Data Mediator Services (DMS). An application program obtains a DataGraph from a DMS; the DMS is specific to some back end data store. The program can then examine and/or update the data contained in the graph. Optionally the program can employ a DMS to propagate the entire set of updates back to the original data source. A DataGraph is an in-memory, non-persistent copy of data. A program can work with this data even when there is no connection to the original data source. A DataGraph is an envelope for DataObjects. Each DataObject contains a set of properties, which can be primitive values or references to other DataObjects contained in the DataGraph. 30

16 Objects (BOs) BOs are application data that represent business elements i.e. a customer or an invoice Each data item in BOs has: Name Type simple/complex, scalar/array Default value Architecture of BOs Are based on, and extend, SDO JSR Can be represented as XSDs and Java Classes Graph provides support for disconnected programming model Object Graph 31 Import and Export When a module wishes to provide ability for another entity to invoke a business function it Export this capability When a module whishes to leverage the ability of another entity the module will Import this function 32

17 What is an Enterprise Service Bus? An Enterprise Service Bus (ESB) is a flexible connectivity infrastructure for integrating applications as services. An ESB performs the following between requestor and service MATCHES & ROUTES communications between services CONVERTS between different transport protocols TRANSFORMS between different data formats IDENTIFIES & DISTRIBUTES business events 33 Shape = Transport protocol Color = Data format Invocation of a mediation flow JMS JMS JMS SOAP SCA MQ Export SCA message built from transport message. Payload is a BO (typically) SOAP SOAP SOAP SCA JMS Import EIS MQ SCA SCA Flow engine executes mediation flow. Primitives mediate the SMO Flow engine SMO SMO Service Message Object Created with payload as body and transport and other headers 34 SCA SCA SMO used to reconstitute SCA message

18 WebSphere Process Server Programming Model Service are assembled into Modules Reusable assets reside in Libraries Imports make external SCA Interfaces and non-sca artifacts visible inside a Module Exports make internal (to the Module) Interfaces visible outside the Module Service use Objects for data Integration Solutions is the Module and Library together Web Client Library Java JC2 Connector to EIS Module Import Import Mediation Module 35 Export Creating a Integration Solution A Tour of Key Features and Functions 3 Top Down Define & Implement Define Modules 1 Define Objects Component Interfaces New 2 Create Define 4 5 Mediations Assemble in Modules Test & Debug Modules & from Existing Assets Notes: 1-5 may be performed in a different order Typically WID users play two roles: J2EE Developer role, and Integration Developer role Bottom Up 36

19 Define Modules New Project Wizard creates Libraries and Modules Libraries Contain artifacts sharable across Modules Data Types, Interfaces, Mapping Modules Contain Module Dependency editor Allows to specify what Libraries are visible to a Module Main Module sees Main Library 37 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 38

20 Objects Object Editor Compose new Objects Creates BOs (implemented as XSDs) Inheritance Create a new BO that inherits data from existing BO Derived BOs Create a new BO form entries in an existing BO Nesting A BO may contain scalars/arrays of other BOs Inherits Contains BO Contains array of BOs 39 Component Interfaces Interface Editor Simple and easy way to define a WSDL interface Creates WSDL with no Services and no Bindings section Multiple Operations Operation One-Way or Request Response Messages May be BOs or simple types Faults 40

21 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 41 Bottom Up Accessing Existing Assets from We need to re-use existing J2EE assets via a variety of bindings We want to invoke these J2EE assets from Web Service EIS via Connector Messaging Java, Session EJB 42

22 Web Service Import Web Service Import a Web Service to a Module from: UDDI WSRR Query Creates Web Services port the in Navigator Add Web Services port to Assembly Editor 43 EIS Import EIS via Connector Enterprise Service Discovery Wizard Discovers operations offered by an EIS Creates: Interfaces For operations offered by an EIS Objects Define data for interaction with an EIS EIS Export and Import Provide SCA integration ESD Wizard Based on the Enterprise Metadata Discovery (EMD) A joint specification from IBM and BEA (1) (1) Whitepaper available at: ibm.com/developerworks/library/specificati on/j-emd/index.html 44

23 Enterprise Metadata Discovery EIS via Connector Import Objects PeopleSoft Adapter EMD API IMPL. PeopleSoft Interface Import in the Assembly Editor EMD API Provides Metadata Requests Metadata 45 Adapters All WebSphere JCA Adapters are included in WebSphere Integration Developer for superior out-of-the-box experience All WebSphere Adapters in WID are for development use Flat File, FTP, JDBC, , SAP, Siebel, PeopleSoft, JD Edwards, Oracle E- Suite The Technology WebSphere Adapters are for production use Flat File, FTP, JDBC, Other features CICS ECI and IMS J2C Connectors CTG no longer bundled in WID! WSRR Discovery Agent (New) WBI Adapter Artifact Importer Access to WSRR! 46

24 Messaging Bindings Generated by Generate Bindings Wizard on Assembly Editor MQ Binding Define JMS Provider in Admin Console Uses WebSphere MQ API to directly access WMQ Queue Manager and WMQ Queues Provides mapping between SCA messages and WMQ message headers and bodies You can work with real MQ messages/headers! MQ-JMS Binding Define JMS Provider in Admin Console Uses WebSphere MQ as the JMS Provider More direct access than via JMS binding and MQ Link! JMS Binding JMS Provider is the WAS native SI-Bus Used for internal WAS/WPS messaging Define JMS Provider 47 Java and EJB Artifact Consumptions Java, Session EJB Drag & Drop + WSDL-Type interface J-Type interface Proxy for J-Type to WSDL-Type interface mapping + Drag and drop a Session EJB or Java Class on the Assembly Editor EBJ Import Java Component A proxy for J-Type to WSDL-Type interface mapping is generated automatically 48

25 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 49 Human Tasks Component Human Task A stand-alone Component not restricted to invocation from 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. State Machine) Human to Human Human interaction invokes a Component which creates a work item for another Human 50

26 Human Task Editor 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 Notification Human Task Event Priority Aging General Properties Permission Settings Client Interface Escalation Settings Human Task 51 Human Task Customizable Notification Human Task Recipients are determined by staff resolution Subject and body for the can be specified Customizable templates Variables may be used in subject and body Human Task variables Input message variables 52

27 Human Task Web Client Generation Wizard Human Task A new wizard to create JavaServer Faces based clients for Human Tasks Inline human tasks of a process Human Task components in a module All three types of Human Tasks: Originating, Participating and Pure HT and Inline HTs All HT Types 53 Human Task Web Client Generation Wizard Human Task Code generation choices: Generated a new EAR and Web projects Generated client can be customized By editing: the JSPs, the style sheets (.css), or the JSF Java classes Company logo Local or remote clients Two style of templates 54

28 BPEL Process Component Process A process component implements a business process. Its implementation language is the Process Execution Language for Web Services (BPEL) and its associated IBM extensions. BPEL: Can describe the orchestration of other services. Has variables to keep process state. Allows sophisticated error handling using fault handlers. Supports asynchronous events through event handlers. Can correlate inbound requests with the right instance of a particular process, using correlation sets to mark that business data within the request that identifies the instance (such as a customer ID). Provides extended transaction semantics through sophisticated compensation support. processes are created with a graphical flow editor that plugs into the Rational tools suite. One can also compose BPEL processes manually using a text editor. 55 BPEL Process composition Process <?xml version="1.0" encoding="utf-8"?> <process name="myprocess" targetnamespace=" expressionlanguage="java" suppressjoinfailure="yes" wpc:autodelete="no" wpc:autonomy="peer" wpc:businessrelevant="yes" wpc:executionmode="longrunning" wpc:validfrom=" t00:00:00" xmlns=" xmlns:wpc=" <partnerlinks> <partnerlink name="caller" partnerlinktype="ns1:callerplt" partnerrole="self"/> <partnerlink name="partner1" partnerlinktype="ns2:partnerplt" partnerrole="partner"/>... </partnerlinks> <variables> <variable messagetype="ns1:inputmessage" name="inputvariable"/> <variable messagetype="ns1:outputmessage" name="resultvariable"/> <variable messagetype="ns2:message" name="state"/>... <reply name="reply" operation="inputoperation" partnerlink="caller" porttype="ns1:callerpt" variable="resultvariable"> <target linkname="link10"/> <target linkname="link11"/> </reply> </flow> </process> 56

29 Process Component Process Process is a directed graph of BPEL Activity Nodes that represents a single business activity Short-running Process There are two types of Processes 1. Short-running Single transaction per Process Basic Process Choreography 2. Long-running Transaction scope at Activity level Persistent DB Asynchronous Activities allowed Compensation support Long-running Process DB Maintains execution state in database 57 Process Editor Process 1.The palette Contains the BPEL activities organized by families 2.The palette submenu Contain a submenu with a wider selection of activities within the family 3.The canvas Area of the editor to assemble the activities to compose your process 4.The action bar Launched from an activity, contains icons that are relevant to that activity. 5.The tray Displays the Interface and Reference Partners, Variables and Correlation Sets 6.The properties area Displays properties that are relevant to the object that is currently selected on the canvas. 58

30 BPEL Modeling Elements Process Interface partners Reference partners Data type variables Correlation sets invoke activity Receive activity Reply activity Choice activity - Case element - Otherwise element Scope activity Timeout activity Snippet activity Sequence activity Parallel activity - Link Assign activity Human task activity Wait activity While loop activity Empty action activity Terminate activity Throw activity Re-throw activity Receive choice activity - OnEvent element - Timeout element Compensation handler Compensate activity Fault handler - Catch element - Catch all element Event handler - OnEvent element - Timeout element 59 State Machine Component State Machine 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 Use a State Machine when: process is heavily eventdriven Reaction to these events is dependent on the process state Process may revert to prior states 60

31 State Machine Editor State Machine Based on UML 2.0 State Machine Events are operations defined on the inbound interfaces Logic invoked in a State Machine is defined in: Java and Visual Snippets Outbound operation - References 61 - Transition - Events (inbound operation - Interfaces) - Action (logic) - Guard (logic) State - State entry (logic) - State exit (logic) - Composite States -Time-out Rules Component Rule Group Rule Group Rule Group Editor Rule Group aggregates rules with the same interface Rules may be defined as Rule Sets or Decision Table Date/time ranges determine 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 62

32 Rules Rule Set and Decision Table Rule Group Rule Set A set of if/then rule statements Decision Table Balanced binary tree format Templates Determine which aspects of the rule can be modified at runtime User interface to modify rules Rule Set and Decision Table can both be templetized Template Rule Set Editor Decision Table Editor 63 Dynamicity with Rules Rule Group Programmer defines rules from templates This exposes the rule parameters to Rules Manager Tools WebSphere Integration Developer Runtime WebSphere Process Server Using Rules Manager, the Analyst changes rules at runtime No need to restart the application Users are authenticated using standard WAS authentication / security Changes may be exported back to WID 64

33 Visual Snippets Visual Snippet Editor Visual Snippet Library Visual Snippets are not Used in: Java Snippets, Mediations, Rules, etc Created using Visual Snippet Editor Enables custom programming without the need for Java skills Visual Snippet Folder Contains both pre-built and custom Visual Snippets 65 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 66

34 Interface Map Component Interface Map Source Interface Target Interface BO Map BO Map Maps the source interface to a target interface i.e. TranslateService <-> Polyglot Maps the Objects Uses several mapping strategies Object Maps Relationships Simple mappings (i.e. Move) 67 Data Mapping Object Maps Interface Map Object Map Editor Creates Data Maps used in the Interface Map component Simple message parts mappings Move, Extract,, Join, etc Custom (via Snippets) Complex mappings Relationship Mapping Visual Editor for Custom Map Relationship Mapping 68

35 Interface Map Component Relationship Mapping Interface Map Relationship Editor Creates relationships between Objects Static Relationship Static cross-referencing between data such as country codes Identify Relationship Dynamic crossreferencing between the keys of BOs from different systems but representing the same information If I have a key of an object in SAP system I can easily find the key of an equivalent object in Siebel system BOs Participating in this Relationship US Maps to USA 69 Interface Map Component Interface Editor Interface Map Operation Mapping Parameter Mapping Choices Parameter Mapping Choices of BO Maps 70

36 Selector Component Date Based Selection Selector Target 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 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 71 Dynamicity with Selectors Selector Programmer defines What components to invoke The selection criteria The selector behavior can be modified at runtime Tools WebSphere Integration Developer Runtime WebSphere Process Server At runtime System Administrator can modify/add/delete Modify or add the date/time Target component From a list of installed with the matching interface Changes may be exported back to WID 72

37 WebSphere ESB Tools Mediation Module Mediation Flows New Module Type Mediation Component Import for External Local Java Component Only Two Component Types are available from Mediation Module: Mediation Flow Component Java Component Other must be defined in the non-mediation Modules Can be accessed from Mediation Module via Imports 73 WebSphere ESB Tools Mediation Flow 1. Operation connections - Connected operations between a source interface and target references 2. Request and Response Mediation flows - This section is used to build a flow for the operation definition created in the top section of the editor. 3. Properties view This section is used to modify properties of the selected node or mediation primitive on the canvas. 4. Mediation flow primitives palette 5. Input node - This is the starting point for the request flow, and sends the message into the request flow. 6. Callout node - An end point in the request flow. It sends the processed message to the target operation. 7. Input response node - Returns the processed message as a response to the source operation Support the composition of complex mediation logic flows by using predefined mediation primitives Enables modeling of Request and Response flows Mediation Flows Support access and modification of transport-level information of SCA calls through Service Message Objects (SMO)

38 WebSphere ESB Tools Mediation Primitives The Event Emitter primitive emits a common base event at a point significant in the mediation flow. The Message Element Setter primitive sets, copies, or deletes the content of message headers or bodies. The Endpoint Lookup mediation primitive queries the WebSphere Service Registry and Repository and retrieves service endpoints, which it places in the message context. The retrieved endpoints can then be used to dynamically invoke a service. The Message Logger primitive logs messages to a database. The Message Filter primitive conditionally routes messages based on the results of pattern evaluation. A pattern is evaluated against the message, and if the result is true, the message is propagated to a terminal associated with the pattern. The Database Lookup primitive enriches the message using data retrieved from a database. The Stop mediation primitive silently stops the execution of the current path in the flow. This is an expected termination, and is not caused by an execution failure in the primitive. The Fail mediation primitive stops the execution of the flow and throws an exception when there is a known execution failure in the primitive. You can define your own exceptions for the Fail primitive. The Custom Mediation primitive allows you to implement your own mediation logic using Java code, or to call an import in the same mediation module. The XSL Transformation primitive transforms message formats between source and target operations, or changes the content of a message. The primitive uses an XSL style sheet to map between 75 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 76

39 Component Assembly Add Exports For inbound or async Activities To expose inside the Module Wire Use Wire to Existing (automatically connects matching References to Interfaces) Wire manually Add Imports Web Services J2C Adapters To access in external Modules Configure QoS Qualifiers 77 Creating a Integration Solution A Tour of Key Features and Functions Top Down Define & Implement Define Modules Define Objects Component Interfaces New Create Define Mediations Assemble in Modules Test & Debug Modules & Top Down from Existing Assets Bottom Up 78

40 Test and Debug Deploy Modules and the associated files are called Projects In fact Projects are implemented as EARs Modules and Libraries Add all Projects associated with the Integration Solution to an instance of the WPS v6.0 server This action will also start the server and publish all EARs Deployable EARs Deployed EARs WPS (Server) 79 Test Integration Test Client 1 Launch Integration Test Client 2 Select Module, Operation 4 Examine: Event Trace & Output 3 Enter Input Data & Launch Operation 80

41 Debug Integration Debuggers Rule Process Visual Java Snippet Mediation Flow State Machine Object Map 81 Debug Debug Perspective 1. Debug navigation toolbar for controlling component execution 2. Variables view 3. Change value of a component variable 4. Active breakpoint view 5. Component view 6. Breakpoint set in the component under debug

42 Summary Simplicity and skill acceleration Provide a layer of abstraction over the J2EE programming model Simpler programming model Invocation - (Service Component Architecture) Data - Objects (SDO ) Composition - SCA + SCA wires = SCA modules Rapid assembly of composite applications from components Solution building blocks are based on integration-level concepts and patterns rather than J2EE artifacts Process Choreography, Mediation, Relationships, Rules, etc rather than EJBs, RARs, EARs, WARs, etc.. Integration solutions are built by creating and assembling components Deploy WebSphere Process Server V6.0.2 Test WebSphere V IBM Italia SpA Thank You Marco Dragoni 2007 IBM Corporation