Changing Ports for the System Management Server

Some communication drivers used with Application Server require additional, manual configuration if you change one or both of the default port(s) used for the System Management Server during initial configuration, or a port used by the System Management Server is changed at any time after that. This additional configuration is required if you use either of the following:

• The Auto Build function in Application Server. The Auto Build function uses either the ABCIP or SIDirect Communications Driver.

• MQTT Communications Driver.

This configuration is not required if you do not change the default System Management ports (HTTP port 80 and HTTPS port 443). However, if a non-default port is configured and then changed back to the default port number, manual configuration is required.

Configure the ports after you have completed all installation and configuration steps, and anytime you change a port number for the System Management Server.

To configure a port for System Management Server

1. As Administrator, open a command prompt or Windows PowerShell window.

2. Run the following command:

   • If you changed the HTTP port, run this command:
     

     netsh http add urlacl url=http://localhost:<changed HTTP port number>/oi/ user=”NT SERVICE\GDIWebServer”

   • If you changed the HTTPS port, run this command:
     

     netsh http add urlacl url=https://localhost:<changed HTTPS port number>/oi/ user=”NT SERVICE\GDIWebServer”

3. Open the Windows Control Panel and select Services.

4. Select Aveva Communication Backend Service and restart the service.