The UltraESB allows its users unlimited and free AS2 messaging with their trading partners, and allows easy integration of the AS2 messaging layer with the backend systems. In this article, we will show how to configure the Mendelson Open Source AS2 to interact with the UltraESB, which is a pre-requisite for the sample configurations 350 and 351.

Setting up the sample AS2 trading partner

Download and install the Mendelson Open Source AS2 version from http://opensource.mendelson-e-c.com/ This is pre-configured to use a PKCS12 certificate store contained in a file "certificates.p12" in its installation directory. The UltraESB ships a compatible certificate store at samples/conf/keys/certificates.p12 and you can thus simply overwrite the original file with it.

asankha@asankha:~/java/ultraesb-1.0-beta-1$ cp samples/conf/keys/certificates.p12 /installationpath/mendelson

Now, start the Mendelson Open Source AS2 [See Footnote 1] with the "mendelson_as2_start.sh" script (or the equivalent under Windows). From the main console, select "File"->"Preferences" and then the "Security" tab. Replace the default password with "password" which is the password for the new key store. Now, select "File"-> "Reload Keystore" to reload the new keystore using the correct credentials.

Next, we will configure the AS2 Partners using the options under "File"->"Partner". By default the local station is identified as "mycompany". Go to the "Security" tab for "mycompany" and select 'Server 2' as the private key for both encryption and signatures.

Now select the 'mendelsontest' partner, and rename it with a new name if you wish. Change its AS2 identifier to 'AdroitLogicAS2' which is the AS2 identifier used by default in the UltraESB samples 350 and 351.

In the "Security" tab, select 'Server 1' as the Partner certificate for encryption and signatures.

Footnotes

[1] You may possibly need to create a directory before extracting the installation ZIP archive, and then set execute permissions and convert the .sh script into Unix line endings. Also, there is a bug in the version 1.1 build 29 and thus you will need to edit the start script to add the servlet JAR file into the CLASSPATH as shown below.

asankha@asankha:~/java/mendelson$ chmod +x mendelson_as2_start.sh 
asankha@asankha:~/java/mendelson$ dos2unix mendelson_as2_start.sh

Edit start script, and ensure jetty/lib/servlet-api-2.5-6.1.1.jar is in the CLASSPATH. e.g.

java -Xmx192M -Xms92M -classpath $CLASSPATH:jetty/lib/servlet-api-2.5-6.1.1.jar de.mendelson.comm.as2.AS2