The CommServe Port Forwarding Gateway Configuration workflow can be used to route traffic via Commvault tunnels to communicate across third-party firewalls when there is port restriction in place. It also can be used to route traffic from infrastructure machines to a standby CommServe server after failover.
Examples of third-party firewalls include the following:
-
Setting up a standby CommServe host in the cloud.
-
Connecting a remote application (for example, the Web Server or Workflow Engine) with an ODBC connection to the CommServe host.
-
A firewall between the CommServe server and other Commvault entities, such as Web Server, Web Console, Java GUI, Custom Reports Engine, Workflow Engine, and Cvcloud.
The CommServe Port Forwarding Gateway Configuration workflow must be run on the production CommServe host to add (or delete) port forwarding gateways.
Choose one of the following procedures based on how you would like to configure port forwarding gateways:
-
Inserting a Specific Configuration for All Clients That Require Port Forwarding Gateways
-
Inserting Separate Port Forwarding Gateway Configurations for Each Client
After running the CommServe Port Forwarding Gateway Configuration workflow, you need to connect the Web Server or Workflow Engine to the CommServe computer. For more information, see Connecting the Web Server or Workflow Engine to the CommServe Computer.