1 / 9

Publication Date: May 2004 pp. 552-561

Using Web Service Technologies to create an Information Broker: An Experience by Mark Turner, Fujun Zhu, Ioannis Kotsiopoulos, Michelle Russell, David Budgen, Keith Bennett, Pearl Brereton, John Keane, Paul Layzell, Michael Rigby. Publication Date: May 2004 pp. 552-561.

treva
Download Presentation

Publication Date: May 2004 pp. 552-561

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Using Web Service Technologies to create an Information Broker: An ExperiencebyMark Turner, Fujun Zhu, Ioannis Kotsiopoulos, Michelle Russell, David Budgen, Keith Bennett, Pearl Brereton, John Keane, Paul Layzell, Michael Rigby Publication Date: May 2004 pp. 552-561 Poster by Dennis Uspenskiy

  2. Summary • Have web service technologies reached sufficient maturity to enable the creation and (rapid) evolution of complex systems? • Can existing protocols be used to build an information broker for seamless access and integration of complex data? • Use sub-set of existing web services protocols and technologies to build a prototype broker using the healthcare domain.

  3. Web Service Technologies Overview • Web Service – Software components that use standard Internet technologies to interact with one another dynamically • Made up of loosely coupled components • Independent of platform and language • Agreed protocols • Simple Web Services Stack • Messaging: Simple Object Access Protocol (SOAP) provides a standard message format • Description: Web Services Description Language (WSDL) describes how to access Web services • Discovery: Universal Description, Discovery and Integration (UDDI) provides a registry which is used to discover available services

  4. Current State of Web Services • Possible to transfer large quantities of information with use of well-established protocols • Adequate for simple service-based development • No flexibility for more complex web service • No support for non-functional factors • Provide simple atomic services • Lack of integration for complex data forms

  5. Healthcare Information Broker • More than a federated database • Function of a broker: on-demand integration of information that was created, modified and stored independently • IBHIS seeks to create a service that will support reliable integration of information that is held in heterogeneous forms and autonomously managed by distinct agencies in the healthcare domain • Dynamically locate services based on the data they can provide, not upon basis of their functionality

  6. First Prototype • Contains a subset of the service-oriented elements; fusion of available web service protocols with concepts of Federated DB System • Successful use of various heterogeneous DBMS platforms (MySQL, IBM DB2 and Oracle) • RPC with SOAP encoding for messaging worked, but document messaging will be required in the future • Own implementation of a registry instead of using UDDI (maps to DAS interfaces); will need to support semantic searches, not just by keyword • WSDL provided adequate description, but lacks support for non-functional descriptions • A number of alternative temporary solutions were necessary; difficulties with data format sent between services • Architecture is tightly coupled with FDBS

  7. Questions • List components of a simple Web Services stack. • Name one benefit of an Information Broker such as IBHIS. • Why can’t a Federated Database System (FDBS) be used in place of Information Broker?

More Related