Fibunet (Import)

Extraction of data from Fibunet accounting for import into Bilendo.

Overview

Here you will find specific information for connecting FibuNet. This is relevant for all customers who use FibuNet as their system.

There are 5 important points in total:

Fibunet System Architecture

Here you can find the Fibunet system architecture, data types and field definitions.
→ To Fibunet Architecture

To secure the connection, FibuNet provides a certificate. While the connection is encrypted, the certificate cannot be verified by external parties. Therefore, access attempts may be rejected.
To address this issue, we recommend setting up your own SSL certificate on a subdomain. You should set up the subdomain in this format:
fibunet.yourdomain.com
In Fibunet, you can then store your own TLS/SSL certificate in the configuration under "TLSCert and TLSKey".

By default, the REST server is configured to be accessible only locally on the server.
To allow access from external IP addresses, these must be enabled in the Fibunet.ini file.
You can find the INI file in the FibuNet data directory: …\FibuNetData\FibuNet.ini
In the [FNRestServer] section, enter "0.0.0.0" instead of "127.0.0.1" for the "HttpsBindIP" entry and restart the FNRestServer service.
After this, the REST server for HTTPS is also bound to all external IP addresses of the server.

You must create a Bilendo user in FibuNet that has access to the relevant company codes (as agreed with the department).

We need the following data in total:

This is the list of static IP addresses through which Bilendo will access your API. These may need to be whitelisted in your firewall accordingly.