Hi all,
we have released a new version of the mendelson opensource AS2.
Please visit http://opensource.mendelson-e-c.com for a download of your version.
Beneath small fixes (as dicussed in this forum) it includes the following issues:
Enhancement:
*Max file size for transfered files has been inproved
*Changes of partner names now rename the underlaying directories instead of creating new ones. (This is not done without asking the user)
*MIC header value may contain blanks now
*Number of internal database connections and JMS connections reduced for lower resource requirements
*AS2 id may contain blanks now
*MIC check is performed for signed messages only now
*Content transfer encoding could setup for each partner now (base64 or binary)
*New replaceable variables available for the command execution after receipt or send are available now. These are ${sender} and ${receiver}
*New filters for the local station in the web client
*All HTTP 2xx answers are accepted as OK now (even if the RFC allows HTTP 200 only)
*The server state could be requested now (beneath the web client) using the URL /as2/ServerState
Fixes:
*Command after receipt (async MDN) has not been executed
*Fixed an error in the MIC calculation if the message was signed and compressed
Updates:
Update to Bouncycastle 1.44 (crypto API)
Update to JORAM 5.2.5 (JMS provider)
We are looking forward for your comments, thank you for using our software.
Regards
Your mendelson development team
Hi all,
updating from an older version of mendelson opensource AS2 to this version is fairly easy.
*First make a backup of your message and program folder
*Start the installer. If it asks to overwrite some files that already exist - DO NOT overwrite them. These are your personal files like certificate storage etc.
*Start the mendelson opensource AS2 server. It will update your database structure to the required one. Your partner settings etc are kept.
-- thats all
Regards
Your mendelson development team
Hi Heller,
like the new colour boxes. All updates fine.
Only small glitch was the user name and password resets for the web interface.
If someone else finds this - this is what heller has said in the past to change the username and password.
"
To change the password of the web interface please modify the file jetty/etc/realm.properties, e.g. to
myuser: mypassword,monitor
Please do not change the rule ("monitor").
"
Thanks
Damon
Hi Heller,
just noticed that the timestamp of the file I just recieved and sent are from 1 hour ago.
The local time here is 8:55am but in the AS2 software the timestamp is 7:55am.
It may have always been like that but I have just noticed that it does not seem to have adjusted to daylight saving even though windows displays the correct time.
Thanks
Damon
damon,
we had such problems already in other projects and mainly this is because the JVM sometimes detects wrong timezones (no idea what the reason is for this). The timezone is stored in the system property "user.timezone".
Could you please try to start the application with your timezone by adding the parameter "-Duser.timezone=Europe/Berlin" to the java call?
The timezone could be one of the zones listed (e.g.) at http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/r...
And thatnks for the hint, we will add the file realm.* in the jetty files to the list of files that should not be overwritten.
Regards
Heller
damon,
if you are using windows and use the AS2.exe file please use the following script to start the AS2 server, this should fix the timezone to Europe/Berlin:
-------------------
set CLASSPATH="as2.jar";"jetty\start.jar"
call :appendJarsAndZips jlib
call :appendJarsAndZips jlib\jms
call :appendJarsAndZips jlib\mina
call :appendJarsAndZips jlib\wings
set JAVA_HOME=jre
:RunIt
%JAVA_HOME%\bin\java -Xmx256M -Duser.timezone=Europe/Berlin -Xms32M -classpath %CLASSPATH% de.mendelson.comm.as2.AS2
:appendToCP
set CLASSPATH=%CLASSPATH%;%1
goto :EOF
:appendJarsAndZips
for %%D in (%1\*.jar,%1\*.zip) do call :appendToCP "%%D"
goto :EOF
----------------------
Regards
Heller
Since there is no "installer" per se for Linux, can you please provide a list of which files should be preserved? I know there are at least two containing certificates, and the jetty/etc/realm.properties mentioned above that contains the web interface passwords.
What else do I need?
Not a big problem by any means, but something that ought to be corrected in future releses: The start and stop sh scripts are in DOS format instead of Unix format.
neil,
please send me the working start and stop scripts in unix format, I will add them to the next release.
Thanks for the hint.
Regards
Heller
neil,
the files to keep during the update are
certificates.p12 (your keystore for encryption/signature)
jetty/etc/jetty.xml (your http port settings)
jetty/etc/keystore (your keystore if you are using SSL)
jetty/etc/realm.properties (your usr/passwd for the web client)
all files in the dir "notificationtemplates" (your mail notification templates)
Regards
Heller
I have emailed them to you.
neil,
thanks, I received your files and have already checked in the start scripts. Btw I sent you some mails a week ago, you seem not to receive my emails, please have a look into your junk folder?
Regards
Heller
I added a patch for the b29 to sourceforge, its the file patch_b29.jar in the sourceforge.net download folder "patch_b29".
After installing the mendelson opensource AS2 server 1.1 b29 please replace the installed "as2.jar" by this file (please rename the downloaded file "patch_b29.jar" to "as2.jar") before starting the server. Please remember that this patch is mainly not required, only if you are running into update problems.
It fixes the following problems:
*French translation problem in the partner panel (thanks to Eric)
*DB Update problem (thanks to Neil)
*Transaction counter fixed in the GUI
Regards
Heller
Because I think it is dangerous to unzip in production directory, I created :
AS2common/
AS2b27/
AS2b29/
AS2 -> AS2b29
In AS2common is all common files ( .p12 , archive directories etc... except databases (but it could be nice also, but I prefere to copy AS2_DB files in new release directory, in case of ... problem)).
Then I do a soft link in release directory
AS2b29/certificates.p12 -> ../AS2common/certificates.p12
Finally I do a soft link on release I want to run :
AS2 -> AS2b29
Ans stop/start scripts is always using ~/AS2/mec_as2_start.sh
I think it could be nice to reconsider the package structure like this example (or another way) to :
1) Avoid certificates.p12 (and other important file) unintentional removal
2) Change quickly the release (up or back)
Just my humble opinion...
In each zip package a
common.dist/ directory that must be renamed manually at first installation to common/
In this directory all local specific files (first 'dummy' certificates.p12, configs, archives (by default, or change in parameters) etc...)
For upgrade, simply keep remove common.dist and use your already present common/ directory.
All specific to release in a $release directory :
b29/
then create a env script in ROOT directory wich create a env variable for which release must be run .
as2.$OS.env that set (Example):
$MEC_AS2_CURRENT (linux)
%MEC_AS2_CURRENT% (windows)
to 'b29'
then start/stop scripts in ROOT directory just launch
$MEC_AS2_CURRENT/mec_as2_start.sh
or
$MEC_AS2_CURRENT/mec_as2_stop.sh
because start/stop script can be specific for a release, why not...
So : unzip -1 mendelson_opensource_AS2_1.1_b31.zip
_______________________________________
common.dist/...
b31/...
as2.win.env
as2.lin.env
mec_as2_start.bat <- source as2.win.env
mec_as2_stop.bat <- source as2.win.env
mec_as2_start.sh <- source as2.lin.env
mec_as2_stop.sh <- source as2.lin.env
______________________________________
If you are already using b29
you have (on linux) :
common/ <- Your very important directory
common.dist/ <- you can remove if you want
b29/
b31/
as2.lin.env <- older 'b29' was crunched with new env 'b31'
mec_as2_start.sh
mec_as2_stop.sh
If you start, b31 will be launched.
But if you want to go back, simply edit as2.lin.env
and change MEC_AS2_CURRENT variable to 'b29'.
Smart ? isn't it ?
I found that an email from you was blocked on Sept 21. I don't have the message. I have whitelisted the mendelson.de domain so hopefully that won't happen again.