Loading...

Configuring Access to the Commvault Message Queue Using TPPM

If the Commvault Message Queue host/port is not accessible from a Web Console/Command Center computer due to firewall restrictions, you must configure third-party ports to map the local host and local port to the destination Commvault Message Queue server and port.

Procedure

  1. On the Web Console/Command Center client, create an additional setting to map the local host and local port to the destination Commvault Message Queue server and port.

    Note: The Web Console/Command Center client uses Message Broker URL to connect to the Commvault Message Queue on its CommCell. By default, the Web Console/Command Center client uses tcp://serverhostname:8052 to connect to the Commvault Message Queue server and port.

    Use the following values for the new additional setting:

    Name: messageBrokerUrl  

    Category: WebConsole

    Type: STRING

    Value: tcp://localhost:localport/

    Where localport is any local port on Web Console/Command Center client.

  2. 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).
  3. Run the ConfigureThirdPartyConnections workflow to map the TPPM local port to the Commvault Message Queue port via network routes.

    Use the following values when running the ConfigureThirdPartyConnections workflow:

    Source client: Web Console/Command Center client

    Source port number: Local port on Web Console client (which you entered in the new additional setting in Step 1, above).

    TPPM type: None.

    Destination client: Client machine where Commvault Message Queue is installed.

    Destination port number: 8052

  4. Restart the Tomcat service on the Web Console/Command Center client for changes to take effect.

Last modified: 6/5/2019 2:00:16 PM