DB2 for z/os in an SOA

Transcription

1 Session: A07 DB2 for z/os in an SOA Maryela Weihrauch, IBM Silicon Valley Lab. May 20 th, :30 p.m. 02:30 p.m. Platform: DB2 for z/os Service Oriented Architecture (SOA) is the center of heated architecture discussions within IBM and at our customers. The possibilities of SOA are as dramatic as the possibilities that the internet created. This session will discuss the DB2 z/os role in SOA with focus on topics like how the DB2 customer can make their legacy DB2 applications available in a SOA architecture, how does DB2 z/os integrate with web services, what are the risk factors. It describes the environment and technologies to involve DB2 for z/os producing & consuming SOA today and what can be expected in the near future. 1

2 Important Disclaimer THE INFORMATION CONTAINED IN THIS PRESENTATION IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY. WHILE EFFORTS WERE MADE TO VERIFY THE COMPLETENESS AND ACCURACY OF THE INFORMATION CONTAINED IN THIS PRESENTATION, IT IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. IN ADDITION, THIS INFORMATION IS BASED ON IBM S CURRENT PRODUCT PLANS AND STRATEGY, WHICH ARE SUBJECT TO CHANGE BY IBM WITHOUT NOTICE. IBM SHALL NOT BE RESPONSIBLE FOR ANY DAMAGES ARISING OUT OF THE USE OF, OR OTHERWISE RELATED TO, THIS PRESENTATION OR ANY OTHER DOCUMENTATION. NOTHING CONTAINED IN THIS PRESENTATION IS INTENDED TO, OR SHALL HAVE THE EFFECT OF: CREATING ANY WARRANTY OR REPRESENTATION FROM IBM (OR ITS AFFILIATES OR ITS OR THEIR SUPPLIERS AND/OR LICENSORS); OR ALTERING THE TERMS AND CONDITIONS OF THE APPLICABLE LICENSE AGREEMENT GOVERNING THE USE OF IBM SOFTWARE. 2 2

3 Agenda Introduction into Service Oriented Architecture (SOA) DB2 z/os Role in SOA Alternatives that involve DB2 z/os access IBM Information Server Overview 3 Service Oriented Architecture (SOA) is the center of heated architecture discussions within IBM and at our customers. The possibilities of SOA are as dramatic as the possibilities that the internet created. This session will discuss the DB2 z/os role in SOA with focus on topics like how the DB2 customer can make their legacy DB2 applications available in a SOA architecture, how does DB2 z/os integrate with web services, what are the risk factors. It describes the environment and technologies to involve DB2 for z/os producing & consuming SOA today and what can be expected in the near future. 3

4 SOA the Theory SOA itself is an abstract concept SOA is a component model that connects functional units, called services, through well-defined interfaces and contracts The interface is defined in a neutral manner Independent of hardware platform, Independent of programming language in which the service is implemented. -> loose coupling between services The benefit of SOA is A Catalog of services its ability to survive changes in the structure and implementation of the internals of each service. 4 There has been much written about the value in using an SOA to manage change in IT systems. SOA requires each IT application to have well-defined interfaces to represent the business function that it supports. These interfaces, or services, provide a catalog of IT functions that can be called as and when needed. The calls can be directly between applications, via workflow applications, or dynamically routed through an Enterprise Service Bus (ESB). If it's done well, a service-oriented approach allows an organization to structure and connect its IT systems together in a flexible manner that maps closely to the needs of the organization. 4

5 SOA: Different things to different people A set of business services composed to capture the business design that an enterprise wants to expose to its customers and clients Roles Business An architectural style which requires a service provider, requestor and a service description. A set of architectural principles and patterns which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composable and single implementation. A programming model complete with standards, tools, methods and technologies such as Web Services. Architecture Implementation 5 The Model-Driven Architecture (MDA), as proposed by the Object Management Group and implemented in a number of IBM Rational products, has a strong correlation to the concepts of SOA in a more abstract level. MDA is based upon the concept that any software process can be defined as a model and even a metamodel (a model of a model) that can then be translated into actual software components of an application. Thus a MDA creates a model that is compiled into a software application that in turn is compiled into an executable that can run on a platform. MDA does not distinguish between concepts of services and objects, but it does allow models to be composed of other subset models themselves, similar to the concept of process aggregation within Business Process Execution Language (BPEL), a core component of SOA. The remaining presentation sees SOA from the architectural role 5

6 Web Services and SOA the Basics A SOA model can be implemented based on XML and Web Services technology 1. Register/Discovery Where is the Web Service? 2. Description What service does it offer? How do I use it? 3. Messaging Let s communicate! Discovery UDDI Description WSDL Messaging SOAP 6 WSDL (Web Services Description Language) is a public description of the interfaces offered by a web service. Expressed in XML, it provides machine readable document that provides a calling application all of the information required to interact with a web service. Sample: <?xml version="1.0"?> - <definitions name="temperatureservice" targetnamespace=" xmlns:tns=" xmlns:xsd=" xmlns:soap=" xmlns=" - <message name="gettemprequest"> <part name="zipcode" type="xsd:string" /> </message> - <message name="gettempresponse"> <part name="return" type="xsd:float" /> </message> - <porttype name="temperatureporttype"> - <operation name="gettemp"> <input message="tns:gettemprequest" /> <output message="tns:gettempresponse" /> </operation> </porttype> A SOAP message is a XML document that contains the following building blocks: - A required Envelope element that identifies the XML document as a SOAP message - An optional Header element that contains header information - A required Body element that contains call and response information - An optional Fault element that provides information about errors that occurred processing the message while Sample: <soap:envelope xmlns:soap=" <soap:body> <getproductdetails xmlns=" <productid>827635</productid> 6

7 Web Services Decouples Interfaces from Applications Turn this Application Application Application Application into this (web services). Service Service Service Service Interface Interface Interface Application Application Application Application Interface Interface Interface Interface Service Service Service Service = interface Rich business abstractions describe the application interface Decouples the interfaces from the business applications The number Business and applications complexity of and their the interfaces interfaces is reduced become reusable But separate connection points still leaving bloated interfaces. 7 So how does basic SOA decouple the interfaces from their applications? 1) SOA uses a programming model that allows a rich abstraction of both the business app and the interface. 2) By abstracting, the interfaces can be clearly separated from the business applications. 3) This enables you to reduce the number and complexity of those interfaces. 4) It allows you to reuse both the interfaces and the business applications. The problem is that you still have to build, find, and manage all of those interfaces somewhere. 7

8 The ESBus shrinks those interfaces Turn this (web services) into this Service Service Service Service Service Service Service Service Interface Interface Interface Enterprise Service Bus Interface Interface Interface Interface Service Service Service Service Service Service Service Service Decouples the point-to-point connections from the interfaces Allows for dynamic selection, substitution, and matching Enables more flexible coupling and decoupling of the applications Enables you to find both the applications and the interfaces for re-use RESULT Greater Business Responsiveness 8 The ESB shrinks the interfaces further. It virtualizes the interface, or in other words, it decouples the point-to-point connections from the interfaces themselves. 2) The interfaces are put into a third party broker which helps you manage the interfaces better. 3) This enables faster and more flexible coupling and decoupling of applications. 4) Because you can find all of the applications and the interfaces, you can then reuse both. 8

9 What would Constitute a SOA Failure? InfoWorld 2006 Performance or scalability issues Poor reliability Lack of security Difficult to manage services Does not meet business needs Too difficult to adapt and build new applicatons Disappointing levels of reusability Goes overbudget Lack of service discovery & goverance Lack of standards-based integration of services Other * * * 1% 1% 36% 32% 39% 35% 35% 62% 64% 65% 60% 60% 53% 58% 53% 55% 54% 50% 52% * Not asked in % 10% 20% 30% 40% 50% 60% 70% D current Q: What would constitute SOA failure? 2006 Base: 473 / 2005 Base: 167 (Among those personally involved with SOA at their company and are deploying SOA and/or have pilot projects in place) 9 9

10 SOA Reference Architecture Business Innovation & Optimization Services Facilitates better decision-making with real-time business information Development Services Interaction Services Process Services Information Services Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data and content in a unified manner IT Service Management Integrated environment for design and creation of solution assets Partner Services Business App Services Access Services Connect with trading partners Facilitates communication ESB between services Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets Apps & Info Assets Manage and secure services, applications & resources Infrastructure Services Optimizes throughput, availability and performance 10 Focusing just on the inner, light-blue boxes in the upper row Interaction Services, Process Services and Information Services addresses the traditional delineation between presentation logic, business logic and data logic introduced by three-tier distributed application architectures and the Model- View-Controller pattern. When Business Application Services are considered as a decomposition of Process Services then an n-tier distributed system architecture is emerging from Access services are dedicated to integrating legacy applications and functions into the service-oriented architecture. This includes simple wrapping of those functions and rendering them as services (in the case where the existing function is a good match with the semantic requirements of the business model in which it will be used), or in more complex cases augmenting the logic of the existing function to better meet the needs of the business design. In the latter case, the access service may in fact invoke multiple legacy functions to achieve the semantic requirements of the service. The Access Services make the assets of legacy application available in the new architecture, therefore providing a low entry level into SOA. 10

11 DB2 Web Services Overview WebSphere Application Server IBM Data Web Services DB2 Stored Procedures HTTP/SOAP Service Web Providers Confix.xml Tables Web Services UDFs HTTP/SOAP Soap Client HTTP/GET Web Browser SQL SQL Applications DB2 provides Web Services data DB2 consumes Web Services data 11 DB2 provides Web Services consumer as well as producer support. Details discussed in following charts. WORF (DB2 Web Services Object Runtime Framework) will be replaced by IBM Data WebServices. 11

12 Web Service from Database Operations J2EE-based WS Runtime Package Eclipse-based Configuration File 1. Database Operations 2. Tooling ( one-click ) WS Description (WSDL) 3. Web Service Artifacts bottom-up development 12 12

13 5 Simple steps to create a Web Service 1. Develop Statements 2. Create Service 3. Drag n drop 4. Deploy Service 5. Test Service 13 13

14 IBM Data Web Services (DWS) Next generation of the DB2 Web Service provider Allows simple and fast SOA-enablement of database operations Successor of WORF Re-architected Makes more use of standard Java libraries (like Transformer API) Full XML integration Better tooling integration (DWB/RAD) More focus on logging, tracing and monitoring XSLT processing Better Web 2.0 integration Simpler tooling, configuration and runtime Support of DB2 V9 trusted context and clientinfo registers

15 DWS Development and Deployment Certain app-server specific settings required Arrow Data sources export/import deploy Data Web Services Tooling Data Web Application Application server Security Tracing/Logging/ Monitoring Application Server Tooling development deployment 15 15

16 DWS Runtime Architecture generate Tooling Service Client HTTP/SOAP Web DWS Application config.xml JDBC J2EE Application Server Database SQL Stored Procedures 16 Tooling (RAD/DWB/.NET) generates DWS Web Application and needed artifacts. The config.xml file contains the WebService to SQL mapping definition. The DWS application is deployed to an J2EE Application Server. The client calls the WebService via SOAP/HTTP. The DWS application maps the request to the defined SQL statement, executes the SQL via JDBC and formats the result as Web Service responds. It supports optional xslt transformation on input as output to customize the message format. 16

17 Value of DataPower for z and DB2 for z/os Simply, the Offloading and Acceleration of high overhead Web Services processing Addresses the same theme as other z offloads (e.g. zaaps, ziips) Compute cycle intensive XML and security-related processing (especially re Crypto) Other general functional capabilities: application level firewalling, routing, filtering,... Appliance model: improved consumability XML Device Layer... Continued

18 DataPower DB2 Web Services Feature High performance Web Services processing and mapping to SQL statement as well as XSLT transformation DataPower communicates with DB2 via DRDA DB2 and DataPower tooling support in plan Web Services Consumers DataPower DB2 Web Services Appliance SOAP DRDA DB2 for z/os 18 18

19 Development and Deployment Today Data sources DWS Drag n drop generate J2EE Web Application deploy J2EE Application server Security Tracing/Logging/ Monitoring Data Studio Web Service definition generate Future Data sources XSLT Script deploy DataPower Security Tracing/Logging/ Monitoring development deployment 19 19

20 DB2 Web Services Consumer PQ91316 adds function as a Web Service consumer to DB2 z/os V7 and V8 Allow mainframe-based enterprise applications to invoke Web Services regardless of their location SQL User-Defined Functions (UDFs) Signature 1 ENDPOINT_URL, SOAP_ACTION, SOAP_BODY as input SOAP body of responds message as output Signature 2 (coming soon) SOAP message as input SOAP response message as output 20 20

21 DB2 Web Services Consumer... Process flow Receive input parms from SQL statement Compose HTTP/SOAP request Invoke TCPIP socket call via zos USS APIs and send HTTP/POST request Receive reply from Web Service Provider Validate HTTP headers Strip SOAP envelope and return SOAP Body Tooling support for DB2 z/os in RAD V7 Create a SQL UDF specifically for a WS operation from WSDL Creates wrapper SQL UDF to hide XML/relational mapping

22 Web Services Consumer Example Local SQL can be replaced by SQL call that resolves into Web Services call SELECT rate FROM Ratetable WHERE country1=c1 AND country2= c2; SELECT rate FROM TABLE (getrate(?,?)); getrate() is a wrapper UDF that calls SOAP UDF and reads XML reply and returns results as SQL result, 22 CREATE FUNCTION getrate ( country1 VARCHAR(100), country2 VARCHAR(100) ) RETURNS DOUBLE LANGUAGE SQL EXTERNAL ACTION NOT DETERMINISTIC SQL Scalar UDF that wraps the Web Service, "getrate", described by RETURN db2xml.extractdouble( db2xml.xmlclob( db2xml.soaphttpv(' '', varchar('<m:getrate xmlns:m="urn:xmethods-currencyexchange" ' 'SOAP- ENV:encodingStyle=" ' '<country1 xsi:type="xsd:string">' country1 '</country1>' '<country2 xsi:type="xsd:string">' country2 '</country2>' '</m:getrate>'))), '//*'); 22

23 Web Services Consumer Example CREATE FUNCTION getrate (country1 VARCHAR(100), country2 VARCHAR(100) ) RETURNS DOUBLE LANGUAGE SQL EXTERNAL ACTION NOT DETERMINISTIC SQL Scalar UDF that wraps the Web Service, "getrate", described by RETURN db2xml.extractdouble( db2xml.xmlclob( db2xml.soaphttpv(' '', varchar('<m:getrate xmlns:m="urn:xmethods-currencyexchange" ' 'SOAP- ENV:encodingStyle=" ' '<country1 xsi:type="xsd:string">' country1 '</country1>' '<country2 xsi:type="xsd:string">' country2 '</country2>' '</m:getrate>'))), '//*'); 23 23

24 Technology XML/SQL and DB2 XML is a key 'data interchange' format Business critical information exchanged between B2B/B2C, inter- and intra-enterprise environments input and output data of Web Services invocation are in XML DBMS provides Large scale storage / Management Transformation / Aggregation Interrogation / Analysis of data Combine strengths of both worlds by additions to SQL that enable XML view of relational data SQL data viewed and updated as XML Done via document shredding and composition DTD and Schema validation XML as a rich data type Atomic storage and retrieval Powerful query capabilities, indexing, 24 24

25 Access DB2 data via IMS TM as Web Services Enabled as Web Services, the unchanged IMS Transactions, accessing DB2 data, can today support a Service Oriented Architecture (SOA) IMS C, Cobol and MFS-based Transactions can be enabled as Web Services via WebSphere/Rational Servers/Tooling IMS Web Services Connectivity Configuration Examples: Service flow Data DB2 Data Existing Applications IMS Applications New Service Logic Portal Service IMS Connect / IMS Connect Java Client W S D L Java Component EJB / Bean WAS IMS Connector for Java TCP/IP IMS Connect O T M A IMS Appls. DB2 UDB for z/os MQ to IMS Bridge W S D L Java Component EJB / Bean WAS JMS to MQ MQ Queues MQ MQ-IMS Bridge (XCF) O T M A IMS Appls. DB2 UDB for z/os 25 Existing legacy IMS application can be brought as asset into SOA. IMS provides Webservices support via several configurations, either via JCA or SOAP Gateway connecting to IMS Connect. 25

26 Access DB2 data via CICS as Web Services Enabled as Web Services, the unchanged CICS Transaction accessing DB2 data, can today support a Service Oriented Architecture (SOA) CICS supports Web Services using the WebSphere Application Server Connector Architecture (JCA) and native Web Services DB2 Service flow Data DB2 Data Existing Applications CICS Applications App Env App App App App App P Converter Converter Converter Converter Converter Core CICS I Protocol P W S -A T W S -S e c E CICS TS v3.1 HTTP W S -R M A P Is M Q Transport W ebsphere Comms Server M Q W S B in d F ile P ip elin ed ef New Service Logic URIMap Portal Service 26 Similar is true for CICS application. CICS has an excellent WebServices provider and consumer support either via JCA or via the native support. 26

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

28 Information Services in IBM Products Business Information Services WebSphere Customer Center WebSphere Product Center IBM Entity Analytics Information Integration Services IBM Information Server Content & Discovery Services WebSphere Information Integrator Content Edition Data Services DB2 V

29 The IBM Solution: IBM Information Server Delivering information you can trust IBM Information Server Unified Deployment Understand Cleanse Transform Deliver Discover, model, and govern information structure and content Standardize, merge, and correct information Combine and restructure information for new uses Synchronize, virtualize and move information for in-line delivery Unified Metadata Management Parallel Processing Rich Connectivity to Applications, Data, and Content 29 Key Point: The culmination of these efforts has led us to our latest platform offering the IBM Information Server. IBM Information Server is a revolutionary new software platform from IBM that helps organizations derive more value from the complex, heterogeneous information spread across their systems. It enables organizations to integrate disparate data and deliver trusted information wherever and whenever needed, in line and in context, to specific people, applications, and processes. IBM Information Server helps business and IT personnel to collaborate to understand the meaning, structure, and content of any type of information across any sources. It provides breakthrough productivity and performance for cleansing, transforming, and moving this information consistently and securely throughout the enterprise, so it can be accessed and used in new ways to drive innovation, increase operational efficiency, and lower risk. IBM Information Server is designed to help companies leverage their information across all its sources. IBM Information Server delivers all of the functions required to integrate, enrich and deliver information you can trust for your key business initiatives. IBM Information Server allows you to: Understand all sources of information within the business, analyzing its usage, quality, and relationships Cleanse it to assure its quality and consistency 29

30 Common Programming Model ESB Web Services EJB JMS SCA/SDO IBM WebSphere Information Services Director Shared Services Metadata Services & Service Registry Logging, Security Load Balancing, Availability Other Services Common Configuration, Installation Administration and Reporting Common Service Backbone Integrated Metadata Management Design Operational IBM Information Server 30 30

31 Conclusion Service Providers Customers Business Partners Suppliers Employees JSP SQL WSDL COBOL HTML XML UML RDB J2EE XSD C++ Java WCCM SQL CICS EJB DB2 Directory & Security Services Web Application Servers Web Presentation Servers End-to-End Systems Management SDO / EMF Clear Case XML Transaction Servers Data Servers J2EE IMS XML Companies acknowledge the benefits of SOA and want to implement it DB2 z/os is an important component in SOA Legacy DB2 z/os applications and Stored Procedures can be published as Web Services and consume Web Services results XML is essential technology in SOA and DB2 made XML a firstclass data type 31 31

32 References Powering SOA with IBM Data Server pen Data Web Services Video and %20- %20The%20new%20way%20to%20build%20Web%20services%2 0for%20DB2%20and%20Informix%20Dynamic%20Server DWE and Data Web Services bendel/?S_TACT=105AGX11&S_CMP=FP 32 32

33 Session A07 DB2 for z/os in an SOA Maryela Weihrauch IBM Sillicon Valley Lab