1 / 21

Concert Conference November 2002

Concert Conference November 2002. Joe Tetzlaff COO Ovid Technologies. Technologies and Standards in the Pursuit of the Universal Search Engine. The World Wide Web and the Universal Search Engine The Information Solution Provider Point of View The Technologies of Integration

dillian
Download Presentation

Concert Conference November 2002

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. Concert ConferenceNovember 2002 Joe Tetzlaff COO Ovid Technologies

  2. Technologies and Standards in the Pursuit of the Universal Search Engine • The World Wide Web and the Universal Search Engine • The Information Solution Provider Point of View • The Technologies of Integration • APIs and Portlets • Z39.50 • Open Archives Initiative • WebServices, SOAP, JSR 168, WSRP • Some questions and conclusion

  3. Title Bar Us

  4. A Vendor Look at Integration • Medical Market • Hospital Information Systems (HIS) • Dozens of brands • Academic Market • Home-grown Portals • Amalgamation of standards or near-standards • Corporate Market • Portals – 100+ major brands

  5. Portals as Universal Search Engines • A generation beyond the “Intranet” • Direct access to applications • Provide personalized view • Site-specific taxonomies • Search capability

  6. Portal Search Engines • Integral part of the portal solution • Index many content types • Word, PDF, PPT, XLS, etc. • Are relational databases • Include a web crawler and are designed to crawl web sites and automatically index data

  7. Information Vendor Search Engines • Boolean & typically proprietary • Are not web sites (aren’t easily “crawled”) • Documents are output in html • Html available in response to a search • Re-indexing the data by other means is • Expensive • Leads to reduced functionality

  8. Integrating Proprietary Systems into the Portal(the EAI Challenge) • EAI - Enterprise Application Integration • Uses APIs (Application Programming Interface) • An API requires programming on both sides, with the “rules” set by the system which writes the API Application Application API Interface API

  9. The EAI Challenge Summary API – Application Programming Interface • Set of rules for systems to communicate • Proprietary to the API • Language/platform dependent • Developers require vast array of skills • Mature technologies (middleware, etc.) • Expensive to maintain

  10. The Portal API: Widget, Gadget, Gear, Bridge, etc. • Portlets are “mini” APIs specified by the portal. • They provide components of a full system’s functionality Application (Ovid) Portal Gadget API Gadget

  11. The Portal API: Widget, Gadget, Gear, Bridge, etc. • Each portlet is proprietary to the Portal Portal Gadget API Application (Ovid) Gadget Widget Portal Widget API

  12. Portlet Summary • Portlets are APIs • Widgets, gadgets, gears, etc. • Connect through a variety of mechanisms • Basic functionality “the 20% of the functionality used 80% of the time” • Easier than full APIs, but still potentially very expensive if many have to be supported

  13. Integration Standards: Z39.50 • Standard since 1988 • Specifically designed for federated searching of distributed systems • Already supported by many proprietary vendors • Has performance and scaling issues ZServer A ZClient ZServer B ZServer C

  14. Integration Standards: Z39.50 • Interconnects, but doesn’t interoperate well • Therefore expensive to maintain Smith-j Enter Author: (ex. John Smith) Smith adj jr John-R-Smith

  15. Integration Standards: Open Archives Initiative (OAI) • Open Archives Metadata Harvesting Protocol • Avoids performance/scalability issues because data is batch harvested and loaded into a central database (such as a portal) Portal Ovid

  16. Integration Standards: Open Archives Initiative (OAI) • Still incur costly data loading (but avoid interoperability problems) • No infrastructure within protocol to permit limited harvesting by specific partners – would have to be built

  17. Integration Technologies: Web Services • Web Services: Web Services for Remote Portals (WSRP) Web Services Directory Portal Dow Jones Ovid UPS

  18. Integration Standards Within Web Services • WSRP • SOAP-based portlet communications standard • Avoids multiple portlet development • Limited functionality • Interoperability problems apply • Doesn’t address security, authentication, scalability, billing, etc. • Only a draft standard • Competing with JSR 168 (Java Specification Request) • Standard Java-based API

  19. Integration Standards within Web Services: SOAP • SOAP (Simple Object Application Protocol) • Uses standard communication (http) • Is human-readable (xml documents) • Relatively inexpensive • Limited functionality • Interoperability problems apply

  20. Integration Technologies: An Information Vendor API via a SOAP Object • SOAP could make an Information “API” practical Portal Ovid Soap Object

  21. Universal Searching: Whose Needs are met? • There is no obvious, ideal integration method or Universal Search capability • Both integrated and full solutions have their place, often for different audiences within the same institution. • Vendors and Institutions working together are ideally positioned to provide the best solution for each user

More Related