DOCSLIB.ORG

Web Services and Service Oriented Architecture

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Web Services and Service Oriented Architecture Web Services and Service Oriented Architecture CS 4720 – Web & Mobile Systems CS 4720 The tradi0onal so5ware model • Organizaons build it all from scratch – “We can't trust anyone! Our compe0tors will sabotage us!” – “We must own everything! Hardware and so5ware!” • Companies that build so5ware need components that do X or Y… – … so they buy COTS components – Service contracts, new releases, regression tes0ng… 2 CS 4720 The tradi0onal so5ware model • How well does this work? • Some project data from the DOD: – 47% of so5ware delivered could not be used • Usually didn't meet requirements – 29% of funded so5ware never delivered • Usually canceled due to cost/schedule overruns – 19% of so5ware useful aer extensive rework • Costs 36 0mes more to fix problems aer release 3 CS 4720 A push to distribu0on • “We're really good at __________, how can we get our __________ out for people to use?” • The idea of distributed compu0ng – “We're good at X, but not so good a Y…” – “What if we got someone to help us with Y… but in a way that we didn’t have to include any fancy libraries… – … and we could use them in web apps! And mobile devices! And even desktop apps!” 4 CS 4720 A Web Service • From W3C: “a so5ware system designed to support interoperable machine-to-machine interac0on over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its descrip0on using SOAP-messages, typically conveyed using HTTP with an XML serializaon in conjunc0on with other Web- related standards” 5 CS 4720 A Web Service? • Huh? • A bit more simply: A program, accessible via the Internet, that can do some func0on (either for free or a fee) and can be dynamically discovered and used. • So… I use web apps all the 0me… are those web services? 6 CS 4720 Web Service as RPC • The earliest form of a true “web services” was an RPC – remote procedure call. • Exactly what it sounds like – there is an exposed func0on/method that is accessed via the web where you pass the parameters and the method name and you get back a return value. • No0ce how this is very different from the RESTful model (verbs vs. nouns) 7 CS 4720 Web Service as SOA • RPC was okay… but it turned out to be a bit more language specific than we'd like • What if we just a structured message (like an XML document) that described what we wanted, as opposed to knowing the exact func0on call? • This is the basis of the Service-Oriented Architecture 8 CS 4720 Word By Word • What is a service? • "A service is a discoverable resource that executes a repeatable task, and is described by an externalized service specifica:on.” • Business alignment – business requirements • Specificaons – self-contained, well specified • Reusability – general enough to be reused • Agreements – based on func0on, not plaorm • Hos0ng and discoverability – available • Aggregaon – can be combined to make bigger services 9 CS 4720 Word By Word • What is an architecture? • "A formal descrip:on of a system, or a detailed plan of the system at component level to guide its implementa:on.” • “The structure of components, their interrela:onships, and the principles and guidelines governing their design and evolu:on over :me." 10 CS 4720 Architecture • Architecture is: – A high-enough level of abstrac0on that the system can be viewed as a whole and yet s0ll provides enough informaon to make decisions. – Supports the func0onality of the system. – All implementaon details are hidden. • Service orienta:on is a way of integra:ng a business as a set of linked services. 11 CS 4720 What are we actually trying to do? Fork Receive PO Update Customer Profile Get Items from Inventory Branch Compute Subtotal Compute Export Tax [ship within US] [ship outside US] Compute Shipping Cost Merge Compute International Shipping Compute Total Ship Order Join 12 CS 4720 OSI Model 13 CS 4720 OSI Model 14 CS 4720 The Stack 15 CS 4720 The Stack ebXML UDDI Registries Discovery ebXML Contracts and CPA agreements OWL-S Service Process and workflow BPEL4WS BPML Model orchestrations WS-AtomicTransaction and WS- BTP QoS: Transactions BusinessXALcAtiNviGty WS-Reliable OWL-WS SSCeLrvice WS-Coordination QoS: Choreography Messaging ebXML Profile WSCI BPSS OWL-S Service WS-Security WSCL QoS: Conversations Grounding ebXML WS-Policy WSDL QoS: Service OWL PSL CPP descriptions and bindings ebXML RDF SOAP messaging Messaging XML, DTD, and XML Schema Encoding HTTP, FTP, SMTP, SIP, etc. Transport 16 CS 4720 The Stack 17 CS 4720 SOA – The Quick Version • Right now, you probably think of a so5ware system as being a collec0on of classes / objects • But users don't think of systems like that… they think of systems as sets of func0onality that help them do something • So… why do we use objects? – Easier to model – Easier to program – Easier to explain to other programmers 18 CS 4720 Or is it actually easier? • Turn our idea of a system 90 degrees • Func0onality objects (procedural abstrac0on) is the key idea, not world objects (data abstrac0on) • This is the key in SOA – An SOA system has the func0onali0es as the main players, not the objects themselves – But more so, these services are provided by many different players 19 CS 4720 But what language do we speak? • SOAP - Simple Object Access Protocol – A communicaon protocol – A format for sending messages – Plaorm independent – XML based – Follows the rules that allow for transmission easily over HTTP, SMTP, etc. • Not really much more than an HTTP request that follows XML/SOAP standards 20 CS 4720 SOAP Model 21 CS 4720 SOAP Model 22 CS 4720 SOAP Request POST /InStock HTTP/1.1! Host: www.example.org! Content-Type: application/soap+xml; charset=utf-8! Content-Length: nnn" " <?xml version="1.0"?>" <soap:Envelope" xmlns:soap="http://www.w3.org/2001/12/soap-envelope"" soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">" " <soap:Body xmlns:m="http://www.example.org/stock">" <m:GetStockPrice>" <m:StockName>IBM</m:StockName>" </m:GetStockPrice>" </soap:Body>" " </soap:Envelope>! 23 CS 4720 SOAP Response • HTTP/1.1 200 OK" Content-Type: application/soap+xml; charset=utf-8" Content-Length: nnn" " <?xml version="1.0"?>" <soap:Envelope" xmlns:soap="http://www.w3.org/2001/12/soap-envelope"" soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">" " <soap:Body xmlns:m="http://www.example.org/stock">" <m:GetStockPriceResponse>" <m:Price>34.5</m:Price>" </m:GetStockPriceResponse>" </soap:Body>" " </soap:Envelope>! 24 CS 4720 Parts of SOAP • The Envelope – required root element defining the document as being a SOAP request • The Header – not required, but contains authen0caon and/or payment info for the request • The Body – the actual message being sent 25 CS 4720 But I like to be dirty! • …. • Bad 0tle aside, some didn't like to be “ed down” by such “conservave talk” of having to follow the SOAP rules! • “It's just XML!” they said. “I don't need of this extra stuff! Just good Plain Old XML…!” • “And that's what we'll call it! POX!” 26 CS 4720 What's the difference? • Following the agreed upon rules… • Validang POX can be hard; SOAP is comparably easy • SOAP services are beqer at being dynamically bound • How we do this is Thursday's lecture 27 CS 4720 A5er all this… What about REST? • REST is an architectural style that is independent, but compable, with XML • POX/HTTP means exchanging plain old XML documents over HTTP; can be RESTful • SOAP is a standard document format for building high-level protocols. Anything that uses SOAP is (by defini0on) not just using plain old XML, and thus not POX; it can also be RESTful 28 CS 4720 So… • So there can be RESTful SOAP applicaons, and RESTful POX applicaons, and non-RESTful SOAP applicaons, and non-RESTful POX applicaons, but no POX/SOAP combinaon… sort of 29 CS 4720 Thoughts • If you want a great experience for .NET/Java devs, you'll typically publish schemas and support SOAP. • If you want a great experience for LAMP folks, you'll support POX messages (or JSON) and will provide a non-XSD descrip0on of your formats. • If you want to reach both audiences, you'll do both #1 and #2. • If you want to reach both audiences before your compeon does, you'll avoid indulging in religious debates and ship something. 30 CS 4720 Using a Web Service • If you took the 0me to create a service, then you probably want people to use it • In order to use a service, users need to know what informaon they can send the service and what informaon is going to be sent back • What would be even beqer is if the so5ware could do all this automacally… 31 CS 4720 Enter WSDL • WSDL: Web Services Descrip0on Language – An XML document used to give the specifics of a service • Locaon • Methods • Allowed messages • Poten0al error messages 32 CS 4720 Enter WSDL 33 CS 4720 The HelloService Example • hqp://oreilly.com/catalog/webservess/ chapter/ch06.html 34 CS 4720 Quick Sidestep: UDDI • UDDI: Universal Descrip0on, Discovery and Integraon • A solu0on in search of a problem • The idea is okay: a language and schema for allowing people to publish their WSDL schemas so that others can discover their services • IBM, Microso5, and SAP announced they were closing their public UDDI nodes in January 2006 • No one used it! 35 CS 4720 Quick Sidestep: UDDI • Where might it work decently? – Perhaps inside a single organizaon for internal code • The public sides were either: – Empty – Overrun with junk • Whichever it was UDDI, isn't really used • Quote Marty Humphrey: “It was a good problem to solve, but a terrible solu0on.” 36 CS 4720 The Original
Load more

