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

WSDL Attachments

WSDL Attachments

Based on the source and target definitions, you can receive and send an attachment as part of the SOAP request. The attachment must be a text file such as an XML document. You cannot attach binary documents such as JPEG, GIF, or PDF files. For example, you can extract an XML document from an Oracle database and pass it to a web service client as an attachment to a response message.
To use a binary file as a source, convert the file into hexbinary or base64binary before you pass it to the web service source. A hexbinary or base64binary files is treated as a text file. Similarly, you can convert the text file response generated by the web service target to a binary file.
The following table describes the attachment group ports in a web service definition:
Port Name
Description
FK_Att_
Name
Generated foreign key pointing to PK_Message in the root group.
Att_Data_
Name
Contains the attachment. You can view the MIME type for the attachment on the Attributes tab.
Att_Index_
Name
Unique identifier for each attachment in the message.
Att_Type_
Name
Type of attachment.

0 COMMENTS

We’d like to hear from you!