You can use EDI studio to send EDI messages to the AS2 web app. The AS2 web app processes the data further to the web server of the EDI partner.
Set up the Process outbound message queue to process the outbound web service actions as set up for AS2.
| Name | Responsible | Description |
|---|---|---|
|
Process outbound messages |
Application Consultant |
If you use EDI messages and post one of the following journals, also a record is added to the Outbound message queue:
Also, a record can be added to the Outbound message queue for sales acknowledgements. When a received sales order message is processed, it is added to the EDI history (with direction 'Inbound' and type 'Order'). If a document flow of type 'Acknowledge' exists for the customer, also a record is created in the Outbound message queue.
An outbound message queue record indicates which message must be run for which journal (or EDI history record in case of a sales acknowledgement). The message to be run is defined by the applicable document flow. When the record is added to the Outbound message queue, the applicable document flow is searched for, and the related message is linked to the Outbound message queue record.
To process the outbound message queue, run the Process outbound message queue batch job. Usually, you run this batch job in a recurring pattern.
You process the outbound message queue for a specific message. Optionally you can run a message for a specific company.
If you use a web service, as defined on the applicable document flow, also define the applicable web service action here. |
|
Run AS2 web app - Outbound |
Application Consultant |
If you use the AS2 protocol to send EDI messages to an EDI partner, use the AS2 web app to manage the interaction with the EDI partner. The AS2 web app runs in the Azure cloud. When you run a web service action using the AS2 protocol, an EDI message is sent to the AS2 web app. The web service action calls the send method of the AS2 web app to send the data to the EDI partner. The AS2 web app send method:
|
| Name | Responsible | Description |
|---|---|---|
|
Process outbound messages |
Application Consultant |
If you use EDI messages and post one of the following journals, also a record is added to the Outbound message queue:
Also, a record can be added to the Outbound message queue for sales acknowledgements. When a received sales order message is processed, it is added to the EDI history (with direction 'Inbound' and type 'Order'). If a document flow of type 'Acknowledge' exists for the customer, also a record is created in the Outbound message queue.
An outbound message queue record indicates which message must be run for which journal (or EDI history record in case of a sales acknowledgement). The message to be run is defined by the applicable document flow. When the record is added to the Outbound message queue, the applicable document flow is searched for, and the related message is linked to the Outbound message queue record.
To process the outbound message queue, run the Process outbound message queue batch job. Usually, you run this batch job in a recurring pattern.
You process the outbound message queue for a specific message. Optionally you can run a message for a specific company.
If you use a web service, as defined on the applicable document flow, also define the applicable web service action here. |
|
Run AS2 web app - Outbound |
Application Consultant |
If you use the AS2 protocol to send EDI messages to an EDI partner, use the AS2 web app to manage the interaction with the EDI partner. The AS2 web app runs in the Azure cloud. When you run a web service action using the AS2 protocol, an EDI message is sent to the AS2 web app. The web service action calls the send method of the AS2 web app to send the data to the EDI partner. The AS2 web app send method:
|
| Related to | Notes |
|---|---|
|
Set up AS2 - Outbound |
|
|
Process EDI messages using AS2 - Outbound |