mendelson opensource AS2 1.1 b27 released

Hi

I have downloaded both the zip file and exe file.

Insalled MEC AS2 and the launched it

The application launched , however when i try to access the httpreciver page or the defaul page through the browser using HTTP://127.0.0.1/mec_as2/httpreceiver or
HTTP://127.0.0.1/mec_as2

i get a service unavailable message .

Avinash75,

the URL path has changed. Its /as2/HttpReceiver now.

Regards
Heller

Hi Heller

Thanks for the quick response

can the rul path be changed to original mec_as2

reason is that i already have partners configured with the mec_as2 url and changing it to AS2 would mean a lot of work.

Avinash75,

the URL path could be set in the file /META-INF/context.xml in the as2.war package. The as2.war file is the deploy file, found in the jetty webapps dir.

Regards
Heller

Hi

I tried usig AS2/http receiever on a new install and it gives me the follwoing error

HTTP ERROR: 503
SERVICE_UNAVAILABLE
RequestURI=/as2/HttpReceiver

Powered by jetty://

Avinash75,

Could you please ensure that the receipt servlet has been deployed properly? To do this please set the properties "lax.stderr.redirect" to "console" and "lax.stdout.redirect" to "console" in the file as2.lax, restart the as2 server and check if any error occurs.

Regards
Heller

Hi Heller

Thanks a lot I didnt use the above solution , but instead what i did was downloaded the installer and installed it on a new machine and it worked like Charm

I couldn't find the as2.lax file you were refering to.

Will,
its in the windows installer package.

Regards
Heller

That explains it. I'm not running windows. Any other ideas on solving the issue? I'd like to use the new system, but even from stock zip I get the 503 message on all http views.

-Will

will,

please use the shell script included on non windows systems. It should display if the deploy process was successful or if any error occured.

Regards
Heller

removed

Just FYI, that is a new zip extraction the following actions were done before running:

# Move old prefs out of way so that it doesn't pick
# them up, and instead creates new default ones
mv ~/.java/de ~/.java/de.old
# Change line endings of start/stop files to unix
# so that they are runnnable
dos2unix mendelson_as2_start.sh
dos2unix mendelson_as2_stop.sh
# Change start/stop files to executable so they can be run
chmod u+x mendelson_as2_start.sh
chmod u+x mendelson_as2_stop.sh
# Run AS2 Server
./mendelson_as2_start.sh


The testing enviroment for this is:

kassah@izaban:~/as2$ java -version
java version "1.6.0_10"
Java(TM) SE Runtime Environment (build 1.6.0_10-b33)
Java HotSpot(TM) 64-Bit Server VM (build 11.0-b15, mixed mode)
kassah@izaban:~/as2$


Hope this helps.

Good Day,

Edit mendelson_as2_start.sh and revise line that initializes CLASSPATH. Should read:

CLASSPATH=as2.jar:jetty/start.jar:jetty/lib/servlet-api-2.5-6.1.1.jar

Worked for me.

Markus

That did the trick! thanks

Hi Heller

I couldnt find the Contect.xml for chnaging the URL to mec_as2 in as2.war file

I believe in the default configuration renaming the war should change the directory (in all cases except moving to the root). So if you wanted it to be http://yourhostname.com:8080/mec_as2/HttpReceiver you would rename the war to mec_as2.war.

I am not authoritative on these things, but it's worth a try =)

Thanks,
Will

Hi

I am facing a strange issue with one of my partners where in the sending partner reports the file transfer as failed , though the receiving unit has already recoved the file and reports a success state .

It is happening to every single file sent to this partner be it small or large .

Avinash75,

thats a logical problem of the AS2 protocol. Something like this would not happen in RosettaNet.

If a system receives a AS2 message and answers with an MDN, everything seems to be ok for the system if a HTTP 2xx returns.
But on the other side its possible that the MDN could not be parsed by any reason But the HTTP 200 is already sent, its just a receipt signal, not a process signal). This leads to the situation where both partners of the transaction have different transaction states.

AS2 has no mechanism like RosettaNet PIP0A1 (Distribute Notification Of Failure) in its protocol.

That means - the problem you are facing seems to be that the partner could not process the MDN by any reason.

Regards
Heller

Hi

Like ${FILENAME} AND ${log} are there any other variables available which can be used in success and failure event commands ?

Avinash75,

no, not so far. But there is always room for enhancements. Which data do you require?

Regards
Heller

Hi

Variables which come quickly to my mind are.

- ${Partner} which can be used in case of multiple partners to exactly figure out for which partner the file tranfser has failed or succeded so that then apropriate action can be taken on the file with regards to partner.

- ${PartnerOutboxPath} to identify the message outbox path for the partner.

-${Host} to identify the host name i.e the local partners name

all this allow smooth scripting for event actions .

Avinash75,

we will add something like this for the next release.

Regards
Heller

Hi Heller,

I upgraded from AS2 1.1 b25 to AS2 1.1 b27 (changed the destination folder to \mec\as2) and retained my old configuration files (certificates.p12, jetty.xml etc).

As the new installer asks for retaining the old configurations, am I right in assuming that the old URLs that I shared with my partners will remain the same?
Will it be /mec_as2/HttpReceiver because under the C:\mec\as2\jetty\webapps folder, there are 2 jar files (mec_as2.war and as2.war)

Regards,
Arun

Arun,

If you deploy both war files, you support 2 URLs - I would remove the old one.

Regards
Heller

Hi Heller,
Thanks for the info. Is it necessary to delete the first WAR file? I have shared my URL with my client in the old format.

http://:/mec_as2/HttpReceiver

Is it necessary to change it to
http://:/as2/HttpReceiver

And will it continue to work as per the old URL too?

I tried exchanging files with the client and got this error. Is this because of the WAR file issue?

[1:54:44 PM] mendelson_opensource_AS2-1245664479106-11@GSL_PROD_MARS: Message sent successfully (HTTP 202); 5.08 KB transfered in 5.16s [0.99 KB/s].
[1:54:45 PM] mendelson_opensource_AS2-1245664479106-11@GSL_PROD_MARS: Will wait for async MDN until 6/22/09 2:24:45 PM.
[1:54:45 PM] Warning on the server site, request could not be executed!
[1:54:45 PM] Error message returned by the call:
[1:54:45 PM] RemoteException occurred in server thread; nested exception is:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: de.mendelson.comm.as2.clientserver.serialize.CommandObjectIncomingMessage; local class incompatible: stream classdesc serialVersionUID = -374663010135332164, local class serialVersionUID = -4895662136249884227
[2:07:10 PM] Keys and certificates loaded from "C:\mec\as2\certificates.p12".

Regards,
Arun

Arun,

the war and jar files have to match because the HTTP receiver (war) serializes data for the as2 server (jar).

Please delete the old war files, this should fix the problem.

Regards
Heller