Applies to: Web Console, Command Center
By default, the Web Server contains the Message Queue service as the destination for a Web Console computer and Command Center computer . If firewall restrictions prevent a Commvault Message Queue host and port from accessing a Web Console computer or a Command Center computer, you must configure third-party ports to map the local host and port to the destination Commvault Message Queue server and port.
For information about configuring Web Server access to the Message Queue, see Configuring Access to the Web Server Using TPPM.
Procedure
To map the local host and the local port to the destination Commvault Message Queue server and port on the Web Console/Command Center client, create an additional setting with the following values:
Name: messageBrokerUrl
Category: WebConsole
Type: String
Value: tcp://localhost:localport/
Where localport is any local port on the Web Console/Command Center client.
Note: The Web Console/Command Center client uses Message Broker URL to connect to the Commvault Message Queue in its CommCell environment. By default, the Web Console/Command Center client uses
tcp://serverhostname:8052to connect to the Commvault Message Queue server and port on the Web Server.
Configure the network route between the Web Console/Command Center client and the machine where Commvault Message Queue is installed (for example, the CommServe/Web Server).
To map the port-forwarding gateway to the Commvault Message Queue port via network routes, run the ConfigureThirdPartyConnections workflow with the following values:
Source client: Web Console/Command Center client
Source port number: Local port on the Web Console client (which you entered in Step 1, above)
TPPM type: None
Destination client: Client machine where Commvault Message Queue is installed
Destination port number: 8052
Restart the Tomcat service on the Web Console/Command Center client for changes to take effect.