Recommended publications
  • Web Services and Service Oriented Architectures 1 ©2009 Cesare Pautasso Web Sites (1992)
    SOA with REST Cesare Pautasso Faculty of Informatics University of Lugano http://www.pautasso.info [email protected] 31.3.2009 Web Services and Service Oriented Architectures 1 ©2009 Cesare Pautasso Web Sites (1992) Web HTML Web Browser HTTP Server WS-* Web Services (2000) SOAP WSDL Client XML Server (HTTP) 31.3.2009 Web Services and Service Oriented Architectures 2 ©2009 Cesare Pautasso RESTful Web Services (2007) PO-XML JSON RSS WADL Web Client HTTP Server WS-* Web Services (2000) SOAP WSDL Client XML Server (HTTP) 31.3.2009 Web Services and Service Oriented Architectures 3 ©2009 Cesare Pautasso Where do Web services come from? • Address the problem of • REST advocates have come enterprise software to believe that their ideas are standardization just as applicable to solve • Enterprise Computing application integration Standards for Interoperability problems. (WS started 2001) • A layered architecture with a variety of messaging, description and discovery specifications • Are all specifications really composable? • Do things from the ground up, quickly, in well factored, distinct, tightly focused specifications • Tools will hide the complexity • “Look ma’, no tools!” 31.3.2009 Web Services and Service Oriented Architectures 4 ©2009 Cesare Pautasso Dealing with Heterogeneity • Web Applications • Enterprise Computing Picture from Eric Newcomer, IONA EricNewcomer, Picture from HTTP CICS IMS 31.3.2009 Web Services and Service Oriented Architectures 5 ©2009 Cesare Pautasso Big Web Services WS-PageCount Messaging 232 pages • High perceived
    [Show full text]
  • Enterprise Integration Patterns with WSO2 ESB
    WSO2 EIP Guide Enterprise Integration Patterns with WSO2 ESB 1 April - 2013 WSO2 EIP Guide Table of Contents 1. Enterprise Integration Patterns with WSO2 ESB . 4 1.1 Messaging Systems . 8 1.1.1 Message Channels . 9 1.1.2 Message . 12 1.1.3 Pipes and Filters . 13 1.1.4 Message Router . 16 1.1.5 Message Translator . 20 1.1.6 Message Endpoint . 24 1.2 Messaging Channels . 27 1.2.1 Point-to-Point Channel . 28 1.2.2 Publish-Subscribe Channel . 31 1.2.3 Datatype Channel . 34 1.2.4 Invalid Message Channel . 38 1.2.5 Dead Letter Channel . 41 1.2.6 Guaranteed Delivery . 47 1.2.7 Messaging Bridge . 51 1.2.8 Message Bus . 54 1.3 Message Construction . 55 1.3.1 Command Message . 56 1.3.2 Document Message . 58 1.3.3 Event Message . 61 1.3.4 Request-Reply . 63 1.3.5 Return Address . 66 1.3.6 Correlation Identifier . 69 1.3.7 Message Sequence . 70 1.3.8 Message Expiration . 70 1.3.9 Format Indicator . 73 1.4 Message Routing . 74 1.4.1 Content-Based Router . 76 1.4.2 Message Filter . 79 1.4.3 Dynamic Router . 82 1.4.4 Recipient List . 86 1.4.5 Splitter . 90 1.4.6 Aggregator . 93 1.4.7 Resequencer . 96 1.4.8 Composed Msg. Processor . 100 1.4.9 Scatter-Gather . 104 1.4.10 Routing Slip . 109 1.4.11 Process Manager . 113 1.4.12 Message Broker . 114 1.5 Message Transformation .
    [Show full text]
  • Page 1 of 9 Codeproject: Efficiently Exposing Your Data with Minimal
    CodeProject: Efficiently exposing your data with minimal effort. Free source code and pr ... Page 1 of 9 6,623,518 members and growing! (20,991 online) Email Password Sign in Join Remember me? Lost your password? Home Articles Quick Answers Message Boards Job Board Catalog Help! Soapbox Web Development » ASP.NET » Samples License: The Code Project Open License (CPOL) C#, XML.NET 3.5, WCF, LINQ, Architect, Dev Efficiently exposing your data with minimal effort Posted: 16 Nov 2009 By V.GNANASEKARAN Views: 1,238 An article on how we can expose our data efficiently with minimal effort by leveraging Microsoft ADO.NET Data Services. Bookmarked: 7 times Advanced Search Articles / Quick Answers Go! Announcements Search Add to IE Search Windows 7 Comp Print Share Discuss Report 11 votes for this article. Win a laptop! Popularity: 4.62 Rating: 4.44 out of 5 1 2 3 4 5 Monthly Competition Download source code - 101 KB ARTICLES Desktop Development Web Development Introduction Ajax and Atlas Applications & Tools For enterprises which have been in business for decades, problems due to silos of applications and data that ASP evolved over the years is a common issue. These issues sometimes become show stoppers when an enterprise is ASP.NET starting a new strategic initiative to revamp its IT portfolio, to float new business models and explore new ASP.NET Controls business opportunities. ATL Server Caching This article is going to discuss possible options available for unification of data silos, and how efficiently an Charts, Graphs and Images enterprise can expose its data with minimal effort by leveraging the recent advancements in technology.
    [Show full text]
  • CS8651-Internet Programming Department of CSE 1 Unit- I Part
    CS8651-Internet Programming Department of CSE CS6501 - Internet programming Unit- I Part - A 1 Define Java. Java is a programming language expressly designed for use in the distributed environment of the Internet. It was designed to have the "look and feel" of the C++ language, but it is simpler to use than C++ and enforces an object- oriented programming model. 2. What is a Class? Class is a template for a set of objects that share a common structure and a common behaviour. 3. What is an Object? Object is an instance of a class. It has state, behaviour and identity. It is also called as an instance of a class. 4. What is an Instance? An instance has state, behaviour and identity. The structure and behaviour of similar classes are defined in their common class. An instance is also called as an object. 5. What are different types of access modifiers (Access specifiers)? Access specifiers are keywords that determine the type of access to the member of a class. These keywords are for allowing privileges to parts of a program such as functions and variables. These are: public: Anything declared as public can be accessed from anywhere. private: Anything declared as private can’t be seen outside of its class. protected: Anything declared as protected can be accessed by classes in the same package and subclasses in the there packages. default modifier : Can be accessed only to classes in the same package. 6. What is method overloading and method overriding? Method overloading: When a method in a class having the same method name with different arguments is said to be method overloading.
    [Show full text]
  • REST in Practice
    REST in Practice Jim Webber, Savas Parastatidis, and Ian Robinson Beijing · Cambridge · Farnham · Köln · Sebastopol · Tokyo REST in Practice by Jim Webber, Savas Parastatidis, and Ian Robinson Copyright © 2010 Jim Webber, Savas Parastatidis, and Ian Robinson. All rights reserved. Printed in the United States of America. Published by O’Reilly Media, Inc., 1005 Gravenstein Highway North, Sebastopol, CA 95472. O’Reilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://my.safaribooksonline.com). For more information, contact our corporate/institutional sales department: (800) 998-9938 or [email protected]. Editor: Simon St.Laurent Indexer: Lucie Haskins Production Editor: Rachel Monaghan Cover Designer: Karen Montgomery Copyeditor: Audrey Doyle Interior Designer: Ron Bilodeau Proofreader: Rachel Monaghan Illustrator: Robert Romano Production Services: Newgen North America Printing History: September 2010: First Edition. The O’Reilly logo is a registered trademark of O’Reilly Media, Inc., REST in Practice, the cover image, and related trade dress are trademarks of O’Reilly Media, Inc. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and O’Reilly Media, Inc., was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this book, the publisher and au- thors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein. ISBN: 978-0-596-80582-1 [M] C o n t e n t s Foreword .
    [Show full text]
  • D.3.1.1B FI-WARE GE Open Specification Page 2
    Private Public Partnership Project (PPP) Large-scale Integrated Project (IP) D.3.1.1b: FI-WARE GE Open Specification Project acronym: FI-WARE Project full title: Future Internet Core Platform Contract No.: 285248 Strategic Objective: FI.ICT-2011.1.7 Technology foundation: Future Internet Core Platform Project Document Number: ICT-2011-FI-285248-WP3-D.3.1.1b Project Document Date: 2012-10-15 Deliverable Type and Security: Public Author: FI-WARE Consortium Contributors: FI-WARE Consortium Future Internet Core Platform Table of Contents 1 Introduction ...................................................................................................................13 1.1 Executive Summary ...............................................................................................13 1.2 About This Document .............................................................................................13 1.3 Intended Audience .................................................................................................13 1.4 Chapter Context .....................................................................................................13 1.5 Structure of this Document .....................................................................................15 1.6 Typographical Conventions ....................................................................................16 1.6.1 Links within this document...............................................................................16 1.6.2 Figures ............................................................................................................16
    [Show full text]
  • Open Source SOA
    Jeff Davis MANNING Open Source SOA Licensed to Venkataramanan Tharagam <[email protected]> Licensed to Venkataramanan Tharagam <[email protected]> Open Source SOA JEFF DAVIS MANNING Greenwich (74° w. long.) Licensed to Venkataramanan Tharagam <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwick, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15 percent recycled and processed without the use of elemental chlorine. Development Editor: Cynthia Kane Manning Publications Co. Copyeditor: Liz Welch Sound View Court 3B Typesetter: Krzysztof Anton Greenwich, CT 06830 Cover designer: Leslie Haimes ISBN 978-1-933988-54-2 Printed in the United States of America 12345678910–MAL–16151413111009 Licensed to Venkataramanan Tharagam <[email protected]> brief contents PART 1HISTORY AND PRINCIPLES ...........................................
    [Show full text]
  • Introduction to Web Services for RPG Developers
    TUG Seneca night school program Introduction to Web services for RPG developers Claus Weiss [email protected] TUG meeting March 2011 Web services and IBM i 1 TUG Seneca night school program Acknowledgement In parts of this presentation I am using work published by: Linda Cole, IBM Canada Scott Klement, Klement Sausage Co., Inc. Web services and IBM i 2 TUG Seneca night school program Agenda . Web Services: What are they? Why use them? . Creating a Web Service Using RPG Using EGL . Consuming a web service Using Web Service explorer With EGL With RPG using EGL or HTTPAPI Web services and IBM i 3 TUG Seneca night school Change in the marketplace, IBM i, & App.Development The 1980’s The 1990’s New Millennium Public Web Service AS/400 iSeries Web Service Client/Server System 38…AS/400 Large, monolithic RPG programs iSeries IBM IBM i i ILE: Smaller, reusable programs 4 Based on IBM Rational Developer for IBM i education material TUG Seneca night school program The Problem: Integration . Integrating software applications across multiple operating systems, programming languages, and hardware platforms is Difficult Not something that can be solved by any one particular proprietary environment . Traditionally, the problem has been one of tight-coupling One application that calls a remote network is tied strongly to it by the function call it makes and the parameters it requests Fixed interface to access remote programs or data, with little flexibility or adaptability to changing environments or needs . What are Web services: self-contained software components, with well-defined interfaces (WSDL), that can be invoked over a network using .
    [Show full text]
  • Testbed-12 REST User Guide Table of Contents
    Testbed-12 REST User Guide Table of Contents 1. Executive Summary . 3 2. Introduction . 8 3. User Guidance. 10 3.1. REST and Open Geospatial Resources . 10 3.2. Principles of REST . 19 3.3. Advantages of REST . 20 3.4. Key Terms . 21 3.4.1. Representational State Transfer (REST) . 21 3.4.2. Hypertext Transfer Protocol (HTTP) . 21 3.4.3. HTTP Method . 21 3.4.4. URI . 21 3.4.5. Resource . 21 3.4.6. Base URL . 21 3.4.7. Capabilities Resource . 22 3.4.8. Hypermedia Controls . 22 3.4.9. Abbreviated Terms . 22 4. Implementer Instructions . 23 4.1. Use Nouns and Don’t Use Verbs . 23 4.2. Use Well-Known Resource Classes . 24 4.3. Use HTTP Status Codes . 25 4.4. Use Well-Known URL Templates and Access Paths . 27 4.4.1. WMTS - URL Templates and Access Paths . 27 4.4.2. WFS - URL Templates and Access Paths . 29 4.4.3. WCS - URL Templates and Access Paths . 30 4.4.4. WPS - URL Templates and Access Paths . 31 4.4.5. WMS - URL Templates and Access Paths . 33 4.5. JSON Examples . 34 4.5.1. JSON and WFS . 34 4.5.2. JSON and WMTS . 43 4.5.3. JSON and WPS . 44 4.5.4. JSON and WMS . 53 4.5.5. JSON and Registry. 57 4.6. API Management . 59 Appendix A: Revision History . 60 Publication Date: 2017-05-16 Approval Date: 2017-02-20 Posted Date: 2016-11-16 Reference number of this document: OGC 16-057r1 Reference URL for this document: http://www.opengis.net/doc/PER/t12-A060 Category: User Guide Editor: Jeff Harrison Title: Testbed-12 REST Users Guide COPYRIGHT Copyright © 2017 Open Geospatial Consortium.
    [Show full text]
  • D3.1.3 FI-WARE GE Open Specifications
    Private Public Partnership Project (PPP) Large-scale Integrated Project (IP) D.3.1.3: FI-WARE GE Open Specification Project acronym: FI-WARE Project full title: Future Internet Core Platform Contract No.: 285248 Strategic Objective: FI.ICT-2011.1.7 Technology foundation: Future Internet Core Platform Project Document Number: ICT-2011-FI-285248-WP3-D.3.1.3 Project Document Date: 2014-05-16 Deliverable Type and Security: Public Author: FI-WARE Consortium Contributors: FI-WARE Consortium Future Internet Core Platform 1.1 Executive Summary This document describes the Generic Enablers in the Apps and Services Ecosystem chapter, their basic functionality and their interaction. These Generic Enablers form the core business framework of the FI-WARE platform by supporting the business functionality for commercializing services. The functionality of the frame work is illustrated with several abstract use case diagrams, which show how the individual GE can be used to construct a domain-specific application environment and system architecture. Each GE Open Specification is first described on a generic level, describing the functional and non-functional properties and is supplemented by a number of specifications according to the interface protocols, API and data formats. D.3.1.3 FI-WARE GE Open Specification Page 2 Future Internet Core Platform 1.2 About This Document FI-WARE GE Open Specifications describe the open specifications linked to Generic Enablers GEs of the FI-WARE project (and their corresponding components) being developed in one particular chapter. GE Open Specifications contain relevant information for users of FI-WARE to consume related GE implementations and/or to build compliant products which can work as alternative implementations of GEs developed in FI-WARE.
    [Show full text]
  • Designing and Implementing Web API for RAI Software
    Siyuan Xue Designing and implementing Web API for RAI software Master’s Thesis in Information Technology November 15, 2019 University of Jyväskylä Faculty of Information Technology Kokkola University Consortium Chydenius Author: Siyuan Xue Contact information: siyuan.xue@outlook.fi Phonenumber: 045-356 0601 Title: Designing and implementing Web API for RAI software Työn nimi: Design and implement Web API for RAI software Project: Master’s Thesis in Information Technology Page count: 52+5 Abstract: The information silo becomes a significant problem with the software evo- lution from desktop applications to web-based applications. In this thesis, the re- search problem is derived from a customer’s requirement to integrate two different health information systems. The design and creation research approach is employed in this study, which involves aware, suggestion, development, evaluation and con- clusion. This paper focuses on building Web Service to break the information silo in healthcare systems, especially between the Electronic Health Record (EHR) and other health information systems. As the outcome of this study, a RESTful Web API is constructed to resolve the information silo issue. Meanwhile, the different alter- native solutions to construct each component of the Web API and open issues are summarized in the evaluation phase. Suomenkielinen tiivistelmä: NA Keywords: Web Service, Web API, REST, resident assessment instrument, maturity model, service description Avainsanat: NA Copyright c 2019 Siyuan Xue All rights reserved. Glossary
    [Show full text]
  • Web Services Testing with Soapui
    Web Services Testing with soapUI Build high quality service-oriented solutions by learning easy and efficient web services testing with this practical, hands-on guide Charitha Kankanamge BIRMINGHAM - MUMBAI Web Services Testing with soapUI Copyright © 2012 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the author, nor Packt Publishing, and its dealers and distributors will be held liable for any damages caused or alleged to be caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. First published: October 2012 Production Reference: 1191012 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-84951-566-5 www.packtpub.com Cover Image by Asher Wishkerman ([email protected]) Credits Author Project Coordinators Charitha Kankanamge Sai Gamare Shraddha Vora Reviewers Evanthika Amarasiri Proofreader Bindu Laxminarayan Maria Gould Ajay Pawar Indexer Acquisition Editor Monica Ajmera Mehta Kartikey Pandey Graphics Lead Technical Editors Valentina D'Silva Hithesh Uchil Aditi Gajjar Azharuddin Sheikh Production Coordinator Technical Editors Prachali Bhiwandkar Vrinda Amberkar Ankita Meshram Cover Work Prachali Bhiwandkar Prashant Salvi About the Author Charitha Kankanamge is Manager, Quality Assurance and Senior Technical Lead at WSO2 with more than 9 years of experience in Software Quality Assurance.
    [Show full text]