MES settings affected when the HTTPS port is changed
- Last UpdatedFeb 06, 2025
- 2 minute read
If the System Management Server (SMS) or common platform HTTPS Port number is changed, the following MES components are affected and need to be reconfigured in the post-install Configurator.
DB/MW communication
-
If the SMS HTTPS Port number is changed, on the AVEVA Identity Manager tab change the AIM HTTPS Port number to match it and reconfigure the DB/MW Communication component. See Configure MES middleware AIM client registration.
-
If the SMS and MES middleware are on different nodes and the common platform HTTPS Port number is changed on the MES middleware node, reconfigure the DB/MW Communication component on that node. See Understand when to reconfigure the DB/MW Communication component.
Middleware proxy
-
If the SMS and MES middleware are on the same node and the HTTPS Port number is changed, change the proxy HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy settings.
-
If the SMS and MES middleware are not on the same node and the common platform HTTPS Port number for the MES middleware node is changed, change the proxy HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy settings.
-
If the SMS is changed, on the AVEVA Identity change the proxy AIM Host Name to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy AIM client registration.
-
If the Common Platform HTTPS Port number is changed, change the proxy AIM HTTPS Port number to match it and reconfigure the Middleware Proxy component. See Configure the MES middleware proxy AIM client registration.
Web portal
If the SMS HTTPS Port number is changed, change the AIM HTTPS Port number to match it and reconfigure the Web Portal component. See Configure the MES Web Portal component.