Setup for Global Command Center

The Global CommCell is created by deploying the core Commvault components—CommServe, Web Server, Command Center, Hub Server, and Global Configuration Manager. This deployment enables centralized aggregation, monitoring, and configuration of all registered Service CommCells. The Global Command Center functions solely as the access portal for this environment.

Commvault Components

The following components must be deployed as part of the Global CommCell:

• CommServe

  For information about installing the CommServe Server, see Server Installations

• Web server

  Along with Web server, install the following packages:

  • Global Configuration Manager

  • Hub Service

  For information about installing the Web server, see Installing the Web Server.

  Note

  Although multiple Web servers can be installed within a CommCell, the Global Configuration Manager and Hub Service may also be optionally installed on a separate machine.

• Command Center

  For information about installing the Command Center, see Installing the Command Center

For supported deployment models and failover requirements, see Deployment Models and Failover Requirements

Set up a Global Web Server

Configure the required Commvault packages on the web server that you want to configure as the Global Command Center.

Enable Global Configuration Manager

You must enable the Global Configuration Manager to allow the Global Command Center to create blueprints and synchronize entities across Service CommCells.

1. Add the bIsGlobalCommcell setting and configure its value to true.

2. Restart Commvault services on the Web server and the CommServe to verify that the Global Configuration Manager is enabled.

Configure Global Configuration Manager Application

1. To set the Global Command Center URL on all web servers in your CommCell environment:

   1. Add the globalConfigManagerBaseUrl setting and configure its value as http://<WebServerHostName>:5005/.

   2. Add the baseUrl setting under the WebConsole path and configure its value as http://<DefaultWebServerHostname>:81/SearchSvc/CVWebService.svc/

2. If the other web servers cannot access port 5005 of the default web server:

   1. Configure a static TPPM for the port.

   2. Replace with localhost and update the port to the static TPPM port.

Configure the Hub Service Application

1. Configure the HTTPS proxy server:

   1. Configure an HTTPS proxy server that is accessible from all machines in the environment.

   2. Forward requests to the Hub Service client on port 5010 (via HTTP or HTTPS).

2. To configure HTTPS for the hub service:

   1. Configure the port to 5010.

   2. If an internal HTTPS proxy server is unavailable, add the following registry keys:

      • CVContainer/DotNet/httpsHostName: Hostname of the Hub Server.

      • CVContainer/DotNet/certPath: Path to the .pfx certificate file.

      • CVContainer/DotNet/certPassword: Certificate password.

3. To set the hub server URL on all web servers, add the hubServiceBaseUrl setting and configure its value as https://<hubServiceProxyServer>/.

4. Restart the services:

   1. On the CommServe and Web servers, restart the Commvault services.

   2. Perform an IIS reset.

Verifying Health

After installation, verify that the Hub Service and Global Configuration Manager (GCM) server are operating correctly.

Verify Hub Service Health

To confirm that the Hub Service is running, access one of the following URLs:

• http://localhost:5010/hub/health

• https:///hub/health

If additional troubleshooting is required, review the HubService.log file for detailed diagnostic information.

Verify Global Configuration Manager (GCM) Health

To check the health status of the Global Configuration Manager (GCM) server, access the following URL:

http://localhost:5005/globalconfig/health

After completing all the steps and successfully verifying the health, the Global Command Center is ready to manage and synchronize entities across the registered Service CommCells.