Management Console architecture

MC accepts HTTP requests from a client web browser, gathers information from the database cluster, and returns that information to the browser for monitoring.

MC accepts HTTP requests from a client web browser, gathers information from the database cluster, and returns that information to the browser for monitoring.

MC components

The primary components that drive Management Console are an application/web server and agents that get installed on each node in the OpenText™ Analytics Database cluster.

The following diagram is a logical representation of MC, the MC user's interface, and the database cluster nodes.

Application/web server

The application server hosts MC's web application and uses port 5450 for node-to-MC communication and to perform the following:

  • Manage one or more database clusters

  • Send rapid updates from MC to the web browser

  • Store and report MC metadata, such as alerts and events, current node state, and MC users, on a lightweight, embedded (Derby) database

  • Retain workload history

MC agents

MC agents are internal daemon process that run on each database cluster node. The default agent port, 5444, must be available for MC-to-node and node-to-node communications. Agents monitor MC-managed database clusters and communicate with MC to provide the following functionality:

  • Provide local access, command, and control over database instances on a given node, using functionality similar to Administration Tools.

  • Report log-level data from the Administration Tools and the database log files.

  • Cache details from long-running jobs—such as create/start/stop database operations—that you can view through your browser.

  • Track changes to data-collection and monitoring utilities and communicate updates to MC .

  • Communicate between all cluster nodes and MC through a webhook subscription, which automates information sharing and reports on cluster-specific issues like node state, alerts,and events.