MOVEit Transfer receives AS2 messages and asynchronous AS2 MDNs though its built-in as2receiver.aspx component. When your AS2 trading partners ask for the URL they should use to post AS2 messages for you, give them a URL containing as2receiver.aspx and the name of your host. For example, https://as2.moveittransfer.com/as2receiver.aspx .

The same URL value is also used when requesting AS2 asynchronous MDNs as an AS2 destination step in MOVEit Automation , but MOVEit Automation lets you specify a macro of [AS2ReceiverURL] (in the MDN URL field) and determines the exact URL at run time, because each AS2 Host can be linked to a specific MOVEit Transfer Host.

Storage and tagging of AS2 messages

AS2 messages are typically stored as files named AS2Data . If you want different MOVEit Automation tasks to process different AS2 messages from the same partner, you can tag each type of AS2 message transmission separately so that MOVEit Automation tasks can distinguish between them.

To tag different types of AS2 transmissions, include a ?Tag=[some-as2-filename] argument on the URLs you provide to your partners. For example, the URL https://as2.moveittransfer.com/as2receiver.aspx?Tag=Blue would force MOVEit Transfer to save AS2 messages from partners using that URL as files named Blue rather than AS2Data .

Storage and tagging of AS2 MDNs

Asynchronous AS2 MDNs are stored as files named MDN =[AS2-ID] where [AS2-ID] is the ID of the original AS2 message.

For example: an AS2MDN filename is MDN=373c55dc-f4b6-4c1b-81a1-e39f3a1c22d7@9b751ee7-d32e-4138-8124-1c107f2cd5d2 .

AS2 MDNs are stored in folders named after the partners who sent them. MOVEit Automation looks for the MDNs by using the values configured for partner name in the AS2 Host definition.

If your MOVEit Transfer hosts multiple Organizations, and you want each organization to use its own store of AS2 messages and MDNs, include an OrgID=[OrgID] tag (for example, OrgID=8011) in the URLs you give to your partners and configure in your requests for asynchronous HTTP MDNs.

For example, to have related AS2 messages and MDNs to go to a particular organization in a multiorganization configuration, do the following:

  • Give partners URLs such as https://as2.moveittransfer.com/as2receiver.aspx?OrgID=8011 or https://as2.moveittransfer.com/as2receiver.aspx?Tag=Blue&OrgID=8011 and
  • Configure a URL of [AS2ReceiverURL]?OrgID=8011 in your asynchronous HTTP MDN field.

What happens to AS2 messages and asynchronous AS2 MDNs?

AS2 messages and asynchronous AS2 MDNs are deleted from MOVEit Transfer as soon as any of the following occur:

  • MOVEit Automation successfully decrypts and/or validates them
  • MOVEit Automation determines that they are unfit
  • MOVEit Automation gives up after (re)trying to deliver any requested MDNs.

AS2 messages that have requested synchronous MDNs are automatically deleted from MOVEit Transfer folders if MOVEit Transfer cannot deliver their respective MDNs.

To apply additional automated clean up rules to AS2 folders and files, use the Folder Settings web interface in MOVEit Transfer .