Table of Contents

Search

  1. Preface
  2. Web Service Concepts
  3. Understanding the Web Services Provider
  4. Using the Web Services Hub Console
  5. Batch Web Service Operations
  6. Writing Client Applications
  7. Working with Web Service Sources and Targets
  8. Editing Web Service Sources and Targets
  9. Working with Web Service Mappings
  10. Working with Web Service Workflows
  11. Appendix A: Web Service Sample Client Applications
  12. Appendix B: Configure the Web Browser

Web Services Provider Guide

Web Services Provider Guide

Web Service Concepts Overview

Web Service Concepts Overview

Web services are business functions that operate over the Web. They describe a collection of operations that are network accessible through standardized XML messaging. The PowerCenter Web Services Provider lets you integrate the PowerCenter metadata and data integration functionalities and expose them as web services. You can write applications that can communicate with Integration Services in any language or platform. You can embed these applications easily in existing components and products.
Web services are based on open standards, such as XML, SOAP, and WSDL, which offer greater interoperability than traditional proprietary applications.
Examples of web services include business services, such as stock quotes, airline schedules, and credit checks.
The components that enable web services include:
  • Simple Object Access Protocol (SOAP).
    SOAP is the communications protocol for web services. It is the specification that defines the XML format for web service messages.
  • Web Service Definition Language (WSDL).
    WSDL is an XML document that describes web service operations.
  • Registry.
    Directory of published web services. Some web service providers publish services in Universal Description, Discovery, and Integration (UDDI). Registering a web service in the UDDI is optional.
    The PowerCenter Web Services Provider does not use the UDDI registry.
To build a web service client for the PowerCenter Web Services Provider, you select the web service you want to interface with and retrieve the WSDL for the selected web service. Use a web service tool kit such as Axis to generate the client proxies. The client proxies contain all of the function calls required to interact with a web service.
You can determine what functions a web service offers, the data the web service requires, and the location of the service by examining the WSDL. The WSDL describes the web service interfaces and the operations available for the service. Use the information in the WSDL to build a client application to use the services.
The following figure shows the building blocks of a web service:
Client components include the client application, client proxies, and web services toolkit including the WSDL. The client application communicates with the web service using XML messages. The client also interacts with the UDDI registry, which finds the service. The client can find the web service in the UDDI registry and get the WSDL from there. The web service can publish services to the UDDI registry.

0 COMMENTS

We’d like to hear from you!