In b57 zip release no batch file to start mendelson AS2 on Windows

The zip release of b57 ("install_mendelson_opensource_as2_1.1b57.zip") has no batch file ("mendelson_as2_start.bat") to start mendelson AS2 on Windows.

Forum
AS2

Comments

Hi,

We have downloaded the installer but are unable to set the amount of memory for Mendleson to use, as well as for it to use 64bit Java.

Can you please advise how this is done in build 57.

In build 55 we used the following in the .bat file:

"C:\Program Files\Java\jdk-12.0.2\bin\java" -Xmx5G -Xms5G -classpath %CLASSPATH% de.mendelson.comm.as2.AS2

Thank you in advance.

Ryno

Ryno,

the mendelson opensource AS2 is delivered with a 32bit VM, it is not possible to define more than 1.3GB of heap there without manually replacing the JVM.

For using a 64bit VM (which is recommended for production use) out of the box please move to the commercial license.

Regards

Permalink

On attempting to send an AS4 message containing the following collaboration info

urn:fdc:peppol.eu:2017:agreements:tia:ap_provider
urn:www.cenbii.eu:profile:bii04:ver2.0
busdox-docid-qns::urn:oasis:names:specification:ubl:schema:xsd:Invoice-2::Invoice##urn:www.cenbii.eu:transaction:biitrns010:ver2.0:extended:urn:www.peppol.eu:bis:peppol4a:ver2.0::2.1
658af823-e8f9-4ee6-9a00-a87824eba1ab

we receive a SignalMessage as such:

2020-01-22T15:41:56.805Z
mendelson-opensource-AS4-200122154156-2@3
8aafeff9-9342-4eea-a328-cac24fad1d2b@phase4

Although the message document is well formed and schema valid, some element/attribute value is inconsistent either with the content of other element/attribute, or with the processing mode of the MSH, or with the normative requirements of the ebMS specification.
[SOAP Validation] If the AgreementRef/@type attribute is not present, the content of the AgreementRef element MUST be a URI.

If we send UBL documents via Mendelson AS4 the SOAP-XML Mendelson generates does set the collaboration info the same way. In order to receive the AS4 message successfully we have to disable the validation of the SOAP-XML first.

According to the EBMS XSD AgreementRef is defined as such:

hence I think this is a bug in the b27 version of Mendelson AS4