Prognosis Components

The Prognosis architecture is made up of four components, each of which can be installed on to a single machine or distributed over several different machines, depending upon the particular network environment. During the installation process, a dialog box will be displayed which is used to select which components are to be installed on that machine.

Installing all components onto one dedicated machine may be appropriate in small environments. However, in larger environments, it may be more appropriate to distribute the different components across two or more dedicated machines in order to balance the workload. For recommendations on where these components should be installed please refer to the Deploying for Infrastructure Monitoring and Deploying Transact Monitoring topics, or for Unified Communications (UC) environments please refer to the Deploying for Collaborate Monitoring

The Prognosis components consist of:

Windows Client

The Windows Client is a mandatory component that provides full access to manage and customize all of the Prognosis features, such as; Configurations, Thresholds, Analysts and Displays. Therefore, it is recommended that the Windows Client only be used by System Administrators or operators whose duties require this functionality. In addition to these administrative functions, the Windows Client will also provide access to view the real-time and historical data that Prognosis collects from the monitored environment.

  • The Windows Client must be installed on a machine running the Microsoft Windows operating system.

  • The Windows Client may be installed on the same machine as other Prognosis server components or on a separate machine.

  • At least one copy of the Windows Client must be installed somewhere in the monitored environment and, if required, other copies may be installed on different machines for use by multiple operators.

For most system operators who are simply monitoring data, it is recommended that they make use of the Prognosis Web Application.

Web Application

The Web Application component is used to serve real-time and historical data from the monitored environment to remote web browsers or mobile devices. It is recommended that most system operators who are simply monitoring data make use of the Web Application which is accessed through a standard web browser.

The Web Application is installed on an MS Windows machine and consists of a set of files that are installed into the IIS Web Server directory.

The Prognosis installation requires that the Web Application be installed with either the Management or Monitoring Server component. However, if required, the Web Application can be installed without the active server component onto any MS Windows machine that has IIS installed. When this is done, a configuration procedure is required to connect the Web Application to the active Prognosis Management or Monitoring Server. For details see the Split Deployment of the Web Application Server and Management Server.

Management Server

This component includes the collectors that provide the raw data for Prognosis and may also be used to manage multiple Management or Monitoring Servers that have been installed in an environment. In this topology, the Management Server is used to consolidate all of the collected data for viewing through the Windows Client and/or Web Application.

  • The Management Server may be installed on any Prognosis supported platform.

Monitoring Server

This component includes the collectors that provide the raw data for Prognosis. 

  • For Unified Communications, the Monitoring Server is installed on an MS Windows machine and for the most part, the collection of data is carried out using 'off-board' monitoring.

  • For Payments and Infrastructure, the Monitoring Server is installed on any supported operating system and includes a mixture of 'on-board' and 'off-board' monitoring.

Multiple Monitoring Servers may be installed in an environment in order to balance the workload or to gather data from different platform types.

Management and Monitoring Server Differences

The only difference between the Management and Monitoring Server components is when installed on MS Windows, the Monitoring Server includes the Prognosis SFTP service. The SFTP service is normally only required for the collection of CDR data in UC deployments. In a non UC deployment, or where the SFTP service is not required or may cause conflict, it is acceptable to install the Management Server component in place of the Monitoring Server.

Provide feedback on this article