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

Request-Response Mappings

Request-Response Mappings

A request-response mapping uses a web service source and a web service target.
If you create a request-response mapping, use source and target definitions created in the same method. If you import the source definition from a WSDL, import the target definition from the same operation in the WSDL. If you create the source definition by defining the columns or by using relational or flat file sources and targets, create the target definition using the same method.
To ensure that the web service source and target definitions are created using the same method, create the source and target definitions in one process.
If you do not import source and target definitions from the same operation in the WSDL or if you do not create them using the same method, you can get unexpected results.
You can use an SQL transformation to update a database or to retrieve multiple database rows in a request-response mapping. The SQL transformation can return multiple database rows to the target. When database errors occur in processing, the SQL transformation receives the errors from the database and sends the error text to the target.
For an example of a web service that uses an SQL transformation to get multiple rows, see the real-time web services examples shipped with PowerCenter. By default, the real-time web services sample programs are installed in the following directory:
/<PowerCenterInstallDir>/server/samples/WebServices/samples/RealTimeWebServices

0 COMMENTS

We’d like to hear from you!