Skip to main content

Roles and Behaviors

Last updated March 2020

Certain roles and behaviors are set up during installation. An overview of each is provided below:

  • Platform nodes , apart from the log aggregator, handle message generation and transmission along with the traditional functionality of Momentum. When performing a cluster installation, you must begin with a Platform node. This initial node displays as nodename(Manager) on the summary installation screen. It functions as the cluster manager and configuration server, in addition to log aggregator. You must reference it (using the fetch-config option) when installing additional nodes. The Manager can be part of the Cassandra cluster, but it is not required. For help determining the necessary number of nodes, see “Redundancy”.

  • Analytics nodes handle UI reporting capabilities, the Analytics database, and the REST server. For help determining the necessary number of nodes, see “Redundancy”.

  • Message Generation enables you to inject messages using HTTP and to use the Engagement Tracking service. It is a licensed feature. For a detailed description, see “Message Generation”.

  • The Engagement Tracking service enables you to track opens and clicks. This option is only available if you are licensed for Message Generation. During installation, be prepared to identify the Platform node that will perform this function. This machine must be accessible to other nodes in a cluster configuration, open to the Internet, and have an active DNS name.

    Only one server can perform this function. It is identified during installation and assigned to the engagement_tracking_host option in the msg_gen.conf file.

  • The Administration account provides access to the web-based UI. The user name is admin. Be sure to retain the password created during installation.

  • The REST server provides access to the API endpoints. Momentum 4 offers a set of REST API that enables client applications to integrate with Momentum and perform actions associated with message generation and reporting. The REST API greatly enhances the feature set of the HTTP listener provided in Momentum 3.14 and later. See the Momentum 4 REST API documentation.

  • The web-based UI provides a flexible, easy-to-use interface to perform various tasks related to message generation and reporting. This application runs on an Analytics node, which is identified during installation. If this node fails in a cluster configuration, another arbitrary Analytics node assumes UI duties. For additional information about the UI, see Getting Started with the Web-based User Interface .

  • Cluster log aggregation applies only if you require aggregation of log files in a cluster configuration. The Manager node functions as the log aggregator. When you choose log aggregation during installation, the required ec_logger module is created in the ecelerity-cluster.conf file on the Manager.

Was this page helpful?