Developer Transformation Guide > Generating Web Service SOAP Messages > Map Ports
  

Map Ports

After you create input ports, map each input port to the SOAP message hierarchy. The location of the port appears next to the node in the Operation area.
You can map ports to the following types of nodes:
Atomic node
A simple element or an attribute that has no children and is not divisible.
Multiple-occurring atomic node
A simple element or an attribute that occurs multiple times at the same location in the hierarchy.
Complex node
An element that contains other elements.
If the parent node does not have a location, the parent node receives the input group name as the location. When the parent node has a location, each node in the hierarchy level must have an output location from the same location.
You can map an input group name to a parent node in a hierarchy level. The Developer tool updates the location field for the parent node in the hierarchy. The Developer tool does not update the child nodes that belong to the group in the hierarchy. When you map input ports to the child nodes, each input port location must be the same location as the location parent node.
After you map an input group to a hierarchy level, you can change it later. You can click Clear or you can delete the lines between the Ports and the Operation area. To delete the lines, drag the pointer of the lines to select them. Click Delete.

Map a Port

When you map a port to a node in the SOAP message, the Developer tool provides different results based on the type of node to which you map the port.
The following table describes the results when you map a single port to different target nodes in the Operation area:
Target Node
Results
Atomic node
When you map a single port to a node and the parent node does not have a location, the node receives the location of the port. The parent node location receives the location of the input group for the single port. When you map a single port to a node and the parent node already has a location, you can change the location for the parent node and clear the location for the other child nodes in the same level. The hierarchy level location changes to the group name of the port.
Multiple-occurring atomic node or the primary key of the multiple-occurring atomic node
When you map a single port to the multiple-occurring atomic node, the Developer tool sets the location for the atomic node to the group of the selected port.
Complex node
When you map a single port to a complex node, the Developer tool sets the location of the complex node to the location of the group that contains the port. The Developer tool prompts you for the single occurring atomic node to assign the port to.
If all single-occurring atomic nodes have a location, you cannot map the complex node.

Map a Group

When you map an input group to a node in the SOAP message, the Developer tool provides different results based on the type of node that you map the port to.
The following table describes the results when you map a group to a node in the Operation area:
Target Node
Results
Atomic node
You cannot map a group to an atomic node.
Multiple-occurring atomic node
You are prompted to choose a port in the input group to update the location for the node and primary key.
Multiple-occurring complex node
The Developer tool sets the location for the complex node to the location of the group.

Map Multiple Ports

When you map multiple ports to a node in the SOAP message, the Developer tool provides different results based on the type of node you map the ports to. You can map multiple ports at the same time if you map them from the same group.
The following table describes the results for the node when you map multiple ports to nodes:
Target Node
Results
Single atomic node
When you map multiple ports to a single node, you update the location for more than one single atomic node in the Operation area. If the hierarchy does not have enough nodes in the level to update, the Developer tool maps ports just for the available nodes.
Multiple-occurring atomic node
When you map multiple ports to multiple-occurring atomic node, you pivot the ports into multiple occurrences of the node. The Developer tool creates instances of the node based on how many ports you map. A message appears that describes the number of ports that you projected.
Multiple-occurring complex node
When you map multiple ports to a complex node, you must select which single-occurring nodes atomic nodes to update. You pivot the ports into multiple occurrences of the node. The Developer tool creates instances of the node based on how many ports you map.