Preparation for installation of Monitor BI Server

The actions described below should be performed by your IT department or your IT supplier. If you have questions about this or about hardware, you can contact the Monitor Support Center by phone: +46 650 766 03 or by e-mail: support@monitorerp.com.

Monitor BI Server can either be installed on the application server (the Monitor server) or on a separate computer in DMZ. Installation on the Monitor server is the recommended method if Monitor BI should only be used locally in the network. If Monitor BI server should be used outside of the network in DMZ, installation on a separate computer in DMZ is the recommended method. For this installation you also need an SSL certificate for the computer, please see below.

Regardless of the method for installation of the BI server, you are required to have an account in Windows with local administrator rights on the computer where the installation is made. During the installation of Monitor BI server, you get to select an account which will run the services installed in connection with the installation. Then you should select this account. You can use the same account that runs the service for the application server (the Monitor server).

To run Monitor BI, the computer must have Microsoft Windows Desktop Runtime 8.0.3 (x64) or later and Microsoft ASP.NET Core 8.0.3 (x64) – Shared Framework or later. Both are required and need to be the same version.

SSL certificate

Purchase an SSL certificate for the server that will function as BI server. This should be a certificate issued by a certification authority such as Verisign, Go Daddy, or Comodo. Certificates are either issued for the computer's DNS name (e.g., "monitor.yourcompany.com") or for an entire domain (as a so-called wildcard certificate "*.yourcompany.com").

When you receive the certificate file, install it on the server that will function as BI server. The certificate file must be installed with the private key linked to your certificate, so we can then connect this certificate during installation.

Firewall configuration

The tables below describe how firewalls should be configured for Monitor BI server.

When the application server (the Monitor server) was installed, firewalls were configured for communication between Windows clients, the application server, and the distribution server. This means you can skip those parts in the tables below.

The distribution servers provide updates for Monitor ERP, options, and licenses. These servers are maintained by Monitor ERP System AB and are available for the Europe and China regions. The DNS names are cdn-eur-01.monitorerp.com and cdn-chn-01.monitorerp.cn. At present there is one server node per region (node number 01). A server node number 02 will shortly be added (DNS name cdn-eur-02.monitorerp.com and cdn-chn-02.monitorerp.cn respectively).

Network's firewall

Protocol	Port	Direction	Function
TCP	7710	DMZ → LAN	Used for updating the BI server.
TCP	8001	DMZ → LAN	Used by the BI Server for communication with the application server (the Monitor server).
TCP	2638	LAN → DMZ	Used by the BI server for communication with the application server database. Port 2638 is set as default for the database engine SQL Anywhere. Another port can also be chosen.
TCP	1443	LAN → DMZ	Used by the BI server for communication with the application server database. Port 1443 is set as default for the database engine Microsoft SQL Server. Another port can also be chosen.
TCP	5432	LAN → DMZ	Used by the BI server for communication with the application server database. Port 5432 is set as default for the database engine PostgreSQL. Another port can also be chosen.
TCP	8007	LAN → DMZ	Used for updating the BI server. Port 8007 is set as default but when installing the BI server you can choose another port.
TCP	443/80	Internet → DMZ	Used for communication between the BI clients and the BI server. Port 443 is used for SSL; port 80 is used otherwise.

Windows firewall in the application server (the Monitor server)

Protocol	Port	Direction	Function
TCP	7710	Inbound, Outbound	Used for updating Windows clients.
TCP	8001	Inbound, Outbound	Used by BI server for communication with application server.
UDP	8002	Inbound, Outbound	Used by Windows clients to automatically find the application server.
TCP	2638	Inbound, Outbound	Used by the BI server for communication with the application server database. Port 2638 is set as default for the database engine SQL Anywhere. Another port can also be chosen.
TCP	1443	Inbound, Outbound	Used by the BI server for communication with the application server database. Port 1443 is set as default for the database engine Microsoft SQL Server. Another port can also be chosen.
TCP	5432	Inbound, Outbound	Used by the BI server for communication with the application server database. Port 5432 is set as default for the database engine PostgreSQL. Another port can also be chosen.

Windows firewall in the BI server

Protocol	Port	Direction	Function
TCP	7710	Outbound	Used for updating the BI server.
TCP	8001	Outbound	Used by the BI server for communication with the application server (the Monitor server).
TCP	2638	Inbound	Used by the BI server for communication with the application server database. Port 2638 is set as default for the database engine SQL Anywhere. Another port can also be chosen.
TCP	1443	Inbound	Used by the BI server for communication with the application server database. Port 1443 is set as default for the database engine Microsoft SQL Server. Another port can also be chosen.
TCP	5432	Inbound	Used by the BI server for communication with the application server database. Port 5432 is set as default for the database engine PostgreSQL. Another port can also be chosen.
TCP	443/80	Inbound	Used for communication between the BI clients and the BI server. Port 443 is used for SSL; port 80 is used otherwise.
TCP	8007	Inbound	Used by the application server (the Monitor server) to communicate updates to the BI server.