How does BxEngine connect to the network
BxEngine
BxEngine is a Windows service that run on the main application server. The app server could be on premise or in the cloud.
BxEngine uses outgoing communication to BxEngine cloud services, including Azure Relay services.
| Service | Address | Direction | Type |
| License | license.bxsoftware.no | Outgoing | 443/HTTPS/TCP |
| BxAPI | api.bxsoftware.no | Outgoing | 443/HTTPS/TCP |
| Azure Relay** |
|
Outgoing | 5671/9350*/9351/9352/ HTTP*/HTTPS/TCP |
| MS SQL | SQL SERVER | Outgoing | 1433/TCP |
References:
Microsoft Azure Relay - https://docs.microsoft.com/en-us/azure/azure-relay/relay-port-settings
Microsoft SQL Server - https://docs.microsoft.com/en-us/sql/sql-server/install/configure-the-windows-firewall-to-allow-sql-server-access?view=sql-server-ver15
* Some scenarios
** MS Azure uses scale-units, and outgoing connections may vary on DNS addresses ranging from g0-prod-db3-001-sb.servicebus.windows.net to g31-prod-db3-001-sb.servicebus.windows.net
- https://techcommunity.microsoft.com/t5/messaging-on-azure/open-outbound-port-requirements-and-ip-address-whitelisting/ba-p/370828
- https://docs.microsoft.com/nb-no/archive/blogs/servicebus/azure-wcf-relay-dns-support
BxSmartPrintPro
BxSmartPrintPro is a Windows service that could run on the main application server or a local computer in the same network as the customers printers. BxSmartPrintPro handles printing and communication with the local Windows print queues.
BxSmartPrintPro connects to the cloud, and to the local print queues.
| Service | Address | Direction | Type |
| License | license.bxsoftware.no | Outgoing | 443/HTTPS/TCP |
| BxAPI | api.bxsoftware.no | Outgoing | 443/HTTPS/TCP |
| Azure Relay | bxsoft.servicebus.windows.net | Outgoing | 5671/9350*/9351/9352/ HTTP*/HTTPS/TCP |
References:
Microsoft Azure Relay - https://docs.microsoft.com/en-us/azure/azure-relay/relay-port-settings
*Some scenarios
BxMobile / Hand terminals
BxMobile is the client running on dedicated scanner devices, or Android/iOS mobile phones. BxMobile connect to our cloud services with outgoing https/443.
| Service | Address | Direction | Type |
| BxAPI | api.bxsoftware.no | Outgoing | 443/HTTPS/TCP |
ERP Integrations
ERP Integrations work from the BxEngine on the main application server to the ERP-system. Network communication is dependent on the ERP-system, and choose integration method (where applicable). BxEngine support often uses the ERP-systems custom APIs, rest/soap/web service based APIs, SQL connections or file based integrations (Local/SMB/FTP etc).
BxWebManager and BxAdmin
BxWebManager and BxAdmin is cloud hosted applications hosted by BxSoftware at app.bxsoftware.no all communications is in-browser and secured with https. Both applications backends connect to BxCloud API for authentication and working with customer data.
3rd party integrations
Consignor OnPremises
BxSoftware supports file-based integration with Consignor OnPremises (COP). File communication is either local or by SMB network from either BxEngine or BxSmartPrintPro. When the ERP/BxEngine is installed in a different network that Consignor Server, BxSmartPrintPro will act as a communications proxy through our cloud api.
Consignor Shipment Server
Consignor Shipment Server integration uses a web services API from BxEngine to Consignors cloud services (HTTPs/443)
Logistra Cargonizer
Logistra Cargonizer integration uses a web services API from BxEngine to Cargonizers cloud services (HTTPs/443)
Axia Frakt
Axia Frakt integration uses a web services API from BxEngine to Axias cloud services (HTTPs/443)
Unifaun Online
Unifaun Online integration uses a web services API from BxEngine to Unifauns cloud services (HTTPs/443)
