Presentation is loading. Please wait.

Presentation is loading. Please wait.

Using WebSphere Enterprise Service Bus for z/OS

Similar presentations


Presentation on theme: "Using WebSphere Enterprise Service Bus for z/OS"— Presentation transcript:

1 Using WebSphere Enterprise Service Bus for z/OS
Andrew Mead Hursley, UK

2 Agenda What is WebSphere Enterprise Service Bus
What was new with V6.1 & V6.1.2 and looking to 6.2 A System z customer scenario

3 WebSphere Application Server, ESB, and Process Server
Choreography And Solution Viewpoint WebSphere Process Server WebSphere ESB Mediation WebSphere Application Server ND Clustering WebSphere Application Server App Server

4 WebSphere Application Server Solaris (SPARC, X86-64), Windows, z/OS
WebSphere ESB Adapters Siebel Business Applications Flat File WebSphere TX Integration JDBC SAP R/3 Messaging Any JMS 1.1 Oracle E-Business Suite FTP JD Edwards WebSphere MQ PeopleSoft HTTP WebSphere ESB Service Retry WSRR Endpoint Lookup Message Logger DB Lookup Set Msg Type XSLT Msg Element Setter WebSphere Admin Console WebSphere Integration Developer Message Router ITCAM Mgmt Message Aggregation CEI Message Splitter Custom This picture provides an overview of what WebSphere ESB is—what’s in the box and the features and functions associated with the product. If you start in the center of the picture, you can see that WESB is built on top of WebSphere Application Server Network Deployment. WebSphere ESB, then, inherits WAS qualities of service, with its world class clustering, failover, scalability, and security. Along with these qualities, WESB also includes a number of key WAS ND features, including UDDI as a services registry, the Web services Gateway, Tivoli Access Manager, DB2, and Edge Components. Moving outward we can see the value that WebSphere ESB adds to the market-leading application server. First, there are the mediation functions, which can be used together to create integration logic for “smart” connectivity. WebSphere ESB offers JMS messaging and MQ interoperability for messaging, as well as a comprehensive clients package for connectivity. The SCA Programming Model enables ease of use, while Web Services support allows you to incorporate leading edge capabilities. On the sides of the picture you can see WebSphere Integration Developer, easy to use tool that supports WESB, as well as WebSphere Adapters, which includes new JCA adapters. Additional Notes: WS-*: We have atomic and security, WSRM is planned for future releases but its not yet a standard. A lightweight Java client is not included in the first WESB release, however, we are working on developing one and WAITING ON NOTE FROM TONY/ GERRY about when it will be done SCA Programming Model Web Services: WebSphere Application Server SOAP/ HTTP SCA AIX, HP-UX (PA-RISC, Itanium), i5/OS, Linux (Intel, p-Series,linux on System z) Solaris (SPARC, X86-64), Windows, z/OS SOAP/ JMS SDO WS-* SMO UDDI Registry 3.0

5 Service Component Architecture (SCA)
Component-based programming model for constructing distributed applications Components run in SCA container Component interfaces described by WSDL Component invocations via API or by wiring in SCA assembly Application data represented by business objects (SDO) Many possible component implementation types ESB focus is on Mediation Flow Component

6 Common Data Model: Business Objects
Business object definition (SDO/XML schema) Business Objects represent structured application data Consistent logical representation, independent of data source or wire format Based upon SDO standard Multiple data bindings can be supported

7 Concepts: Mediation Module
Interactions with external service requesters and providers defined by imports and exports Interfaces are defined using the Web Services Description Language (WSDL) Which may contain several service operations Different kinds of requester and provider are made available via different bindings for the imports and exports Mediation module Export Import

8 Export/Import Bindings
WebSphere Adapters (e.g. CICS, IMS, SAP...) Web services (SOAP/HTTP, SOAP/JMS) JMS / WebSphere MQ JMS / WebSphere MQ EJB Native (SCA) Java invocation

9 Concepts: Integrating request-response interactions using WebSphere ESB Mediation Flow Components
Processing is performed by one or more mediation flows, comprising instances of mediation primitives Processing of requests is separated from processing of responses WebSphere ESB Mediation Flow Components can act as ‘service intermediaries’ Allowing the mediation flow component to pass a (potentially modified) request from a service requester to a service provider pass a (potentially modified) response from a service provider to a service requester Request processing within a mediation flow component can send a response back to the requester without necessarily needing to contact a service provider

