Key Capabilities
- IATA PADIS support with bidirectional IATA PADIS/XML translation
- Automatic EDIFACT-subset schema detection and validation for aviation industry messaging
- CONTRL acknowledgment generation/processing with interchange header management for routing
Overview
When receiving PADIS documents, IATA PADIS connectors validate document interchange headers and convert the PADIS document into XML. This is useful as a staging step, because XML is the primary format that Arc uses to manipulate data in a flow. The IATA PADIS connector automatically reads the input file to determine the appropriate PADIS schema, then parses the document according to this schema. IATA PADIS is a subset of the EDIFACT standard, so many of the features and functionality of the IATA PADIS connector are shared with the more general EDIFACT connector. When generating PADIS documents, IATA PADIS connectors convert XML into PADIS document syntax and apply the appropriate interchange headers. This is useful as the final step for creating a PADIS document, after the XML data has been fetched and transformed elsewhere in the flow.Interchange header validation can be avoided by enabling the Test Indicator setting.
Connector Configuration
This section contains all of the configurable connector properties.Settings Tab
Translation Configuration
Settings related to the core operation of the connector.EDI Partner
Interchange Settings
Settings related to the IATA PADIS interchange headers. When generating PADIS documents from XML, these settings are used to generate document headers. When parsing PADIS documents, these settings are used to validate the incoming document.Acknowledgments
Settings related to generating and requesting acknowledgments.Sample Files Tab
Advanced Tab
EDI Delimiters
Settings that specify which characters separate elements, segments, etc.Interchange Settings
Additional settings related to the IATA PADIS interchange headers. These options appear or disappear based on the Syntax Version specified on the Settings tab.Functional Group Settings
Settings related to the functional group headers of PADIS documents. These optional identifiers can help group similar interchanges together or facilitate sub-addressing within an organization.Advanced Settings
Settings not included in the previous categories.Logging
ログの作成と保存を制御する設定です。
| 設定 | 説明 |
|---|---|
| Log Level | コネクタが生成するログの詳細度です。サポートを依頼する際は、これをDebug に設定してください。 |
| Log Subfolder Scheme | 選択した間隔に従って、コネクタがLogs フォルダ内のファイルをグループ化するよう指示します。Weekly オプション（デフォルト）は、コネクタが毎週新しいサブフォルダを作成し、その週のすべてのログをそのフォルダに保存するよう指示します。この設定を空白のままにすると、コネクタはすべてのログをLogs フォルダに直接保存します。多数のトランザクションを処理するコネクタでは、サブフォルダを使用することでログを整理しやすくなり、パフォーマンスが向上します。 |
| Log Messages | 処理したファイルのログエントリにファイル自体のコピーを含めるには、これをオンにします。これを無効にすると、Transactions タブからファイルのコピーをダウンロードできなくなる場合があります。 |
Miscellaneous
Miscellaneous 設定は、特定のユースケース向けの設定です。
| 設定 | 説明 |
|---|---|
| Other Settings | 非表示のコネクタ設定をセミコロン区切りのリストで設定できます（例：setting1=value1;setting2=value2）。通常のコネクタのユースケースや機能では、これらの設定の使用は必要ありません。 |
EDI Partners Tab
Automation Tab
Automation
Settings related to the automatic processing of files by the connector.Performance
コネクタへのリソースの割り当てに関する設定です。
| 設定 | 説明 |
|---|---|
| Max Workers | このコネクタでファイルを処理するためにスレッドプールから消費されるワーカースレッドの最大数です。設定すると、Advanced Settings ページのPerformance Settings 部分にあるデフォルト設定が上書きされます。 |
| Max Files | コネクタに割り当てられた各スレッドが送信するファイルの最大数です。設定すると、Advanced Settings ページのPerformance Settings 部分にあるデフォルト設定が上書きされます。 |
Alerts Tab
SLAs Tab
Converting Formats
The following sections detail the process of converting PADIS documents to XML and vice versa.PADIS to XML
Setting the Translation Type to IATA to XML instructs the connector to parse incoming PADIS documents into XML. The connector first reads all of the header information for the Interchange and Functional Group sections of the document and validates them against the configured connector settings (unless Test Indicator is enabled). The connector then parses out the specific PADIS schema used in the document and loads the schema from theedifact_schemas folder on disk (additional schema files can be downloaded from our website for free).
Using the schema, the connector generates XML representing the structure of the document, populates the XML with the values from the document, and provides context to each value either as XML comments or as attributes in the XML elements (based on the value of Generate Descriptions As).
To see this process with a set of test PADIS documents, navigate to the Transactions tab of an IATA PADIS connector (with Translation Type set to IATA to XML) and select More > Create Test Files. PADIS documents for an invoice, purchase order, purchase order acknowledgment, and shipping notice are automatically generated and placed in the Transactions directory. After these test files are processed by the connector, navigate to the Transactions tab to see the resulting XML.
Once PADIS documents are converted to XML, the data can be transformed and manipulated in many ways. Commonly, PADIS data needs to be stored in a database or other back-end application system. Since Arc uses XML to represent inserts into these back-end systems, storing the PADIS data becomes a matter of mapping one XML structure onto another. This is typically done with the visual designer-driven XML Map Connector.
XML to PADIS
Setting the Translation Type to XML to IATA instructs the connector to generate a PADIS document out of an XML representation of the document. After the connector has constructed the PADIS message out of the data parsed from the XML, it adds functional group and interchange headers according to the configured connector settings. To see this process with a set of test XML files, navigate to the Transactions tab of an IATA PADIS connector (with Translation Type set to XML to IATA) and select More > Create Test Files. XML files representing an invoice, purchase order, purchase order acknowledgment, and shipping notice are automatically generated and placed in the Transactions directory. After these test files are processed by the connector, navigate to the Transactions tab to see the resulting PADIS document.Use With the XML Map Connector
Upload Test File
IATA PADIS Acknowledgments
The following sections detail the two types of IATA PADIS acknowledgments (ACKs), and how Arc expects, processes, and generates ACKs.Technical versus Functional Acknowledgments
Technical ACKs, sometimes called interchange ACKs, are an indication that an interchange has taken place between the two parties, although not necessarily that any individual message has been exchanged. These serve as a receipt to the sender indicating that the PADIS message was successfully received, but it does not specify whether there were any issues with processing the message content. Functional ACKs are an indication that an interchange has been processed by the receiving party. They can report acceptance, acceptance with issues, or rejection of the received document. These serve as both a receipt that an interchange was successfully received and that it was fully processed.Expecting, Processing, and Generating Acknowledgments
Expecting Acknowledgements
IATA PADIS connectors operating in XML to IATA mode can be configured so that technical and/or functional ACKs are expected for a message. When one or both Technical acknowledgment (CONTRL) and Functional acknowledgment (CONTRL) are checked in the Acknowledgments section of the Settings tab, the connector maintains a Pending ACK status for a transmission until the appropriate ACKs have been returned and processed. This means that the connector status can be used to determine whether the recipient has confirmed that they received the interchange. See the EDIFACT connector for a detailed description of this feature. The IATA PADIS connector works the same way.確認応答（ACK）を必要とするEDI メッセージがその確認応答を受け取っていない場合、Pending-Timeout ヘッダーがメッセージに追加されます。メッセージはACK を待つ間、Pending ステータスになります。割り当てられた時間内にACK を受信しない場合、Pending-Timeout ヘッダーには、メッセージのステータスがError に変わった日時が設定されます。ACK を受信してメッセージがSuccess に更新されると、空文字列の値を持つ新しいヘッダーが追加されます。