There should be two entries in the "config.ini" which tell us the SSL certificate:
sslKeystorePath=the-path-to-pfx-file-here
sslKeystorePassphrase.enc=here-is-the-encrypted-password-for-the-pfx-file
To include a new certificate, you can adjust these two entries accordingly. Please note: If you enter a new password, change the entry sslKeystorePassphrase.enc to sslKeystorePassphrase and enter the password in "plain text" first. The server will then encrypt the password the next time it is started and save it again as sslKeystorePassphrase.enc.
After you have made the changes, please restart the application so that they are applied.
FAQ 231
To find out why no statement data is displayed, please check the following things:
Have you already set up a fetch schedule for the bank statements (Settings -> Fetch schedules) and executed it?
If yes: Please check which authorizations the bank has set for you to collect the statement. To do this, an initialized user would have to select the appropriate bank under "Banks" and look in the "Order types" tab to see which order types for "Tagesauszüge" (statements) are entered there. "C53" and/or "STA" (and possibly others) are to be expected.
Please also check which order type is set on the bank's settings page in the "Account statements" tab for "Account statements". It should be an order type for which you also have permission (see previous step). Here C53 = "camt.053" and STA = "MT940". If authorization is only available for C53 and MT940 is set here, you should switch to camt.053. Similarly, if you only have authorization for STA and camt.053 is set here, you should switch to MT940.
Under "Orders" -> "Retrieved files" -> "Retrieve file from bank" you can test for the previously determined order type(s) whether account statements can be fetched via manual retrieval. Select the bank, enter "C53" or "STA" as the order type and select "from the current provision". Here, there is direct feedback as to whether the fetching was possible and whether any data was available. If a blue message appears for both order types that no data was available, then the bank actually does not offer statements for download - please contact your bank directly in this case to clarify why this is the case. If statement data could be retrieved, please check whether this is also displayed under "Account statements".
If the fetched statements are not displayed: A scenario that occurs frequently is that the bank authorizes both C53 and STA, but only provides account statements for STA. If the fetch schedules are now running with C53, they will not receive any data. In this case, the fetch schedules should be changed to STA/MT940 (change the format from camt.053 to MT940 in the bank's "Account statements" tab). After that, the fetch schedules should be restarted again to get the data.
FAQ 248
BL Banking Web can be updated automatically by running the included "Update Check" program: If you have created an entry in the Start menu during the installation, you can call up the menu item 'Update Check' from there. Otherwise you can start the program UpdateCheck.exe directly via the file manager. This is located in the "bin" folder inside the installation directory, hence by default in C:\Program Files\blbankingweb\bin. An Update-Wizard will guide through the update process in both cases. If you have no graphical interface available/only have shell access to the server, you can start UpdateCheck with the flag "-c" to work in the terminal.
Alternatively, you can download the newest version for your platform directly from the following links and re-install the program in the current installation directory.
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
Save the downloaded file in the installation directory. Run the file there to update the existing installation. In the case of pure terminal access, you must use the "-c" flag here again (e.g. "sh blbankingwebunix
After the program update is complete, the database may be updated in the background, which may take a few minutes. If the BL Banking Web Service is not directly accessible after the update, you should 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 (Section 5): https://www.blbanking.de/manual/BLBankingWebInstallationInstruction.pdf
The changelog and specific update notes can always be found at this URL: https://www.blbanking.de/license/changeweb?lang=en
FAQ 249
An administrator can unlock a locked user. To do this, please log in with the administrator and navigate to “Settings” -> “User administration. In the "Password errors" column of the user table there is a "Reset password errors" button for the blocked user. Click this button to unlock the user.
If the user has forgotten their password and is unable to log in even after resetting the password error counter, the user must be reset. Please note: This will also deactivate the user's EBICS access (or accesses), so the user will need to initialize themselves again at the bank (or banks) afterwards. To reset the user, the administrator must click on the user's checkbox in the user management table, click on "More actions" and then click on "Reset user password". In the following dialog window you can assign a new password for the user, which they can then use to log in again. If the checkbox "Also lock user at the bank" is displayed, it should be activated to make sure that a new initialization is possible immediately after the password change. Click "Submit" to confirm the password reset. After the user has logged in again with the password you assigned, they must first assign a new password of their own and then re-initialize for all banks where they were initialized.
FAQ 250