Web Services Guide

10.2.1
- 10.5.7
- 10.5.6
- 10.4.0
- 10.2.2 Service Pack 1
- 10.2.2

Back Next

Rules and Guidelines to Map Input Ports to Elements

Review the following rules when you map input ports to elements in the method input hierarchy:

You can map an input port to one element in the hierarchy. You can map the same port to any number of keys in the hierarchy.

The input port and the element must have compatible datatypes.

You can map ports from one input group to multiple hierarchy levels in the method input.

You must map input ports to the keys in the method input. Any port that you map to a key must be of string, integer, or bigint datatype. Map data to the keys in all levels in the method input above the hierarchy level that you are including in the request 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 method input hierarchy.

You must map the RequestInput root element to the child element of Rest_Consumer_input group for method input definition.

You can map multiple string, bigint, or integer input ports to a key in the Method 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.

If the web service produces a JSON document, ensure that xmlRoot is the first node in the response hierarchy. If xmlRoot is not the first node for a web service with JSON response, null values may appear.

Rename Saved Search

Table of Contents

Web Services Guide

Web Services Guide

Rules and Guidelines to Map Input Ports to Elements

Rules and Guidelines to Map Input Ports to Elements