Table of Contents

Search

  1. Preface
  2. Web Services
  3. SOAP Web Services
  4. WSDL Data Object
  5. Schema Object
  6. How to Create a SOAP Web Service
  7. Operation Mappings
  8. Parsing Web Service SOAP Messages
  9. Generating Web Service SOAP Messages
  10. Web Service Consumer Transformation
  11. REST Web Services
  12. How to Create a REST Web Service
  13. REST Web Service Consumer Transformation
  14. REST and SOAP Web Service Administration
  15. Datatype Compatibility

Web Services Guide

Web Services Guide

Rules and Guidelines to Map Ports to the Operation Output

Rules and Guidelines to Map Ports to the Operation Output

When you configure the Output transformation, you map ports to the operation output hierarchy.
Consider the following rules and guidelines when you map input ports to the operation output hierarchy:
  • The input port and the node must have compatible datatypes.
  • You can map an input port to one node in the hierarchy.
  • You can map ports from one input group to nodes in the same hierarchy level in the operation output.
  • You can map different ports from one input group to nodes in different hierarchy levels in the operation output.
  • Map input ports to the keys in the operation output. Any port that you map to a key must be a string, integer, or bigint datatype. Map data to the keys in all levels in the operation output above the hierarchy level that you are including in the SOAP message. Include the foreign keys for all levels above and including the level you are mapping.
    You do not have to map input ports to keys if you are mapping only the lowest level of the operation output hierarchy.
  • You can map multiple input ports of different datatypes to a key. When you click the
    Location
    field for a key, you can reorder the input ports or remove one of the ports.