10 Anatomy of a Mediation Primitive
Integration Developer Anatomy of a Mediation Primitive One or more typed input Terminal (shipped primitives only have one) 0..n output typed output terminals Fail terminal fired if processing fails Acts like a Java catch block if wired If not wired then causal exception is thrown up causing flow failure Receives original message from input terminal

11 WebSphere ESB v6.0.1 Mediation Primitives
MessageFilter – routes within a flow XSLTransformation – transforms content MessageLogger – logs to database DatabaseLookup – adds content from database CustomMediation – executes custom logic (Java) Fail – terminates flow with an exception Stop – terminates flow normally

12 WebSphere ESB v6.0.2 Additional Primitives
EventEmitter - emits a common base event at a point significant in the mediation flow. Message Element Setter - sets, copies, or deletes the content of message headers or bodies Endpoint Lookup - 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

13 WebSphere ESB 6.1 Additional Primitives
Business Object Mapper Primitive: performs structure-structure mapping, provides access to relationships function. Service Invoke: allows a service to be invoked from within a request or response flow (not just at the end, as in 6.0.2) Set Message Type: allows a weakly typed element (xs:any, xs:anyType, ...) to have a type asserted for it at runtime Fanout: allows a flow to be split - and to operate on repeating elements of the message, and may be paired with Fanin Fanin: allows a flow that has been split using Fanout to be joined - can be used to perform aggregation

14 Dynamic Service Invocation
Service endpoints Mediation flow component Mediation Module Dynamic Endpoint Selection – based on endpoint contained in SMO Property configuration – promoted from MediationFlow component Endpoint Lookup via WSRR

15 Typical Integration Developer Task Flow
Identify service endpoints to be integrated Assert basic connectivity between endpoints Implement mediation function to allow communication Test and debug mediation function Deploy results to the runtime

