FINS IAA-XML Data Transformation Engine
The Siebel Data Mapper provides you with a declarative interface to specify maps for both inbound and outbound data transformation. The maps you set up using the Siebel Data Mapper call the FINS IAA-XML Data Transformation Engine to complete the data transformation. The FINS IAA-XML Data Transformation Engine both transforms Siebel internal object hierarchy to external integration object hierarchy, defined in IAA-XML DTD, and external integration object hierarchy to Siebel internal integration object hierarchy. The FINS IAA-XML Data Transformation Engine walks through and transform elements in heterogeneous commands and with proper input integration objects and maps it combines results as a single property set. The FINS IAA-XML DTE also removes the empty-valued integration component fields when required. Using the Siebel Data Mapper one can often reduce or even eliminate the number of scripts you need to write.
Like any other Siebel business service, FINS IAA-XML Data Transformation Engine has specific methods as described in the following table.
| Name | Display Name | Description |
|---|---|---|
ToExternal |
Transform To External Hierarchy |
Transforms Siebel internal integration object hierarchy into the IAA-XML external hierarchy. |
ToInternal |
Transform To Siebel Hierarchy |
Transform IAA-XML external hierarchy into the Siebel internal integration object hierarchy. |
FINS IAA-XML Data Transformation Engine business service uses combination of method, and method arguments to achieve different tasks. The following table lists all the method arguments available to use with FINS IAA-XML Data Transformation Engine business service.
| Argument | Default Value | Description |
|---|---|---|
XMLHierarchy |
N/A |
Property set in internal or external integration object hierarchy. |
<MapArgs> |
N/A |
See Business Processes and Rules: Siebel Enterprise Application Integration. |
Each method defined for the FINS IAA-XML Data Transformation Engine business service takes some input arguments and produces some output arguments as listed in the following two tables.
| Name | Display Name | Data Type | Type | Optional |
|---|---|---|---|---|
XMLHierrarchy |
XML Property Set |
Hierarchy |
Input/Output |
No |
<MapArgs> |
- |
String |
Input |
Yes |
| Name | Display Name | Data Type | Type | Optional |
|---|---|---|---|---|
XMLHierrarchy |
XML Property Set |
Hierarchy |
Input/Output |
No |
<MapArgs> |
- |
String |
Input |
Yes |