CornerDrugstore.com Web Service Integration Guide

Table of Contents
1 Document Information
     1.1 Overview
     1.2 Who Should Read This Guide?
     1.3 Document Assumptions
     1.4 Concepts Used in this Document
     1.5 Document Conventions
2 Introduction
     2.1 What are Web Services?
3 CornerDrugstore.com Health Content Web Services
     3.1 Health News Web Service Documentation
4 Appendices
     4.1 Appendix A: References and Resources
     4.2 Appendix B: Document Control

1 Document Information
This section details the audience, assumptions, contributions, and conventions used in this document.
1.1 Overview
This document is designed to help developers implement CornerDrugstore.com Web Services into their applications.

1.2 Who Should Read this Guide?
This document is useful for developers who want to create applications capable of interacting with CornerDrugstore's tools to provide more robust offerings on third-party Web sites.

1.3 Document Assumptions
This document assumes the reader has working knowledge of XML, SOAP or HTPP Get/Post, XSL/XSLT, and an understanding of how to integrate dtat into an application or Web site. Additionally, the reader should be familiar with the terms described in section 1.4.

1.4 Concepts Used in this Document
This section lists terms relevant to this product, and provides definitions for those terms. Some of these definitions come from http://www.webopedia.com/.
SOAP
Simple Object Access Protocol provides a way for applications to communicate with each other over the Internet, independent of platform. Unlike OMG's IIOP, SOAP piggybacks a DOM onto HTTP (port 80) in order to penetrate server firewalls, which are usually configured to accept port 80 and port 21 (FTP) requests. SOAP relies on XML to define the format of the information and then adds the necessary HTTP headers to send it.
SOAP was developed by Microsoft, DevelopMentor, and Userland Software and has been proposed to the Internet Engineering Task Force (IETF) as a standard.
XML
Short for Extensible Markup Language, a specification developed by the W3C. XML is a pared-down version of SGML, designed especially for Web documents. It allows designers to create their own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations.
API
Abbreviation of application program interface, a set of routines, protocols, and tools for building software applications. A good API makes it easier to develop a program by providing all the building blocks. A programmer puts the blocks together.
Most operating environments provide an API so that programmers can write applications consistent with the operating environment. Although APIs are designed for programmers, they are ultimately good for users because they guarantee that all programs using a common API will have similar interfaces. This makes it easier for users to learn new programs.
URI
Short for Uniform Resource Identifier, the generic term for all types of names and addresses that refers to objects on the World Wide Web. A URL is one kind of URI.
DTD
Short for document type definition. A DTD states what tags and attributes are used to describe content in an SGML document, where each tag is allowed, and which tags can appear within other tags. For example, in a DTD one could say that LIST tags can contain ITEM tags, but ITEM tags cannot contain LIST tags. In some editors, when authors are inputting information, they can place tags only where the DTD allows. This ensures that all the documentation is formatted the same way.
XSD
XSD (XML Schema Definition), a Recommendation of the World Wide Web Consortium (W3C), specifies how to formally describe the elements in an Extensible Markup Language (XML) document. This description can be used to verify that each item of content in a document adheres to the description of the element in which the content is to be placed.
WSDL
Short for Web Services Description Language, an XML-formatted language used to describe a Web service's capabilities as collections of communication endpoints capable of exchanging messages. WSDL is an integral part of UDDI, an XML-based worldwide business registry. WSDL is the language that UDDI uses. WSDL was developed jointly by Microsoft and IBM.
Java
Java is an object-oriented language similar to C++, but simplified to eliminate language features that cause common programming errors. Java source code files (files with a .java extension) are compiled into a format called bytecode (files with a .class extension), which can then be executed by a Java interpreter. Compiled Java code can run on most computers because Java interpreters and runtime environments, known as Java Virtual Machines (VMs), exist for most operating systems. Bytecode can also be converted directly into machine language instructions by a just-in-time compiler (JIT).
Perl
Short for Practical Extraction and Report Language, Perl is a programming language developed by Larry Wall, especially designed for processing text. Because of its strong text processing abilities, Perl has become one of the most popular languages for writing CGI scripts. Perl is an interpretive language, which makes it easy to build and test simple programs.
.NET
A Microsoft operating system platform that incorporates applications, a suite of tools and services and a change in the infrastructure of the company's Web strategy. There are four main principles of .NET from the perspective of the user:
  • It erases the boundaries between applications and the Internet. Instead of interacting with an application or a single Web site, .NET will connect the user to an array of computers and services that will exchange and combine objects and data.
  • Software will be rented as a hosted service over the Internet instead of purchased on a store shelf. Essentially, the Internet will be housing all your applications and data.
  • Users will have access to their information on the Internet from any device, anytime, anywhere.
  • There will be new ways to interact with application data, such as speech and handwriting recognition.
  • PHP
    PHP Hypertext Preprocessor is a server-side, HTML embedded scripting language used to create dynamic Web pages.
    In an HTML document, PHP script (similar syntax to that of Perl or C) is enclosed within special PHP tags. Because PHP is embedded within tags, the author can jump between HTML and PHP (similar to ASP and Cold Fusion) instead of having to rely on heavy amounts of code to output HTML. And, because PHP is executed on the server, the client cannot view the PHP code.
    PHP can perform any task any CGI program can do, but its strength lies in its compatibility with many types of databases. Also, PHP can talk across networks using IMAP, SNMP, NNTP, POP3, or HTTP. PHP was created sometime in 1994 by Rasmus Lerdorf. During mid 1997, PHP development entered the hands of other contributors. Two of them, Zeev Suraski and Andi Gutmans, rewrote the parser from scratch to create PHP version 3 (PHP3).
    ASP
    A specification for a dynamically created Web page with an .ASP extension that utilizes ActiveX scripting -- usually VB Script or Jscript code. When a browser requests an ASP page, the Web server generates a page with HTML code and sends it back to the browser. So ASP pages are similar to CGI scripts, but they enable Visual Basic programmers to work with familiar tools.
    XSL
    Short for Extensible Style Language, a specification for separating style from content when creating HTML or XML pages. The specifications work much like templates, allowing designers to apply single style documents to multiple pages. XSL is the second style specification to be offered by the World Wide Web Consortium (W3C). The first, called Cascading Style Sheets (CSS), is similar to XSL but does not include two major XSL innovations -- allowing developers to dictate the way Web pages are printed, and specifications allowing one to transfer XML documents across different applications. W3C released the first draft of XSL in August 1998, and promotes the specifications as helpful to the Web's speed, accessibility, and maintenance.
    XSLT
    Short for Extensible Style Language Transformation, the language used in XSL style sheets to transform XML documents into other XML documents.
    An XSL processor reads the XML document and follows the instructions in the XSL style sheet, and then it outputs a new XML document or XML-document fragment. This is extremely useful in e-commerce, where the same data need to be converted into different representations of XML. Not all companies use the exact same programs, applications and computer systems.

    1.4 Document Conventions
    Commands and keywords appear in boldface.
    New, important terms are italicized when accompanied by a definition or discussion of the term. Please note is used to denote additional helpful suggestions or important notices.

    2 Introduction
    2.1 What are Web Services?

    Web services are applications whose logic and functions are accessible using standard Internet protocols and data formats such as Extensible Markup Language (XML) over Hypertext Transfer Protocol (HTTP), and SOAP (Simple Object Access Protocol). Like component-based development, Web services represent black-box functionality that can be reused without worrying about how the service is implemented.

    A Web service interface is defined strictly in terms of the messages that the service accepts and generates. Applications using a Web Service can be implemented on any platform in any programming language, as long as they can create and consume messages defined for the service interface. A Web service can also aggregate other services to provide a higher-level set of features.

    Why should developers should be intereseted in Web Services?

    Interoperability - Any Web Service can interact with any other Web Service and can be written in any language.

    Ubiquity - Web Services communicate using HTTP and XML. Any connected device that supports these technologies can both host and access Web Services.

    Low Barrier to Entry - The concepts behind Web Services are easy to understand, and developers can quickly create and deploy them using many tool-kits availble on the web.

    Industry Support - Major content providers and vendcors are supporting the Web Services movement.

    Most Web services make use of either SOAP or XML over HTTP (also known as REST) to make requests and deliver responses via the Internet.

    XML over HTTP (or XML/HTTP) uses URLs with specific name/value pairs to invoke methods and processes within CornerDrugstore's Web Services framework. The URL is the primary method used for message passing. Once the URL is processed, a well-formatted XML document is returned as a response. Because XML/HTTP is based on such a widely accepted methodology, most developers should have no problem creating applications capable of quickly communicating with the Web services that expose this interface.

    SOAP (Simple Object Access Protocol), a more complex method of sharing messages between client and server, was developed to deal with the limitations of XML/HTTP. SOAP is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. It uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics.

    CornerDrugstore Web Services offers developers the choice of XML/HTTP or SOAP to access information in our catalog and databases. Which method should you use? Mostly, it depends on what you are the most comfortable with. There is significant industry debate over which Web Services method is the "best"; at CornerDrugstore, we decided to take a neutral approach and offer access via both methods.



    3 CornerDrugstore.com Health Content Web Services
    3.1 Health News Web Service Documentation
    Summary description for Global.

    CornerDrugStore.HealthNews.HealthNews.GetNewsFeed(System.String,System.Int32)
    Gets the entire news feed

    Paramaters:
  • sSessionID -
  • intNumberArticles -

  • Return:
    Xml Document containing a list of news items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeed xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
        </GetNewsFeed>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeedResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetNewsFeedResult>xml</GetNewsFeedResult>
        </GetNewsFeedResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetNewsFeed?sSessionID=string&intNumberArticles=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetNewsFeedFeatured(System.String,System.Int32)
    Gets the featured news items

    Paramaters:
  • sSessionID -
  • intNumberArticles -

  • Return:
    Xml Document containing a list of news items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeedFeatured xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
        </GetNewsFeedFeatured>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeedFeaturedResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetNewsFeedFeaturedResult>xml</GetNewsFeedFeaturedResult>
        </GetNewsFeedFeaturedResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetNewsFeedFeatured?sSessionID=string&intNumberArticles=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetNewsFeedIgnoreArticles(System.String,System.Int32,System.String)
    Gets the featured news items removing a specified list of articles

    Paramaters:
  • sSessionID -
  • intNumberArticles -
  • sIgnoreItems - comma seperated list of items to ignore

  • Return:
    Xml Document containing a list of news items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeedIgnoreArticles xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
          <sIgnoreItems>string</sIgnoreItems>
        </GetNewsFeedIgnoreArticles>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsFeedIgnoreArticlesResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetNewsFeedIgnoreArticlesResult>xml</GetNewsFeedIgnoreArticlesResult>
        </GetNewsFeedIgnoreArticlesResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetNewsFeedIgnoreArticles?sSessionID=string&intNumberArticles=string&sIgnoreItems=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string&sIgnoreItems=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetHealthHighlights(System.String,System.Int32)
    Gets a list of Health Highlight items

    Paramaters:
  • sSessionID -
  • intNumberArticles -

  • Return:
    Xml Document containing a list of Health Highlights items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetHealthHighlights xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
        </GetHealthHighlights>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetHealthHighlightsResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetHealthHighlightsResult>xml</GetHealthHighlightsResult>
        </GetHealthHighlightsResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetHealthHighlights?sSessionID=string&intNumberArticles=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetFYI(System.String,System.Int32)
    Gets a list of FYI items

    Paramaters:
  • sSessionID -
  • intNumberArticles -

  • Return:
    Xml Document containing a list of the FYI items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetFYI xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
        </GetFYI>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetFYIResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetFYIResult>xml</GetFYIResult>
        </GetFYIResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetFYI?sSessionID=string&intNumberArticles=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetFDA(System.String,System.Int32)
    Gets a list of FDA items

    Paramaters:
  • sSessionID -
  • intNumberArticles -

  • Return:
    Xml Document containing a list of the FDA items

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetFDA xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intNumberArticles>int</intNumberArticles>
        </GetFDA>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetFDAResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetFDAResult>xml</GetFDAResult>
        </GetFDAResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetFDA?sSessionID=string&intNumberArticles=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intNumberArticles=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetNewsArticle(System.String,System.String)
    Gets all the information for a particular news item

    Paramaters:
  • sSessionID -
  • sArticleID -

  • Return:
    Xml Node of news information

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsArticle xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <sArticleID>string</sArticleID>
        </GetNewsArticle>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetNewsArticleResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetNewsArticleResult>xml</GetNewsArticleResult>
        </GetNewsArticleResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetNewsArticle?sSessionID=string&sArticleID=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&sArticleID=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetKeywordSearch(System.String,System.String)
    Searches all news items for a search criteria

    Paramaters:
  • sSessionID -
  • sSearchCriteria -

  • Return:
    XmlDocment containing the found articles

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetKeywordSearch xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <sSearchCriteria>string</sSearchCriteria>
        </GetKeywordSearch>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetKeywordSearchResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetKeywordSearchResult>xml</GetKeywordSearchResult>
        </GetKeywordSearchResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetKeywordSearch?sSessionID=string&sSearchCriteria=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&sSearchCriteria=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetTopics(System.String)
    Returns a list of the Health Topics

    Paramaters:
  • sSessionID -

  • Return:
    XmlDocment containing the list of topics

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetTopics xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
        </GetTopics>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetTopicsResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetTopicsResult>xml</GetTopicsResult>
        </GetTopicsResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetTopics?sSessionID=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetCategoryTopics(System.String,System.Int32)
    Returns a list of the Health Topics for a particular category

    Paramaters:
  • sSessionID -
  • intCategoryID -

  • Return:
    XmlDocment containing the list of topics

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetCategoryTopics xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <intCategoryID>int</intCategoryID>
        </GetCategoryTopics>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetCategoryTopicsResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetCategoryTopicsResult>xml</GetCategoryTopicsResult>
        </GetCategoryTopicsResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetCategoryTopics?sSessionID=string&intCategoryID=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&intCategoryID=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetCategories(System.String)
    Returns a list of the Health Categories

    Paramaters:
  • sSessionID -

  • Return:
    XmlDocment containing the list of categories

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetCategories xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
        </GetCategories>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetCategoriesResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetCategoriesResult>xml</GetCategoriesResult>
        </GetCategoriesResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetCategories?sSessionID=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string
    

    HTTP Post Response

    xml
    
    CornerDrugStore.HealthNews.HealthNews.GetTopicSearch(System.String,System.String)
    Searches all news items for a search topic

    Paramaters:
  • sSessionID -
  • sTopic -

  • Return:
    XmlDocment containing the found articles

    Example Calls for this Web Service:
    SOAP

    SOAP Request

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetTopicSearch xmlns="http://webservices.cornerdrugstore.com">
          <sSessionID>string</sSessionID>
          <sTopic>string</sTopic>
        </GetTopicSearch>
      </soap:Body>
    </soap:Envelope>
    

    SOAP Response

    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetTopicSearchResponse xmlns="http://webservices.cornerdrugstore.com">
          <GetTopicSearchResult>xml</GetTopicSearchResult>
        </GetTopicSearchResponse>
      </soap:Body>
    </soap:Envelope>
    
    HTTP GET

    HTTP GET Request

    	/HealthNews/HealthNews.asmx/GetTopicSearch?sSessionID=string&sTopic=string
    

    HTTP Get Response

    xml
    
    HTTP POST

    HTTP Post Request

    sSessionID=string&sTopic=string
    

    HTTP Post Response

    xml
    
    4 Appendices
    Additional Information about CornerDrugstore.com Web Services.
    4.1 Appendix A: References and Resources
    This section contains additional resources for information on Web Services, XML, and SOAP.

    Web Services Resources
  • WebServices.org
  • Web Services Architect
  • Web Services Journal
  • XMethods
  • IBM's DeveloperWorks
  • Oracle Technology Network Web Services Center
  • CapeScience


  • XML Resources
  • O'Reily's XML.com
  • XML.org
  • XMLFiles.com
  • RESTwiki


  • SOAP Resources
  • Developmentor
  • SoapWare.org
  • SoapLite.com
  • W3Schools tutorial

  • 4.2 Appendix B: Document Control
    This section shows the version, date, author, and change description for this document.

    Version: 2.0
    Date: 5/03/2007
    Description: Removed Health Content Webservices and Prescription Webservices

    Version: 1.5
    Date: 9/14/06
    Description: Removed Authorization Webservice and SubmitRefill_1_0

    Version: 1.0
    Date: 3/24/03
    Description: Initial Document; Authorization and Health Content Webservices documentation.