The simplest way to test the AS2 service is by using your browser. Type in the following address.

http://<URL or IP of Integration Server>/partner/AS2Retrieve/

A correctly configured AS2 service replies with an MDN (file). Please save that file and open it in a regular text editor. The content should be similar to the following.

------=_Part_0_24916054.1236247212828
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MDN for -
Message-ID: null
From: null
To: null
Received on: n.a.
Status: failed: authentication-failure
Comment: This is not a guarantee that the message has
been completely processed or understood by the receiving
translator
------=_Part_0_24916054.1236247212828
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: Lobster AS2-Server (IS/5.7.19_14147)
Original-Recipient: rfc822; null
Final-Recipient: rfc822; null
Original-Message-ID: null
Received-Content-MIC: 2jmj7l5rSw0yVb/vlWAYkK/YBwk=, sha1
Disposition: automatic-action/MDN-sent-automatically; failed: authentication-failure
Failure: You're unknown to this system
------=_Part_0_24916054.1236247212828--

If you get such a response, the AS2 service is reachable and ready to use (you can ignore the authentication error in the MDN since we were only interested in the reachability).

Different Port

If the default HTTP port (80) is not used, you can determine the correct one as follows. The configuration file./etc/as2.xml contains the following entry.

<Call name="setContext">
	<Arg>Main Server</Arg>
	<Arg>/partner/*</Arg>
	<Arg>/AS2Retrieve/*</Arg>
</Call>

You can use the name of the HTTP server (here Main Server) in the Admin Console to find the ports of the listeners.

Based on that information, the URLs might then, for example, be

http://<host>:8080/partner/AS2Retrieve
https://<host>:8443/partner/AS2Retrieve