AS2 Extraction Business Process
- The AS2Extract business process calls the JDBC adapter to obtain the name of the trading partner inbound folder from the AS2TradingPartnerInfo table.
- The AS2Extract business process calls the File System adapter to write the business document to a file in the inbound folder.
The following table describes the extraction business processes:
| Business Process | Description |
|---|---|
EDIINTParse |
This business process is invoked for all inbound AS2 messages. It employs the EDIINT Pipeline service to determine the AS2 Relationship parameters, and then invoke one of the following EDIINTParse subprocesses: AS2Extract (for File System), MailboxAS2Add (for Mailbox), and AS2Inbound (for Direct Processing). Parses messages; is configured on the default application AS2 URL (Sterling B2B IntegratorIP_ADDRESS:port/b2bhttp/inbound/as2). EDIINT Parse invokes the default instance of the EDIINT Header Scanning service and uses the value of the AS2-To header to attempt to find the appropriate row in the AS2TradingPartnerInfo database table. If the row is found, the value configured for “Wait for MDN” prompts the default instance of the EDIINT Pipeline service whether to build an MDN. If the EDIINT Pipeline service does not build an MDN, it propagates the MDN building information to the business process called to handle the payload data (either AS2Extract or MailboxAS2Add or AS2Inbound). Additionally, this business process queries the name of HTTP Client Adapter from the AS2_PROFILE table. Note: This business
process uses the EDIINT Pipeline service instead of the EDIINT Message
service because of the ability of the former service to handle large
and high-concurrency files.
Note: The Sterling B2B Integrator AS2
Edition includes a configured URL that runs the EDIINTParse business process on both the base port
and the base port + 33.
|
AS2Extract |
Extracts business payload data to the trading partner's inbound subdirectory. Determines whether a Message Disposition Notification (MDN) must be built and sent before extracting payload data. If an MDN must be built and sent, the default instance of the EDIINT MDN Building service is invoked to build the MDN. The process for sending the MDN is then initiated synchronously and data is extracted if the process for sending the MDN completes successfully. Note: MDNs are only built and sent by the EDIINT MDN Building
service if you are using deferred extraction. Otherwise, they are
built and sent by the EDIINT Pipeline service.
|
MailboxAS2Add |
Extracts business payload data to the trading partner's inbound mailbox. Determines whether an MDN needs to be built and send before extracting payload data. If the MDN does need to be built and sent, the default instance of the EDIINT MDN Building services is called to build the MDN, and the process for sending the MDN is then invoked synchronously. If the process for sending the MDN completes successfully, the payload data is extracted. Note: MDNs
are only built and sent by the EDIINT MDN Building service if you
are using deferred extraction. Otherwise, they are built and sent
by the EDIINT Pipeline service.
|
AS2Inbound |
Forwards business payload data as Primary Document
to the user defined business process. Determines whether a Message
Disposition Notification (MDN) must be built and sent before extracting
payload data. If an MDN must be built and sent, the default instance
of the EDIINT MDN Building service is invoked to build the MDN. The
process for sending the MDN is then initiated synchronously and data
is extracted if the process for sending the MDN completes successfully.
Note: MDNs
are only built and sent by the EDIINT MDN Building service if you
are using deferred extraction. Otherwise, they are built and sent
by the EDIINT Pipeline service.
|