An SSL certificate is required to operate BL Banking Web as a HTTPS server. The SSL certificate can be changed at a later date and must be changed when it expires. The currently valid SSL certificate is made known by two entries in the configuration file.
config.ini
in the installation directory of BL Banking Web. Open the config.ini
in a text editor. The following entries must be changed:
sslKeystorePath=
Here is the path to the certificate. Example: C\:\Program Files\blbankingweb\conf\my-certificate.pfx
sslKeystorePassphrase.enc=
Here is the encrypted password for the certificate.
Replace the path in the entry sslKeystorePath
.
sslKeystorePassphrase.enc
to sslKeystorePassphrase
and enter the password unencrypted (in plain text).When the program is started, the server encrypts the password and saves the entry again as sslKeystorePassphrase.enc
.
You can have BL Banking Web updated automatically by running the included Update Check program.
UpdateCheck.exe
directly via the file manager. This is located in the bin
folder inside the installation directory, by default in C:\Program Files\blbankingweb\bin
.An Update Wizard will guide you through the update process.
If you have no graphical interface available or only have shell access to the server, you can start Update Check with the flag -c
to work in the terminal, under Linux e. g. sh UpdateCheck -c
.
You can download the current version of BL Banking Web for your platform directly.
Download links:
Windows:
https://www.blbanking.de/current/blbankingweb_windows-x64.exe
Unix (archive):
https://www.blbanking.de/current/blbankingweb_unix.tar.gz
Unix (shell script):
https://www.blbanking.de/current/blbankingweb_unix.sh
MacOS:
https://www.blbanking.de/current/blbankingweb_macos.dmg
<Installation directory>/bin/blbankingweb
.In the case of pure terminal access, you must use the -c
flag again, e. g. sh blbankingweb_unix_<version-number>.sh -c
under Linux.
Note: After the program update is complete, the database may be updated in the background, which may take several minutes. If the BL Banking Web Service is not directly accessible after the update, do not exit it until the database update has been completed. The status of the database update can be followed in the installation directory under logs/application.log
.
You can find further information regarding the update in our Intallation Guide for BL Banking Web in Section 5.
The change log and specific update notes can be found online: Revision history BL Banking Web.
BL Bankingnbsp;Web is a server-based application. All application data is stored in a database, including user data and their keys. An H2 database is supplied, which can be installed locally or on a server.
An external database is generally used for multiple users and larger data volumes. You can find more information in chapter Settings – System settings – General. The following databases are supported:
You can transfer the currently used database to a new installation or migrate to another database.
Check database settings
Backup database
Migrate database
Save the following files from the installation directory:
config.ini
.. .conf/production.conf
.. .conf/bl-default.keystore
Install BL Banking Web in the new directory as you did for the first installation.
To avoid a security problem, you must adjust a setting in the operating system.
You can update BL Banking Web if you receive the following message when you start the program: *The new version N.NN.NN is available. You will find the new functions in the Change log. The message does not appear if the setting Inform about new program versions is switched off in your user preferences.
In the case of a server installation (default), the update must be carried out by a system administrator who has access to the server on which BL Banking Web is installed. A data backup is recommended beforehand, especially if you have installed BL Banking Web locally or with an H2 database. Back up the working directory, under Windows by default C:\ProgramData\blbankingweb
.
Update check with installation
With an automatic update check, you can check at any time whether an update is available.
bin
subdirectory of the installation directory, under Windows by default C:\Program Files\blbankingweb\bin
.
3 The wizard checks whether a newer version is available for the installed version.Downloads
.Download installation file directly
As an alternative to the update check, you can download the current installation file for your operating system at any time via the following links:
Windows: https://www.blbanking.de/current/blbankingweb_windows-x64.exe
Unix (archive): https://www.blbanking.de/current/blbankingweb_unix.tar.gz
Unix (shell script): https://www.blbanking.de/current/blbankingweb_unix.sh
MacOS: https://www.blbanking.de/current/blbankingweb_macos.dmg
Specific information on the update can be found in the Change log
<installation directory>/bin/blbankingweb
, in which the executable program file is located, e.g. blbankingweb.exe
. The file name contains the version number, e.g. blbankingweb_windows-x64_N_NN_NN
.Start the update check with the -c
flag.
Example for the command under Linux: sh UpdateCheck -c
Alternatively to the update check, you can download the current installation file for your operating system at any time via the following links:
Windows: https://www.blbanking.de/current/blbankingweb_windows-x64.exe
Unix (Archiv): https://www.blbanking.de/current/blbankingweb_unix.tar.gz
Unix (Shell-Skript): https://www.blbanking.de/current/blbankingweb_unix.sh
MacOS: https://www.blbanking.de/current/blbankingweb_macos.dmg
Install the program in the existing installation directory. In the command line, use the -c
flag again.
Example for the command under Linux: "sh blbankingwebunix<version number>.sh -c
logs/application.log
.Note: During the database update, the BL Banking Web service is not directly accessible. Do not stop the service until the update has been completed.
Further information on the update can be found in the installation instructions for BL Banking Web in Section 5.
To install an update with a graphical user interface, see FAQ 268.