Architecture

The NetScaler MAS database is integrated with the server, and the server manages all the key processes, such as data collection, NITRO calls. In its data store, the server stores an inventory of instance details, such as host name, software version, running and saved configuration, certificate details, entities configured on the instance. A single server deployment is suitable if you want to process small amounts of traffic or store data for a limited time.

Currently, NetScaler MAS supports two types of NetScaler MAS server deployments: single server and high availability.

The following image shows the different subsystems within NetScaler MAS and how communication happens between the NetScaler MAS server and managed instances.

localized image

The Service subsystem in NetScaler MAS acts as a web server that handles HTTP requests and responses that are sent to subsytems within NetScaler MAS from the GUI or API, using ports 80 and 443. These requests are sent to the subsystems over the message bus (Message Processing System) by using the IPC (Inter-process Communication) mechanism. A request is sent to the Control subsystem, which either processes the information or sends it to the appropriate subsystem. Each of the other subsystems—Inventory, Stylebooks, Data Collector, Configuration, AppFlow Decoder, AppFlow Analytics, Performance, Events, Entities, SLA Manager, Provisioner, and Journal—has a specific role.

Instance plug-ins are shared libraries that are unique to each instance type supported by NetScaler MAS. Information is transferred between NetScaler MAS and managed instances by using NITRO calls, or through the SNMP, Secure Shell (SSH), or Secure Copy (SCP) protocol. This information is then processed and stored in the internal database (Data Store).

Architecture

In this article