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 Web Service Consumer Transformation Use Cases
  15. REST and SOAP Web Service Administration
  16. Datatype Compatibility

Web Services Guide

Web Services Guide

Pivoting Multiple-Occurring Ports

Pivoting Multiple-Occurring Ports

You can map multiple input ports to a multiple-occurring node in the SOAP message. The Developer tool pivots the input data into multiple nodes in the SOAP message.
To change the number of elements to pivot, choose
Override existing pivoting
in the
Map Options
dialog box.
If you remove one of the pivoted port instances from the
Ports
area, the Developer tool removes all instances from the
Operation
area.

Pivoting Example

An input group might have the following rows:
Num
Name
Location
emp_name1
emp_name2
emp_name3
101
HR
New York
Alice
Tom
Bob
102
Product
California
Carol
TIm
Dave
Each row contains a department number and three employees names.
Employee is a multiple-occurring node in the SOAP message hierarchy. You can map all instances of Employee from the input row to the SOAP message hierarchy. Select all occurrences of Employee. Click
Map
. The
Map Options
dialog box prompts you to choose a node from the list.
The Developer tool changes the Employee node to include the multiple name nodes in the SOAP message hierarchy:
Department num name location Employee (unbounded) emp_name1 emp_name2 emp_name3
The SOAP message returns the following hierarchy:
<department> <num>101</num> <name>HR</name> <location>New York</location> <employee> <emp_name>Alice</name> </employee> <employee> <emp_name>Tom</name> </employee> <employee> <emp_name>Bob</name> </employee> </department> <department> <num>102</num> <name>Product</name> <location>California</location> <employee> <emp_name>Carol</name> </employee> <employee> <emp_name>Tim</name> </employee> <employee> <emp_name>Dave</name> </employee> </department>

0 COMMENTS

We’d like to hear from you!