Prognosis Installation and Configuration

Before the SQL Reporting Solution can be installed, a Management Server installation must exist on a server in the topology, refer to the Deployment Scenarios with SQL Server and decide on how the deployment will best suit the deployment requirements.

Once the topology has been decided, the Prognosis software must be installed on either a dedicated Reporting Server (aka Management Server) or the MS SQL Server. The following information is provided for either scenario and relates to the Reporting Server that is running Prognosis and also the SQL Reporting solution.

Prognosis and SQL Reporting Compatibility

Starting from version 11.5, the Prognosis version and the SQL Reporting version must be the same version, for this release that version is 11.9.

This has been made easy, as the SQL Reporting installer now comes bundled with the Prognosis installer, so it is mandatory to install the same Prognosis version in order to access the SQL Reporting installer.

Install the Management Server

During the installation and configuration of Prognosis on the Reporting Server (or MS SQL Server), the following considerations must be made:

  • Before starting the installation of the Management Server, ensure that the Prognosis license file contains the Insight Runtime (INR) product license.

  • During installation, on the Prognosis Components selection screen, select the 'Management Server' component, it is also recommended to select the 'Windows Client' as well.

  • After the installation has been completed, it is recommended to verify that Prognosis is receiving data in order to make verifying a successful deployment easier. Then the SQL Reporting can be deployed.

Install the Management Server using the Installation Procedures for Windows installation procedure.

Management Server Configuration

On the Reporting Server, ensure that no data is lost during SQL server outage situations. It is recommended that the Store and Forward for ODBC Collections is enabled. For further information, refer to Store and Forward (SAF) for ODBC Collections.

Monitoring Server Configuration

To ensure that no data is lost in outage situations, it is recommended that the Store And Forward (SAF-SIZE) setting for the connected Reporting Server be added into the NETWORK Configuration on each Monitoring Server. The size should be set large enough to store at least one day’s worth of collected data in the event of an outage. For further information refer to Store and Forward Facility (SAF) for Database Collections.

The following example sets a SAF_SIZE of 2000 MB for data collections destined for the server \PRGN-RPT:

SUBSYS NETWORK

SAF-SIZE ( \PRGN-RPT, 2000 )

For further information about outage handling see the Outage Handling for Reporting Solutions.

Monitoring Avaya Communications Manager

If this deployment of Reporting Advanced is monitoring Avaya Communications Manager, then additional configuration is needed to ensure that required data is collected for the Unified Communication Report Pack.

Without this configuration, data will be missing from various pre-packaged Avaya reports.

Edit the <Prognosis_Home>\Server\Configuration\irAvaya_PBX.ini file, and ensure the AdvancedReporting setting is set to true:

[SAT]
AdvancedReporting = true
Provide feedback on this article