With Be.ENERGISED a connection to the worldwide roaming network of Hubject (Intercharge) can easily be achieved. The following article describes the necessary configuration settings to establish a connection from Intercharge to your be.ENERGISED instance.
To prepare be.ENERGISED for using Intercharge, you must make the basic settings for using roaming interfaces. To do this, navigate to the Roaming/Intercharge Network menu item in your be.ENERGISED instance and select Settings here. Then you have the possibility to make the necessary settings for EMP and CPO instances.
In this menu you can configure the operator and provider ID information. This information can be obtained from Hubject.
After you have completed the CSR (Certificate Signing Request) from Intercharge and received a certificate, you must upload this certificate to the administration. Click the button "Upload certificate" and select the PEM file received from Hubject. If the certificate has been uploaded, you will see detailed information about the certificate to the right of the button. If no data or the correct data displayed is wrong, the certificate file is incorrect. Please check the settings or contact our support.
Finally, select the interface endpoint; it defines whether you want to connect to the productive or the test system of Hubject.
Configuration of the Intercharge Platform
After you have made the relevant settings in be.ENERGISED, you have to make some more additional settings on the Intercharge platform. Please navigate to the Intercharge administration page at https://portal.hubject.com and log in with your Hubject access data.
Please go to Service Type Settings and select Authorization.
Here you can configure the interface endpoint.
Please use the following setting here:
Service URL: https://INSTANCE.htb.solutions:443/roaming/interfaces/intercharge/authorization
Replace "INSTANCE" by your instance name so that the URL is then e.g. https://meine-beenergised-domain.htb.solutions:443/roaming/interfaces/intercharge/authorization
Online Requests: Yes
Broadcast Requests: Yes
Server certification: "User certificates