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 Input Ports to Nodes

Rules and Guidelines to Map Input Ports to Nodes

Review the following rules when you map input ports to nodes in the operation input hierarchy:
  • You can map an input port to one node in the hierarchy. You can map the same port to any number of keys in the hierarchy.
  • The input port and the node must have compatible data types.
  • You can map ports from one input group to multiple hierarchy levels in the operation input.
  • You must map input ports to the keys in the operation input. 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 input 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 input hierarchy.
  • You can map multiple string, bigint, or integer input ports to a key in the
    Operation Input
    area to create a composite key. When you click the
    Location
    field for a composite key, you can reorder the input ports or remove one of the ports.