In this section: |
A Transform component represents one configured transformation. It contains information on the dependencies and the rules of a particular transform. The iWay Transformation Engine processes input data and builds the output data according to these rules. The serialized form of a Transform component is called a Transform template.
A Transform template contains a blueprint of a transformation. It provides an XML representation of a Transform component, referencing its various parameters and rules. It is typically distinguished by a .gxp extension file format.
In this section: |
The main modules within a Transform component are Dictionary and Mapping rules.
A data dictionary is an iWay representation of e-business metadata that describes the layout and grammar of a transaction or a document. The layout and grammar are stored in one or more files that contain dictionary components, such as headers or structures.
Dictionaries are required when the input or output data is not structural, for example, in EDI or SWIFT formats. Most dictionaries are converted to XML from the specifications of particular message types, which are managed and published by organizations. iWay Transformer supports the following dictionary component types:
The following table lists the component types that are supported for each data format.
Format |
Header |
Structure |
Message |
Segment |
Datatype |
Field |
---|---|---|---|---|---|---|
EDIFACT |
Yes |
Yes |
No |
No |
No |
No |
EDI HIPAA |
Yes |
Yes |
No |
No |
No |
No |
EDI X12 |
Yes |
Yes |
No |
No |
No |
No |
Fixed Width |
No |
Yes |
No |
No |
No |
No |
IDOC |
No |
Yes |
No |
No |
No |
No |
SWIFT |
No |
Yes |
No |
No |
No |
No |
HL7 |
No |
No |
Yes |
Yes |
Yes |
Yes |
CSV |
No |
Yes |
No |
No |
No |
No |
XML |
No |
Yes |
No |
No |
No |
No |
You can edit the majority of non-XML Transformer dictionaries using the Dictionary Builder.
In iWay Transformer, dictionaries are typically used as a starting point for designing your mappings.
|
iWay Software |