Editing Jameica-hibiscus (section)

=== story: running "Hibiscus Payment-Server" on a Synology DiskStation ===
yes, I know, I should purge this.

* http://Jochen.Hayek.name/wp/blog-en/2015/02/12/hibiscus-payment-server-synology-diskstation/
* http://willuhn.de/products/hibiscus-server/
* https://www.synology.com/en-global/releaseNote/JavaManager
* Synology's JavaManager assists in installing Oracle's JVM <strong>successfully</strong>
* I succeeded running the hibiscus server shell script to start the hibiscus server
* I have operated the hibiscus server successfully for months now on openSUSE VMs
* my previous self-installed Oracle JVM were <strong>unsuccessful</strong> attempts
* just as I operated the openSUSE based hibiscus servers, the Synology BusyBox+IPKG based hibiscus server seems to run <strong>stably</strong> and <strong>successfully</strong> for now
* i.e. "all" my bank accounts, that I can communicate with through HBCI/FinTS, are now getting synchronised to databases on my local NAS twice an hour (or as often as I want); this synchronisation happens <strong>independently</strong> of any desktop or notebook PC being online
* another piece of software (developed by myself) dumps these databases to CSV-like bank statement text files, and informs me of changes to them through XMPP AKA Jabber communication
* corruption of the hibiscus-server databases does not hurt me at all – it is only a means to communicate with the banks – it's just that the bank-enforced HBCI/FinTS communication isn't stateless and stores records on databases   – everything I need in the end are the CSV-like text files – setting up the bank account details on hibiscus-server is a piece of cake