16 Integration Developer 1. Integration developer specifies the service endpoints that need to be integrated Module Editor Allows the user to define and connect the contents of a module. The module defines the unit of deployment to the WebSphere ESB Uses the ‘module editor’ to construct a mediation module specifies how a subset of WebSphere ESB’s service requesters and service providers interact Within the module Service requesters are represented as ‘exports’ Service providers are represented as ‘imports’ The integration (mediation) function is represented as a ‘mediation flow component’ Imports and exports are connected to the mediation flow component Export Represents a service offered by the module, such as a Web Service client or a JMS application. Import Represents a service provider invoked by the module, such as a Web Service provider or a JMS application The Integration Specialist specified how service requesters and service providers interact by creating a ‘Mediation Module’. In fact this is a special kind of ‘SCA’ module. SCA stands for the ‘Service Component Architecture’. The special thing about a mediation module (that makes it different from any other kind of module) is that it MUST contain a Mediation Flow Component. It may also contain - imports (which are the standard way that the Service Component Architecture describes ‘service requesters’ (things that are not part of the WebSphere ESB infrastructure itself, but which the WebSphere ESB integrates with, and which may cause service requests). - exports (which are the standard way the the Service component architecture expresses the existence of service providers) - wires (connecting between the component and the imports/exports) - (where necessary) Other components, used to create custom mediation primitives (see more on this later) Interface Interface offered by the component Reference Specifies the interface of a service used by the component Mediation Flow Component Allows the integration specialist to compose a variety of useful intermediation functions e.g. routing, message transformation, and logging

17 Integration Developer 2. Integration Developer asserts the basic connectivity between these endpoints The integration developer uses the mediation tooling to specify the essential connectivity between a requester and one or more service providers Provider’s invoked operation The Integration Specialist now defines the behaviour of the MediationFlow component. Initially, the basic context, defined by interfaces and references of the Mediation Flow Component is present. Each blue line in the ‘Operation Mediation’ section (the upper pane) specifies the connectivity between an operation on the component’s interface and an operation on one of the mediation flow component’s references Client’s requested operation Provider’s invoked operation

18 Integration Developer 3. Decides on the mediation function required to allow endpoints to communicate effectively The integration developer constructs a mediation flow for the service request by selecting and connecting mediation primitives from supplied function ‘Callout’ Causes the specified operation to be invoked Mediation primitives have; Input terminals: attachment points at which the primitive expects to receive a message for processing Output terminals: attachment points at which the primitive will produce the result of its processing on a message Different output terminals represent different outcomes of the processing of the message. Properties: each primitive has a set of properties that is used to customize its behaviour. A mediation flow is a collection of mediation primitives connected by wires. The entry to a mediation flow occurs at an ‘input’, which represents the invocation of a specified operation on the mediation flow component’s interface and typically terminates at a ‘callout’.which represents the invocation of a specified operation on one of the mediation flow component’s references. ‘Input’ Represents the invocation of the specified operation on the mediation flow component’s interface ‘Callout’ Causes the specified operation to be invoked Primitives Perform basic logic or message manipulation

19 4. Integration developer customizes the elements of the mediation flow
e.g. Customizes the XSLT transform mediation primitive by using mapping tool to construct an XSLT transform The structure of the message is represented graphically A properties view is provided where the details of the mapping can be specified Define functions that apply to the mapping

20 Integration Developer 5. Debugs the composed/configured mediation function: WID Mediation Visual Debug Use the visual debugging tools to debug a solution Debug mediation flows using an in-place visual debugger Breakpoints can be added, step into, through, or over areas of interest while inspecting the values of the messages

21 Test and Debug – Integration Test Client
Select Module, Operation Launch Integration Test Client Examine, Event Trace & Output Enter Input Data & Launch Operation

22 What was new in WebSphere Enterprise Service Bus v6.1
Supports a broader set of mediation patterns quickly and with reduced development effort New message splitting and aggregation patterns New service retry capability Updated Business Object Mapper and relationship support Integrates a broader range of services with expanded connectivity New WebSphere TX integration New WS-Notification support New generic HTTP support Enhanced 3rd party JMS support Enables streamlined operational infrastructure with platform currency Updated WAS 6.1 based runtime 64 bit enabled Improves consumability and usability across the solution lifecycle Easier server installation and configuration Expanded XML and WSDL support WebSphere ESB V6.1 eGA Date: December 21, 2007 GA: January 18, 2008 z/OS GA: February 1, 2008 Supports a broader set of mediation patterns quickly and with reduced development effort New message splitting and aggregation patterns New fan out, fan in, and inline service invocation capability New service retry capability Improves continuous availability and quality of service for underlying business services Updated Business Object Mapper and relationship support Enhanced GUI mapper can now be used in mediations for common transformation requirements, and relationship transforms for tracking unique record identifiers across packaged applications and databases Integrates a broader range of services with expanded connectivity New WebSphere TX integration Delivers universal transformation for complex data formats and industry standards New WS-Notification support Enables publish-and-subscribe web services, including brokered interactions New generic HTTP support Integrates RESTful clients (ie Ajax) and legacy web services Enhanced 3rd party JMS support Provides better integration with applications via messaging systems Enables streamlined operational infrastructure with platform currency Updated WAS 6.1 based runtime JDK 5 support, Enhanced performance New and expanded OS platforms, including 64-bit exploitation and i5/OS support Also support for Windows Vista (non-production), remote DB2 on z/OS, and enhanced WAS XD support Improves consumability and usability across the solution lifecycle Easier server installation and configuration Faster installation, default configurations, and templates to accelerate configuration of clustered environments Expanded XML and WSDL support Enables interoperability with a broader range of services and industry standard message formats

23 WebSphere ESB 6.1.2 Available 1 Aug 2008
Enhanced support for Web Services Description Language (WSDL) XML Schema Definition (XSD), enabling the use of many industry-standard XML schemas. Improved error messages, logging, and First Failure Data Capture (FFDC) usage. FFDC can reduce defect resolution times and the number of times IBM Support asks a client to recreate a problem with different trace settings turned on. Adds support for manipulating MQCIH message headers for WebSphere MQ, which are exploited by the CICS bridge to enable interaction with CICS applications. Adds new format support for the following additional message formats: Delimited and full support for Comma Separated Values (CSV) Fixed-width format, and JavaScript Object Notation (JSON) Enhances support for COBOL Copybook, C Struct, and PLI

24 WESB 6.2 on z/OS GA Jan 16th 2009 Increased flexibility to administratively configure service mediations through policies Full set of mediation capabilities manageable via policies Integration with WebSphere Service Registry and Repository for policy management and governance Based on WAS 6.1

25 WebSphere ESB for z/OS – Extends the value of WebSphere Application Server for z/OS
Clustering support for fault tolerance, scalability Java platform with zAAP offload Native application integration WebSphere MQ for z/OS (including CICS) WebSphere TX integration CICS Transaction Gateway (JCA) IMS Connect (JCA) DB2 – DB2 Universal JDBC Provider, IBM Application Connectivity to DB2 for z/OS Feature Integration with z/OS Workload Manager so you can set performance goals for user requests. Built-in servant scalability, so WLM can start them up when performance goals are being missed. Exploitation of RRS for transaction management. Cuts SMF records to support monitoring and management. 64-bit support for larger heaps. WebSphere extends the value of core business transactions and data on zSeries, CICS and IMS applications, DB2 and IMS databases - for asset reuse with integration projects. CICS, IMS, DB2 and MQ are enabled for SOA today – reuse for integration with WebSphere. There are an estimated 180 to 200 billion lines of Cobol in use (Gartner). Cobol processes 75% of all business transactions, including 90% in Finance industry (Ovum)

26 WebSphere ESB for z/OS Built on WebSphere Application Server for an integrated SOA platform
Integrates seamlessly with WebSphere platform Delivers business-critical qualities of service Easily extended to WebSphere Process Server Integrated solution for service mediation and hosting Delivers leadership in SOA standards for service composition, and leverages the embedded messaging and web services engines from WebSphere Integrates seamlessly with the industry-leading WebSphere platform for streamlined IT operations Delivers business-critical qualities of service of WebSphere Application Server Network Deployment Easily extended to WebSphere Process Server for service orchestration and Business Process Management Integrated solution for both service mediation and service hosting Built on the industry-leading WebSphere Application Server Provides service-oriented integration with first-class web services connectivity, JMS messaging, and pre-built mediation function Built on proven Java Enterprise standards, and providing leadership in SOA standards Support Java Enterprise/SOA standards J2EE, JMS, HTTP, SOAP, UDDI, XML, WSDL, BPEL, SCA. SDO WebSphere Integration Developer provides an easy to use, visual integrated development environment Rapid time to value with an ecosystem of hundreds of ISV business applications, and WebSphere Adapters for enterprise applications (SAP, Oracle) Includes Common Event Infrastructure (CEI) bus for monitoring business events Integrates everything with WebSphere Adapters for enterprise applications, the breadth of the WebSphere ecosystem, and support for standard protocols Optimized for standard XML and web services formats, with basic support for other common formats Provides business visibility with embedded event engine for Business Activity Monitoring solutions

27 Ball State University Industry: Education URL: Ball State University bridges disparate systems and solves key administrative issue with IBM SOA solution. “SOA has been such a gift to us. It enables us to embrace a new technology that provides services at a level that we couldn’t even imagine before.” –Dr. O’Neal Smitherman CHALLENGE Coordinate 40 name and address systems to streamline administrative processes and ensure information integrity for users SOLUTION SOA with Enterprise Service Bus to connect siloed applications without hand-coding individual API calls (WESB, CICS TS, System z) BENEFITS Ability to develop and implement services in an SOA environment for resolving name and address discrepancies in 10 months, as opposed to several years for hand-coding individual application connections Confidence that IBM solution can lead to wider use of SOA to further streamline administrative business processes Services created here can be reused in later SOA efforts Ball State University: Overview: Ball State University (BSU), based in Muncie, Indiana, is a publicly assisted university of about 20,000 students with a penchant for high technology. Business need: Coordinate 40 name and address systems to streamline administrative processes and ensure information integrity for users. Solution: SOA with Enterprise Service Bus to connect siloed applications without hand-coding individual API calls Benefits: Ability to develop and implement services in an SOA environment for resolving name and address discrepancies in 10 months, as opposed to several years for hand-coding individual application connections; confidence that IBM solution can lead to wider use of SOA to further streamline administrative business processes; services created here can be reused in later SOA efforts Customer Quote: “If you tried to have each system be aware of 40 other systems where addresses are kept, you’d be constantly in maintenance mode trying to accommodate how another system maintains addresses and how do you communicate to it. So, the advent of SOA and Web services is not just an evolutionary step, to me it’s a revolutionary step.” Customer information Customer name:Location:Ball State UniversityAmericas,  United StatesIndustry: Education Focus area: CIO Program, Enabling Business Flexibility, Service Oriented ArchitectureGeography: AmericasDate Published: 10/22/2007Last Updated: 10/22/2007Back to top Solution implementation Key Components Software • IBM WebSphere® Enterprise Service Bus • IBM CICS® Transaction Server • IBM DB2® • IBM WebSphere Application Server • IBM WebSphere Host Access Transformation Service, Version 7 • IBM WebSphere Integration Developer Servers • IBM System z9™ Business Class • IBM System Storage™ DS Services • IBM Software Lab Services • IBM Global Technology Services • IBM Hardware Lab Services IBM Business Partner • Sirius Business Solutions Pull quotes: “We would not have been able to solve the address reconciliation problem without IBM literally throwing the full force of its resources at it.” –Dr. O’Neal Smitherman, CIO, Ball State University “If you tried to have each system be aware of 40 other systems where addresses are kept, you’d be constantly in maintenance mode trying to accommodate how another system maintains addresses and how do you communicate to it. So, the advent of SOA and Web services is not just an evolutionary step, to me it’s a revolutionary step.” –Fred Nay, IT Director, Ball State University “SOA has been such a gift to us. It enables us to embrace a new technology that provides services at a level that we couldn’t even imagine before.” –Dr. O’Neal Smitherman Ball State University (BSU), based in Muncie, Indiana, is a publicly assisted university of about 20,000 students with a penchant for high technology. Named the nation’s number one wireless campus in a 2005 Intel survey, BSU is ranked by the Carnegie Foundation as a doctoral/research-intensive institution and ceaselessly promotes technology as a means to innovation. On the dynamic BSU campus where students can wirelessly connect to cameras in route busses to see how far away their bus is, expectations are high that technology can solve any problem—certainly any administrative one—with the right amount of attention and resolve. Therefore, it was frustrating for students, alumni and faculty that a consistent version of their names and addresses could not be automatically reconciled into all 40 systems in which the university’s name and address information resided due to a lack of information integrity. With 200 siloed systems altogether on campus, Fred Nay, director of the Computer Center, struggled with the question of how disparate systems could be made to talk together seamlessly and provide a single version of the truth in every context. “We considered the idea of buying an SAP system to consolidate information and make it available to users when needed,” he says. “But an SAP system would have helped us integrate maybe 15 systems leaving us to deal with the rest. We needed to get them all hooked up together in a seamless, transparent mode.” The solution was a service oriented architecture (SOA) built with IBM Enterprise Service Bus, IBM System z9 Business Class mainframe, IBM DS8100 storage and other IBM middleware software products. The success of the solution has changed the way BSU is approaching its technology mission. “SOA has been such a gift to us,” says CIO Dr. O’Neal Smitherman. “It enables us to embrace a new technology that provides services at a level that we couldn’t even imagine before. Our hope is to move into an entire architecture that allows Web services development to be almost transparent. As we’ve worked with it, it really has been exciting to see how easy it is to develop a Web service when you’ve got the architecture in place.” IBM helps accelerate IT response An alumnus did not receive his diploma because of a name and address defect within the university’s multiple application systems. The alumnus called the president of the university, and the president issued a directive to make all the name and address systems work with each other ASAP. Challenged by Smitherman to present the two best ways to solve this problem, Nay joined his CIO at an IBM SOA acceleration workshop. The result was that Nay unequivocally pushed for an SOA solution. “There was definitely a learning curve up front,” says Nay. “But prior to having an SOA maintaining the name and address logic, if you tried to have each system be aware of 40 other systems where addresses are kept, you’d be constantly in maintenance mode trying to accommodate how another system maintains addresses and how do you communicate to it. So, the advent of SOA and Web services is not just an evolutionary step, to me it’s a revolutionary step.” The IBM workshop took place 10 months ago. Since then, the IBM Global Services team (IBM Software Lab Services, IBM Global Technology Services and IBM Hardware Lab Services) has helped BSU deploy an Enterprise Service Bus (ESB) and implement additional IBM software. IBM Premier Business Partner Sirius Computer Solutions, based in San Antonio, Texas, has helped install the IBM mainframe hardware and DS8100 storage. Through mentoring and training, the University Computing staff at BSU has taken the reins to complete the name and address project and build on top of an established, proven SOA solution. “We would not have been able to solve the address reconciliation problem without IBM literally throwing the full force of its resources at it,” says Smitherman. “Without IBM we would not be as advanced with our SOA as we are, and without SOA it would have taken years instead of ten months to develop the solutions we have finished.” Building reusable components with SOA The IBM SOA solution runs in the mainframe environment utilizing IBM CICS Transaction Server, Version 3.1. This version strengthens the application development capabilities of CICS and extends CICS applications to an SOA. In a scenario in which information is provided as a service and applications are decoupled rather than hard-coded together, CICS makes it possible for transactions to readily connect with multiple interfaces and repositories to provide authoritative data. IBM WebSphere Enterprise Service Bus, Version 6.0.2, works in conjunction with IBM WebSphere Application Server, Version 6.1, to communicate between decoupled back and front ends, choosing the destination for a message and transforming it into the correct format. IBM WebSphere Host Access Transformation Server (HATS), Version 7, generates Web Services Definition Language (WSDL) that is callable by BSU’s .NET front end to publish information to the user interface. IBM WebSphere Integration Developer enables developers to assemble complex applications across the ESB by connecting reusable components. IBM DB2, Version 8, is the database for the SOA. Making students’ lives easier As BSU completes the name and address integration project —and testing is nearly complete— it is in the early stages of creating a new set of services with IBM in the SOA environment, utilizing Websphere Process Server and Websphere Business Modeler to map the business process of students enrolling in Distance Learning classes. The services created here can be reused for the other enrollment programs within the university. A messaging service that students can sign up for to get emergency notifications via SMS or any other medium utilizing SOA has also been created and is completing testing. Through it all, CIO Smitherman has been traveling his own journey through the new world of SOA. His work is defined by the many stakeholders in the university who need to be persuaded to break down siloed IT systems and to think of business processes as having commonalities that SOA can build on. Technology can streamline administrative processes at BSU, and SOA is the way. “When you go into this, you go into it thinking that you’re going to work with the technology, and for the CIO, that’s true,” says Smitherman. “But by far the more time-consuming and the more difficult parts of this process are the cultural and business process discussions that have to take place. It’s the human involvement that can make this technological innovation work.”

28 New and changed mediation primitives Service Message Object Updates
Mediation Updates New and changed mediation primitives Service Message Object Updates

29 WESB Enhancements BO Map Primitive
Enable use of Business Object Maps in Mediation modules An alternative to XSLT transforms Supports relationship based mapping New Business Object Map primitive Embeds a BO map inside a mediation flow Alternative to XSLT transformation for manipulating SMO content Includes support for maps that use relationship-based transforms (ie. support all functions of BO Map)

30 SVT example

31 Relationships System C System B System A customerCountry England Wales
Used to map same data that has different representations in different systems. System C System B System A customerCountry England Wales Poland Italy Spain …. custCont ENG WAL ITA ESP cCountry 00123 00456 00789 01123

32 WESB Enhancements Service Invocation and Retry Primitive
Invokes a target service from within a request or response flow Includes built-in retry capability; retries x times in event of failure Can try/retry a list of target endpoints in turn until success Can exploit multiple endpoints returned from the Endpoint Lookup primitive for this purpose Also acts as a building block for aggregating content from more than one service Capability similar to existing Callout, but flow continues inline (no switch to response flow) New context area in the SMO contains invocation request/response body content New ServiceInvoke primitive Invokes a target service from within a request or response flow Includes built-in retry capability; retries x times in event of failure Can try/retry a list of target endpoints in turn until success Also acts as a building block for aggregating content from more than one service Capability similar to existing Callout, but flow continues inline (no switch to response flow) New context area in the SMO contains invocation request/response body content Service invocation can be asynchronous

33 New: FanOut and FanIn Mediation Primitive
Messages can be split for further processing Results can be aggregated New FanOut and FanIn primitives FanOut splits an incoming message based upon a repeating element, or sets up ‘parallel’ paths that are later joined by FanIn Allows composite messages to be split up for individual processing of the parts; and assembly of composite messages Also, aggregation is supported using ServiceInvoke primitive Invoke multiple services and combine the results Invoke service A Store away context and any part of Response-A Invoke service B Populate response based on Response-A, Response-B and any saved context information

34 Splitting and Aggregating - details
New FanOut and FanIn primitives FanOut splits an incoming message based upon a repeating element ...or sets up branching paths that are later joined by FanIn Allows composite messages to be split up for individual processing of the parts; and assembly of composite messages Aggregation supported using ServiceInvoke primitive Invoke multiple services and combine the results

35 Splitting and Aggregating - example

36 WESB Enhancements Custom Mediation Primitive
Multiple input and output terminals User-defined properties Easy access to ESB mediation primitive programming model Custom mediation executes Java code in a mediation flow Currently restricted to one output terminal, fired when mediate method returns Allows new terminals to be defined User control of the firing of terminals (from the user Java code) Allows user-defined properties to be set Configured in the flow editor Available to be set as promoted properties in runtime admin console Existing custom mediation instances will work with no modification

37 Summary and Conclusion

38 Key evolution in 6.1, centering on Consumability
Conclusion Key evolution in 6.1, centering on Consumability both administration and development interfaces Completeness of capability Additional connectivity Additional mediation function Continued maturation and evolution

39


Download ppt "Using WebSphere Enterprise Service Bus for z/OS"

Similar presentations


Ads by Google