- 20 Sep 2023
- 1 Minute to read
Managing the CTERA Messaging Service
- Updated on 20 Sep 2023
- 1 Minute to read
The CTERA Messaging Service enables sending notifications from the portal to various consumers, for example the Varonis Data Security Platform and the Edge Filer Syslog service, which are connectors running on top of the CTERA Messaging Service. Some features such as managing local quotas on edge filers also require the CTERA Messaging Service.
Notifications are sent asynchronously in the background and are created in real-time from portal events.
Messaging tasks can be performed in the global administration view only.
CTERA Messaging Service Requirements
The CTERA Messaging Service must be installed on CTERA Portal application servers and not on preview servers.
For port requirements, see Port Requirements.
For production environments that use the messaging service, the CTERA Portal must include three application servers defined as messaging servers, that are neither the main, primary, database server nor the replication, secondary, server. For each messaging server you must add an extra 16GB RAM to the server RAM and a minimum of 250GB storage.
The additional RAM and storage requirements for the CTERA Messaging service must be applied to the server disk and not to the data disk.
For a POC, small, or test environment, with a single server deployment, the requirement is a 64-bit virtual machine with 4 vCPU, 32GB RAM, 250GB SSD storage.
In a test deployment with messaging, you specify the primary database server as the messaging server. If you defined more than one server for the test deployment, you cannot set the primary database server as a messaging server and you then require 3 application servers.
CTERA recommends contacting your CTERA account manager to ensure correct sizing.
To move from a small POC environment to a production environment, see Moving From a Single Server Environment to a Multiple Server Environment.
Enabling the CTERA Messaging Service
Before you can set up the CTERA Messaging Service in the user interface, you must first turn it on by running the following CLI:
set /settings/platformServicesSetting/enabled true