INOVX V-Suite CORE installations will automatically add program exceptions to the windows firewall for INOVx applications. However, System Administrators may want to configure firewall ports or may need to configure interoffice firewall devices/routers. This topic describes through which ports, INOVx applications are communicating with each other.

The following diagram depicts how applications communicate which each other. 



Database SQL Server inbound ports (1A and 1B)

INOVX installation will not automatically add program exceptions for Microsoft SQL Server. V-Suite CORE communicates with the Microsoft SQL Server Database Engine via TCP. Each SQL Instance on the database server will use a different port. The default instance of the Database Engine uses port 1433, but that can be changed. Instances of SQL Server Express and named instances of the Database Engine use dynamic ports. That means that every time that the Database Engine starts, it identifies an available port and uses that port number. If the named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433. If other instances of the Database Engine are installed, it will probably use a different TCP port. Because the port selected might change every time that the Database Engine is started, it is difficult to configure the firewall to enable access to the correct port number. Therefore, if a firewall is used, we recommend reconfiguring the Database Engine to use the same port number every time. This is called a fixed port or a static port. Refer to this article to configure a SQL Server instance fixed port. Refer to this article for detailed information about configuring Windows Firewall to allow SQL Server access.

INOVx Enterprise Server (IES) inbound ports (2)

V-Suite CORE communicates via a bi-directional channel with IES. Each version of IES has a different default inbound port (2) so that clients communicate with the appropriate version of IES. Please refer to the table at the end of this topic, listing version specific TCP ports for IES.

V-Suite CORE client inbound ports (3)

V-Suite CORE communicates via a bi-directional channel with IES. IES needs to communicate with connected V-Suite CORE clients to deliver database change events at V-Suite CORE inbound port (3). This will by default be the first available port but can be configured via the V-Suite CORE client configuration file.

INOVX Server inbound ports (4)

V-Suite CORE communicates with INOVX services via TCP. Each version has a different default inbound port (4) so that clients communicate with the appropriate version of the service. Please refer to the table at the end of this topic, listing version specific TCP ports.

 

 V-Suite 2017

V-Suite 2018

V-Suite 2019

 IES

 5564 

5565

5566

 ILS

 5700 

5701

5702

 Meridium Integration Server

 9101 

9102

9103

 MIMIR Integration Server 

 9200 

9202

9203

 PHD Integration Server 

 9001 

9002

9003

 PI Integration Server 

 9011

9012

9013

 PCMS Integration Server 

 9210

9211

9212