Version 23.4.8841

• Overview
• Connector Configuration
  • Settings Tab
    • Configuration
    • Infor System Configuration
    • Inbound
    • Outbound
    • Message
    • Logging
    • Miscellaneous
  • Automation Tab
    • Automation Settings
    • Performance
  • アラートタブ
    • コネクタのE メール設定
    • サービスレベル（SLA）の設定
• Establishing a Connection
• Sending Files
• Receiving Files

The Infor connector supports transmitting EDI documents to and from the Infor CloudSuite Industrial (formerly Syteline) platform.

Overview

Infor connectors perform two functions when sending or receiving EDI documents to Infor CloudSuite Industrial. When sending, the connector converts XML documents into a flat file structure accepted by CloudSuite, then sends the resulting file to the remote data folder where it can be picked up by Infor. When receiving, the connector polls the data folder for flat files, which it then converts into XML.

Connector Configuration

This section contains all of the configurable connector properties.

Settings Tab

Configuration

Settings related to the core configuration of the connector.

• Connector Id The static, unique identifier for the connector.
• Connector Type Displays the connector name and a description of what it does.
• Connector Description An optional field to provide a free-form description of the connector and its role in the flow.

Infor System Configuration

Settings provided in the connection to the Infor system.

• Trading Partner Code The code identifying the documents in the Infor system.

Inbound

Folder locations for demand-side documents in the Infor system.

• Inbound Data Logic Folder The folder location for demand-side file pickup and drop-off.
• Inbound Archive Folder The folder location for archiving processed demand-side documents.

Outbound

Folder locations for outbound documents in the Infor system.

• Outbound Data Logic Folder The folder location for supply-side file pickup and drop-off.
• Outbound Archive Folder The folder location for archiving processed supply-side documents.

Message

• Save to Sent Folder Check this to copy files processed by the connector to the Sent folder for the connector.
• Sent Folder Scheme Instructs the connector to group messages in the Sent folder according to the selected interval. For example, the Weekly option instructs the connector to create a new subfolder each week and store all messages for the week in that folder. The blank setting tells the connector to save all messages directly in the Sent folder. For connectors that process many messages, using subfolders helps keep messsages organized and improves performance.

Logging

• Log Level The verbosity of logs generated by the connector. When you request support, set this to Debug.
• Log Subfolder Scheme Instructs the connector to group files in the Logs folder according to the selected interval. For example, the Weekly option instructs the connector to create a new subfolder each week and store all logs for the week in that folder. The blank setting tells the connector to save all logs directly in the Logs folder. For connectors that process many transactions, using subfolders helps keep logs organized and improves performance.
• Log Messages Check this to have the log entry for a processed file include a copy of the file itself. If you disable this, you might not be able to download a copy of the file from the Input or Output tabs.

Miscellaneous

Miscellaneous settings are for specific use cases.

• Other Settings Enables you to configure hidden connector settings in a semicolon-separated list (for example, setting1=value1;setting2=value2). Normal connector use cases and functionality should not require the use of these settings.

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

• Send Whether files arriving at the connector are automatically sent.
• Retry Interval The number of minutes before a failed send is retried.
• Max Attempts The maximum number of times the connector processes the file. Success is measured based on a successful server acknowledgement. If you set this to 0, the connector retries the file indefinitely.
• Receive Whether the connector should automatically query the data source.
• Receive Interval The interval between automatic query attempts.
• Minutes Past the Hour The minutes offset for an hourly schedule. Only applicable when the interval setting above is set to Hourly. For example, if this value is set to 5, the automation service downloads at 1:05, 2:05, 3:05, etc.
• Time The time of day that the attempt should occur. Only applicable when the interval setting above is set to Daily, Weekly, or Monthly.
• Day The day on which the attempt should occur. Only applicable when the interval setting above is set to Weekly or Monthly.
• Minutes The number of minutes to wait before attempting the download. Only applicable when the interval setting above is set to Minute.
• Cron Expression A five-position string representing a cron expression that determines when the attempt should occur. Only applicable when the interval setting above is set to Advanced.

Performance

Settings related to the allocation of resources to the connector.

• Max Workers The maximum number of worker threads consumed from the threadpool to process files on this connector. If set, this overrides the default setting on the Settings > Automation page.
• Max Files The maximum number of files sent by each thread assigned to the connector. If set, this overrides the default setting on the Settings > Automation page.

アラートタブ

アラートとサービスレベル（SLA）の設定に関連する設定.

コネクタのE メール設定

サービスレベル（SLA）を実行する前に、通知用のE メールアラートを設定する必要があります。アラートを設定をクリックすると、新しいブラウザウィンドウで設定ページが開き、システム全体のアラートを設定することができます。詳しくは、アラートを参照してください。

サービスレベル（SLA）の設定

サービスレベルでは、フロー内のコネクタが送受信すると予想される処理量を設定し、その量が満たされると予想される時間枠を設定できます。CData Arc は、サービスレベルが満たされていない場合にユーザーに警告するE メールを送信し、SLA を At Risk（危険） としてマークします。これは、サービスレベルがすぐに満たされない場合に Violated（違反） としてマークされることを意味します。これにより、ユーザーはサービスレベルが満たされていない理由を特定し、適切な措置を講じることができます。At Risk の期間内にサービスレベルが満たされなかった場合、SLA はViolated としてマークされ、ユーザーに再度通知されます。

サービスレベルを定義するには、予想処理量の条件を追加をクリックします。

• コネクタに個別の送信アクションと受信アクションがある場合は、ラジオボタンを使用してSLA に関連する方向を指定します。
• 検知基準（最小）を、処理が予想されるトランザクションの最小値（量）に設定し、毎フィールドを使用して期間を指定します。
• デフォルトでは、SLA は毎日有効です。これを変更するには、毎日のチェックをOFF にし、希望する曜日のチェックをON にします。
• 期間終了前にステータスを’At Risk’ に設定するタイミングを使用して、SLA がAt Risk としてマークされるようにします。
• デフォルトでは、通知はSLA が違反のステータスになるまで送信されません。これを変更するには、‘At Risk’ 通知を送信のチェックをON にします。

次の例は、月曜日から金曜日まで毎日1000ファイルを受信すると予想されるコネクタに対して構成されたSLA を示しています。1000ファイルが受信されていない場合、期間終了の1時間前にAt Risk 通知が送信されます。

Establishing a Connection

The following settings are required to connect to Infor:

• Trading Partner Code identifies the documents in the Infor system.
• Inbound Data Logic Folder is for demand-side file pickup and drop-off.
• Inbound Archive Folder is for archiving processed demand-side documents.
• Outbound Data Logic Folder is for supply-side file pickup and drop-off.
• Outbound Archive Folder is for archiving processed supply-side documents.

After these fields have been specified, the connector can exchange documents with the Infor system.

Sending Files

After a connection to Infor has been established, XML files in the Input tab of the Infor connector are converted to the Infor standard flat file format and uploaded. If Send Automation is enabled on the Automation tab, the connector automatically polls this folder for processing.

Receiving Files

Files that are found when polling Infor CloudSuite are downloaded to the Infor connector Output tab. The standard flat file structure is automatically converted into XML. If the Infor connector is connected to other connectors in a flow, the file is passed to the next connector.