AS3 Message Exchange

Single Message Exchange Process

In a single document exchange, you create a business process that includes the AS3 Build service (which you have configured). The AS3 payload can be retrieved from various sources (for example, retrieving from a legacy system or using the File System adapter to collect a message) and is then stored as a primary document within the business process prior to invoking the AS3 Build service. The document retrieved should not have any exclamation mark in its filename. The mailbox functionality fails if it receives any file with that character in the name.

Multiple Message Exchange Process

In a multiple document exchange, the Bulk Message Generation option (which you configure during trading partner contract creation) is used to initiate multiple exchanges with your partner. As part of the contract creation process, a scheduled business process is created. This scheduled business process, when invoked, confirms that the message exchange with your partner has not been suspended in a previous attempted exchange. It then uses the default instance of the File System adapter within the business process to collect the documents from the specified payload directory and to initiate a predefined business process.

If any connection errors occur, the message exchange to your partner is suspended for the period you specified in the contract.

Receiving an AS3 Message

AS3 and MDN messages enter Sterling B2B Integrator though the FTP Server adapter. As part of configuring this adapter, you need to create User Accounts for your trading partners and assign the User IDs to the trading partner mailboxes. The necessary AS3 mailboxes were either automatically created during the creation of partner contracts or you created them manually.

During the FTP Server adapter configuration, you can indicate if SSL is required when connecting to the FTP Server. When you configure to use SSL, you must give the public certificate to your partners to use during the SSL handshake procedure.

For more information on configuring the FTP Server adapter, see FTP Server Adapter Instance for AS3.

Negative MDNs

When an error occurs in the processing of an inbound AS3 message (with an MDN request specified, a negative MDN is generated and sent back to the trading partner in the mode specified by the Responder Action.

If an error occurs in the processing of an inbound AS3 message without an MDN request specified, a workflow exception occurs and the transaction record is not stored in the MDN Correlation (MSGMDNCORRELATION) table.

Outbound Negative MDNs

When any of these error conditions occur in the processing of an inbound AS3 message with an MDN request specified, a negative MDN is generated with the following disposition-modifier values and sent to the trading partner:

The receiver could not authenticate the sender.

Error: authentication-failed

The receiver could not decrypt the contents of the message.

Error: decryption-failed

The receiver could not decompress the message.

Error: decompression-failed

Any other processing error (not specified above).

Error: unexpected-processing-error

The transaction status is updated to Processed with errors and stored in the MDN Correlation (MSGMDNCORRELATION) table.

Inbound Negative MDNs

When a negative MDN is received from a trading partner, the corresponding transaction status in the MDN Correlation (MSGMDNCORRELATION) table is updated to Processed with errors and the disposition type and disposition modifier values are extracted from the Disposition header of the original message.