Dear Group,

We are attempting to implement an architecture to communicate with our business partners using the AS2 standard. What I’ve read about the AS2 standard sounds like it involves many RFCs, that define it as an S/MIME message posted over HTTP(s). My first question is, has anyone had any luck implementing an AS2 connection without using the TN builtin WM.EDIINT package?

For incoming communication, we are planning on exposing a WM service in our DMZ that will accept HTTP posts of bytes or an input stream, create a MIME message from that stream and then verify the data against the provided signature, and extract the payload. My other question is, how and what do we send back in the same HTTP session to be AS2 compliant.

Many thanks for your help.

Mathew,

1. I am afraid there will be a lot of work to do without wm.ediint package as this is the package that has all transport related and ediint processing services.

2. For inbound ediint, wM with its content handler and ediint.receive service does all the job of recognizing the ediint content. Theoretically it is possible to have custom content handler to deal with ediint data that is captured at your DMZ server, decrypting, verifying the signature and extracting the payload. In this case I am not seeing why webMethods software to do this?

3. In the same HTTP session, we are not sending back anyhting except for the http response header status code of 200. MDN will be sent asynchronously for ediint message. May be you want to check upon synch MDN standard.

4. My understanding in protocol is ediint AS2 is http and not http/s. Ofcourse, the mime is encrypted and signed.

HTH
DG

Matthew,

Did you have a look at OpenAS2 ( http://www.openas2.org ). This application can be used as a replacement of the EDIINT, but it’s still in Alpha status, not ready for a production environment. It reads and writes files to/from an inbound and outbound directory, webMethods can do the same.

Andre.