Skip to main content

Domino Web Service Application Development for the IBM eServer iSeries Server

An IBM Redbooks publication

Note: This is publication is now archived. For reference only.


Published on 21 November 2002

  1. .PDF (3.8 MB)

Share this page:   

ISBN-10: 0738427314
ISBN-13: 9780738427317
IBM Form #: SG24-6862-00

Authors: Yessong Johng and Kim Greene Clayton McDaniel Vinit Saraswat Jing Han Zhao

    menu icon


    "Contextual collaboration" is a new term whirling in the industry today. This phenomenal new type of business asset can be realized by two major mechanisms: the components managing mechanism and the services delivery mechanism. The component managing mechanism deals with calendar, workflow, messaging, e-mail, and so on, while the services delivery mechanism deals with receiving and responding to a request. In terms of IBM product offerings, we have Domino for the component managing mechanism and WebSphere for the services delivery mechanism.

    We need standards to connect the applications from different business entities: your customers, your suppliers, your business partners, and you. These business entities may run their business applications on different platforms, different application languages, different networks, and so on. To connect these un-identical entities together, we need standards. For that, we have Web Service standards such as SOAP, WSDL, XML, and UDDI.

    This IBM Redbooks publication provides real application scenarios which illustrate how to transform existing Domino applications into either a Web Service provider or a Web Service requester. This is achieved and served through the integration of Domino and WebSphere Application Server.

    Table of Contents

    Chapter 1. Introduction

    Chapter 2. Writing my first Web Service application

    Chapter 3. Transforming a Domino application to a Web Service application

    Chapter 4. Consuming Web Services from a Domino application

    Appendix A. Creating your own Web Service application

    Appendix B. Using UDDI for both ends - publishing and requesting


    Others who read this also read