TerminalNames
The TerminalNames element includes the terminal names that are to be used.
This value is required if the WireOutput element is specified.
For X12 data, the TerminalNames element contains the following elements. All are required
| X12_TransactionTerminal | Used for valid transaction output. |
| X12_RejectTerminal | Used for rejected transactions, groups, and interchanges. |
| X12_RejectLogTerminal | Used for error logs associated with the rejected transactions, groups, and interchanges. |
| FA_InboundTerminal | Used for received, or inbound, 997 and 999 acknowledgements. |
| FA_OutboundTerminal | Used for generated, or outbound, 997acknowledgements. |
| TA1_InboundTerminal | Used for received, or inbound, TA1 acknowledgements. |
| TA1_outboundTerminal | Used for generated, or outbound, TA1 acknowledgements. |
For EDIFACT data, the TerminalNames element contains the following elements. All are required.
| EDIFACT_TransactionTerminal | Used for valid transaction output. |
| EDIFACT_RejectTerminal | Used for rejected messages, groups, and interchanges. |
| EDIFACT_RejectLogTerminal | Used for error logs associated with the rejected messages, groups, and interchanges. |
| CONTRL_InboundTerminal | Used for received, or inbound, CONTRL acknowledgements. |
| CONTRL_OutboundTerminal | Used for generated, or outbound, CONTRL acknowledgments. |
These terminals are not accessed until the compliance check maps are ready to write data to them. If you know that certain types of output are not to be generated, for example TA1 acknowledgements, you can specify a nonexistent terminal name such as "DUMMY*" in the configuration. However, this can cause adapter errors if the output is later generated due to other configuration changes. A better solution is to route any unexpected output types to a special terminal, such as EDI_OTHER.
See the WebSphere Transformation Extender Integration Servers documentation for more information about the PUT to WIRE functionality.