---
title: "Managing Portal Servers"
slug: "managing-portal-servers-2"
tags: ["8.2", "Portal"]
updated: 2025-01-02T13:36:05Z
published: 2025-01-02T13:36:05Z
canonical: "kb.ctera.com/managing-portal-servers-2"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.ctera.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Portal Servers

As a global administrator, you can manage the servers on which CTERA Portal is installed.

CTERA Portal servers are Tomcat servers (Apace Tomcat) running on CentOS Linux machines. The database used by the CTERA Portal is a PostgreSQL database.

You can use third-party tools to monitor the tomcat servers and portal database. For example, Nagios, www.nagios.com, provides complete monitoring of CentOS Linux operating systems, including operating system metrics, service state, process state, and file system usage. To monitor the database you can use a tool such as Open PostgreSQL Monitoring (OPM).

          **Note**

          

For details about adding servers, refer to the [installation documentation for your environment](/v1/docs/installing-a-ctera-portal-5).

CTERA monitoring is available using external tools. CTERA officially supports Datadog and Nagios monitoring systems.

## Viewing Servers

**To view the CTERA Portal servers:**

1. In the global administration view, select **Main > Servers** in the navigation pane.  

The **Servers** page is displayed, listing all the servers for the CTERA Portal.  

![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-RS87F3Y4.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A51Z&se=2026-11-11T05%3A33%3A51Z&sr=c&sp=r&sig=9%2FxbK1xENY3ES%2F%2Bs54yA7h3hdNpM4aBYB9Irs8Ow3Fg%3D)
2. To view server settings, click the server name.  

The server window is displayed with the server name as the window title.

For details refer to [Editing Server Settings](/v1/docs/editing-server-settings-5).

## Initializing Server Modules

Some of the portal infrastructure takes a long time to initialize. To make the installation process faster the relevant modules are started in background as a separate task. The portal can be used even before these modules are initialized.

If a server is added to the portal cluster the background job will run to update the modules on every server.

If the server infrastructure has not been successfully deployed, you can deploy it manually, by running the following [CLI](/v1/docs/execute-cli-commands-from-the-global-admin-user-interface): `platform-services rerunlazyinstall --force`

The relevant modules are started for every server and the status is displayed in the **Servers** page. ![image.png](https://cdn.document360.io/30792387-cdcb-4791-aa14-94929bbcd3fe/Images/Documentation/image-1JR6C2AT.png?sv=2026-02-06&spr=https&st=2026-11-11T04%3A33%3A51Z&se=2026-11-11T05%3A33%3A51Z&sr=c&sp=r&sig=9%2FxbK1xENY3ES%2F%2Bs54yA7h3hdNpM4aBYB9Irs8Ow3Fg%3D)