You can enable automatic static third-party port mapping (TPPM) by adding the isTppmTaskEnabled additional setting to the Command Center computer. This forces the Command Center and the Web Server to communicate using network tunnels instead of direct connections.
Enable Automatic Static TPPM
Note
-
If the Web Server port value is different than the default port value, you must include that value in the TPPM whitelist in the Web Server FwConfig file. Similarly, If the Custom Reports Engine port value is different than the default port value, you must include that value in the TPPM whitelist in the Web Server FwConfig file.
-
If this feature is enabled on upgraded setups, you must include the Custom Reports Engine port in the TPPM whitelist in the Web Server FwConfig file.
-
On the Command Center computer, add the isTppmTaskEnabled additional setting as shown in the following table.
For information about adding an additional setting to a server, see Adding a Setting for Servers and Server Groups.
Property
Value
Name
Category
CVD
Type
Integer
Value
1: Enable
0: Disable
-
If the Custom Reports Engine port (port 80) is not present in the TPPM whitelist in the Web Server FwConfig file, then add port 80 to the TPPM whitelist.
-
Restart CVD services on the Command Center computer.
Verify That Automatic Static TPPM Is Enabled
Web Console Registry
On the Command Center computer, before enabling automatic static TPPM, the Web Console registry will have a default port of 81 or 5000. After enabling automatic static TPPM, the Web Console registry will have the Web Server TPPM port.
Custom Reports Engine Registry
On the Command Center computer, before enabling automatic static TPPM, the Custom Reports Engine registry will have a default port of 80. After enabling automatic static TPPM, the Custom Reports Engine registry will have the Custom Reports Engine TPPM port.
Cvd.log
On the Command Center computer, you will see logs with CvTppmTask, which shows the TPPM ports being used. For example, see the following image:
