Communications Manager Control Center

This page displays a list of servers registered with Communications Manager Control Center.

The following information about every server is available:

• The host name of the server as seen from server where Communications Manager Control Center is installed. To access the details of the server, click the host name.

  This page provides general information, information about components that have been installed on the server, and information about the Tomcat services that are running on the server.

  You can click a component's name to open the page with information about this component and its sub-components. This option is available for Contract Manager and Instances. If you access the component page for a Communications Manager Instance, you can also see information about services specific to this Instance that are running on the server.

  To go back to the servers overview, use the breadcrumb button.

  After installation, you can only see the host name of the server where Communications Manager Control Center is installed. It is an internal host name and may differ from the <host> value in the address described above.

• An optional description of the server.

• The port where you can access the Management Service of the server. To obtain the correct value, you can run the InfoPorts.exe tool on the server.

All entries on this page are editable, and you can change the host name, description, and port at will. You can also add and remove entries.

When you add a server to Communications Manager Control Center, you must provide the server's API key. To obtain the key, follow the steps described below:

1. Log in at the remote server.

2. Navigate to the Programs\5.8\Management folder of the Communications Manager installation.

3. Run InfoServer.exe with the Services!Password parameter.

You can only configure the server API key when you add the server to Communications Manager Control Center. It cannot be modified afterwards.

The server API key is a communication password that must be kept secret. If the key has been compromised, you must generate a new one.

1. Log in to the server whose API key was compromised.

2. Navigate to the Programs\2025.3\Management folder of the Communications Manager installation.

3. If the server has Communications Manager Control Center, stop it with StopControlCenter.exe.

4. Run the GenerateNewServerApiKey.exe tool and specify the Services!Password parameter.

5. Copy and save the new server API key displayed in the console.

6. Run StartControlCenter.exe to start Communications Manager Control Center again, if it was stopped.

7. Open Communications Manager Control Center, navigate to the Servers page and remove the server.

8. Add the server again using the new server API key.

You can view the Communications Manager log files of any registered server in Communications Manager Control Center.

1. Open Communications Manager Control Center and navigate to the Servers page.

2. Click the link to the required server.

3. In the General section located at the top of the page, click the ellipsis button.

4. Select the View Log Files option. In the displayed dialog window, select the component and application for which you want to see the log files. If the application has multiple logs, select the required log file.

   Initially, Communications Manager Control Center only displays the last lines of the log file. To view the entire log file, select Show entire file. Depending on the file size, it may take some time to load the entire file.

   The dialog window caches the contents of the log file. When you switch between different log files, remember to click the Refresh icon to get the latest version of the log file from the server.

   When a log file rotates, Communications Manager Control Center displays the latest version of the file.

You can also view a log file for a specific Contract Manager or an Instance.

1. Open Communications Manager Control Center and navigate to the Servers page.

2. Click the link to the required server.

3. Click the link to the required Contract Manager or Instance.

4. In the General section located at the top of the page, click the ellipsis button.

5. Select the View Log Files option. In the displayed dialog window, you can only view the log files for the selected Contract Manager or Instance.

You can start and stop components of a Communications Manager installation in the Control Center.

This requires the user to be logged in as an Administrator with OAuth2 and is only available for components that have been configured. The Control Center itself cannot be started or stopped this way.

This functionality is available both on the Server page and on the Component pages. To access this functionality from the Server page, do the following:

1. Open Communications Manager Control Center and navigate to the Servers page.

2. Click the link to the required server.

3. In the Component section, click the ellipsis button in the row of a specific component.

4. Select the Start or Stop action. The Start action is available if the component is in the Stopped state, and the Stop action is available if the component is in the Started state.

5. Confirm that you want to carry out the selected action.

6. A console dialog appears where you can monitor the progress of the action. Wait for the action to complete, and then click the Close button to close the console dialog.

To access this functionality from the Component page, do the following:

1. Open Communications Manager Control Center and navigate to the Servers page.

2. Click the link to the required server.

3. In the Component section, click on a specific component to go the Component page.

4. In the General section located at the top of the page, click the ellipsis button.

5. Select the Start or Stop action. The Start action is available if the component is in the Stopped state, and the Stop action is available if the component is in the Started state.

6. As above, confirm that you want to carry out the selected action.

7. As above, monitor the progress of the action in the console dialog.