Table of Contents

Search

  1. Preface
  2. Transformations
  3. Source transformation
  4. Target transformation
  5. Access Policy transformation
  6. B2B transformation
  7. Aggregator transformation
  8. Cleanse transformation
  9. Data Masking transformation
  10. Data Services transformation
  11. Deduplicate transformation
  12. Expression transformation
  13. Filter transformation
  14. Hierarchy Builder transformation
  15. Hierarchy Parser transformation
  16. Hierarchy Processor transformation
  17. Input transformation
  18. Java transformation
  19. Java transformation API reference
  20. Joiner transformation
  21. Labeler transformation
  22. Lookup transformation
  23. Machine Learning transformation
  24. Mapplet transformation
  25. Normalizer transformation
  26. Output transformation
  27. Parse transformation
  28. Python transformation
  29. Rank transformation
  30. Router transformation
  31. Rule Specification transformation
  32. Sequence Generator transformation
  33. Sorter transformation
  34. SQL transformation
  35. Structure Parser transformation
  36. Transaction Control transformation
  37. Union transformation
  38. Velocity transformation
  39. Verifier transformation
  40. Web Services transformation

Transformations

Transformations

Field mapping for web service sources

Field mapping for web service sources

You can map response fields into a relational structure of output groups and fields for output.
The response shown in the Field Mapping tab shows the hierarchical structure of the data that comes from the source.
When you select fields in the Response area, the fields appear in the Output Fields area in a relational structure with generated primary keys and foreign keys. For example, in the Response Fields area you select First_Name and Last_Name, and then you select Email_Address, which is located under a different parent in the hierarchy. In the Output Fields area, the structure is relational with assigned primary and foreign keys, as shown in the following image:
The Output Fields area indicates the primary and foreign keys.
Consider cardinality when you map response fields to the relational structure. Cardinality imposes constraints on the number of times a field or group can occur at a specific point in the XML structure. A cardinality of 0-many means the field or group can have zero to many occurrences. A cardinality of 1-1 means a field or group is required and can only occur once.
If you map a field with 0-1 or 1-1 cardinality, the first parent node that has 0 to more than 1 cardinality is also mapped. If a parent group with 0 to more than 1 cardinality does not exist, the system creates a group. For example, if you map Email_Comment, which has cardinality of 0-1, the Email_Address_Data group, which has cardinality of 0-many, is automatically mapped.

Packed fields

You can pack fields to reduce the number of output groups for a request message. You can mark fields to be packed when you configure field mapping. When you run the
mapping
task, the task packs the element and its children into a single XML string.
Fields can come from the source already marked for packing. The Pack icon displays next to elements marked to be packed. To pack a field, click the Pack icon, as shown in the following image:
You cannot pack fields that are children of packed fields.
In the following image, you can see that the Phone_Data element is packed:
You can use XPath expressions to mark multiple fields for packing or unpacking. In the Response Fields area, click the arrow and select Mark Packed Structures, as shown in the following image:
In the following image, all fields that have ID as a child are marked to pack:

0 COMMENTS

We’d like to hear from you!