mendelson AS4 Files

Installation of the mendelson AS4
---------------------------------
1. Installation (Windows)
Please download the installer and execute it. You are done with the installation.
Start the AS4.exe 


2. Installation (non Windows)
Please install a JVM for your system, must be >= Java 11.
Please download the mendelson AS4 .zip file from the download server. Extract it.
Set the file as2_start.sh to executable and check if the pathes used in the
script fit your java installation and your system.
Execute ./as2_start.sh



Upgrade of the mendelson AS4
--------------------------------
To upgrade the mendelson opensource AS4 from a previous installed version please perform the following steps:

1.Make a backup of the installation directory of the mendelson opensource AS4. If anything happens during the update this backup could be copied 
over the installation and will restore the full state before the upgrade

2.Delete the jlib directory found below the installation directory. If you keep the jlib/**.jar files and then perform the update you will mix up 
old and new libs and anything might happen on program start

3.Upgrade
3.1 Upgrade (Windows) 
Please download the installer, execute it and let it install directly over the existing installation. There are some personal files that must 
not be overwritten. The installer will perhaps ask if you want to overwrite them (depends on the current state), answer with NO to keep your personal settings.
Afterwards start the mendelson opensource AS4 server. It will perform some database upgrades. If any additional steps are required the program will inform you.

3.2 Upgrade (non-Windows)
Please download the mendelson AS4 .zip archive and extract it directly over the existing installation. 
Please copy the following files from your backup (step 1) to the installation:
*certificates.p12 (your underlaying keystore for encryption and signature)
*jetty10/etc/keystore (your underlaying TLS keystore)
*jetty10/etc/jetty.xml (your receipt web server settings, will not be able before 2023 - please do not edit this file!)
*jetty10/jetty.config (jetty config file - you could edit this file for the HTTP server settings)
*notificationtemplates/* (your personal templates for the mail notification, skip this step if you haven't modified them)
*.passwd
*Modify the start script if required (path to java installation etc)

4. Upgrade from mendelson opensource AS4 b31 or older
The older versions (mendelson opensource AS4 b31 or older) came with an embedded jetty9 HTTP server. This has been replaced by a jetty10 
in the current version. The underlaying jetty10 has to be configured using the client. There is nothing you can use from your formerly 
jetty9 configuration beneath the keystore file as the jetty9 and jetty10 configuration is incompatible!
*Please copy the TLS keystore file jetty9/etc/keystore to jetty10/etc/keystore. 
*Please do NOT copy the jetty9/etc/jetty.xml file somewhere - the structure of this config file has been changed and this configuration file cannot be used any longer.
*Please setup the main configuration values for the underlaying jetty10 in the file jetty10/jetty.config - please do not edit the file jetty10/etc/jetty.xml!
*Delete the jetty9 directory. It might also be required to change your classpath to jetty10/start.jar and jetty10/lib/*.jar if you use an older start script


Running the mendelson opensource AS4
-------------------------------------
Under Windows please start the file AS4.exe. Under Linux/Mac OS please install a JRE 11 and edit the file as4_start.sh. Setup the path to the java installation, 
then run the start script after setting it to executable.
There are some important command line parameter:

Windows: The parameter "-console" shows the console output of the start. If any error occurs please have a look at the "log/CCYYMMDD/events directory".

Windows/Linux: If you are using the BDEW profile please use the command line parameter "-enableBrainpoolTLS". This enables the use of the Brainpool curve for TLS,
this is disabled normally. If there are still any connections/authorization problems please use a TLS proxy like stunnel. Please do not forget to set the 
HOST http parameter in this case if your proxy does not set this, else a connection attempt will sometimes result in a HTTP 403.