Deployment and Installation Guide -...

Deployment and Installation Guide Prognosis 11.0

Prognosis 11.0

Copyright

Copyright 2000-2016 Integrated Research Limited (ABN 76 003 588 449). All rights reserved.

This guide is protected by copyright law and international treaties. No part of this document may be reproduced in any form or distributed, and no derivative works such as translations may be made, without prior written permission from Integrated Research. Unauthorized reproduction or distribution of this document or of the computer software, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under the law.

Date of Issue: 28 June 2016 Product Version: Prognosis 11.0

Trademarks

Prognosis and IR are registered trademarks of Integrated Research Limited.

Other product names mentioned in this manual may be trademarks, registered trademarks and/or service marks of their respective owners and may not be used for commercial purposes without express permission from their respective owners.

Third Party Software License Notices

Please refer to the Third Party Software License Guide on the Prognosis installation CD or in the Documentation folder of the Prognosis installation path for details of third party software license notices.

Disclaimer

The information in this guide is published as is and without warranties of any kind, expressed or implied, including those regarding the accuracy or completeness of the information, warranties of merchantability and fitness for a particular purpose, or those arising from a course of dealing, usage or trade practice.

In no event will Integrated Research be liable for any special, incidental, consequential, or indirect damages, or for any damages whatsoever (including, without limitation, those resulting from lost profits, lost data or business interruption) in connection with the furnishing, performance, use, inability to use, or the results of this guide. The information in this guide is subject to change without notice.

Latest Updates

The content in this document was current at the time of publication. However, for the latest updates please refer to the Prognosis Online WebHelp via the User Interface or through:

https://online.prognosis.com

https://online.prognosis.com/

Deployment and Installation Guide

Contents Deployment and Installation ..................................................................................................................... 5 About this Guide ....................................................................................................................................... 6

General Information ........................................................................................................................................... 7

Installation General Information ................................................................................................................ 8 Connectivity .............................................................................................................................................. 9 Firewalls ................................................................................................................................................. 11 License File ............................................................................................................................................ 13 Online Help Center ................................................................................................................................. 15 Port Requirements .................................................................................................................................. 16 Software Security Recommendations ..................................................................................................... 26 Time Synchronization ............................................................................................................................. 27 Virtualization Support .............................................................................................................................. 28

Deployment ...................................................................................................................................................... 29

Deployment ............................................................................................................................................ 30 Prognosis Components .......................................................................................................................... 31 Deployment - Infrastructure .................................................................................................................... 33 Deployment - Payments ......................................................................................................................... 43 Deployment - Unified Communications ................................................................................................... 66

Installation ........................................................................................................................................................ 79

Installation .............................................................................................................................................. 80 Server on MS Windows .......................................................................................................................... 81 Server on UNIX/Linux ........................................................................................................................... 140 Server on HP NonStop ......................................................................................................................... 162 Web Application .................................................................................................................................... 194 Windows Client ..................................................................................................................................... 204 UC Reporter ......................................................................................................................................... 214 Service Packs and Patches .................................................................................................................. 219

Configuration ................................................................................................................................................. 229

Configuration ........................................................................................................................................ 230 Setting up a Management Server ......................................................................................................... 231

Index ............................................................................................................................................................... 233

Deployment and Installation Guide

Deployment and Installation

Before commencing to install the various IR Prognosis components it is strongly recommended that the contents of this guide be carefully studied and understood. Detailed information for the deployment and installation is contained in this guide.

To carry out the IR Prognosis implementation we recommend that the following steps be taken:

Check the various information notices and ensure that any requirements are met.

General Information (page 8)

Become familiar with the various Prognosis components.

Product Components (page 31)

Check the supported platforms and work out an appropriate deployment plan for the Prognosis installation in your environment.

Deployment for Infrastructure (page 33)

Deployment for Payments (page 43)

Deployment for Unified Communications (page 66)

Proceed with the appropriate installation/upgrade on each machine in the environment.

Server on MS Windows (page 81)

Server on UNIX/Linux (page 140)

Server on HP NonStop (page 162)

Windows Client (page 204)

Web Application (page 194)

UC Reporter (page 214)

Service Packs and Patches (page 219)

Where applicable, carry out the required configuration steps for each vendor product to be monitored.

Configuration (page 230)

Prognosis 11.0

About this Guide Before reading this documentation it is expected that the reader will have an understanding of the environment, the hardware and the various software applications that are to be monitored. Where necessary this guide will cover the interaction between IR Prognosis and other hardware/software but it will not provide detailed information about their operations. Please refer to the individual hardware/software manuals and guides for such information.

Audience & Purpose

This Prognosis Deployment and Installation Guide is intended as a reference source for personnel who are responsible for installing and maintaining the system environment. It contains the necessary installation steps required to install Prognosis and any subsequent updates. Information on how to uninstall the product is also included.

General Information

General Information

Prognosis 11.0

Installation General Information This section contains some important setup considerations which should be reviewed before commencing the IR Prognosis installation.

For details see the following sections:

Connectivity (page 9)

Firewalls (page 11)

License File (page 13)

Online Help Center (page 15)

Port Requirements (page 16)

Software Security Recommendations (page 26)

Time Synchronization (page 27)

Virtualization Support (page 28)

Other requirements for specific Prognosis components are contained in the Deployment and Installation sections.

General Information

Connectivity Prior to IR Prognosis version 10.2, communications between servers was not encrypted and backward connectivity was available for at least the previous three Prognosis server versions.

In Prognosis version 10.2 an optional setting was introduced that enabled encrypted communications between servers. With this feature options were available that still allowed connectivity to previous Prognosis server versions.

However, now in Prognosis 11 all communications between servers are encrypted and there is no option to disable this feature. Therefore connectivity with earlier Prognosis servers will only be available with version 10.2 and later servers which have the encryption option enabled.

A Management Server must always be the same or a more recent Prognosis version than its associated Monitoring Servers, The illustration below shows a valid managing scenario where the 10.5, 10.4, 10.3 & 10.2 servers all have the encrypted communication option enabled. Please note that minor Prognosis versions 10.5.1 and 10.4.1 are equally suitable to be managed by a Prognosis 11 server.

With Prognosis 11, if an earlier version server does not have encrypted communication enabled, then that server will not work with a Prognosis 11 Management Server.

As the option to encrypt communications was introduced in Prognosis 10.2, any prior version will not operate with a Prognosis 11 Management Server, as illustrated below.

FIPS Compliance

The changes introduced with Prognosis 11 also provide an option to enable a further level of enhanced encryption on Prognosis MS Windows servers. This option allows Prognosis to comply with Federal Information Processing Standards (FIPS 140-2).

Prognosis versions prior to version 11 do not have the option to be FIPS compliant. Therefore, in order to be FIPS compliant, Prognosis 11 MS Windows servers cannot communicate with non-compliant Prognosis versions. As a result, if FIPS compliance is enabled then all Prognosis Monitoring and Management MS Windows servers must be on Prognosis 11.

For further details see the FIPS Encryption section in the Prognosis ‘Getting Started’ Guide.

Prognosis 11.0

Windows Client

The Prognosis Windows Client can only connect to a server of the same version. For example, a Prognosis 11 Windows Client cannot connect to a Prognosis10 server nor can a Prognosis10 Windows Client to connect to a Prognosis 11 server.

General Information

Firewalls If IR Prognosis is being installed on a network that is configured to prevent connections between machines by the use of firewalls, then this may also prevent Prognosis from making connections between servers.

In situations where only the MS Windows firewall is being used, the Prognosis installer will automatically make the necessary settings. In other cases, the firewall settings will need to be made manually. The following section provides details.

Windows Firewall with Advanced Security (Windows Server 2008 R2 and above)

When the “Windows Firewall” service is running, then the Prognosis installation will automatically make the following changes:

For Management/Monitoring Server installation, the following five firewall rules will be added in order to

allow Prognosis connectivity and CDR delivery:

IR Prognosis - Server Connectivity (%PROGNOSIS_INSTALL%\Server\x64\irnetrtr.exe)

IR Prognosis - Avaya PBX CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_PBX.exe)

IR Prognosis - Avaya Legacy CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_Legacy.exe)

IR Prognosis - Avaya Definity CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_DEFINITY.exe)

IR Prognosis - Avaya RTCP CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irrtcpcol.exe)

In addition, if a Management/Monitoring Server is selected and a Prognosis for Unified Communications license is used (with TMA, SBM, or TCE product codes), one firewall rule will be added to allow CDR

delivery:

IR Prognosis - CDR Delivery (Port 22 with TCP protocol)

If the Web Application is selected, one firewall rule will be added to allow the Prognosis web application

access:

IR Prognosis - Secure Web Site (Port 443 with TCP protocol)

If port 443 is not available the installer will check the availability of port 8080, if this is not available it will continue to search incrementing the port number by 1 each time (i.e. 8081, 8082 etc) until an available port is found.

If the "Windows Firewall" service is not running, then no changes will be made by the Prognosis installation.

If there are any firewall rules that block port 22 or port 443 then Prognosis will disable them and add a

new firewall rule that will allow these ports access.

Other MS Windows Firewall Applications

The firewall will need to be manually configured to provide access for the following application:

Server Connectivity (%PROGNOSIS_INSTALL%\Server\x64\irnetrtr.exe)

In addition, for Prognosis for Unified Communications:

Avaya PBX CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_PBX.exe)

Avaya Legacy CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_Legacy.exe)

Avaya Definity CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irAVAYA_DEFINITY.exe)

Avaya RTCP CDR Delivery (%PROGNOSIS_INSTALL%\Server\x64\irrtcpcol.exe)

CDR Delivery (Port 22 with TCP protocol)

Prognosis 11.0

UNIX

The firewall will need to be manually configured to provide access for the following application:

IR Prognosis - Server Connectivity (irnetrtr.exe)

HP NonStop

The Prognosis base port 1960 plus any necessary vendor specific ports will need to be opened manually across the Firewall. Please refer to the Port Requirements topic (page 16) for details of the required ports.

In order to establish Prognosis connections the port number will need to be opened on the Firewall in the direction of the connection. The Prognosis servers make one TCP/IP connection between them, and that

connection is used for all traffic between the servers.

Uninstall

Uninstallation of Prognosis will revert all firewall settings that have been made, except overriding "Don't allow exceptions" on Windows with old Windows Firewall.

Remove added rules/exceptions

Enable disabled rules

Not reverting "Don't allow exceptions"

General Information

License File

Licensing a New or Upgrade Installation

In most cases an IR Prognosis license will be sent by email as an attached text file. When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files. The installation process will automatically search for a license file in this folder. However, if a valid license is not found an alternative location can be specified or browsed for.

Updated Licenses on an Existing Installation

Over time it may be necessary to upgrade the license file on an existing Prognosis installation. This can occur when additional Prognosis products have been purchased or when an existing product is renewed for an additional time period.

When this occurs, a new license file will be sent as an email attachment. When received carry out the following procedure.

Procedure

Step 1 Save the attached license file from the email to a convenient location.

Step 2 Copy the license file to the configuration directory of each applicable Prognosis installation. When copying, accept to overwrite the existing license file.

The default configuration directories are as follows:

MS Windows: <Install_path>\Prognosis\Server\Configuration

HP NonStop: <Volume>.<PrognosisSubVol>

e.g. $DATA.PRGNOSIS

UNIX: /home/<user>/prognosis/server/configuration

Step 3 After the files have been copied to the configuration directory, restart Prognosis.

For HP NonStop two license files are required, 'license' and 'licext'. These should both be saved as per the instructions above.

For UNIX/Linux installations that do not utilize the Prognosis MS Windows FTP Installation/Upgrade feature, the license files must be FTP'd/uploaded to the UNIX/Linux server in ASCII mode, not Binary mode.

Prognosis 11.0

Checking on License Status

The current status and expiry date of all Prognosis licenses in the network can be viewed from the Prognosis Licenses Display. To access this Display from the Prognosis Web Application use the following procedure.

Procedure

Step 1 Open and log on to the Prognosis Web Application - View Systems Tool.

Step 2 Go to the first (Group) navigation panel and click on Servers.

This will open the& Server Display in the main panel.

Step 3 On the Servers Display, click on the Prognosis Configuration link at the top of the screen.

This will open the Prognosis Status on Entire Network Display.

Step 4 Click on the Licenses link at the top of the Display. This will open the Prognosis Licenses Display.

In the 'Expires' column the expiry date of each Prognosis license will be shown. An orange background indicates that the license will expire within the next 30 days, a red background indicates that the license has already expired.

Multiple entries for a single server may be shown as different products may have different expiry dates in the license file.

General Information

Online Help Center A complete reference guide for the IR Prognosis system and all its associated products is available through the Help button on the Prognosis Web Application or the Help menu on the Windows Client. From both of these interfaces the Help Center is available as a dynamic web site (WebHelp) which will be updated with new or amended information as required. In addition, the Windows Client also offers a local Help Center, via HTML Help (chm), which can be accessed by selecting 'Help > Help Source > Use Local Help' from the Menu bar.

For those customers that have access to IR Prognosis Online, the latest Prognosis Help Center can also be accessed from the 'Knowledge > Online Help' Menu bar item.

https:\\online.prognosis.com

Important Notes

Accessing HTML Help (chm) files over a network

The Prognosis HTML Help files will be installed on the same machine as the Windows Client and in this case local access will not be an issue. However, following a past Microsoft security update #896358 it may not be possible to view the HTML Help files over a network connection. If this is an issue in your environment, the following Microsoft Knowledge Base article may be of assistance:

http://support.microsoft.com/default.aspx/kb/896358

This does not affect access to the web based Help Center.

Accessing WebHelp via the Windows Client on a Virtual Machine

Accessing the WebHelp via the Prognosis Windows Client makes use of Microsoft Internet Explorer functionality. In an MS Windows Virtual Machine it may be found that the default 'High' security setting of IE will prevent the Help Center from opening and a dialog simiar to the following will be displayed:

In this situation, follow the Microsoft instructions and add 'http://help.prognosis.com' to the 'Trusted Sites' dialog box through the Tools > Internet Options menu path on the IE interface. Should this not be possible in your environment, the local Prognosis Help Center from the Windows client will function normally.

http://online.prognosis.com/

http://support.microsoft.com/default.aspx/kb/896358

Prognosis 11.0

Port Requirements IR Prognosis requires the use of a number of Ports on each machine. This section details each of the 'Base' ports that are required and also any other ports that might be required in particular circumstances.

Base Ports

Prognosis reserves the use of a number of ports; starting from the port number specified in the NETWORK configuration, through to that port number plus six. The ports used are:

Port Protocol Executable Usage

<PortNumber>+0 Default 1960

TCP IRNETRTR By default this is the base port. This port is used for; router-to-router, local process to router and Windows Client to router communications where TCP/IP is used. All requests and data messages are sent via this port across nodes as well as to individual collectors that actually gather raw data. It is also the port that the GUI connects to.

On HP NonStop, IPC is used for internal messaging and messaging to other HP NonStop nodes. Therefore, on HP NonStop, this port is only used for Windows Client connections and cross platform (Windows/UNIX) connections.


TCP IRPROMGR Used for connections from child processes back to Process Manager in order to detect process failures and to instigate process restarts. It is used for local communications only.

On HP NonStop this function is performed via IPC, so this port is not used.


UDP IRNETRTR Used to send and receive Auto-Discovery multicasts (UDP protocol) in order to discover other Prognosis Servers. This port is not used if Auto-Discovery is disabled (e.g. if Managing-Nodes are used).

Auto-Discovery between HP NonStop nodes is done via IPC, but this port is still used on HP NonStop for Auto-Discovery of cross platform systems.


N/A N/A Not currently used.


TCP IRLSTNR Used by the Tivoli Integration interface.


TCP IRWASP Disabled. Used by the former Prognosis Web Interface.


TCP IRJVMCOL Listening port for connections from JVM probe (HP NonStop only).

General Information

Changing the Base Port

The default base port used by Prognosis is 1960 with the following six ports also reserved for its use. The installer will check the availability of port 1960 and if this is not available will switch to port 19600. If port 1960 is not available the installer will continue to search incrementing the port number by 10 each time.

The Base port number can be changed after installation by amending the port number in the TCPIP-PORT statement of the NETWORK Configuration; this will also reserve the following six ports for Prognosis use. Prognosis will need to be restarted after amending the NETWORK Configuration for the change to take effect.

Common Ports

The following 'Common' ports are applicable for inbound data to Prognosis and should be enabled where the specified service is to be used, e.g. LDAP authentication.

Port Protocol Usage

22 TCP SSH port used for integration with the EMC Smarts VoIP Availability Manager product. This is used in order to remotely connect to Prognosis and request information via IRCLVIEW.

25 TCP Port for Dispatch Manager email alerts via SMTP.

389 TCP LDAP Non-secure access. Only required if LDAP is to be used instead of Active Directory.

443 TCP Default IIS port between the Prognosis Web Application and the IIS Web Server. If not available, the installer will check the availability of port 8080, if this is not available it will continue to search incrementing the port number by 1 each time up to port 8089.

514 UDP Syslog - Used for system logging

636 TCP LDAP secure access.

6767 TCP Default port between the IIS Web Server and the Prognosis server.

Prognosis 11.0

Ports for Unified Communications

The following vendor specific ports are also used in addition to the set of Prognosis base ports and any required Common ports.

Acme Packet SBC

Port Protocol Usage

22 TCP Open for SFTP connections on the Prognosis side for CDRs pushed from the Acme SBCs.

161 UDP SNMP queries from the Monitoring Server to the SBCs.

Alcatel-Lucent PBX

Port Protocol Usage

21 TCP File Transfer Protocol (FTP) standard port.

23 TCP Common Telnet port to access the CLI interface for the PBX.

161 UDP SNMP queries from the Monitoring Server to the PBXs.

162 UDP Standard port to receive SNMP Traps from PBXs.

AudioCodes SBC

Port Protocol Usage

161 UDP SNMP queries from the Monitoring Server.

5060 UDP Port for receiving RTCP data from the SIP Interface Table.

Avaya Aura Communication Manager

Port Protocol Usage


5005 UDP Port for receiving RTCP packets from Avaya SIP end points.

5022 TCP Common SSH port for the Avaya PBX to issue SAT commands.

5023 TCP Common Telnet port for the Avaya PBX to issue SAT commands.

Only needed for Avaya PBX if SSH is not supported.

50000-50002 TCP Configurable ports for Avaya PBX to push CDR data to Prognosis.

Defaults: 50000 for AVAYA_PBX, 50001 for AVAYA_LEGACY 50002 for AVAYA_DEFINITY.

To use a non-default port see the Non-default CDR Port topic for details.

General Information

Port Protocol Usage

135 and 49152 - 65535

TCP WMI - Dynamic port range used for soft phone host metrics.

For easier firewall traversal this can be configured to use a fixed port with Windows Server 2008 and higher, for details see:

http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v=vs.85).aspx

Avaya Aura System and Session Manager

Port Protocol Usage

22 TCP Open for SFTP connections to the Session Manager for CDRs.



Avaya Communication Server 1000

Port Protocol Usage

22 TCP Common SSH port to access the CLI interface for the PBX.

23 TCP Common Telnet port to access the CLI interface for the PBX.

161 UDP SNMP queries to the Call Server and Signaling Server for server statistics.

162 UDP Standard port to receive SNMP Traps from the Signaling Server.

Avaya IP Office

Port Protocol Usage

161 UDP SNMP queries from the Prognosis Monitoring Server.


Avaya Modular Messaging

Port Protocol Usage

161 UDP Message Storage Server (MSS)

SNMP queries from the Monitoring Server.

135 and 49152 - 65535

TCP Message Application Server (MAS)

WMI - Dynamic port range used for server host metrics.



http://msdn.microsoft.com/en-us/library/windows/desktop/bb219447(v%3dvs.85).aspx




Prognosis 11.0

Avaya Session Border Controller for Enterprise

Port Protocol Usage

161 UDP SNMP queries from the Prognosis Monitoring Server to Avaya SBC-E device.

Cisco Emergency Responder

Port Protocol Usage

22 TCP SSH port set up to collect data.

161 UDP SNMP queries from the Prognosis Monitoring server to Cisco Emergency Responder.

Cisco Express Suite

Cisco Unified Communication Manager Express/Cisco Survivable Remote Site Telephony

Port Protocol Usage


23 TCP Telnet port set up to collect data.

Cisco Unity Express

Port Protocol Usage


23 TCP Telnet port set up to collect data.

Cisco Unified Contact Center Express (CUCCX)

Port Protocol Usage

161 UDP SNMP queries from the Prognosis Monitoring server to Cisco UCCX.

443 or 8443 TCP Standard port on Cisco Clusters for 3rd party applications, such as Prognosis, to retrieve data via SOAP Perfmon..

General Information

Cisco Unified Communications Manager 5+

Port Protocol Usage

22 TCP SSH port for SFTP to collect Call Detail Records (CDR) and Call Detail Diagnostic Records (CMR) from CUCM 5+ clusters.

80 TCP Used for polling Cisco IP phones for QOS and device data via HTTP and/or XML.

161 UDP SNMP queries from the Prognosis Monitoring Server to Cisco CUCM 5+ Clusters.

443 or 8443 TCP Standard port on Cisco Clusters for 3rd party applications, such as Prognosis, to retrieve data via SOAP AXL and SOAP Perfmon.

Standard port on Cisco TelePresence Endpoints to retrieve call statistics.

135 and 49152 - 65535

TCP WMI - Dynamic port range used for soft phone host metrics.



Cisco Unified Computing System

Cisco UCS B-Series

Port Protocol Usage

161 UDP SNMP queries from the Prognosis Monitoring server to Cisco UCS B-Series. SNMP interface for UCS Manager.

Cisco UCS C-Series

Port Protocol Usage


Cisco Unified Presence

Port Protocol Usage

161 UDP SNMP queries from the Prognosis Monitoring Server to Cisco Unified Presence devices.

443 or 8443 TCP Standard port on Cisco Clusters for 3rd party applications, such as Prognosis, to retrieve data via SOAP Perfmon.

Cisco Unity

Prognosis 'on board' monitoring is provided for Cisco Unity, therefore there are no port requirements.



Prognosis 11.0

Cisco Unity Connection

Port Protocol Usage

22 TCP SSH port for SFTP to collect data.

161 UDP SNMP queries from the Prognosis Monitoring Server to the Cisco Unity Connection devices.

443 or 8443 TCP Standard port on Cisco Clusters for 3rd party applications, such as Prognosis, to retrieve data via SOAP Perfmon.

Cisco Unified Border Element (CUBE)

Port Protocol Usage


161 UDP SNMP queries from the Prognosis Monitoring Server to Cisco Unified Border Element devices.

1812 or 1645 and

1813 or 1646

UDP RADIUS Authorization and Accounting ports. The specific ports required will depend on how RADIUS is configured in the environment.

Microsoft Skype for Business

Port Protocol Usage

80 TCP SDN- Port used by the Skype SDN API to send real time inflight voice

quality (For Office 2016 preview client) information to Prognosis. For HTTP this will default to port 80 inbound to the Prognosis server, but it can use a configurable port depending on what is set in the Skype SDN API.

389 TCP LDAP Non-secure access.

636 TCP LDAP secure access.

1433 TCP SQL - Default port used by SQL monitoring.

135 and 49152 - 65535

TCP WMI – Dynamic port range used for server and soft phone host

metrics.



135, 445 and 49152 - 65535

TCP Remote Event Log - Dynamic port range used for remote event log

management.







General Information

Port Protocol Usage

5985 or 5986 TCP Used instead of WMI in NATed Skype environments to collect MS Windows and Skype for Business performance metrics. By default ports 5985 and 5986 are used for HTTP and HTTPS respectively.

Sonus SBC

Port Protocol Usage


1813 UDP Sonus RADIUS listener port. This is the port which Sonus uses when pushing RADIUS accounting information to Prognosis.

Prognosis 11.0

Ports for Contact Center

The following vendor specific ports are also used in addition to the set of Prognosis base ports and any required Common ports.

Avaya Application Enablement Services (AES)

Port Protocol Usage


Avaya Aura Contact Center (AACC)

Port Protocol Usage

162 UDP Standard port to receive SNMP Traps.

135 and dynamic 1024

- 65535

TCP DCE/RPC protocol used to collect Real Time Data (RTD) from the AACC servers.

Note some firewalls support inspection of DCE/RPC protocol, MS Windows should already allow outbound traffic using default Windows firewall rules.

135 and 49152 - 65535

TCP Server statistics from the AACC

WMI – Dynamic port range used for server host metrics.

This can be configured to use a fixed port with Windows Server 2008, and higher, for easier firewall traversal, for details see:


1972 TCP SQL queries from the AACC database.

Avaya Experience Portal (AEP)

Port Protocol Usage

80 or 443 TCP Avaya Experience Portal Manager (EPM) HTTPS port for web service traffic.

161 UDP SNMP queries from the Monitoring Server to the EPM.

162 UDP Standard port to receive SNMP Traps.

Cisco Unified Contact Center Enterprise (UCCE)

Port Protocol Usage

161 UDP SNMP queries from the Monitoring Server

7890 TCP REST Diagnostic API.



General Information

Cisco Voice Portal (CVP) and Cisco Voice XML Gateways

Port Protocol Usage

161 UDP SNMP queries from the Monitoring Server to the Cisco Voice Portal and Cisco Voice XML Gateways.

Verint Impact 360 Infrastructure Monitoring

Port Protocol Usage

135 and 49152 - 65535

TCP Standard WMI ports on all Verint servers

WMI – Dynamic port range used for server and soft phone host

metrics.



162 UDP SNMP Trap port for all Verint alarming.

1433 TCP MSSQL infrastructure monitoring for the Verint database server roles.

Verint Call Recording Assurance

Port Protocol Usage

443 TCP Default HTTPS Verint DAS API port on the Verint Application server.



Prognosis 11.0

Software Security Recommendations Quite often there can be issues which may raise security concerns when installing and operating new software applications. A list of recommendations that should be implemented to overcome any such issues that were detected during the development of IR Prognosis are detailed in the 'Software Security Recommendations' topic in the Prognosis Online Help Center.

General Information

Time Synchronization Due to the time calculations that some pre-packaged Where Clauses use in IR Prognosis, it is important to ensure that all Prognosis servers in the monitored environment are synchronized with a time server. This will avoid missing data from Displays and Database Collections, or Alerts from Thresholds and Analyst rules.

Prognosis 11.0

Virtualization Support Most IR Prognosis servers support operation on a virtual machine, with the following provisions:

Virtualization is supported for:

Prognosis for Infrastructure version 10 and later

Prognosis for Payments version 10 and later

Prognosis for Unified Communications version 10 and later

Prognosis UC Reporter

Virtualization platform metrics

Machine platform metrics, such as Windows CPU busy, from the virtual environment may not be reliable.

Virtualization scalability

The insertion of a virtualization layer introduces significant complexity in scalability calculations. The Prognosis scalability guidelines can only be used as a guide as the impact of other virtual machines is impossible to know.

Deployment

Deployment

Prognosis 11.0

Deployment The IR Prognosis installation consists of the following components;

Windows Client,

Web Application,

Monitoring Server

Management Server (optional)

Reporting for Unified Communications (optional)

For a detailed description of each of these please refer to the Prognosis Components topic (page 31).

How and where these components are installed depends on the type and size of the environment to be monitored. The following topics will help to explain the best way to set up the Prognosis system.


Prognosis Components (page 31)

Prognosis for Infrastructure Deployment (page 33)

Prognosis for Payments Deployment (page 43)

Prognosis for Unified Communications Deployment (page 66)

Deployment

Prognosis Components The IR Prognosis architecture is made up of five components, each of which can be installed on to a single machine or distributed over a number of 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 work load. For recommendations on where these components should be installed please refer to the Deployment for Infrastructure (page 33) and Deployment for Payments (page 43) topics, or for Unified Communications (UC) environments please refer to the Deployment for Unified Communications topic (page 66)

The Prognosis components consist of:

Windows Client

The Windows Client is a mandatory component which 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 administration 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.

Prognosis 11.0

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 consists of a set of files which are installed into the IIS Web Server directory of a designated MS Windows machine. The Web Application must be installed together with the Prognosis Management or Monitoring Server component on to an MS Windows machine.

Management Server

The Prognosis Management Server is an optional component. It is used where multiple Monitoring Servers have been installed in an environment, when this occurs 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 needs to be selected whenever Web Application and/or the Prognosis for Unified Communications Reporting functionality are required..

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

The Management Server MS Windows installation will include UC Reporting (a Unified Communications feature). This component consists is used to generate high quality reports that provide a business level view of monitored Unified Communications environments.

Monitoring Server

This component includes the collectors that provide the raw data for Prognosis. For Unified Communications this component 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, this component 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.

Deployment

Deployment - Infrastructure To use IR Prognosis at least one copy of the Windows Client and one Monitoring Server must be installed. The topics in this section show alternative deployment scenarios for the Prognosis installation.

The Prognosis Web Application component can only be installed with a Prognosis server component onto any MS Windows machine that has the IIS role running.

System Requirements


Supported Platforms and Middleware (page 34)

Server Requirements (page 35)

Deployment Scenarios

Please ensure that these deployment scenarios are reviewed in order to gain a basic understanding of how Prognosis is setup to monitor the network environment. These scenarios cover installations to monitor simple environments through to more complex installations for multi-device group, multi-product environments. Detailed installation instructions are contained in another section of this guide.


Single Machine (page 37)

Separate Monitoring Server (page 38)

Single Management Server (page 39)

Multiple Management Servers (page 41)

Prognosis 11.0

Supported Platforms and Middleware - Infrastructure

Supported Platforms

Operating System Vendor Chipset Version

Windows Microsoft Intel64 / AMD64 Windows Server 2008 R2 - 2012 R2 (64 bit only)

Linux Red Hat

Novell

x86

Intel64 / AMD64

zLinux

x86

Intel64

zLinux

RHEL 5.0 - 7.2

RHEL 5.0 - 7.2

RHEL 5.0 - 7.2

SuSe 11.0 - 13.2

SuSe 11.0 - 13.2

SuSe 11.0 - 13.2

UNIX Oracle (Sun)

IBM

HP

SPARC

x86

Power

Itanium2

Solaris 10.0 - 11.0

Solaris 10.0 - 11.0

AIX 6.1 - 7.1

HP-UX 11i v2 - 11i v3

Virtual I/O Server IBM Power VIOS 1.5 - 2.2

NonStop HP Integrity NonStop NS-series

Integrity NonStop i

Integrity NonStop X

H06.03 - H06.29

J06.03 - J06.20

L15.02 - L15.08

Supported Middleware

For details of the middleware currently supported by IR Prognosis for Infrastructure, please go to https://online.prognosis.com/prognosis-solution-briefs/ and in the 'Download Supported Platforms Guides' section click on the 'Prognosis Infrastructure' download link.

https://online.prognosis.com/prognosis-solution-briefs/

Deployment

Server Requirements - Infrastructure The IR Prognosis for Infrastructure system requirements for a dedicated Prognosis server installation are as

follows:

MS Windows

Component Minimum Requirements

Installation Hard Drive Space: The installation requires the following minimum hard drive space.

- Server component.................1.8 GB (single or combined Management/Monitoring servers)

Plus, where installed with the server:

- Windows Client:.....................500 MB

- Web Application:....................200 MB

Temp Files: A further 70 MB of free space is required for temporary files during the installation.

Plus: 800 MB free space on the c:\ drive regardless of the drive that Prognosis is being installed on.

Operating Hard Drive Space: After installation the Prognosis server requires at least the following amount of disk space for database operations:

- Windows server......................2.0 GB

The amount of actual disk space required depends on how much historical data is configured to be collected and stored locally.

UNIX/Linux


Installation Disk Space: The basic initial Prognosis server installation will require the following minimum disk space.

- UNIX/Linux - All versions:.........600 MB

Operating Disk Space: After installation the Prognosis server requires at least the following amount of disk space for database operations:

- UNIX/Linux - All versions:.........1.0 GB


Prognosis 11.0

HP NonStop


Installation Disk Space: The basic initial Prognosis server installation will require the following minimum disk space (includes 300MB for packaged Troubleshooting database).

- HP NonStop - All series:............2.0 GB


- HP NonStop - All series:............2.0 GB


Deployment

Deployment - Single Machine In a small network environment it is possible to install all of the necessary IR Prognosis components onto a single machine. As the Windows Client and Web Application components must always be installed onto an MS Windows machine, this scenario would require all components to be installed on to the MS Windows machine. If the Monitoring Server needs to be on another supported platform, then please refer to the Separate Monitoring Server (page 38) or the Single Management Server (page 39) topics.

Deployment Steps

Step 1 Install the Prognosis components

On an MS Windows machine run the Prognosis installation and make the selection to install the following components:

Windows Client - Mandatory component

Web Application

Monitoring Server - Mandatory component

Step 2 Check that the server is visible to Prognosis

Once the installation is finished, open the Windows Client/Web Application and check that the Monitoring Server is visible. Most basic network monitoring will commence automatically.

Step 3 Product configuration

For specific product monitoring it may be necessary to carry out a number of configuration steps on the Monitoring Server. These steps are contained in the relevant product sections of the Prognosis Help Center.

Prognosis 11.0

Deployment - Separate Monitoring Server As both the Windows Client and Web Application components must be installed onto an MS Windows machine, the use of separate machines will always be required when the Monitoring Server is to be installed onto a machine running one of the other IR Prognosis supported platforms. In addition, in most network environments it is advisable to install a copy of the Windows Client component onto a separate machine to the Monitoring Server when Prognosis is installed, in order to monitor critical 'on-board' MS Windows applications.

The Prognosis Web Application can only be installed with a Prognosis Server component on to an MS Windows machine that has IIS installed. Where a connection to a non-Windows Server is required an intermediary Management Server installed on an MS Windows machine will need to be used. See the Single

Management Server Deployment topic (page 39).

In this scenario the User Interface components are installed onto one or more separate MS Windows machines which are then linked to the Prognosis Monitoring Server. The number of Windows Client installations depends upon how many operators need access to this functionality.

Deployment Steps

Step 1 Install the Monitoring Server (plus Web Application if applicable)

On a machine that is running any of the supported Prognosis server platforms, i.e. MS Windows, UNIX/Linux and/or HP NonStop, run the Prognosis installation and select:


If this is an MS Windows machine the Web Application can also be installed, so in addition to the Monitoring Server select;

Web Application - this should only be installed on an MS Windows machine along with a Prognosis Server component.

Step 2 Install the Windows Client

On a separate machine, running MS Windows, run the Prognosis installation and select the following component;

Windows Client - Mandatory component

Step 3 Check that the server is visible to Prognosis

From the Windows Client/Web Application check that the Monitoring Server is visible. Most basic network monitoring will commence automatically.


For specific product monitoring it may be necessary to carry out a number of configuration steps on the Monitoring Server. These steps are contained in the relevant product sections of the Prognosis Help Center.

Deployment

Deployment - Single Management Server In many network environments it may be advisable to use multiple IR Prognosis Monitoring Servers, this can be to split the monitoring load or it could be to allow the monitoring of different platform types. In this case an optional Prognosis Management Server can be used which is linked to each Monitoring Server and will consolidate all of the collected data for viewing through the Web Application or Windows Client.

The Prognosis Web Application can only be installed with a Prognosis Server component on to an MS Windows machine that has IIS installed. Therefore, where a connection to a non-Windows Monitoring Server is required the Management Server will need to be installed onto an MS Windows machine. If the Web Application is not being used, the Management Server may be installed onto any Prognosis supported

platform.

Deployment Steps

Step 1 Install the Management Server

On a machine that is running any of the supported Prognosis platforms, run the Prognosis installation and select the Management Server component.

If this is an MS Windows machine, the Web Application and/or Windows Client components can also be included with this installation if required. Note that the Web Application component can only be installed on to an MS Windows machine that is running a Prognosis Server component.

Step 2 Install the Monitoring Servers (MS Windows)

On each MS Windows machine that is to be monitored, run the Prognosis installation and select the Monitoring Server component.

Step 3 Install the Monitoring Servers (UNIX/Linux)

On each UNIX/Linux machine that is to be monitored, run the specific Prognosis installation for the required platform.

Step 4 Install the Monitoring Servers (HP NonStop)

On each HP NonStop machine that is to be monitored, run the specific Prognosis installation for the required platform.


If the Windows Client has not been installed on the Management Server, then this component can now be installed onto one or more separate MS Windows machines.

Step 6 Check that the Management Server is visible to Prognosis

From the Windows Client/Web Application check that the Management Server is visible.

Prognosis 11.0

Step 7 Configure the Management Server

Configure the Management Server so that it can see each Monitoring Server. See: Setting up a Management Server (page 231).

Step 8 Check that the all servers are visible to Prognosis

From the Windows Client/Web Application check that the Management Server and all configured Monitoring Servers are now visible.


For specific product monitoring it may be necessary to carry out a number of configuration steps on each Monitoring Server. These steps are contained in the relevant product sections of the Prognosis Help Center.

Deployment

Deployment - Multiple Management Servers For very large networks or in a 'Managed Service Provider" (MSP) environment, a 'master' Management Server may be employed to consolidate data from other Management Servers, as illustrated below.

The Prognosis Web Application can only be installed with a Prognosis Server component on to an MS Windows machine that has IIS installed. Therefore, where a connection to a non-Windows Monitoring Server is required the 'Master' Management Server will need to be installed onto an MS Windows machine. If the Web Application is not being used, the Management Server may be installed onto any Prognosis supported platform.

Deployment Steps

Step 1 Install the 'Master' Management Servers

On a machine that is running any of the supported Prognosis platforms, run the Prognosis installation and select the Management Server component.

If this is an MS Windows machine, the Web Application and/or Windows Client components can also be included with this installation if required. Note that the Web Application component can only be installed on to an MS Windows machine that is running a Prognosis Server component.

Step 2 Install the 'Lower Level' Management Servers

On a separate machine, which can be running any of the supported Prognosis platforms, run the Prognosis installation and select the Management Server component.

Step 3 Install the Monitoring Servers (MS Windows)

On each MS Windows machine that is to be monitored, run the Prognosis installation and select the Monitoring Server component.

Prognosis 11.0

Step 4 Install the Monitoring Servers (UNIX/Linux)

On each UNIX/Linux machine that is to be monitored, run the specific Prognosis installation for the required platform.

Step 5 Install the Monitoring Servers (HP NonStop)

On each HP NonStop machine that is to be monitored, run the specific Prognosis installation for the required platform.


If the Windows Client has not been installed on the 'Master' Management Server, then this component can now be installed onto one or more separate MS Windows machines.

Step 8 Check that the Management Server is visible to Prognosis

From the Windows Client/Web Application check that the Prognosis 'Master' Management Server is visible.

Step 9 Configure the 'Master' Management Server

The Management server now needs to be configured so that it can see the 'Lower Level' Management Servers. See: Setting up a Management Server (page 231).

Step 10 Configure the 'Lower-Level' Management Server

The 'Lower-Level' Management servers now need to be configured so that each one can see its associated Monitoring Servers. See: Setting up a Management Server (page 231).

Step 11 Check that the all servers are visible to Prognosis

From the Windows Client/Web Application check that all configured Management Servers and Monitoring Servers are now visible.


For specific product monitoring it may be necessary to carry out a number of configuration steps on each Monitoring Server. These steps are contained in the relevant product sections of the Prognosis Help Center.

Deployment

Deployment - Payments This section provides information, example deployment scenarios and installation steps for the range of IR Prognosis for Payments products.

System Requirements


Supported Platforms and Middleware (page 44)


Deployment and Installation

Please ensure that the topic applying to the relevant Payments application for your environment is reviewed in order to gain a basic understanding of how Prognosis should be installed. These topics provide an outline of the Prognosis products that are required, where they should be installed and high level installation procedures. Detailed installation instructions for each platform are contained in another section of this guide and detailed configuration steps are provided in the Prognosis for Payments User Guide.


ACI BASE24 (page 48)

ACI BASE24-eps (page 51)

ACI Money Transfer System (page 55)

ACI Postilion (page 57)

ACI Proactive Risk Manager (page 60)

FIS Connex (page 62)

FIS IST/Switch (page 64)

Prognosis 11.0

Supported Platforms and Middleware - Payments

Supported Platforms

Product Vendor Platform Version

ACI BASE24 HP Integrity NonStop NS-series

Integrity NonStop i

Integrity NonStop X

H06.03 - H06.29

J06.03 - J06.20

L15.02 - L15.08

ACI BASE24-eps HP

UNIX

Integrity NonStop NS-series

Integrity NonStop i

Integrity NonStop X

Oracle (Sun)

IBM

H06.03 - H06.29

J06.03 - J06.20

L15.02 - L15.08

Solaris 10.0 - 11.0

AIX 6.1 - 7.1

ACI Money Transfer System

UNIX IBM AIX 6.1 - 7.1

ACI Postilion Microsoft Windows Windows Server 2008 R2 - 2012 R2 (64 bit only)

ACI Proactive Risk Manager

Microsoft Windows Windows Server 2008 R2 - 2012 R2 (64 bit only)

FIS Connex HP Integrity NonStop NS-series

Integrity NonStop i

Integrity NonStop X

H06.03 - H06.29

J06.03 - J06.20

L15.02 - L15.08

FIS IST/Switch UNIX IBM AIX 6.1 - 7.1

Supported Middleware

For details of the middleware currently supported by IR Prognosis for Payments, please go to https://online.prognosis.com/prognosis-solution-briefs/ and in the 'Download Supported Platforms Guides' section click on the 'Prognosis Payments' download link.


Deployment

Server Requirements - Payments The IR Prognosis for Payments system requirements for a dedicated server installation are as follows:

MS Windows



- Server component......................1.8 GB (single or combined Management/Monitoring)

Plus, where installed with the Server:

- Windows Client:........................500 MB

- Web Application:.......................200 MB



Operating Hard Drive Space: After installation the Prognosis server requires at least the following amount of disk space for database operations:

- Windows server.........................2.0 GB

- ATM & POS Transaction Manager:.........3.0 GB

- ATM Monitoring (including Reporting):..3.0 GB

- Postilion Monitoring:..................1.0 GB

- Money Transfer System (MTS)............2.0 GB

- Proactive Risk Manager (PRM):..........1.0 GB


UNIX



- UNIX/Linux - All versions:............600 MB

Prognosis 11.0



- UNIX server:..........................1.0 GB

- ATM Monitoring:.......................1.0 GB

- ATM & POS Transaction Manager:........3.0 GB

- Money Transfer System (MTS):..........2.0 GB


Deployment

HP NonStop



- HP NonStop - All series:...............2.0 GB


- HP NonStop - All series:...............2.0 GB

- ATM Monitoring:........................1.0 GB

- ATM & POS Transaction Manager:.........3.0 GB


Prognosis 11.0

Deployment - ACI BASE24

IR Prognosis supports ACI BASE24 running on HP NonStop servers (page 44)

A deployed IR Prognosis for Payments solution for ACI BASE24 will consist of a subset of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on a HP NonStop machine that is running the ACI BASE24 application, it collects information from the ATM or POS log files for online viewing and to store in historical databases.

In larger ATM Manager implementations (i.e. over 5,000 ATMs), 'offboarding' the data collection component to the Management Server is recommended. See the AIM for BASE24 'Running Offboard on Windows' topic in the Prognosis for Payments User Guide for details.

Management Server/Web Application

The Prognosis Management server should be installed on to a separate MS Windows machine within the environment. Its purpose is to aggregate and consolidate the data collected from the various Monitoring Servers and present it to the system operators via the Prognosis Web Application and/or Windows Client. Normally, only one Management Server is required, however, multiple copies may be installed where multiple Monitoring Servers are to be monitored independently or in order to spread the Prognosis client load. The Web Application provides a web interface for viewing collected data and should be installed with the Management server.

Windows Client

This component provides the full user interface for configuring and controlling Prognosis as well as presenting data from the monitored environment. The Windows Client can be installed on the same machine as the Management Server or it can be installed on one or more separate MS Windows machines and linked to the Prognosis Management Server.

ATM Manager Reporting Server

This component is installed on an MS Windows machine and is only necessary if the Prognosis ATM Manager Reporting product is required and has been licensed. This product provides regular daily, weekly and monthly reports on availability and service response times. It uses an SQL database to store and summarize this information. Normally, it is only necessary to have one Reporting Server. However, additional Reporting Servers may be installed for redundancy purposes or in order to report on multiple Monitoring Servers.

Deployment

ATM Manager Reporting Client

This component is installed on an MS Windows machine and provides the ability to connect to an existing Monitoring Server for the purpose of producing ad-hoc ATM Availability or Service Response Time reports. There can be many AIM Reporting Clients connected to a single Monitoring Server. This component is installed separately to the regular Prognosis installation.


Deployment Steps (page 50)

Prognosis 11.0

Deployment Steps - ACI BASE24 To install the various IR Prognosis components in the ACI BASE24 environment, carry out the steps in the following procedure.

Procedure

Step 1 General Information (page 8)

Read the Installation General Information section.

Step 2 Read Installation Checklist (HP NonStop) (page 166)

Read the Installation Checklist and ensure that all requirements are met before attempting to install the Prognosis Monitoring Server component on to the HP NonStop machine.

Step 3 Install the Monitoring Server (HP NonStop) (page 170)

On the HP NonStop machine where BASE24 is installed, install the Prognosis for HP NonStop Monitoring Server component.

Step 4 Read Installation Checklist (MS Windows) (page 83)

Read the Installation Checklist and ensure that all requirements are met before attempting to install the Prognosis Management Server component.

Step 5 Install the Management Server (MS Windows) (page 89)

On a separate MS Windows machine install the Prognosis for Windows Management Server component. The Prognosis Web Application should also be included with the Management Server installation. Also, if required, the Prognosis Windows Client can be included.

Step 6 Install the Windows Client (page 204)

Optionally, or in addition to the Management Server, the Windows Client component can be installed onto one or more separate MS Windows machines and should be linked to the IP address of the Management Server.

Step 7 Configure the Management Server (page 231)

Configure the NETWORK Configuration on the Management Server. This requires a MANAGED-NODE statement to be added for each Monitoring server.

MANAGED-NODE (<monitoring_server>[:<port>])

Step 8 Check that all servers are visible to Prognosis

From the Web Application or Windows Client, check that the Management Server and all configured Monitoring Servers are now visible in the Navigation panel (Web) or Node Navigator (Windows)

Step 9 Configure each Monitoring Server for XPNET Manager

On each Monitoring server, carry out the XPNET Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Step 10 Configure each Monitoring Server for Transaction Manager

On each Monitoring Server, carry out the Transaction Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Step 11 Configure each Monitoring Server for Transaction Surveillance

(Optional) If the Prognosis Transaction Surveillance product has been licensed on the Monitoring server, carry out the Transaction Surveillance configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Step 12 Configure ATM Manager

(Optional) If the Prognosis ATM Manager product has been licensed on the Monitoring server, carry out the ATM Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Deployment

Deployment - ACI BASE24-eps

IR Prognosis supports ACI BASE24-eps running on UNIX (AIX, Solaris) and HP NonStop servers (page 44)

A deployed IR Prognosis for Payments solution for ACI BASE24-eps will consist of a subset of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on a HP NonStop or UNIX machine that is running the ACI BASE24-eps application, it collects information from the ATM or POS log files for online viewing and to store in historical databases.



Windows Client


ATM Manager Reporting Server

This component is installed on an MS Windows machine and is only necessary if the Prognosis ATM Manager Reporting product is required and has been licensed. This product provides regular daily, weekly and monthly reports on availability and service response times. It uses an SQL database to store and summarize this information. Normally, it is only necessary to have one Reporting Server. However, additional Reporting Servers may be installed for redundancy purposes or in order to report on multiple Monitoring Servers.

Prognosis 11.0

ATM Manager Reporting Client

This component is installed on an MS Windows machine and provides the ability to connect to an existing Monitoring Server for the purpose of producing ad-hoc ATM Availability or Service Response Time reports. There can be many AIM Reporting Clients connected to a single Monitoring Server. This component is installed separately to the regular Prognosis installation.



Deployment

Deployment Steps - ACI BASE24-eps To install the various IR Prognosis components in the ACI BASE24-eps environment, carry out the steps in the following procedure.

Procedure





and/or

Read Installation Checklist (UNIX) (page 144)

Read the Installation Checklist and ensure that all requirements are met before attempting to install the Prognosis Monitoring Server component on to the UNIX machine.

Step 3 Install the Monitoring Server Component (HP NonStop) (page 170)

On the HP NonStop machine where BASE24-eps is installed, install the Prognosis for HP NonStop Monitoring Server component.

and/or

Install the Monitoring Server Component (UNIX) (page 146)

On the UNIX machine where BASE24-eps is installed, install the Prognosis for UNIX/Linux Monitoring Server component.






Optionally, or in addition to the Management Server, the Windows Client component can be installed onto one or more separate MS Windows machines that are linked to the IP address of the Management Server.





From the Web Application or Windows Client, check that the Management Server and all configured Monitoring Servers are now visible in the Navigation panel (Web) or Node Navigator (Windows)

Step 9 Configure each Monitoring Server for XPNET Manager

(Optional - HP NonStop Only) If the Prognosis XPNET Manager product has been licensed on the Monitoring server, carry out the XPNET Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.


On each Monitoring Server carry out the Transaction Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Prognosis 11.0


(Optional) If the Prognosis Transaction Surveillance product has been licensed on the Monitoring server, carry out the Transaction Surveillance configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.


(Optional) If the Prognosis ATM Manager product has been licensed on the Monitoring server, carry out the ATM Manager configuration steps as detailed in the Prognosis for ACI BASE24 and BASE24-eps User Guide.

Deployment

Deployment - ACI MTS

IR Prognosis supports ACI MTS running on UNIX (AIX) servers (page 44)

A deployed IR Prognosis solution for ACI MTS monitoring will consist of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on a UNIX machine that is running the MTS application, it collects the real-time data metrics from the MTS system for online viewing and to store in historical databases.



Windows Client


The type of Prognosis component to be installed is selected during the installation process.



Prognosis 11.0

Deployment Steps - ACI MTS To install the various IR Prognosis components in the ACI MTS environment, carry out the steps in the following procedure.

Procedure



Step 2 Read Installation Checklist (UNIX) (page 144)


Step 3 Install the Monitoring Server (UNIX) (page 146)

On the UNIX machine where MTS is installed, install the Prognosis for UNIX/Linux Monitoring Server component.











From the Web Application or windows Client, check that the Management Server and all configured Monitoring Servers are now visible in the Navigation panel (Web) or Node Navigator (Windows)

Step 9 Configure each Monitoring Server

On each Monitoring Server carry out the configuration steps as detailed in the Prognosis for ACI MTS User Guide.

Deployment

Deployment - ACI Postilion

IR Prognosis supports ACI Postillion running on MS Windows servers (page 44)

A deployed IR Prognosis solution for ACI Postilion monitoring will consist of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on an MS Windows machine that is running the Postilion Realtime server, it collects the real-time data metrics from the Postilion system for online viewing and to store in historical databases.



Windows Client





Prognosis 11.0

Prognosis supports multiple Realtime servers and can be deployed and managed via multiple Prognosis Management servers. Prognosis is also compatible with Postilion Active/Active.

Typical Components for each Postilion System Role include:

Realtime: - Postilion Applications

- Transactions Scribe on Realtime DB

- OS

- System

- SQL Server

- Prognosis Monitoring Server

Office: - Postilion Applications

- OS

- System

- SQL Server

Portal: - Postilion Applications

- OS

- System

- Apache Tomcat

Nixbridge: - Postilion Applications

- OS

- System

Management Server: - Prognosis Management Server

- Web Application

- OS

- System

- Microsoft IIS

Prognosis can also provide system and database level monitoring to other payments systems within the environment and has modules for several common payment applications, including PRM, BASE24, and ReD.

Deployment

Deployment Steps - ACI Postilion To install the various IR Prognosis components in the ACI Postilion environment, carry out the steps in the following procedure.

Procedure




Read the Installation Checklist and ensure that all requirements are met before attempting to install the Prognosis server components.

Step 3 Install the Monitoring Server (MS Windows) (page 89)

On the Postilion Realtime server, install the Prognosis for Windows Monitoring Server component.











On each Monitoring Server carry out the configuration steps as detailed in the Prognosis for ACI Postilion User Guide.


(Optional) If the Prognosis Transaction Surveillance product has been licensed on the Monitoring server, carry out the Transaction Surveillance configuration steps as detailed in the Prognosis for ACI Postilion User Guide.


(Optional) If the Prognosis ATM Manager product has been licensed on the Monitoring server, carry out the ATM Manager configuration steps as detailed in the Prognosis for ACI Postilion User Guide.

Prognosis 11.0

Deployment- ACI Proactive Risk Manager

IR Prognosis supports ACI Proactive Risk Manager (PRM) running on MS Windows servers (page 44)

A deployed IR Prognosis solution for PRM monitoring will consist of the following components:

Monitoring Server

The Prognosis Monitoring server is used to collect the required data. This needs to be installed on to each MS Windows machine in the PRM environment, including the AuthProc (PRM 7)/Analytic Gateway (PRM 8) Gateway server, the UI server and the NRT database server. However, if the AuthProc/Analytic Gateway server or the UI server has already been set up as a Management Server, then no further Prognosis installation is required on this machine. In cases where there is no option to run Prognosis on the NRT database server, it is possible to configure one of the other servers (Management, UI or Authproc) to monitor the NRT database server remotely. In this case, on the required server, follow the instructions for configuring that particular machine and, in addition, carry out the instructions for configuring the NRT database on the same machine.


The Prognosis Management server can be installed on to a separate MS Windows machine or it can be installed on to either the UI server or the AuthProc (PRM 7)/Analytic Gateway (PRM 8) server. It is recommended not to use the Near Real Time (NRT) database server. Its purpose is to aggregate and consolidate the data collected from the various Monitoring Servers and present it to the system operators via the Prognosis Web Application and/or Windows Client. Normally, only one Management Server is required, however, multiple copies may be installed where multiple Monitoring Servers are to be monitored independently or in order to spread the Prognosis client load. The Web Application provides a web interface for viewing collected data and should be installed with the Management server.

Windows Client





Deployment

Deployment Steps - ACI Proactive Risk Manager To install the various IR Prognosis components in the ACI Proactive Risk Manager environment, carry out the steps in the following procedure.

Procedure




Read the Installation Checklist and ensure that all requirements are met before attempting to install the Prognosis server components.

Step 3 Install the Monitoring Server (MS Windows) (page 89)

On each MS Windows machine in the PRM environment, including the AuthProc (PRM 7)/Analytic Gateway (PRM 8) Gateway server, the UI server and the NRT database server, install the Prognosis Monitoring Server component.


On a separate MS windows machine install the Prognosis for Windows Management Server component. The Prognosis Web Application should also be included with the Management Server installation. Also, if required, the Prognosis Windows Client can be included.









On each Monitoring Server carry out the configuration steps as detailed in the Prognosis for Proactive Risk Manager User Guide.

Prognosis 11.0

Deployment - FIS Connex

IR Prognosis supports FIS Connex running on HP NonStop servers (page 44).

A deployed IR Prognosis solution for FIS Connex monitoring will consist of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on a HP NonStop machine that is running the Connex applications, it collects information from the ATM or POS log files for online viewing and to store in historical databases..


The Prognosis Management server should be installed on to a separate MS Windows machine within the environment. Its purpose is to aggregate and consolidate the data collected from the various Monitoring Servers and present it to the system operators via the Prognosis Web Application and/or Windows Client. Normally, only one Management Server is required, however, multiple copies may be installed where Monitoring Servers are to be monitored independently or in order to spread the Prognosis client load. The Web Application provides a web interface for viewing collected data and should be installed with the Management server.

Windows Client





Deployment

Deployment Steps - FIS Connex To install the various IR Prognosis components in the FIS Connex environment, carry out the steps in the following procedure.

Procedure





Step 3 Install the Monitoring Server (HP NonStop) (page 170)

On the HP NonStop machine where Connex is installed, install the Prognosis for HP NonStop Monitoring Server component.













On each Monitoring Server carry out the Transaction Manager configuration steps as detailed in the Prognosis for FIS Connex User Guide.


(Optional) If the Prognosis Transaction Surveillance product has been licensed on the Monitoring server, carry out the Transaction Surveillance configuration steps as detailed in the Prognosis for FIS Connex User Guide.

Prognosis 11.0

Deployment - FIS IST/Switch

IR Prognosis supports FIS IST/Switch on running on UNIX (AIX) servers (page 44)

A deployed IR Prognosis solution for FIS IST/Switch monitoring will consist of the following components:

Monitoring Server

The Prognosis Monitoring server is installed on the UNIX machine that is running the IST/Switch applications, it collects information from the Transaction Log Table (SHCLOG) for online viewing and to store in historical databases.


The Prognosis Management server should be installed on to a separate MS Windows machine within the environment. Its purpose is to aggregate and consolidate the data collected from the various Monitoring Servers and present it to the system operators via the Prognosis Web Application and/or Windows Client. Normally, only one Management Server is required, however, multiple copies may be installed where Monitoring Servers are to be monitored independently or in order to spread the Prognosis client load. The Web Application provides a web interface for viewing collected data and should be installed with the Management server.

Windows Client





Deployment

Deployment Steps - FIS IST/Switch To install the various IR Prognosis components in the FIS IST/Switch environment, carry out the steps in the following procedure.

Procedure



Step 2 Read Installation Checklist (UNIX) (page 144)


Step 3 Install the Monitoring Server (UNIX) (page 146)

On the UNIX machine where IST/Switch is installed, install the Prognosis for UNIX/Linux Monitoring Server component.













On each Monitoring Server carry out the Transaction Manager configuration steps as detailed in the Prognosis for FIS IST/Switch User Guide.


(Optional) If the Prognosis Transaction Surveillance product has been licensed on the Monitoring server, carry out the Transaction Surveillance configuration steps as detailed in the Prognosis for FIS IST/Switch User Guide.

Prognosis 11.0

Deployment - Unified Communications This section includes a number of scenarios that illustrate suggested ways that Prognosis for Unified Communications may be deployed based upon various UC environments. These environments may include one or more vendor types and/or device groups, e.g. Avaya PBXs, Cisco Clusters or Cisco Express devices.

Prognosis for Unified Communications monitoring is only available on MS Windows platforms.

Components

For Unified Communications deployment it is recommended that the various Prognosis components be installed as follows:

The following two components should only be installed on a machine dedicated to Prognosis, i.e. no other applications should be installed.

Monitoring Server

This is used to monitor one or more PBXs/Clusters by connecting to and polling their external APIs over the UC network. This component is mandatory for data monitoring.

Management Server

This is used to aggregate and consolidate data from multiple Monitoring Servers (installed on separate machines) and MS Windows Servers.

The remaining components do not require a dedicated machine and may be installed on any machine running the Microsoft Windows operating system.

Windows Client

The Windows Client is used to view real-time and historical data from the UC environment. It is also used to configure Prognosis. 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 monitoring environment.

Web Application

The Web Application component is used to provide access to Prognosis performance data via a web browser over the Internet or an Intranet. It can only be installed with a Prognosis Server component on to an MS Windows machine that has IIS installed.

System Requirements


Supported Platforms and Vendors (page 68)


Scalability (page 71)

Deployment

Deployment Scenarios

Please ensure that these deployment scenarios are reviewed in order to gain a basic understanding of how Prognosis for Unified Communications is setup to monitor various vendor systems. These scenarios cover simple installations to monitor single vendor environments to more complex installations for multi-device group, multi-vendor environments.


Single Vendor Network (page 73)

Multi Vendor Network (page 75)

Multiple Monitoring Servers (page 76)

Deployment Considerations

In an environment containing one or more device groups, bandwidth usage on the WAN link between the Network Operations Center and a remote group may be a concern. To minimize Prognosis bandwidth usage on the WAN it is recommended to position a Prognosis Monitoring Server close to (i.e. in the same LAN as) the device group being monitored. The result of configuring the Prognosis deployment in this manner is that the higher bandwidth traffic between the Monitoring Server and the device group will be restricted to the LAN, while the metrics collected by the Monitoring Server will be passed from the Monitoring Server to the central Prognosis Management Server as low bandwidth, compressed binary data traffic, thus conserving Prognosis bandwidth usage on the WAN link.

Prognosis 11.0

Supported Platform and Vendors - Unified Communications

Supported Platforms

Operating System Vendor Chipset Version

Windows Microsoft Intel64 / AMD64 Windows Server 2008 R2 - 2012 R2 (64 bit only)

Supported Vendors

For details of the vendor devices currently supported by IR Prognosis for Unified Communications, please go to https://online.prognosis.com/prognosis-solution-briefs/ and in the 'Download Supported Platforms Guides' section click on the 'Prognosis UC' download link.


Deployment

Server Requirements - Unified Communications The IR Prognosis for Unified Communications system requirements for a dedicated server installation on an

MS Windows machine are as follows:

MS Windows



- Server component....................1.8 GB (single or combined Management/Monitoring)

Plus, where installed with the Server:

- Windows Client:.....................500 MB

- Web Application:....................200 MB



Operating Hard Drive Space: After installation the Prognosis server requires at least the following amount of disk space for normal operations:

- Windows server......................2.0 GB

In addition, the Prognosis server requires the following amount of space for the storage of historical data.

- Common UC databases................34.0 GB

Plus, the maximum database size for each vendor type is:

- Alcatel-Lucent OmniPCX:.............1.5 GB

- Avaya Aura Communication Manager:..65.5 GB

- Avaya Communication Server 1000:....2.2 GB

- Avaya IP Office:....................4.6 GB

- Avaya Modular Messaging:............7.1 GB

- Avaya System/Session Manager:.......1.0 GB

- Contact Center:.....................1.0 GB

- Cisco Emergency Responder (CER):....1.0 GB

- Cisco UCM 5+ (per cluster):.........7.0 GB

- Cisco Express Suite:................1.0 GB

- Cisco UCS B-Series: ................3.0 GB

- Cisco UCS C-Series:.................1.0 GB

- Cisco UCCX:.........................1.0 GB

- Cisco Unified Presence:.............1.0 GB

- Cisco Unity Connection:.............1.0 GB

- Microsoft Skype for Business:......87.0 GB

- Session Border Controllers:........ 1.0 GB

- UC Reporter (up to):..............180.0 GB

UPGRADE: Twice the recommended minimum disk space is required for a backup and restore of these databases during an upgrade to a later Prognosis version.

Prognosis 11.0

Minimum Server Specifications

Component Version/Size

Processor (CPU): Intel® Xeon® Dual-Core processor 2.4GHz

System Memory (RAM): 4 GB

Recommended Server Specifications

Component Version/Size

Processor (CPU): Intel Xeon 3450 2.67GHz Quad Core processor

System Memory (RAM): 8 GB

Deployment

Scalability - Unified Communications Each Prognosis for Unified Communications Monitoring Server running with the recommended specifications is aimed to support one of the following environments. For larger more complicated environments, please refer to the Multiple Monitoring Servers (page 76) topic in the Deployment section.

Vendor Platform Max Devices

Max Endpoints Notes

Acme Packet

Net-Net 50 SBCs Not applicable -

Alcatel OmniPCX Enterprise

10 PBXs 40,000 phones, 160,000 BHCA

The 40,000 phones can be distributed among 10 different PBXs on a single Monitoring Server.

Avaya CM 30 PBXs 60,000 phones,

240,000 BHCA

The 60,000 phones can be distributed among 30 different PBXs but they share the same RTCP Collector on the Monitoring Server.

Avaya CS1000 10 PBXs 40,000 phones,

160,000 BHCA

The 40,000 phones can be distributed among 10 different PBXs on a single Monitoring Server.

Avaya System Manager (SMGR)

1 Not applicable

Avaya Session Manager (SM)

10 Not applicable

Cisco CUCM 30 clusters 80,000 phones (a), or

60,000 phones (b),

240,000 BHCA

(a) Up to 80,000 phones from 1 super cluster, or

(b) Up to 60,000 phones in up to 20 different clusters on a single Monitoring Server.

Cisco CUC 30 clusters Not applicable -

Cisco CUP 30 clusters Not applicable -

Cisco UCCX 30 clusters Not applicable -

Cisco UCS B-Series 10 systems 40 chassis, 320 Blades

The 40 chassis and 320 Blades can be distributed among 10 different UCS B-Series Systems on a single Monitoring Server.

Cisco UCS C-Series 30 systems Not applicable -

Cisco UBE (Enterprise Edition)

50 systems Not applicable -

Prognosis 11.0

Vendor Platform Max Devices

Max Endpoints Notes

Cisco SRST 125 routers 30,000 phones 125 routers per Monitoring Server and a maximum of 1000 routers with 8 Monitoring Servers. The 30,000 phones can be distributed among 125 routers per Monitoring Server.

Cisco CME 125 routers 30,000 phones 125 routers per Monitoring Server and a maximum of 1000 routers with 8 Monitoring Servers. The 30,000 phones can be distributed among 125 routers per Monitoring Server.

Cisco CUE 125 routers 30,000 mailboxes 125 routers per Monitoring Server and a maximum of 1000 routers with 8 Monitoring Servers. The 30,000 mailboxes can be distributed among 125 routers per Monitoring Server.

Microsoft Lync 2010 and Lync 2013

(Standard and Enterprise Editions)

10 central sites

60,000 users The 60,000 users can be from one central site or up to 10 different central sites on a single Monitoring Server.

Prognosis monitoring requires that the Lync Monitoring SQL Server be deployed.

Microsoft Skype for Business 2015

As per Lync As per Lync As per Lync

Deployment

Deployment - Single Vendor Network A single installation of the Prognosis for Unified Communications Server is capable of monitoring multiple Unified Communications device groups. The Monitoring Server should be a standalone machine with a connection to each device group. The Prognosis Web Application will also need to be installed on to the Monitoring Server which will give access to monitored data via a web browser. The Prognosis Windows Client can be installed on the same machine as the Monitoring Server or a copy can be installed on one or more separate machines that are connected to the Monitoring Server.

In the case of Avaya Aura Communication Manager up to 10 Avaya PBXs can be monitored by a single Server installation. If you have a requirement to monitor more than 10 Avaya PBXs please contact Prognosis

Technical Support.

Deployment Steps

Step 1 Install the Monitoring Server (plus Web Application and UC Reporter if required)

On an MS Windows machine that is separate from the UC environment devices, install the following Prognosis components:


Web Application - Mandatory on this machine if the Prognosis Web Application is required.

Windows Client - Optional on this machine


Optionally, or in addition to the Monitoring Server installation, the Windows Client component can be installed onto one or more separate machines that are linked to the IP address of the Monitoring Server.

Step 3 Configure the Monitoring Server

The Monitoring Server will now need to be configured to monitor the required vendor products. These steps are contained in the relevant Prognosis product guides.

Step 4 Check that all devices are visible to Prognosis

From the Windows Client/Web Application check that all vendor devices to be monitored are shown. If they are not, recheck the configuration steps on the Monitoring Server.

Prognosis 11.0

Step 5 Start Alerts and Databases (if applicable)

Depending upon the vendor type, certain Alerts and Databases may now need to be started. Where applicable these will be detailed in the relevant Prognosis product guides.

Deployment

Deployment - Multi Vendor Network IR Prognosis can be used to monitor different Unified Communication vendor types through the same Monitoring Server. However, this excludes Cisco CallManager 3.3 and Cisco Unified CallManager 4.x, which require 'on-board' monitoring and as such need a different set up which is covered in the Cisco UCM 3.3 and 4 section.

Deployment Steps

Step 1 Install the Monitoring Server (plus Web Application if required)

On an MS Windows machine that is separate from the UC environment devices, install the following Prognosis components:





Optionally, or in addition to the Monitoring Server installation, the Windows Client component can be installed onto one or more separate machines that are linked to the IP address of the Monitoring Server.

Step 3 Configure the Monitoring Server

The Monitoring Server will now need to be configured to monitor the required vendor products. These steps are contained in the relevant Prognosis product guides.





Prognosis 11.0

Deployment - Multiple Monitoring Servers IR Prognosis can be set up to use multiple Monitoring Servers. This is usually needed when large numbers of device groups from different vendor types are being monitored. A separate Monitoring Server for each vendor type is recommended. When multiple Monitoring servers are used, a Prognosis Management Server needs to be installed in order to combine data for display.

There must NOT be more than one Monitoring Server connected to the same device group, as this will negatively impact the performance of the devices in the group. The same device or node names must not be used in different device groups. All device and node names need to be unique across the entire monitoring network. The duplication of the names that Prognosis allocates to two different device groups can lead to the Prognosis GUI showing the message 'Data source unavailable'.

Deployment Steps

Step 1 Install the Monitoring Server (for Device Groups A & B)

On a machine that is separate from the UC environment devices install the Prognosis Monitoring Server component. This will be the Monitoring Server for Device Groups A and B.

Step 2 Install the Monitoring Server (for Device Group C)

On another machine that is also separate from the UC environment devices install another copy of the Prognosis Monitoring Server component. This will be the Monitoring Server for Device Group C.

Deployment

Step 3 Install the Management Server

On another separate machine install the the following Prognosis components:

Management Server - Mandatory component




Optionally, or in addition to the Management Server installation, the Windows Client component can be installed onto one or more separate machines that are linked to the IP address of the Management Server.

Step 5 Configure the Management Server

Configure the Management Server so that it can see each Monitoring Servers. See: Setting up a Management Server (page 231).

Step 6 Configure the Monitoring Servers

The Monitoring Servers will now need to be configured to monitor the required vendor products. These steps are contained in the relevant Prognosis product guides.





Installation

Installation

Prognosis 11.0

Installation When ready to proceed, the various Prognosis components can now be installed on the required machines. For details please refer to the following sections:


Installing the Server on MS Windows (page 81) This installation can include the MS Windows Client and Web Application components

Installing the Server on UNIX/Linux (page 140)

Installing the Server on HP NonStop (page 162)

Installing the Web Application (page 194) This component must be installed with the MS Windows server component

Installing the Windows Client (page 204) The information in this section is for a standalone installation

Installing UC Reporter (page 214) This component must be installed with the MS Windows server component

Service Packs and Patches (page 219)

Installation

Server on MS Windows This section describes installing or upgrading the IR Prognosis Management and/or Monitoring Server on to a machine running the Microsoft Windows operating system. If required, the Prognosis Windows Client and/or Web Application can also be installed together with the server component on this machine.

Before starting the installation please pay particular attention to the following topics:


Deployment (page 30)

When ready to start the installation please refer to either of the following sections:

New Installation (page 82)

Upgrade Installation (page 99)

Associated topics:

Unattended Installation (page 130)

Uninstalling (page 133)

Unattended Uninstall (page 139)

The Web Application component needs to be installed with a Prognosis server component on to an MS

Windows machine which is running IIS. See Installing the Web Application (page 194) for details.

Prognosis 11.0

New Installation The following topics will provide details for a new installation of the IR Prognosis server component on to an MS Windows machine.


Installation Checklist (page 83)

CopSSH (page 86) - for Prognosis for Unified Communications

Proxy Server Settings (page 88) - for Web Session Recorder

Installation Procedure (page 89)

Installing Prognosis with Oracle (page 97)

For an upgrade to an existing Prognosis installation please refer to the Upgrade (page 99) section.

Installation

Installation Checklist Checklist for installing the IR Prognosis server on an MS Windows machine. Before proceeding with the installation please go through the following checklist and ensure that all items have been addressed.

Installation Checklist - MS Windows

1. Release Notes

Before proceeding please take time to read the latest Release Notes for this Prognosis installation. The Release Notes document can contain important information relating to the installation process and the operation of Prognosis. This document can be downloaded from the Prognosis Online web site.

Go to: https://online.prognosis.com/products/download

2. Prognosis Installation Files

Ensure that you have the Prognosis for Windows installation file (Prognosis11.x.x.exe). This can be downloaded from the Prognosis Online web site and saved to a suitable drive/folder on the Windows server (where required the installation may also be provided on CD/DVD).


3. Has the Prognosis 11 license been received?

When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files. If the license file has not been received, please contact your Prognosis account manager.

See: License File (page 13)

4. Check the Prognosis server requirements

See: Server Requirements - MS Windows (page 35).

5. Pre-requisite software

The following software is required on the server. If the installer does not find this software on the destination machine it will be automatically installed.

Microsoft Visual C++ 2013 Redistributable Package (x86) – needed to run 32-bit Prognosis code (on both 32-bit and 64-bit Windows)

Microsoft Visual C++ 2013 Redistributable Package (x64) – needed to run 64-bit Prognosis code (on 64-bit Windows)

Microsoft .NET Framework 4.6. This is needed to run .NET Prognosis code (on both 32-bit and 64-bit Windows). The Prognosis .NET Framework installation may not have all of the latest updates included, therefore you may find that during your next patch window a large number of updates will be generated and this should be planned for. The alternative is to install the required .NET Framework version and the associated updates prior to the Prognosis installation.

6. Ensure that the correct level logon is available (username/password)

Administrator privileges will be required for the system on which Prognosis will be installed.

https://online.prognosis.com/products/download


Prognosis 11.0


7. Determine which disk drive and folder path Prognosis is to be installed on.

The server installation cannot be made into any of the following folders:

- /Program Files - /Program Files (x86) - /Users - /Documents and Settings - /WINDOWS

This is because Prognosis needs to save/modify files in its installed location as the logged in user. In MS Windows problems can occur when trying to do this in these folders unless the user is an administrator, which may not be the case.

8. Is SNMP installed?

If installed, the SNMP service enables Prognosis to monitor remote devices. Prognosis will still run without the SNMP service but some data will be unavailable. SNMP can be installed from the Add/Remove Programs Control Panel applet by selecting the Add/Remove Windows Components wizard and installing the Management and Monitoring Tools component.

9. Check if CopSSH is installed. (Prognosis for Unified Communications)

Effective with version 10.3, Prognosis no longer relies on CopSSH for monitoring Cisco UCM 5+, Acme Packet SBC and Avaya Aura Session Manager environments. Provided that no version of CopSSH is found on the machine the Installation will now install its own SFTP server. However, if an existing copy of CopSSH is found a manual procedure may be required.

See: CopSSH (page 86).

10. Disable virus checking software.

It is preferable that all types of virus checking software be disabled on the destination machine. However, if this is not possible then the Prognosis folder/directory should be added to the virus checking exclusion list. Active virus checking software may cause system problems ranging from errors when accessing configurations to the slow transfer of data between servers.

11. Proxy Server Settings (Web Session Recorder only)

This instruction is only applicable for users of the Prognosis Web Application Management product suite, specifically the Web Session Recorder. If a Proxy server is being used on the network it may be necessary to configure the Internet Explorer settings so that the required internet access is made available to the Prognosis Web Session Recorder.

See: Proxy Server Settings (page 88)

12. Oracle database monitoring

If Oracle is already installed on the MS Windows machine where Prognosis is to be installed and Oracle database monitoring is required (provided that the appropriate Prognosis license has been obtained) some additional configuration steps will be required.

See: Installing Prognosis with Oracle topic (page 97).

13. Is the Prognosis Windows Client to be included with this installation?

See the Windows Client section (page 204) for information specific to this component.

Installation


14. Is the Prognosis Web Application to be included with this installation?

See the Web Application section (page 194) for information specific to this component.

On MS Windows 8, Windows Server 2012 and above, the Prognosis Web Application Installation may fail unless all pending Windows updates have been applied. It is therefore strongly recommended that the Windows Update facility be manually run before attempting to install Prognosis in order to ensure that the system is completely up to date.

15. Is Prognosis UC Reporter required with this installation?

See the UC Reporter section for information specific to this component.

Once the checklist has been completed, proceed with the Prognosis installation. For details see, Installation Procedure (page 89).

Prognosis 11.0

CopSSH

Prognosis for Unified Communications only

Effective with IR Prognosis 10.3, CopSSH is no longer installed, Prognosis now includes its own SFTP server. CopSSH was previously installed as an SFTP server in order to obtain CDR data from Cisco Unified Communications Manager 5+, Acme Packet Session Border Controller and Avaya Communication Manager CS1000.

When installing a Prognosis 10.3 (or later) Monitoring Server component with a Prognosis for Unified Communications product license, the installer will detect if a copy of CopSSH currently exists on the destination machine and will take the following action:

Copy of CopSSH does not exist

The Prognosis SFTP server component will be automatically included with the installation.

Copy of CopSSH does exist

If the CopSSH copy was installed by a previous Prognosis version, the installer will automatically remove the existing CopSSH version and install the new Prognosis SFTP server component.

If the CopSSH copy was not installed by a previous Prognosis version, the installer will check the CopSSH version number:

a) If the version is lower than 3.1.1, the Prognosis installer will show a message asking that it be uninstalled and the Prognosis installation will terminate. In this case the old CopSSH version will need to be manually uninstalled and then the Prognosis installation can be started again which will automatically install the new SFTP server component.

b) If the version is 3.1.1 or later, the installer will provide an option to continue using this CopSSH version. If the option to continue using CopSSH is accepted, the installer will continue but will not enable the new Prognosis SFTP server component and will not configure Prognosis for CopSSH. In this case it will be necessary to manually create a user account for SFTP connectivity after the Prognosis installation has been completed, to do this see the Create a User Account for SFTP Connectivity topic.

CopSSH Access Rights

For Prognosis installations that continue to use CopSSH, the CopSSH service is set up to run under the local user account 'SvcCOPSSH' which requires the following rights to be assigned:

'Act as part of the operating system',

'Create a token object'

'Logon as a service'

It is important to be aware that once these rights have been assigned they may be revoked by synchronization of the machine settings with the Group Policies. If this happens it will cause the service to fail to start with the following error: "Logon failure: the user has not been granted the requested logon type at this computer". To correct this problem the Group Policies need to be modified by the System Administrator.

Installation

Create a User Account for SFTP Connectivity

Should the Prognosis installation detect a copy of CopSSH 3.1.1 or later on the destination machine, the installer will provide an option to continue using this CopSSH version. If this option is accepted then it will be necessary to manually create a local user account (PrognosiCDR) after the installation is compete.

Effective with Prognosis 10.3 the installation will normally install its own SFTP server which does not require a local user account.

To manually create the local user account for CopSSH use the following procedure.

Procedure

Step 1 On the Prognosis Monitoring server open a command line and create a local user account named 'PrognosisCDR'. Specify that the account never expires:

C:\>net user PrognosisCDR <password> /ADD /EXPIRES:NEVER /COMMENT:"User

account for sftp connectivity"

Step 2 From the command line go to the CopSSH folder path and activate the user for sshd by running the following command:

C:\<CopSSH_Path>>copsshadm.exe --command activateuser --user PrognosisCDR

--passphrase <password>

Step 3 Update the Prognosis PASSWORD Configuration by adding a new Entry Name of 'sftp' with the Username 'PrognosisCDR' and an appropriate password.

Step 4 In the Prognosis installation folder create the path; '3rdparty\copssh\home\PrognosisCDR\CDRData', which is where the collected CDR data will be stored.

<Install_Path>\Prognosis\3rdparty\copssh\home\PrognosisCDR\CDRData

Step 5 Update the required vendor configuration. For details please refer to the vendor chapters for Enabling CDR data collection in the Prognosis for Unified Communications Guide.

Prognosis 11.0

Proxy Server Settings

Prognosis Web Session Recorder only

This instruction is applicable for users of the IR Prognosis Web Application Management product suite, specifically the Web Session Recorder.

If you are using a Proxy server on your network you may need to configure your Internet Explorer settings so that the required internet access is made available to the Prognosis Web Session Recorder. This should be done prior to installing Prognosis.

Setting up Internet Proxy Settings

To do this open Internet Explorer and proceed as follows:

Step 1 From the menu bar select Tools and then Internet Options.

Step 2 From the Internet Options dialog box select the Connections tab.

Step 3 At the bottom of the dialog in the Local Area Network (LAN) settings box click on the LAN Settings… button.

Step 4 In the Proxy server box of the displayed dialog check the option to “Use a proxy server for your LAN” and then input the address details of the Proxy server. When finished select the OK button.

Step 5 If required, select the Advanced tab and select or de-select any of the options as required.

Step 6 Click the OK button to save your changes.

Once your Internet Explorer has been configured to use the Proxy server you can install Prognosis. Upon installation Prognosis will automatically copy your 'Internet Settings' from the current user to a default user, it is the default user that Web Session Recorder is set up to use when running.

If at a later stage changes are made to your internet settings please refer to the Prognosis Web Session

Recorder section of the Prognosis for Infrastructure User Guide.

Installation

Installation Procedure The following procedure is used to install the IR Prognosis Management and/or Monitoring Server components onto a machine running the MS Windows® operating system.

If required, the Windows Client and/or Web Application can also be installed with the server onto the same machine. To do this, select the required client components along with the server at Step 4.

Administrator rights are required for the machine onto which the Prognosis Server is being installed.

Procedure

Step 1 Place the Installation CD into the CD drive of the required machine. If Autorun is activated the CD will start the installation automatically. If the installation fails to start, go to Windows Explorer, select the CD drive, copy the Prognosis installer to a local drive and then run the Prognosis11.x.x.exe file.

or

Download the Prognosis installer to a local hard disk and then run the Prognosis11.x.x.exe file.

The exe file is a self-extracting executable that will extract into a folder named 'Prognosis11.x.x'. On slow machines this may take a few minutes. Once extracted, the folder will contain:

- Prerequisites folder

- Backup-restore folder

- Prognosis11.x.x.msi

- Setup.exe

Setup.exe will now run automatically and initially check for the required pre-requisite software (page 83).

a) If the pre-requisite software is not found on the destination machine, it will be automatically installed. This may result in some non-Prognosis dialog boxes being displayed, but normally it will only be necessary to 'click' through these until the software has been installed.

b) If the required pre-requisite software is found on the destination machine, or after it has been installed, the Prognosis Welcome dialog will open.

Click the Next button to proceed.

Prognosis 11.0

Step 2 End-User License Agreement

The next step in the installation is the acceptance of the End-User License Agreement (EULA).

Carefully read the End User License agreement and then click the check box to accept the terms and conditions.

The 'Send usage data to IR' option will be selected by default. Please read these conditions and if this is not acceptable, uncheck the adjacent check box.

The Next button will become active once the License Agreement has been accepted and can then

be selected to continue with the installation.

If the End-User License Agreement (EULA) is not acceptable, click the Cancel button and the

installation will be aborted.

Installation

Step 3 License

The installation will now request the Prognosis license file (page 13) information.

In most cases the license information is sent by email as an attached text file. When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files

The License dialog box will default to the same folder path as the installation files, should the license be located elsewhere or should an invalid license be found, an alternative license location can be specified or browsed for.

The license field may be left blank, however this will only allow the Prognosis Windows Client to be installed. Please note that the Windows Client cannot be used with the UC Foundation Edition license.

When completed click the Next button to continue.

Prognosis 11.0

Step 4 Prognosis Components

From this dialog box select the components that are to be installed on this machine. For details about each component see the Product Components topic (page 31).

a) To only install the Prognosis server components check:

the Management and/or Monitoring Server options (leave other options unchecked).

b) To add one or both client components check either or both of the following options:

Windows Client

Web Application

In order to select the Web Application option, a Management or Monitoring Server component must also be selected. A warning message will be displayed if it is not.

Click the Next button to continue.

Installation

Step 5 Destination Folder

This dialog box is used to assign the folder path where this copy of Prognosis will be installed.

Check that the default path shown in the Destination Folder field is where you wish Prognosis to be installed. If not, click the Browse button where an alternative folder path can be specified.

Please note the following:

Prognosis cannot be installed into any of the following folders of an MS Windows machine:


This is because Prognosis needs to save/modify files in its installed location as the logged in user. In MS Windows problems can occur when trying to do this unless the user is an administrator, which may not be the case.

Prognosis cannot be installed into an existing folder. A new folder must be created.

Absolute file name length cannot exceed 258 characters. As the relative path and field names of the Prognosis packaging can reach up to 210 characters, it is strongly recommended to limit the

absolute path for the Prognosis home installation folder to 45 characters.

Click the Next button to continue. If a new folder name has been input Prognosis will now create the

new folder.

Prognosis 11.0

Step 6 Prognosis Web Application Port

The following dialog box will only appear when the Web Application component has been selected and the default port 443 is already in use. When the default port is found to be in use, the Prognosis installer will try to find an alternative port starting with 8080 and incrementing by 1 up to 8089. When one of these port is found to be available, it will be shown in the input field on this dialog box, if none of these ports are found to be available, the input field will be empty.

If the installer nominated port number is acceptable, click the Next button to proceed.

If the nominated port number is not acceptable, an alternative user-selected port number can be entered. In this case after clicking the Next button, the installer will check the port number for both

format (digit only and < = 65535) and availability. If the format is incorrect the following warning message will be displayed and if the port is unavailable the Prognosis Web Application Port dialog box will be redisplayed.

Installation

Step 7 Ready to Install Prognosis

This dialog box confirms that all the installation settings that have been made and that Prognosis will make any necessary Firewall (page 11) changes. If the Web Application component has been included it will confirm the port that has been configured.

If any changes are required click the Back button to return the required dialog and make the

necessary adjustments.

If you are satisfied with the settings, click the Install button to begin copying the installation files to

the nominated folder.

Prognosis 11.0

Step 8 When the installation is complete the final dialog box will be shown

Click the Finish button to complete the installation.

The Prognosis installation may include new drivers. These drivers may not become effective until after the next reboot of the Windows Server. If a reboot is required, a prompt will be shown advising that a reboot

of the machine can be made now or later.

'PROGNOSIS' PASSWORDS Configuration entry During installation on a MS Windows platform a 'PROGNOSIS' entry will be added to the Prognosis PASSWORDS Configuration. This entry is used by Analysts and Thresholds (and is used by the default Windows Analyst) to tell Prognosis to run commands with the Local System Account (NT AUTHORITY/SYSTEM) and not the user that started the Analyst. As such, it is recommended that the SECURITY Configuration be modified to limit access to this PASSWORDS Configuration entry to specific

users.

Configuration

After the installation has been completed there are a number of configuration steps that now need to be undertaken.

Management Server

If a Prognosis Management Server is being used with remote Monitoring Servers, it will be necessary to configure the Management Server to see the other machines. To do this see the Setting up a Management Server (page 231) topic.

Monitoring Server

Each Monitoring Server may need vendor specific configurations for the type of data monitoring that it will be undertaking. These configurations are detailed in the product sections of the Prognosis Online Help Center.

Installation

Installing Prognosis with Oracle on MS Windows This procedure is only used where Oracle is already installed on the MS Windows machine where IR Prognosis is to be installed and where Oracle database monitoring is required (provided that the appropriate Prognosis license has been obtained). If Oracle database monitoring is to be enabled after the Prognosis installation, please refer to the Oracle Database Server Management section of the Prognosis for Distributed Systems User Guide.

Procedure

Step 1 Before installing Prognosis, make sure that the account to be used has a valid Oracle environment and ask your Database Administrator to set it up to access Oracle.

Step 2 Test the environment

It is necessary to be able to use tnsping (on Oracle 8.x use "tnsping80.exe") to check access to the various names in the tnsnames.ora file (on Oracle 8.x this file is found at "...\Orant\net80\admin\tnsnames.ora"). If this test is not successful, then Prognosis will not be able to connect to Oracle and the problem should then be referred to your local Database Administrator for resolution. Such problems may include, Oracle listener not running, underlying database down, or incorrect tnsnames.ora etc).

Step 3 Install the Prognosis server using the standard procedure (page 89).

After the Prognosis installation has been completed, proceed with the following steps.

Step 4 Configure the Database

Log on to sqlplus using the sys account (requires administrator permissions). The Database Administrator may be required to provide assistance with the sys user log on.

After log on run the following entry for each Oracle instance (ORACLE_SID) that is to be monitored.

@ Prognosis\Server\Configuration\prognosis_grants.sql

This will create an Oracle user named 'prognosis' with the password 'prognosis' which has access rights to all required tables. Now log in to sqlplus using the 'prognosis' user to check it.

This Oracle sqlplus script creates a user and sets up permissions so that Prognosis can read from the various system tables and views without requiring any kind of system privilege. The DBA may need to edit this script to conform to the security and other policies of the site. The script must be executed as the sys (or equivalent) user. DO NOT RUN THIS SCRIPT WITHOUT FIRST CHECKING THAT IT IS APPROPRIATE FOR THE SITE.

Step 5 PASSWORD Configuration (in Prognosis Windows Client)

Add the 'prognosis' user name and password for Oracle and Oracle Alias into the Prognosis PASSWORDS Configuration. Use the key 'Oracle' or 'OracleAlias<alias-name>'. See the Security/Passwords Configuration section of the Prognosis System Guide for details.

Step 6 DBMS Configuration

In order to undertake Oracle database monitoring through Prognosis you will need to set up the Prognosis Database Management Subsystem (DBMS) configuration. A default Configuration is provided with your Prognosis installation, this can be found in the Document Navigator in the following folder path:

Knowledge > Common > Oracle > Configuration

Use this configuration to control access to the DBMS installations by Prognosis. The Prognosis process that relies on this configuration is called IRDBCOL.

SUBSYS DBMS

ODBC RECONNINT (<Interval>, <Unit>)

ORACLE DRIVER (ORACLE_ODBC_DRIVER)

ORACLE ALIAS (<DBName>)

Prognosis 11.0

ODBC RECONNINT

Specifies how often Prognosis tries to reconnect to the DBMS after a failure. The minimum is 1 minute.

ORACLE DRIVER (ORACLE_ODBC_DRIVER)

Always use this entry for the Oracle collector on Windows.

ORACLE ALIAS

Specifies the database names that are to be monitored, add one per line. Use the connection names as defined in tnsnames.ora, i.e. the ones tested in step 2.

Step 7 Start the DBMS configuration then open the Welcome to Prognosis Display and drill down to Oracle Central. These Displays have 30 second intervals, so you will need to wait a few moments for data to appear.

Troubleshooting

Once the above steps have been completed either all the expected data will appear in the Displays, or the only data to appear will be the Alias names and asterisks. If the latter is the case, open the "...\Prognosis\Server\Configuration\WVLOG.TXT" file and check the Oracle error listed there (e.g. ORA-XXXX). If the local Database Administrator cannot resolve the listed error, please contact Prognosis Technical Support.

Installation

Upgrade Installation The following products can be upgraded to IR Prognosis version 11.

Prognosis 9.1 SP4

Prognosis for Unified Communications 9.6.1 Update 7

Prognosis for Unified Communications Foundation Edition 10.0

Prognosis 10.0 SP1

Prognosis 10.1

Prognosis 10.1.5 (patch 4)

Prognosis 10.2 (patch 1)




For Skype for Business, the following products can be upgraded to Prognosis 11:



For any other earlier versions it will be necessary to upgrade to one of the abovementioned products first before being able to undertake this latest upgrade.

Before starting the upgrade please pay particular attention to the following topics:

Upgrade Information (page 100)

Upgrade - FIPS Encryption (page 102)

Upgrade Checklist (page 104)

Upgrade Process (page 107)

Upgrade Troubleshooting (page 109)

Backup/Rollback Previous Version (page 112)

Upgrade Procedure

- Prognosis 9.1 SP4 (page 120)

- Prognosis for Unified Communications 9.6.1 Update 7 (page 120)

- Prognosis for Unified Communications Foundation Edition 10.0 (page 120)

- Prognosis 10.0 or later (page 115)

- Manual Upgrade Procedure (page 128) (optional for 64 bit upgrades/mandatory for migrating from 32 bit machines)

If upgrading from a Prognosis for Unified Communications 9.6.1 Update 7 version that also has IP Telephony Management Reporter installed, please also refer to the Upgrading from IPT Management Reporter topic (page 216).

Prognosis 11.0

Upgrade Information

Platforms/Middleware

Please be aware that some platforms/middleware that were previously supported in earlier Prognosis versions may no longer be supported in this latest Prognosis release. For details of what is currently supported please go to https://online.prognosis.com/prognosis-solution-briefs/ and select 'Download Prognosis Infrastructure and Payments Supported Platforms'.

Upgrade Order

The upgrade should be completed top/down from the Windows Client, the highest level Management Server and UC Reporter to any lower-level Management and Monitoring Servers:

The Prognosis 10 upgrade cannot be completed on a server where there is more than one copy of an existing Prognosis version.

Backup

As the Prognosis 11 upgrade process will uninstall the earlier Prognosis version, it is strongly recommended that a backup of the previous version be made prior to attempting the upgrade. Should the upgrade process fail, the previous version can then be restored. For details see the Backup/Rollback Previous Version topic (page 112).


Installation

What DOES happen on Upgrade?

All documents (i.e. Displays, Thresholds etc.) in the 'My Displays & Configurations' folder of the IR Prognosis Windows Client will be maintained.

All documents (i.e. Displays, Thresholds etc.) in the 'Knowledge' folder of the Prognosis Windows Client will be deleted and replaced with new files.

irgui.ini will be restored.

Static Configurations will be maintained.

The following statistics will be reset;

- Availability

- Dispatch Manager Logs

- Problem Logs

- File Manager Logs

Prognosis log file (wvlog.txt) is backed up but will not be restored.

All .ini files will be merged on upgrade (old values are kept on upgrade).

Software Inventory history will be maintained on upgrade (file SWINVDB).

UDEFSREC will be merged with a new UDEFSREC (records are replaced with newer ones).

If the Tomcat Web Server was previously installed by Prognosis then it will be completely removed.

Please note that:

The contents of the 'My Displays & Configurations' folder will not be upgraded.

Windows Client security is not maintained during upgrade.

Modifications to standard Displays, Thresholds, Analysts etc. are not kept.

All Prognosis Configurations that were running at the time will be automatically started on upgrade.

File Manager Logs are NOT maintained.

Prognosis 11.0

Upgrade - FIPS Encryption

Web Application - Administration Tool

The Prognosis Web Application - Administration Tool has been modified to use the HMAC encryption algorithm using .NET.

Where older versions of Prognosis (10.2 and above, but below P11) are being managed, it will no longer be possible to update the PASSWORDS Configuration of older versions from the P11 Web Application - Administration Tool:

The PASSWORDS Configuration will not be visible in the configuration page;

Access to the URL for modifying the PASSWORDS Configuration will be blocked.

In addition, it will no longer be possible to add a new systems to be monitored by older versions of Prognosis from the P11 Web Application - Administration Tool:

The expand button for importing configurations from the older versions of Prognosis is removed from the node navigation panel. Running the ircfg command manually will also fail with the error 'Node <nodename> is running Prognosis <version>. Unable to import configurations from versions of Prognosis prior to 11.0';

The 'Add System' button and 'Remote Credentials' section will be disabled for the older versions of Prognosis. Access to the URLs for adding system/adding remote credentials will also be blocked for these Prognosis versions.

File Transfer Utility (send to Web Application from Windows Client)

The file transfer utility from the Prognosis Windows Client, using the ‘Send to Web’ function, will now use the .NET HMAC encryption algorithm, similar to the Web Application - Administration Tool. This means that it will no longer be possible to ‘Send to Web” from Prognosis version 11 or later to earlier Prognosis versions.

PACE XML

Encryption for Pace XML has been updated to use the Microsoft CNG HMAC encryption algorithm.

PASSWORDS Configuration

Passwords have been updated to use the latest encryption algorithm. On upgrade, passwords stored in the Prognosis PASSWORDS Configuration will be automatically updated to use the latest encryption mode. This has been done for MS Windows and UNIX/Linux. HP NonStop is currently unaffected.

Installation

NETWORK Configuration

On upgrade from previous versions of Prognosis to version 11 or later, the following will apply:

The ‘ALLOW-LEGACY-CONNECTIONS’ and ‘FORCE-LEGACY-CONNECTIONS’ in the NETWORK Configuration will have no effect on communication between servers. These entries will remain in the NETWORK Configuration as valid syntax, but the following comment will be added to indicate that these will no longer work:

From Prognosis 11, node to node communications will always be encrypted.

! ALLOW-LEGACY-CONNECTIONS and FORCE-LEGACY-CONNECTIONS will be still valid

! NETWORK static conf syntax but will have no affect on node communication.

A Prognosis 11 upgrade on an MS Windows server will add the ‘FORCE-FIPS-ENCRYPTION’ statement to the NETWORK Configuration. However, this will be disabled by default. To enable FIPS it will be necessary to un-comment the ‘FORCE-FIPS-ENCRYPTION’ statement:

! Use this command to force all net router communication to and from this node

! to be encrypted using the FIPS 140-2 certified OpenSSL library.

! FORCE-FIPS-ENCRYPTION ()

Prognosis 11.0

Upgrade Checklist Checklist for upgrading the IR Prognosis server on an MS Windows machine. Before proceeding with the upgrade please go through the following checklist and ensure that all items have been addressed.

Upgrade Checklist - MS Windows

1. Release Notes




Ensure that you have the Prognosis for Windows installation file (Prognosis11.x.x.exe). This can be downloaded from the Prognosis Online web site and saved to a suitable drive/folder on the Windows server (where required the installation may also be provided on CD/DVD).



When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files. If the license file has not been received, please contact your Prognosis account manager.


4. Which version of Prognosis is currently installed?

The upgrade facility is only available from certain Prognosis versions. For details see the MS Windows Upgrade Installation topic (page 99).

5. Has Prognosis 11 already been installed on the Windows Client and any higher level Management servers?

If not, these must be upgraded first.

6. Check the Prognosis server requirements.

See: Server Requirements - MS Windows (page 35).

7. Check that this version of Prognosis will still monitor the required platform/middleware versions.


8. Are there any customized Prognosis solutions installed?

If there are currently any customized solutions created by the Integrated Research Consulting Group on this server, have Prognosis 11 solutions been provided? If not, please contact your Prognosis account manager.

Prognosis 9.1 and Prognosis for Unified Communications 9.6.1 customized solutions

will not work on Prognosis 10 or later.

9. Carry out a backup of the previous Prognosis version.

See: Backup Instructions (page 112).





Installation


10. Pre-requisite software

The following software is required on the server. If the installer does not find this software on the destination machine it will be automatically installed (for Unattended Installations (page 130), this software will need to be manually .installed first.)

Microsoft Visual C++ 2013 Redistributable Package (x86) – needed to run 32-bit Prognosis code (on both 32-bit and 64-bit Windows)

Microsoft Visual C++ 2013 Redistributable Package (x64) – needed to run 64-bit Prognosis code (on 64-bit Windows)

Microsoft .NET Framework 4.6. This is needed to run .NET Prognosis code (on both 32-bit and 64-bit Windows).

11. Ensure that the correct level logon available (username/password)

Administrator privileges will be required for the system on which Prognosis will be installed.

12. Determine which disk drive and folder path Prognosis is to be installed on.

The server installation cannot be made into any of the following folders:


This is because Prognosis needs to save/modify files in its installed location as the logged in user. In MS Windows problems can occur when trying to do this in these folders unless the user is an administrator, which may not be the case.

13. SSL Certificate (Web Application)

The upgrade process may overwrite an existing SSL certificate that has been assigned to the Prognosis Web Application. Therefore, it is recommended that any applicable SSL certificate be backed up before attempting the upgrade and then re-assigned (re-bind) after the upgrade is completed. This does not apply for Self-signed Certificates'.

14. Is SNMP installed?

If installed, the SNMP service enables Prognosis to monitor remote devices. Prognosis will still run without the SNMP service but some data will be unavailable. SNMP can be installed from the Add/Remove Programs Control Panel applet by selecting the Add/Remove Windows Components wizard and installing the Management and Monitoring Tools component.

15. Check if CopSSH is installed. (Prognosis for Unified Communications)

Effective with version 10.3, Prognosis no longer relies on CopSSH for monitoring Cisco UCM 5+, Acme Packet SBC and Avaya Aura Session Manager environments. Provided that no version of CopSSH is found on the machine the Installation will now install its own SFTP server. However, if an existing copy of CopSSH is found a manual procedure may be required.

See: CopSSH (page 86).

16. Disable virus checking software.

It is preferable that all types of virus checking software be disabled on the destination machine. However, if this is not possible then the Prognosis folder/directory should be added to the virus checking exclusion list. Active virus checking software may cause system problems ranging from errors when accessing configurations to the slow transfer of data between servers.

Prognosis 11.0


17. Proxy Server Settings (Web Session Recorder only)

This instruction is only applicable for users of the Prognosis Web Application Management product suite, specifically the Web Session Recorder. If a Proxy server is being used on the network it may be necessary to configure the Internet Explorer settings so that the required internet access is made available to the Prognosis Web Session Recorder.

See: Proxy Server Settings (page 88).

18. Create an IRFAX

Generate a new IRFAX as a snapshot of the system before the upgrade.

19. Is the Prognosis Windows Client to be included with this installation?

See the Windows Client section (page 204) for information specific to this component.

20. Is the Prognosis Web Application to be included with this installation?

See the Web Application section (page 194) for information specific to this component.

21. Is Prognosis UC Reporter required with this installation?

See the UC Reporter section (page 214) for information specific to this component.

Once the checklist has been completed proceed with the Prognosis upgrade. For the upgrade procedure please refer to the topic below which corresponds to the Prognosis version being upgraded :

- Prognosis 9.1 SP4 (page 120)

- Prognosis for Unified Communications 9.6.1 Update 7 (page 120)

- Prognosis for Unified Communications Foundation Edition 10.0 (page 120)

- Prognosis 10.0 or later (page 115)

- Manual Upgrade Procedure (page 128) (optional for 64 bit upgrades/mandatory for migrating from 32 bit machines)

After completing the upgrade procedure, all required Prognosis Databases, Analysts and Thresholds

should be stopped and restarted in order to take up any new records etc.

Installation

Upgrade Process This topic describes the automatic backup/rollback procedure used by the IR Prognosis upgrade process. This is different to the manual backup, which is strongly recommended and described in the Backup/Rollback Previous Version topic (page 112).

Once the upgrade is started, the following four step process will take place:

Step 1 Automatic backup of the previous Prognosis configuration. A backup folder will be created on the root drive where the previous Prognosis version is installed in the following format:

\PrognosisBackup\PrognosisBackup-<MachineName>-yyyy-mm-ddThh.mm.ss

e.g. C:\PrognosisBackup\PrognosisBackup-ServerA-2013-08-27T09.46.44

The following files will be backed-up:

Registry: HKLM/Software/Wow6432Node/IntegratedResearch/Prognosis

Configurations: All enabled

Analysts: All running Analysts

Thresholds: All running Thresholds

Databases: All running databases (including autosumm dbs, sqlite dbs)

.ext files none

.csv .pl, .pm, .bat none

Log files: Prognosis_Home\Install.log

Prognosis_Home\Patches\audit.log

Prognosis_Home\Server\Configuration\wvlog.txt

Prognosis_Home\Server\Configuration\Autosumm*.log

.ini files Prognosis_Home\User Interface\irgui.ini

Prognosis_Home\Server\Configuration\*.ini

Cisco *-config.ini files and discovered clusters dirs

.txt files Prognosis_Home\Server\Configuration\Datastore.txt

Prognosis_Home\Server\Configuration\rollupscheduletable.txt

files mentioned in 'rollupscheduletable.txt'

Prognosis_Home\Server\Configuration\rollup*.txt

Prognosis_Home\Server\Configuration\*autosumm*.txt

.xml files Prognosis_Home\User Interface\prompt.xml

Prognosis_Home\Server\Configuration\*\*.xml

Prognosis_Home\www\webserver\tomcat\webapps\ROOT\SipEntities.xml

Prognosis_Home\www\webserver\tomcat\webapps\ROOT\EntitiesLink.xml

Web Application Files

(Upgrading from Prognosis 10 and later)

Prognosis_Home\WebUI\IIS\Dashboards\reportlistdata.xml

Prognosis_Home\WebUI\IIS\Dashboards\Prognosis.owl

Prognosis_Home\WebUI\IIS\Dashboards\search.xml

Prognosis_Home\WebUI\IIS\Dashboards\prompt.xml

Prognosis_Home\WebUI\IIS\Dashboards\persistviewsUI.xml

Dashboards and queries that are referenced in key displays and mashups navigation panel in the web UI interface

Dashboards and queries that are referenced by reportlistdata.xml file

Prognosis_Home\WebUI\IIS\Web.config

Prognosis 11.0

If the Web Application default port/certificate settings have been changed, these will not be backed up and therefore on restore will revert

back to the default settings.

Other Prognosis_Home\User Inteface\My Documents And Configuration/*

Prognosis_Home\Server\Configuration\defssrv

Prognosis_Home\Server\Configuration\defscnf

Prognosis_Home\Server\Configuration\udefssrv

Prognosis_Home\Server\Configuration\udefsrec

Prognosis_Home\Server\Configuration\udefserr

Prognosis_Home\Server\Configuration\IPTM

Alcatel 'ticket' dir if found

If the backup fails, the installation of the new Prognosis version will terminate and no changes will be made to the previous Prognosis installation.

Step 2 Uninstall the previous Prognosis version.

The Prognosis upgrade will uninstall the previous Prognosis version together with all its associated components, services, registry entries, start menu shortcuts, directories etc.

Step 3 Install the new Prognosis version

Step 4 Restore the previous Prognosis configurations to the new Prognosis installation.

The PrognosisBackup folder will be used to restore user configurations to the new installation.

When upgrading from Prognosis 10 or later, the following Web Application features will be restored:

Web Application Files

(Upgrading from Prognosis 10 and later)

Changes made to reportlistdata.xml will be saved to reportlistdata_user.xml (the new reportlistdata.xml will not be modified)

Changes made to search.xml will be saved to search_user.xml (the new search.xml will not be modified)

Changes made to persistviewsUI.xml will be saved to persistviewsUI _user.xml (the new persistviewsUI.xml will not be modified)

Saved dashboard files will be restored

Saved queries obtained from the dashboard files will be stored in persistviewsUI_user.xml

Prognosis.owl file will be merged

The web.config will be merged and changes to web.config in the latest version will be applied to the restored file

Upon successful restoration the PrognosisBackup directory will be automatically removed.

In the event of any upgrade failure, please refer to the Upgrade Troubleshooting topic (page 109).

Installation

Upgrade Troubleshooting The following provides some details on how to address possible upgrade failures. If in doubt about any upgrade failure please contact IR Prognosis Technical Support.

Upgrade fails during backup of the previous version (Upgrade process - Step 1 (page 107))

In this case the installer will rollback leaving the earlier version untouched. After checking the log file and attending to the issue that caused the failure, the upgrade may be attempted again. For details see the 'Troubleshooting Backup Issues (page 110)' and 'Previous Prognosis Control Panel Running (page 110)' sections that follow.

Upgrade fails during uninstallation of the previous version (Upgrade Process - Step 2 (page 107))

In this case the installer will rollback with the backup process completed. However, the earlier Prognosis version may be fully or only partially uninstalled. A manual uninstall of the earlier version may be required (see the Installation Guide from the earlier version for instructions on how to carry this out). The Prognosis 11 installer can now be run again, this time it will run as a 'new' installation, not an upgrade. Once the installation is complete, the configuration from the earlier version may be restored by running the 'restore' utility. See the 'Running the Manual Restore Utility (page 109)' section below.

Upgrade fails before running the restore process (Upgrade Process - Step 3 (page 107))

The previous version has been uninstalled at this stage, so the Prognosis 11 installer can now be run again, this time it will run as a 'new' installation, not an upgrade. Once the installation is complete, the configuration from the earlier version may be restored by running the 'restore' utility. See the 'Running the Restore Utility (page 109)' section below.

Upgrade fails while running the restore process (Upgrade Process - Step 4 (page 107))

In this case the Prognosis 10.x configuration has been restored partially and encountered some unexpected errors. Since the PrognosisBackup folder is not removed, it may be restored manually by running the 'restore' utility, see the 'Running the Manual Restore Utility (page 109)' section below. However, before doing a manual restore it is recommended to check the restore log file to determine the cause of the error. For more details please see the 'Troubleshooting Restore Issues' (page 111) section that follows.

Running the Manual Restore Utility

Upgrade on the same drive as the previous Prognosis version Backup folder

a) Install the new Prognosis version on the same drive as the PrognosisBackup folder

b) Go to the 'Backup_restore' folder of the new Prognosis installation, e.g. C:\Prognosis\Backup_restore

c) Double click on 'PrognosisRestore.bat

Upgrade on a different drive to the previous Prognosis version Backup folder

a) Install the new Prognosis version on the required drive, e.g. E:\Prognosis

b) Go to the 'Backup_restore' folder of the new Prognosis installation, e.g. E:\Prognosis\Backup_restore

c) Open a command prompt with administrative privileges and run PrognosisRestore.bat specifying the location of the backup folder, e.g. E:\Prognosis\Backup_restore>PrognosisRestore.bat C:\PrognosisBackup\PrognosisBackup-ServerA-2013-08-27T09.46.44

Prognosis 11.0

Troubleshooting Backup Issues

When an error has occurred during the Prognosis backup, it will be necessary to fix the error manually before re-running the Prognosis installer. To do this proceed as follows:

Step 1 To determine the cause of the failure, open the backup log which resides in the following folder path:

<RootDrive>\PrognosisBackup\PrognosisBackup-<MachineName>-<DateTime>\Log\Backup.log

where <RootDrive> is the drive where Prognosis 9 is installed.

Example:

C:\PrognosisBackup\PrognosisBackup-ServerA-2013-12-01T09.00.00\Log\Backup.log

Step 2 Search for the text ‘Error:’ in the log file. This will typically reveal what items have not been backed up successfully. These will usually be Analyst, Threshold or Database documents where the Prognosis SECURITY Configuration is preventing the installer from executing certain commands.

Example

Backing up Thresholds

----------------------

No THRESHOLD detected in MyAlert listing. Error: No threshold data

returned.

or

Copying Database Templates and Files to Backup Location.

---------------------------------------------------------

Error reading 'Trouble_Shooting',error: Access denied to database Trouble

Shooting.

Step 3 Open the previous Prognosis version make a backup copy of the SECURITY Configuration file. Copy this to a temporary location.

Step 4 In the original SECURITY Configuration replace the entire text content with:

SUBSYS SECURITY

GRANT (*,*,*)

Step 5 The upgrade can now be run again. As the security has now been deactivated the upgrade should run without failure.

Step 6 Copy the backup SECURITY Configuration file from the temporary location into the new Prognosis installation.

Previous Prognosis Control Panel Running

If the old Prognosis Start/Stop Control Panel is still running, it may cause the upgrade to fail. This will be indicated by a message similar to the following the 'install.log' (this is located in the same folder path as the 'backup.log - see above).

2013-11-25 14:00:37 running process off 'irstartstop.exe':

'E:\PROGNOSIS\Server\Configuration\IRStartStop.exe', PID=4936

2013-11-25 14:00:37 The Prognosis Service Control Panel is running. Please close

the Prognosis Service Control Panel and press OK to continue.

2013-11-25 14:00:39 running process off 'irstartstop.exe':

'E:\PROGNOSIS\Server\Configuration\IRStartStop.exe', PID=4936

2013-11-25 14:00:39 The Prognosis Service Control Panel is still running. Please

close the Prognosis Service Control Panel and run setup again. Setup incomplete.

Action ended 14:00:41: InstallFinalize. Return value 3.

To overcome this problem, simply close the Prognosis Control Panel dialog box on the Windows Desktop.

Installation

Troubleshooting Restore Issues

When an error has occurred during the Prognosis restore, the Prognosis installer will log the error and continue. In this case, the backup folder will not be removed. The items which have not been successfully restored can usually be restored manually from the backup folder. To do this proceed as follows:

Step 1 To determine the cause of the failure, open the restore log which resides in the following folder path:

<Prognosis11 Folder>\Backup_restore\Restore-<MachineName>-<DateTime>.log

where <Prognosis11 Folder> is the folder where the new Prognosis version is installed.

Example:

C:\Prognosis\Backup_restore\Restore-ServerA-2013-12-01T09.00.00.log

Step 2 Search for the text ‘Error:’ in the log file. This will typically reveal what items have not been restored successfully.

Step 3 Open the backup folder which can be found in the following folder path:

<RootDrive>\PrognosisBackup\PrognosisBackup-<MachineName>-<DateTime>

where <RootDrive> is the drive where Prognosis 9 is installed.

Example:

C:\PrognosisBackup\PrognosisBackup- ServerA-2013-12-01T09.00.00

Step 4 Locate the missing item in the backup folder.

Step 5 Copy the item to the new Prognosis version into the Server/Configuration folder.

Step 6 Open a command prompt with administrative privileges and change to the Prognosis/Server/Configuration folder.

Step 7 Run "..\ircmd" on the copied document.

Example

C:\Prognosis\Server\Configuration>..\ircmd myalerts_threshold.txt

Example

The restore log indicates that there is an error in restoring Thresholds.

Resolution:

i. From the backup folder open the 'Threshold' sub-folder and locate the required Threshold template (.txt) file.

ii. Copy the Threshold file into the Prognosis\Server\Configuration folder of the new installation.

iii. Open a command prompt with administrative privileges and change to the Prognosis\Server\Configuration folder.

iv. Run “..\ircmd” on the copied Threshold txt file.

Prognosis 11.0

Backup/Rollback Previous Version As the upgrade process will remove the earlier IR Prognosis version, it is recommended that a manual backup of the previous version be made prior to attempting the upgrade. This provides an opportunity to roll back to the previous version if necessary.

This procedure is a complete backup of the previous Prognosis version, it should not be confused with the automatic 'backup' which is carried out by the new Prognosis upgrade process which is only used to transfer configuration data to the new version and is then automatically deleted. See the Upgrade Process

topic (page 107) for further details.

Pre-Version 10

Backup

The following files, if installed, should be backed-up. The following examples are based on a default installation.

Step 1 Create a backup location outside of the existing Prognosis installation folder that can be used to store the backup items (e.g. C:\Prognosis-Backup).

Step 2 Back up the whole Prognosis installation folder (e.g. C:\Program Files\Prognosis). To do this simply 'zip' the whole Prognosis folder and copy to the backup location.

Step 3 Back up the Prognosis folder of the Windows Start Menu (e.g. C:\Users\All Users\Microsoft\Windows\Start Menu\Programs\Prognosis). To do this, locate and then copy the Prognosis folder to the backup location.

Step 4 Back up the following Windows Registry keys. To do this open the Registry Editor (regedit), locate each key, click the File Menu and then select Export. In the Save box select the backup location and then click Save.

a) Back up the Registry Key (Old installation log data): HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS\ServiceName Example:

HKEY_LOCAL_MACHINE\Software\IntegratedResearch\PROGNOSIS\PROGNOSIS

b) Back-up the Registry Key for the InstallShield uninstall settings. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\<PRODUCT_GUID> Example: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall\{2B10CE30-4318-11DO-8640...}

<PRODUCT_GUID>

Where there are multiple installations of Prognosis on the same machine, it is important that the Uninstall Key being backed up is the correct one. To do this locate the Uninstall Keys that have a prefix matching {2B10CE30-4318-11DO-8640...}, if there is more than one Prognosis installation then there will be multiple Uninstall Keys with this prefix. Click on each one and check the Key Value 'LogFile', this will indicate the path of that particular Prognosis installation. Check each Uninstall Key to find the 'LogFile' value that matches the path of the installation to be backed up.

Installation

Rollback

After completing a backup, should it be necessary, it is then possible to roll back to the previous Prognosis installation.

If a complete or part Prognosis 10.x installation needs to be removed first, see the Rollback instructions in the 'Version 10 Onwards' section below.

To restore the previous version:

Step 1 Expand the backed-up Prognosis files into the required folder (e.g. C:\Program Files\Prognosis).

Step 2 Restore the backed-up Prognosis Start Menu item to the Start Menu folder (e.g. C:\Users\All Users\Microsoft\Windows\Start Menu\Programs).

Step 3 Restore the exported registry keys. Do this by locating the registry files (.reg) that were created as part of the Backup procedure and then double click on them.

Version 10 and later

Backup

The following files, if installed, should be backed-up. The following examples are based on a default installation.

Step 1 Create a backup location outside of the existing Prognosis installation folder that can be used to store the backup items (e.g. C:\Prognosis-Backup).

Step 2 Back up the whole Prognosis installation folder (e.g. C:\Prognosis). To do this simply 'zip' the whole Prognosis folder and copy to the backup location.

Step 3 Back up the Prognosis folder of the Windows Start Menu (e.g. C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Prognosis). To do this, locate and then copy the Prognosis folder to the backup location.

Step 4 Back up the following Windows Registry keys. To do this open the Registry Editor (regedit), locate each key, click the File Menu and then select Export. In the Save box select the backup location and then click Save.

a) Back up the Registry Key (Old installation log data): HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IntegratedResearch\Prognosis\<service-name> Example: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IntegratedResearch\Prognosis\Prognosis

b) Back-up the Registry Key for the InstallShield uninstall settings (Uninstall Key). HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\<PRODUCT_GUID> Example: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{2B10CE30-4318-11DO-8640...}

<PRODUCT_GUID>

To locate the <PRODUCT_GUID>, search for the “ProductCode” key value under “HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\IntegratedResearch\Prognosis\Prognosis.

Prognosis 11.0

Rollback

After completing a backup, should it be necessary, it is then possible to roll back to the previous Prognosis installation.

If a complete or part Prognosis installation needs to be removed first, carry out these steps:

Step 1 Stop all running Prognosis processes.

Step 2 Delete all files from the Prognosis folder (e.g. C:\Prognosis).

Step 3 Delete the Prognosis folder from the Windows Start Menu.

Step 4 Delete the newly created uninstall registry key, once again, checking for the correct PRODUCT_GUID (see Backup procedure):

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Windows\CurrentVersion\Uninstall\<PRODUCT_GUID>

To restore the previous version:

Step 5 Expand the backed-up Prognosis files into the required folder (e.g. C:\Prognosis).

Step 6 Restore the backed-up Prognosis Start Menu item to the Start Menu folder (e.g. C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Prognosis).

Step 7 Restore the exported registry keys. Do this by locating the registry files (.reg) that were created as part of the Backup procedure and then double click on them.

There could be some locked files/folders - delete as much as possible. Locked files/folders are released

by rebooting the machine.

Any steps involving the Registry Key’s should only be attempted by a qualified System Administrator with knowledge of these files. Incorrect actions could cause serious damage to the system. If in doubt please contact Prognosis Technical Support.

Should the 'Rollback' not be successful, please contact Prognosis Technical Support for assistance.

Installation

Upgrade Procedure - MS Windows (from version 10+) The upgrade procedure covered in this topic is applicable for upgrading a IR Prognosis MS Windows server from the following Prognosis versions to the latest release:

Prognosis 10.0 SP1, 10.1, 10.1.5 (patch 4), 10.2 (patch 1), 10.3 (patch 7), 10.4 (patch 7) & 10.5 (patch 5)

Prognosis for Unified Communications Foundation Edition 10.0

For Skype for Business, the following products can be upgraded to Prognosis 11:

Prognosis 10.4.1 (patch 7) & 10.5.1 (patch 11)

Procedure


or






- Setup.exe





Prognosis 11.0


The next step in the installation is the acceptance of the End User License Agreement (EULA).





If the license agreement is not acceptable, click the Cancel button and the installation will be

aborted.

Installation






Windows Client

Web Application



Prognosis 11.0


This dialog box confirms that the installation settings have been made and that Prognosis will make any necessary Firewall (page 11) changes. If the Web Application component has been included it will confirm the port that has been configured.



At this stage a backup of the previous Prognosis version's configuration will take place, see the Upgrade Process topic (page 107) for details. Should an error occur in the backup or the subsequent restore process a message box will now appear, for steps on how to attempt to overcome this situation please refer to the Upgrade Troubleshooting topic (page 109).

Installation



The Prognosis upgrade may include new drivers. These drivers may not become effective until after the next reboot of the Windows Server. If a reboot is required, a prompt will be shown advising that a reboot of the machine can be made now or later.

If the Web Application component is detected, the installer will check for the system state. If a reboot is required after a previous installation, or a Windows update, the installer will terminate and show a message requesting a reboot before re-running the installation.



Prognosis 11.0

Upgrade Procedure - MS Windows (from pre-version 10) The upgrade procedure covered in this topic is applicable for upgrading a IR Prognosis MS Windows server from the following Prognosis versions to the latest release:

Prognosis 9.1 SP4,

Prognosis for Unified Communications 9.6.1 Update 7,

Procedure

Step 1 Place the Installation CD into the CD drive of the required machine. If Autorun is activated the CD will start the installation automatically. If the installation fails to start, go to Windows Explorer, select the CD drive, copy the Prognosis installer to a local drive and then run the Prognosis 11.x.x.exe file.

or

Download the Prognosis installer to a local hard disk and then run the Prognosis 11.x.x.exe file.





- Setup.exe





Installation


The next step in the installation is the acceptance of the End User License Agreement (EULA).





If the license agreement is not acceptable, click the Cancel button and the installation will be

aborted.

Prognosis 11.0

Step 3 Upgrade

Setup will now detect if a valid Prognosis version is available for upgrade:

The following message will be shown where a valid Prognosis version is detected..

Click the Next button to proceed with the upgrade.

If a valid version is not found, click the Cancel button to terminate the upgrade and refer to the

Upgrade Installation topic (page 99) for further details.

Installation

Step 4 License


In most cases the license information is sent by email as an attached text file. When received, it is recommended that the license file be saved to the same folder as the Prognosis installation files

The License dialog box will default to the same folder path as the installation files, should the license be located elsewhere or should an invalid license be found, an alternative license location can be specified or browsed for.

The license field may be left blank, however this will only allow the Prognosis Windows Client to be installed. Please note that the Windows Client cannot be used with the UC Foundation Edition license.


Prognosis 11.0






Windows Client

Web Application



Installation


This dialog box is used to assign the folder path where this copy of Prognosis will be installed.






Prognosis cannot be installed into an existing folder. However, for upgrade, the folder of the previous Prognosis version may be used as long as it is not within one of the folders mentioned above.

Absolute file name length cannot exceed 258 characters. As the relative path and field names of the Prognosis packaging can reach up to 210 characters, it is strongly recommended to limit the

absolute path for the Prognosis GUI home installation folder to 45 characters.


new folder.

Prognosis 11.0


This dialog box confirms that the installation settings have been made and that Prognosis will make any necessary Firewall (page 11) changes. If the Web Application component has been included it will confirm the port that has been configured.



At this stage a backup of the previous Prognosis version's configuration will take place, see the Upgrade Process topic (page 107) for details. Should an error occur in the backup or the subsequent restore process a message box will now appear, for steps on how to attempt to overcome this situation please refer to the Upgrade Troubleshooting topic (page 109).

Installation



The Prognosis upgrade may include new drivers. These drivers may not become effective until after the next reboot of the Windows Server. If a reboot is required, a prompt will be shown advising that a reboot of the machine can be made now or later.

If the Web Application component is detected, the installer will check for the system state. If a reboot is required after a previous installation, or a Windows update, the installer will terminate and show a message requesting a reboot before re-running the installation.



Prognosis 11.0

Manual Upgrade Procedure This procedure will need to be used when migrating an existing IR Prognosis 32 bit installation to the latest Prognosis version on a 64 bit Windows server. In these cases the standard Upgrade procedure (page 120) cannot be used.

This procedure may also be used when upgrading an existing 64 bit Prognosis Windows server to the latest version if it is not practical to use the standard upgrade procedure or if there is a need to migrate the previous Prognosis version to the new version on a different machine.

Procedure

Step 1 From a folder on a local machine run the standard Prognosis installer (Prognosis11.x.x.exe). The exe file is a self-extracting/self-installing executable that will extract itself into a folder named 'Prognosis11.x.x'. On slow machines this process may take a few minutes. Once extracted, this folder will contain the following:




- Setup.exe

Step 2 The Setup.exe will automatically start to run on the local machine. This should be cancelled when the 'Welcome to Prognosis' dialog is displayed.

Step 3 Copy the Backup_restore folder to the existing Prognosis version home folder (for example, C:\Prognosis9\Backup_restore).

Note that the following files should be in this folder:

backup.bat,

backup.pl,

BackupPrognosis.pm,

PrognosisBackup.bat,

PrognosisRestore.bat.

Step 4 Run the PrognosisBackup.bat script in C:\Prognosis9\Backup_restore. When this command

finishes, a \PrognosisBackup folder will be created on the current drive, for example C:\PrognosisBackup\PrognosisBackup-machinename-datetimestamp. This folder contains the back up of the previous Prognosis system.

Step 5 If migrating Prognosis 9 to a different machine running Prognosis 11, copy the PrognosisBackup folder created in the previous step to the new machine. For example, copy to

"C:\MyBackup\PrognosisBackup-machinename-2013-09-27T09.46.44" on the target

machine.

Step 6 Installing Prognosis 11

Upgrade

To upgrade on the existing machine, uninstall Prognosis 9.x and then install Prognosis 11 as a new installation.

Migrate

To migrate to a different machine, install Prognosis 11 on the target box as a new installation.

Installation

Step 7 Restoring the configuration

Upgrade

From the Prognosis 11 Backup_restore folder, run the PrognosisRestore.bat script, specifying

the backup folder path created in Step 2. For example:

C:\Prognosis\Backup_restore>PrognosisRestore.bat

"C:\PrognosisBackup\PrognosisBackup-machinename-2013-09-27T09.46.44"

Migrate

From the target machine, run the PrognosisRestore.bat script from Prognosis 11 installation

folder by specifying the backup folder path in Step 3. For example:

C:\Prognosis\Backup_restore>PrognosisRestore.bat

"C:\MyBackup\PrognosisBackup-machinename-2013-09-27T09.46.44"

Upon successful restore, the backup folder will be removed.

Prognosis 11.0

Unattended Installation Unattended installation is an automated process for installing IR Prognosis with minimal user intervention. This feature is most useful when the standard installation needs to be performed on a number of separate machines. The Prognosis unattended installation can be carried out by using the msiexec command. The command includes parameters that provide all the information required to complete the installation without any user intervention. This reduces the risk of errors that may be introduced during the setup process and provides consistency in the configuration of multiple machines.

The unattended installation method assumes that any prerequisites required for the Prognosis installation have been attended to, see the Installation Checklist topic (page 83) for details.

For an unattended installation the msiexec command is used with either of the following switches:

/q, /qn or /quiet for 'quiet' mode without user interaction, or

/passive for 'quiet' mode with a progress bar.

It is recommended to always run msiexec with a log file in order to troubleshoot any installation problems. To

do this include the following switch:

l*v <path>\install.log

MS Windows Server 2008 and later

If the unattended installation is being undertaken on an MS Windows Server 2008 (or later) machine with User Account Control (UAC) enabled, it is recommended to invoke the unattended installation from an 'elevated' command prompt. This is done by using a right-click to start the command prompt and choose Run as administrator. If the unattended install is attempted from a non-elevated command prompt the installer

will prompt for permission to install the software. If this is not accepted the installation will fail.

Pre-requisite software

The following software is required on the Prognosis server. For Unattended Installations, this software will need to be manually .installed on each machine before commencing the installation.

Microsoft Visual C++ 2010 SP1 Redistributable Package (x86) – needed to run 32-bit Prognosis code (on both 32-bit and 64-bit Windows)

Microsoft Visual C++ 2010 SP1 Redistributable Package (x64) – needed to run 64-bit Prognosis code (on 64-bit Windows)

Microsoft .NET Framework 4 full – needed to run .NET 4 Prognosis code (on both 32-bit and 64-bit Windows).

Command Parameters

The msiexec command is run with a number of parameters that are used to specify the installation requirements. When adding the command parameters it is important to note the following:

Parameter labels must be in UPPER CASE

Value Strings are case-sensitive.

We recommend that all value strings be enclosed in quotation marks. However, if a value string includes a blank, the entire value string must be enclosed in quotation marks.

From a command prompt input:

>msiexec /quiet /i "<path_to_msi>\Prognosis10.msi" /l*v "C:\install.log"

ACCEPTENDUSERLICENSEAGREEMENT=1 ADDLOCAL="ALL"

LICENSE="<path_to_license>\license"

Installation

The following table shows the various parameters than can be included with the msiexec command for an unattended Prognosis installation.

Parameter Label Value String Description

ACCEPTENDUSERLICENSEAGREEMENT=

(mandatory)

0 or 1 Accept the terms of the Prognosis license agreement. In order for the installation to proceed this must be set to 1 (Accept). Selecting 0 (decline) will terminate the installation.

ADDLOCAL=

(mandatory)

ALL,

ManagementServer,

MonitoringServer,

WebApplication,

WindowsClient

UCReporting

or

<component>, <component>,...

Specify the Prognosis components (page 31) to be installed.

The 'ALL' value will install all supported components,

Certain single components can be added or multiple components can be added using a comma-separated list

- ManagementServer

- MonitoringServer

- WindowsClient

- WebApplication (can only be added with a Server component)

- UCReporting (can only be added with Management Server)

There is no default value for unattended installation, a value must be provided.

Note: Component names are case sensitive.

HOMEDIRECTORY=

(optional, if omitted the default is C:\Prognosis)

path Folder where Prognosis is to be installed. For example E:\Prognosis.

LICENSE=

(mandatory for server components, optional for the Windows Client)

path\file_name Specifies the location of the Prognosis license key (page 13) to be used.

PROGNOSISSECUREWEBSITEPORT=

(optional)

<port number> A user specified IIS port number to be used by the Prognosis Web Application.

This parameter is optional, if omitted the default is to use port 443. However, if port 443 is not available, the installer will check the availability of port 8080, if this is not available it will continue to search incrementing the port number by 1 each time up to port 8089.

Prognosis 11.0

Parameter Label Value String Description

REBOOT=

(optional, if omitted the default is 1)

0 or 1 If set to 0, the system state will not be checked, the installation will proceed regardless of any reboot requirement. Note that the Prognosis Web Application installation may fail with this setting.

If set to 1, the system state will be checked and if a reboot is found necessary the installation will terminate. Check the log file for a reboot request.

REUSECOPSSH=

(optional, if omitted the default is 0)

0 or 1 Effective with version 10.3, Prognosis no longer relies on CopSSH and will install its own SFTP server. However, if a Prognosis Monitoring Server component is selected with a Unified Communication license, the installation will detect if a copy of CopSSH currently exists on the machine and, if a reuseable version of CopSSH is found, the value from this parameter will apply:

If set to 0 the existing copy will not be used and the installation will terminate. The existing CopSSH copy will need to be uninstalled and the Prognosis installation restarted.

If set to 1, the existing copy of CopSSH will be reused and a manual configuration of CopSSH will be required. See the CopSSH topic (page 86) for details.

Examples:

C: >msiexec /quiet /i "D:\Prognosis10.msi" /l*v "C:\install.log"

ACCEPTENDUSERLICENSEAGREEMENT=1 ADDLOCAL="ALL" LICENSE="C:\Downloads\license"

C: >msiexec /passive /i "D:\Prognosis10.msi" /l*v "C:\install.log"

ACCEPTENDUSERLICENSEAGREEMENT=1

ADDLOCAL="ManagementServer,MonitoringServer,WebApplication,WindowsClient"

LICENSE="C:\temp\license" HOMEDIRECTORY="C:\Progonsis10"

PROGNOSISSECUREWEBSITEPORT=9979

When the /quiet switch is used, the msiexec command returns control to the user immediately (i.e. before the install has completed), while with the /passive switch control is not returned until the install completes and a Progress Bar is displayed. The exit code of the msiexec command is not reliable, so to determine if the installation is successful it will be necessary to refer to the log file. A Windows installer log file analyzer can be used for this if necessary (e.g. wilogutl.exe which is freely downloadable from Microsoft). In practice, simply searching for the string "Return value 3" in the installer log file will usually show the reason for an installation failure.

Installation

Uninstalling The IR Prognosis Server installation on an MS Windows operating system can be removed using either of the following methods. An initial attempt should be made using the MS Windows Control Panel which in most cases will easily remove all of the Prognosis Server components from the machine. Should this method fail, the manual uninstall procedure should be used.

For details see the following topics:

Using Windows Control Panel (page 134)

Using Manual Uninstall Procedure (page 135)

For Prognosis for Unified Communications versions before 10.3, the following procedure may be necessary if the automated uninstall fails:

Manual Uninstall of CopSSH (page 137)

Prognosis 11.0

Using Windows Control Panel IR Prognosis can be removed from the server using the standard Windows Control Panel applet.

Procedure

Step 1 It is recommended that all running applications be closed.

Step 2 From the MS Windows Start menu select Control Panel.

Step 3 From the Control Panel Window under Programs click on Uninstall a Program.

Step 4 On the Uninstall or change program window scroll down to Prognosis.

Step 5 Right click on Prognosis and select Uninstall from the context menu.

Step 6 A prompt requesting confirmation of the uninstall may be displayed, depending on the Windows settings. Click the Yes button to continue, or click the No button to cancel the uninstall.

Step 7 Setup will now shut down Prognosis and proceed to remove all parts of the application and data collected since the product was installed.

Installation

Using Manual Uninstall This section is to be used when the normal IR Prognosis uninstall, through the 'Uninstall or change a program' function, has not been successful. It provides step by step instructions for removing Prognosis completely from the system.

Procedure

These steps describe in chronological order the actions needed to remove Prognosis manually from the system.

Step 1 Stop the Prognosis service.

Open the Windows Services Control Panel; right click on the Prognosis entry and then select Stop

from the context menu.

Step 2 Uninstall the Prognosis Web Session Recorder (if installed).

From the 'Uninstall or change a program' function on the Windows Control panel, attempt to uninstall the Prognosis Web Session Recorder item. If the uninstall fails and is not clean delete the following Registry entries using Regedit (type 'Regedit' in the MS Windows search box):

HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft\Windows/CurrentVersion/Uninstall/Prognosis Web Session Recorder

HKEY_LOCAL_MACHINE/SOFTWARE/IntegratedResearch/Prognosis Web Session Recorder

Step 3 If this is a Prognosis for Unified Communications installation which has CopSSH installed, it will be necessary to uninstall CopSSH before proceeding further. See the Manual Uninstall of CopSSH topic (page 137) for details. After uninstalling CopSSH proceed with the next step of these instructions.

Step 4 Remove the Prognosis service.

C:\>sc delete prognosis

Successful response:

C:\>sc delete prognosis

[SC] Delete Service SUCCESS

Step 5 Manually delete the Prognosis folder

Step 6 Delete Registry Keys. Using Regedit (type 'Regedit' in the MS Windows search box) locate and

delete the following registry keys:

(32 bit machine) HKEY_LOCAL_MACHINE/SOFTWARE/IntegratedResearch/Prognosis/Prognosis

or

(64 bit machine) HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/IntegratedResearch/Prognosis/Prognosis

Then:

HKEY_LOCAL_MACHINE/SOFTWARE/Wow6432Node/Microsoft/Windows/CurrentVersion/Uninstall/{0FCC2BF6-5B88-447E-9EEC-4E64B5CC69EC}.

Step 7 Delete Start menu shortcuts.

Click the Windows Start button

Locate and right click on the Prognosis folder that is to be removed and then click 'Delete' on the shortcut menu.

Prognosis 11.0

Step 8 Remove Prognosis entries from IIS.

If Prognosis 11 was manually uninstalled, it may be necessary to manually remove the web site. To do this, go to the Internet Information Services (IIS) Manager (type 'IIS' in the MS Windows search box), then select 'View Sites' in the Actions panel on the right. On the Sites page, find the IrPrognosisSite, right click and select Remove.

Next, go to the Application Pools page, click on Application Pools in the Connections panel on the left side. Find the PrognosisAppPool and delete this as well.

A Prognosis self-signed certificate is the third element that would have been installed. To remove this, click on the machine name in the Connections panel then select the "Server Certificates" icon in the IIS panel in the center of the page. on the "Server Certificates" page remove the Prognosis certificate.

Step 9 When finished shut down and then restart the machine.

Installation

Manual Uninstall of CopSSH

Prognosis for Unified Communications only. Effective with Prognosis 10.3, CopSSH will no longer be installed. However, the following procedure may be required for earlier Prognosis versions.

The procedure to manually uninstall CopSSH is dependent on any previous attempts to uninstall IR Prognosis. In order to undertake this uninstall procedure it is necessary to stop the Prognosis service and be logged in as either a local Administrator or a member of an administrative group.

The uninstallation options are shown in the following two scenarios.

Scenario 1 - IR Prognosis uninstallation has not been attempted

Follow these steps if you have not attempted to uninstall Prognosis. The CopSSH installation should be intact.

Step 1 Stop all sftp and sshd connections to 3rdparty/copssh

To do this, open the Windows Task Manager, select the 'Processes' tab and then sort by 'User Name'. Look for any processes with a user name of SvcCOPSSH or PrognosisCDR. Next stop the 'OpenSSH SSHD' Windows service and see if all these processes stop. If they all stop, you are done. Otherwise, manually kill (via Task Manager, right-click "End Process") any remaining sshd.exe processes, followed by any remaining sftp_server.exe processes (the order of terminating these processes is important).

Step 2 De-activate the PrognosisCDR user account:

<Install_Path>\Prognosis\3rdparty\CopSSH\bin > copsshadm.exe -c

deactivateuser -u PrognosisCDR"

Step 3 Uninstall CopSSH

<Install_Path>\Prognosis\3rdparty\CopSSH > uninstall_Copssh.exe

Step 4 The CopSSH uninstallation leaves some files behind which will need to be removed manually.

(a) Check that the "copSSHD" NT service has been removed by either opening the Services control panel, or use the command line interface to the Service Control:

sc query copSSHD

The service can be deleted with the command:

sc delete copSSHD

(b) Clean up the Windows Registry. Remove the following keys in the undermentioned Registry node: HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions HKEY_LOCAL_MACHINE\SOFTWARE\Itefix HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\COPSSH HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\copSSHD

(c) Remove the Start Menu item. If CopSSH was installed manually then the Start Menu item will be present, otherwise it will be absent. To do this check the location of the shortcut by viewing the value of the registry "Programs" under Registry key: HKEY_CURRENT_USER\Software\\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders This will provide details of where the shortcut "CopSSH" is present. If the "COPSSH" directory exists, then delete it.

Prognosis 11.0

(d) Delete the environment variable "CYGWIN" from the system.

(e) Remove the directory <Install_Path>\3rdparty\CopSSH if it is still present.

(f) Remove the following local user accounts: - PrognosisCDR - sshd - SvcCOPSSH To do this the net command can be used, for example:

netuser sshd /delete

(g) Remove local user profile: (MS Windows Vista and later) C:\Documents and Settings\SvcCOPSSH" (Pre MS Windows Vista) C:\Users\SvcCOPSSH

Scenario 2 - IR Prognosis uninstallation was attempted but failed

In this situation the Prognosis uninstallation was attempted but failed to uninstall CopSSH. It is possible the CopSSH installation may be corrupted by this partial uninstallation.

The procedure for uninstalling in this case is to follow the instructions from Scenario 1 starting at Step 4, i.e. omit the first three steps and proceed with the instructions in the fourth step.

It is possible that some directories and files under the CopSSH installation directory are owned by either the SvcCOPSSH or PrognosisCDR user and cannot be deleted. You will need to change the owner of the files under CopSSH to your login name. This can be done by opening the 'Properties' applet for the highlighted directory, then select the 'Security' tab and choose 'Owner'. On some machines the effect of this change may not be immediately apparent. Restarting Windows Explorer or rebooting the machine may be required.

Installation

Unattended Uninstall To uninstall IR Prognosis, it is recommended to stop all running Prognosis services and applications.

For an unattended uninstall the msiexec command is used with either of the following switches:

/q, /qn or /quiet for 'quiet' mode without user interaction, or

/passive for 'quiet' mode with a progress bar.

It is recommended to always run msiexec with a log file in order to troubleshoot any uninstall problems. To do

this include the following switch:

l*v <path>\uninstall.log

MS Windows Server 2008 and later

If the unattended uninstall is being undertaken on an MS Windows Server 2008 (or later) machine with User Account Control (UAC) enabled, it is recommended to invoke the unattended uninstall from an 'elevated' command prompt. This is done by using a right-click to start the command prompt and choose Run as administrator. If the unattended uninstall is attempted from a non-elevated command prompt the installer will

prompt for permission to uninstall the software. If this is not accepted the uninstall will fail.

Procedure

To invoke the unattended uninstall, it is preferred that the original msi file that was used for the installation be available, for example: D:\Prognosis11.x.x.msi. Otherwise, the product code GUID can be specified.

From a command prompt run:

> msiexec /passive /x “<path_to_msi>\Prognosis11.x.x.msi” /l*v

"c:\uninstall.log"

or

> msiexec /quiet /x <product_GUID> /l*v "c:\uninstall.log"

Examples:

C:\>msiexec /quiet /x "D:\Prognosis11.x.x.msi" /l*v "C:\uninstall.log"

C:\>msiexec /passive /x {503B0A85-9E2D-4E4A-80EF-A99356E555A7} /l*v

"C:\uninstall.log"

The GUID shown in the example above is the Prognosis 11 MSI Product Code. In general, the MSI product code GUIDs can be found in the Registry under HKLM/SOFTWARE/Microsoft/Windows/CurrentVersion/Uninstall. To find Prognosis product code GUIDs, look for product code in the Registry under HKLM/SOFTWARE/IntegratedResearch/IntegratedResearch. Alternatively, examine the Prognosis MSI file with the Orca utility, looking for the Product Code in the

Property table.

Should the unattended uninstall fail it may be necessary to revert to a standard manual uninstall, please refer to the Manual Uninstall topic (page 135) for details.

Prognosis 11.0

Server on UNIX/Linux This section provides the procedures for installing the IR Prognosis Management and/or Monitoring Server on a machine running the UNIX or Linux operating system.




Overriding the Default Tarball (page 141)




Associated topics:




Installation

Overriding the default tarball If there is a need to override the install/upgrade script to install a particular tarball, or if the install/upgrade script will not install IR Prognosis on the machine due to it not recognizing the operating system version, it is not necessary to edit install.sh. Instead, the -t command line switch can be used.

For example, to force the install of the AIX 433 tar file, use: ./install.sh -t paix43.gz, where the file paix43.gz

has been copied to the scratch directory from where you are running the install.

For more information on this and other command line switches type: ./install.sh -h

Prognosis 11.0

New Installation The following topics will provide details for a new installation of the IR Prognosis server component on to a UNIX/Linux machine.


Important Installation Notes (page 143)



Installing Prognosis with Oracle on UNIX (page 148)


Installation

Important Installation Notes It is important that the following information is read prior to attempting a IR Prognosis installation on UNIX or Linux platforms.

Installation Directory (page 143)

Linux - Red Hat Enterprise 64 bit (AMD or x86_64) (page 143)

Installation Directory

Before installation, it will be necessary to create a new non-root user (e.g. prgn) in a distinct group (e.g. prgnosis) specifically to install and administer Prognosis. If there is a requirement to monitor MQSeries, make this user a member of the mqm group as well.

The User and Group names must be 8 characters or less in length.

Prognosis will automatically create an installation directory using the directory name that was input during the install, e.g. prgn950. Do not create this directory yourself, the install script will do this automatically and it will not install on an existing directory.

To ensure that the correct 'permissions' are in place, Prognosis needs to create this installation directory on an existing directory that is owned by the user, usually this is the user’s $HOME directory. Therefore, when the Prognosis installation (install.sh) asks for the install directory, input; $HOME/prgn<nnn> (nnn being the Prognosis version number). This will be correct as the $HOME directory is owned by the Prognosis user and prgn<nnn> will be the name of the installation directory automatically created.

Should it be necessary to install Prognosis on a directory that is currently not owned by the Prognosis user, e.g. on a directory called /tools, proceed as follows;

Step 1 cd /tools

Step 2 mkdir prognosis

Step 3 chown prgn prognosis

Step 4 chgrp prgnosis prognosis

Now there will be a /tools/prognosis directory that is owned by user prgn. When the installation (install.sh) asks for the install directory, input; /tools/prognosis/prgn<nnn>.

The script used for a new Prognosis installation is install.sh, for usage instructions type 'install.sh -h'. Prognosis Upgrades use upgrade.sh. See the UNIX Upgrade Installation (page 150) section for further details.

If the directory is owned by root, or a symbolic link is being used that is owned by root then Prognosis will not install. It is essential that Prognosis be installed in a non-root directory. Always be sure to change the

ownership of the directory or the symbolic link, to the Prognosis user before starting your installation.

Linux - Red Hat Enterprise 64 bit (AMD64 or x86_64)

On 64bit machines, 32 bit C++ library packages must be installed prior to the Prognosis installation (libstdc++.i686 and compat-libstdc++-33.i686). Prior to installation check if these libraries are installed, for example run:

$ rpm -qa --qf "%{name}-%{arch}\n" | grep libstdc++.*i686

libstdc++-i686

compat-libstdc++-33-i686

If the libraries are not installed, install them by executing the following command:

yum install libstdc++.i686 compat-libstdc++-33.i686

Prognosis 11.0

Installation Checklist Checklist for installing the IR Prognosis server on a UNIX or Linux. machine. Before proceeding with the installation please go through the following checklist and ensure that all items have been addressed.

Installation Checklist - UNIX/Linux

1. Release Notes




Ensure that you have the Prognosis for UNIX/Linux installation files. These will either be provided by CD/DVD or can be downloaded from the Prognosis Online web site:



Save the Prognosis license file ('license'') as follows, according to the installation procedure (page 146) being used:

a) If upgrading from an MS Windows machine that has FTP access to the UNIX/Linux server, save the licence file to a convenient location on the MS Windows machine.

b) If upgrading directly on the UNIX/Linux server FTP/upload the license file in ASCII mode to a convenient location on the UNIX/Linux machine. For hard disk upgrades it is preferable to use the Temp Directory - see step 8 (page 144).

If the license file has not been received, please contact your Prognosis account manager.



See: Server Requirements - UNIX/Linux.

5. On what UNIX/Linux system is Prognosis being installed?

Ensure that the correct Prognosis 11 installation files are available (i.e. HP-UX, Linux, Solaris or AIX).

6. Hostname/IP Address (if installing from a Windows machine)

Obtain the DNS hostname or IP address of the UNIX/Linux server on which Prognosis is being installed. This will be required during the installation procedure.


Root password will be required in order to make some files 'setuid root'.

8. Create a Temp directory (If installing from MS Windows or hard disk)

If installing Prognosis from MS Windows or hard disk it will be necessary to create a temp directory on the UNIX/Linux server to store the installation files (install.sh & compressed tar file). Alternatively, the standard UNIX /tmp directory can be used.

9. Check that the correct library packages have been installed.

On 64bit Linux machines, 32 bit C++ library packages must be installed prior to the Prognosis installation (libstdc++.i686 and compat-libstdc++-33.i686).

See: Linux - Red Hat Enterprise 64 bit (AMD64 or x86_64) (page 143).



Installation

Installation Checklist - UNIX/Linux

10. Installation Directory

Prognosis will automatically create an installation directory using the directory name input during the install. Do not create this directory yourself, the install script will do this for you and it will not install on an existing directory.

See: Installation Directory (page 143).

11. Obtain the Oracle Home directory (only if Oracle monitoring required).

See: Installing Prognosis with Oracle on UNIX (page 148).

12. Obtain the Oracle TNS Admin directory (only if Oracle monitoring required).


13. Obtain the MQSeries home directory (only If MQ Series monitoring required).

14. Obtain 'Home' directories for DB2 Instances (only if DB2 monitoring required).


Prognosis 11.0

Installation Procedure The installation of the IR Prognosis server component on a UNIX/Linux machine can be undertaken by the System Administrator using one of the following methods.

Installing from a Windows Machine

Step 1 If not already done, create a new temp directory (page 144) on the hard disk of the UNIX/Linux machine to store the installation files. Alternatively the existing /tmp directory can be used.

Step 2 Place the Prognosis installation CD into a CD drive on an MS Windows machine that has FTP access to the UNIX/Linux server. The installation program will run and the 'Welcome to Prognosis' screen will be displayed.

Step 3 Click the Next button to open the FTP Details screen.

Step 4 On the FTP Details screen complete the details of the UNIX/Linux server where Prognosis is to be installed.

- Hostname (page 144) DNS hostname or IP address of the UNIX/Linux server.

- Username/Password (page 144) Username and password for accessing the UNIX/Linux machine.

- Temporary Directory (page 144) An empty directory on the UNIX/Linux machine to be used as a temporary location for storing the Prognosis installation files.

When complete click the Next button.

Step 5 On the next dialog box, specify/select the location of the Prognosis license file (page 13).


Step 6 The installation will now confirm that the files are ready to be transferred to the specified UNIX/Linux machine.

Click the Next button to start the transfer.

Step 7 When the transfer is complete go to the UNIX/Linux machine and change to the Prognosis 'Temporary Directory'.

Step 8 Input: chmod +x install.sh to change the mode on the installation script.

Installation

Step 9 Input: ./install.sh to run the installation script.

Step 10 Follow the comments and answer the questions as required.

Step 11 Once Prognosis is installed it can then be started by logging into the Prognosis user account and typing 'startprog'.

Installing from CD

Step 1 Place the Prognosis Installation CD into the UNIX machine’s CD-ROM drive, or a CD-ROM drive that is accessible from the UNIX machine.

Step 2 Change to the CD-ROM directory that corresponds to the required UNIX/Linux platform and run the installation script - install.sh.


During the installation you will be asked to input the location of the licence file (page 13).


Installing from Hard disk

Step 1 If not already done, create a new temp directory (page 144) on the hard disk of the UNIX/Linux machine to store the installation files. Alternatively the existing /tmp directory can be used.

Step 2 Place the Prognosis installation CD into the UNIX machine’s CD-ROM drive, or a CD-ROM drive that is accessible from the UNIX machine.

Step 3 Change to the CD-ROM directory that corresponds to the required UNIX/Linux platform, then copy the install.sh file and the appropriate compressed tar file (e.g. plin24.gz for Linux Kernel 2.4) to

the hard disk temp directory.

Step 4 Change to the hard disk temp directory, e.g. cd/tmp

Step 5 Input: chmod +x install.sh to change the mode on installation script.

Step 6 Input: ./install.sh to run the installation script.


Provided that the Prognosis licence file has been copied to the same directory as the tarball (i.e. the hard disk temp directory) the installer will not prompt for a license file location.


Prognosis 11.0

Installing Prognosis with Oracle on UNIX This procedure is only used where Oracle is already installed on the UNIX server where IR Prognosis is to be installed and where Oracle database monitoring is required (provided that the appropriate Prognosis license has been obtained). If Oracle database monitoring is to be enabled after the Prognosis installation, please refer to the Oracle Database Server Management section of the Prognosis for Distributed Systems User Guide.

Procedure

Step 1 Before installing Prognosis, make sure that the account to be used has a valid Oracle environment and ask your Database Administrator to set it up to access Oracle.

Step 2 Test the environment

Check access to the various names in $TNS_ADMIN/tnsnames.ora by using 'tnsping <tnsname>'. Should you encounter any problems, your Database Administrator should be able to resolve these, e.g. Oracle listener not running, incorrect tnsnames.ora etc.

Step 3 Install the Prognosis server using the standard procedure (page 146).

After the Prognosis installation has been completed, proceed with the following steps.

Step 4 Configure the Database

Log on to sqlplus using the sys account (requires administrator permissions). The Database Administrator may be required to provide assistance with the sys user log on.

After log on run the following entry for each Oracle instance (ORACLE_SID) that is to be monitored.

@ prognosis/server/configuration/prognosis_grants.sql

This will create an Oracle user named 'PROGNOSIS' with the password 'PROGNOSIS' which has access rights to all required tables. Now log in to sqlplus using the 'PROGNOSIS' (case sensitive) user to check it.

This Oracle sqlplus script creates a user and sets up permissions so that Prognosis can read from the various system tables and views without requiring any kind of system privilege. The DBA may need to edit this script to conform to the security and other policies of the site. The script must be executed as the sys (or equivalent) user. DO NOT RUN THIS SCRIPT WITHOUT FIRST

CHECKING THAT IT IS APPROPRIATE FOR THE SITE.

Step 5 PASSWORD Configuration (in Prognosis)

In the Prognosis PASSWORDS Configuration, add the user name and password that Prognosis will use to access Oracle. This entry can be either:

- 'Oracle', when monitoring a single Oracle instance or if all instances have the same username/password, or

- 'OracleAlias<alias-name>', when monitoring multiple instances that use different usernames/passwords.

By default the username/password are both 'PROGNOSIS' (case sensitive).

Step 6 DBMS Configuration

In order to undertake Oracle database monitoring through Prognosis you will need to set up the Prognosis Database Management Subsystem (DBMS) configuration. A default Configuration is provided with your Prognosis installation, this can be found in the Document Navigator in the following folder path:

Knowledge > Common > Oracle > Configuration

Use this configuration to control access to your DBMS installation(s) by Prognosis. The Prognosis process that relies on this configuration is called IRDBCOL.

SUBSYS DBMS

ODBC RECONNINT (<Interval>, <Unit>)

ORACLE DRIVER (ORACLE_OCI_DRIVER)

ORACLE ALIAS (<DBName>)

Installation

ODBC RECONNINT

Specifies how often Prognosis tries to reconnect to the DBMS after a failure. The minimum is 1 minute.


Always use this entry for the Oracle collector on UNIX

ORACLE ALIAS

Specifies the database names that you are going to monitor, add one per line. Use the connection names as defined in tnsnames.ora, i.e. the ones tested in step 2.

The following is a sample configuration for Oracle on UNIX.

SUBSYS DBMS

ODBC RECONNINT (1, minute)


ORACLE ALIAS (daja)

ORACLE ALIAS (dajb)

Step 7 Start the DBMS configuration then open the Welcome to Prognosis Display and drill down to Oracle Central. These Displays have 30 second intervals, so you will need to wait a few moments for data to appear.

Trouble Shooting

If data does not appear on the Oracle Central Display , i.e. only asterisks appear, then look in the wvlog.txt file, on your UNIX server, and check for the Oracle error listed there.

If the error says that the username/password is invalid, then check the username and password in the DBMS configuration. If this is correct then check that the LD_LIBRARY_PATH has $ORACLE_HOME/lib in it (i.e. with $ORACLE_HOME substituted with the actual value of $ORACLE_HOME. If it doesn't, then modify the profile for the Prognosis user to add it in, and restart Prognosis.

If the error says that there is an unknown or erroneous NLS parameter, then see if the environment in which Prognosis is running has the NLS_LANG environment value set. If this is the case, then use 'unset NLS_LANG' to remove it and restart Prognosis - this may fix the problem. If it does then modify the profile for the Prognosis user to remove or unset it.

If the error is something else then refer to your Database Administrator or to Prognosis Technical Support.

Prognosis 11.0


Prognosis 9.1 SP4

Prognosis 10.0 SP1

Prognosis 10.1










Upgrade Procedure (page 155)

Installation

Upgrade Information Prior to carrying out an upgrade to the Prognosis Server on a UNIX/Linux machine, please take note of the following points:

The command upgrade.sh -h can be used to obtain information and usage instructions.

Because the upgrade is done 'in place', it is strongly recommended that a full back-up of the existing system be made before upgrading.

Prognosis should be shut down before starting the Upgrade script.

The Upgrade script (upgrade.sh) should be run as the user who owns the Prognosis system being upgraded. Do not run this script as root.

If an existing Prognosis system is already running, the new version can be installed into a separate location by using install.sh and manually configuring it. Once installed and operating satisfactorily the

previous version can then be removed.



Upgrade Order



Prognosis 11.0


Existing Configuration files will be maintained.


- Availability


- Problem Logs

- File Manager Logs

Prognosis log file (wvlog.txt) is deleted.

.ini files from the previous Prognosis version will be reused. Any customizations to these .ini files will be maintained.

Old UDEFSREC is merged with new UDEFSREC (old records are replaced with newer ones).

All Database Collections, Thresholds and Analysts that are running at the time of upgrade will be backed up. These will be restored with any customizations and will be restarted in the new Prognosis version. If the new version contains any additions/improvements to these documents then the new documents will not be started. In order to use the latest versions, it is recommended to compare the existing documents with the new documents (the IRCMD List command may be used for this) and then copy any of the new features over to the existing documents.

What DOES NOT happen on Upgrade?

New versions of Prognosis Configurations will not be automatically started on upgrade.

Availability Logs are NOT maintained. However, any availability data recorded in Prognosis databases is maintained. Fields such as 'Mean Time Between Failure'(MTBF) are reset.

Installation

Upgrade Checklist Checklist for upgrading the IR Prognosis server on a UNIX or Linux. machine. Before proceeding with the upgrade please go through the following checklist and ensure that all items have been addressed.

Upgrade Checklist - UNIX/Linux

1. Release Notes




Ensure that you have the Prognosis for UNIX/Linux installation files. These will either be provided by CD/DVD or can be downloaded from the Prognosis Online web site:



Save the Prognosis license file ('license'') as follows, according to the upgrade procedure (page 155) being used:

a) If upgrading from an MS Windows machine that has FTP access to the UNIX/Linux server, save the licence file to a convenient location on the MS Windows machine.

b) If upgrading directly on the UNIX/Linux server FTP/upload the license file in ASCII mode to a convenient location on the UNIX/Linux machine. For hard disk upgrades it is preferable to use the Temp Directory - see step 11.

If the license file has not been received, please contact your Prognosis account manager.



The upgrade facility is only available from certain Prognosis versions. For details see the UNIX/Linux Upgrade Installation topic (page 150).



6. On what UNIX/Linux system is Prognosis being upgraded?

Ensure that the correct Prognosis 11 installation files are available (i.e. HP-UX, Linux, Solaris or AIX).


See: Prognosis for Infrastructure - UNIX/Linux Server Requirements (page 35)

or Prognosis for Payments - UNIX/Linux Server Requirements. (page 45)







Prognosis 11.0

Upgrade Checklist - UNIX/Linux



Current Prognosis 9.1 customized solutions will not work on Prognosis 10+.


Copy the previous complete Prognosis directory, preserving file 'attributes', to an appropriate backup location.

11. Hostname/IP Address

Obtain the Hostname or IP address of the UNIX/Linux server on which Prognosis is being upgraded. This will be required during the upgrade procedure.


Root password will be required in order to make some files 'setuid root'.

13. Create a Temp directory (If upgrading from MS Windows or hard disk)

If upgrading Prognosis from MS Windows or hard disk it will be necessary to create a temp directory to store the upgrade files (install.sh & compressed tar file). Alternatively, the standard UNIX /tmp directory can be used.

14. Check that the correct library packages have been installed.

On 64bit Linux machines, 32 bit C++ library packages must be installed prior to the Prognosis installation (libstdc++.i686 and compat-libstdc++-33.i686).

See: Linux - Red Hat Enterprise 64 bit (AMD64 or x86_64) (page 143)

15. Installation Directory

Prognosis will automatically create an installation directory using the directory name input during the install. Do not create this directory yourself, the install script will do this for you and it will not install on an existing directory.

See: Installation Directory (page 143).

16. Obtain the Oracle Home directory (only if Oracle monitoring required).

See Installing Prognosis with Oracle on UNIX (page 148).

17. Obtain the Oracle TNS Admin directory (only if Oracle monitoring required).


18. Obtain the MQSeries home directory (only if MQ Series monitoring required).

19. Obtain 'Home' directories for DB2 Instances (only if DB2 monitoring required).

20. Create an IRFAX


Once the checklist has been completed, proceed with the Prognosis upgrade. For details see, Upgrade Procedure (page 155).

Installation

Upgrade Procedure The upgrade of the IR Prognosis server component on a UNIX/Linux machine can be undertaken by the System Administrator using one of the following methods.

Upgrading from a Windows Machine

Step 1 If not already done, create a new temp directory (page 154) on the hard disk of the UNIX/Linux machine to store the upgrade files. Alternatively the existing /tmp directory can be used.

Step 2 Place the Prognosis installation CD into a CD drive on an MS Windows machine that has FTP access to the UNIX/Linux server. The installation program will run and the 'Welcome to Prognosis' screen will be displayed.


Step 4 On the FTP Details screen complete the details of the UNIX/Linux server where Prognosis is to be upgraded.

- Hostname (page 154) DNS hostname or IP address of the UNIX/Linux server.

- Username/Password (page 154) Username and password for accessing the UNIX/Linux machine.

- Temporary Directory (page 154) The new empty directory or the existing /tmp directory on the UNIX/Linux machine that will be used as a temporary location for storing the Prognosis upgrade files.


Step 5 On the next dialog box, specify/select the location of the Prognosis license file (page 153).




Step 7 When the transfer is complete go to the UNIX/Linux machine and change to the Prognosis 'Temporary Directory'.

Step 8 Input: chmod +x upgrade.sh to change the mode on the installation script.

Prognosis 11.0

Step 9 Input: ./upgrade.sh to run the upgrade script.


Step 11 Once Prognosis is upgraded it can then be started by logging into the Prognosis user account and typing 'startprog'.

Upgrading from CD

Step 1 Place the Prognosis Installation CD into the UNIX machine’s CD-ROM drive, or a CD-ROM drive that is accessible from the UNIX machine.

Step 2 Change to the CD-ROM directory that corresponds to the required UNIX/Linux platform and run the upgrade script - upgrade.sh.


During the upgrade installation you will be asked to input the location of the licence file (page 153).


Step 5 Once Prognosis is upgraded, it can be started by logging into the Prognosis user account and typing 'startprog'.

Upgrading from a Hard Disk

Step 1 If not already done, create a new temp directory (page 154) on the hard disk of the UNIX/Linux machine to store the upgrade files. Alternatively the existing /tmp directory can be used.

Step 2 Place the Prognosis installation CD into the UNIX machine’s CD-ROM drive, or a CD-ROM drive that is accessible from the UNIX machine.

Step 3 Change to the CD-ROM directory that corresponds to the required UNIX/Linux platform, then copy the upgrade.sh file and the appropriate compressed tar file (e.g. plin24.gz for Linux Kernel 2.4) to

the hard disk temp directory.

Step 4 Change to the hard disk temp directory, e.g. cd/tmp.

Step 5 Input: chmod +x upgrade.sh to change the mode on the installation script.

Step 6 Input: ./upgrade.sh to run the upgrade script.


Provided that the Prognosis licence file has been copied to the same directory as the tarball (i.e. the hard disk temp directory) the installer will not prompt for a license file location.

Step 8 Once Prognosis is upgraded it can then be started by logging into the Prognosis user account and typing 'startprog'.

Installation

Unattended Installation Unattended installation is an automated process for installing IR Prognosis with minimal user intervention. This feature is most useful when the standard installation needs to be performed on a number of separate machines. It works in two parts:

1. Create an 'Answer File'. The 'Answer File' is a simple text document that contains the answers to all of the questions asked during a standard installation.

2. Run the 'Unattended Installation' command. This command runs the installation process and makes use of the 'Answer File' to provide all the information required to complete the installation without any user intervention.

Because unattended installation uses an 'Answer File' to install Prognosis there is little interaction required by system administrators during the installation process. This reduces the risk of errors that may be introduced during the setup process and provides consistency in the configuration of multiple machines.

For details see the following topic:

Creating and Using the Answer File (page 158)

Prognosis 11.0

Creating and Using the Answer File There is a choice of two driver scripts, installauto.sh and installautononroot.sh, that:

1) Call 'install.sh -i installdirectory' as non-root Prognosis user to extract the gzipped tar file into an install directory.

2) Call installroot.sh as root.

3) Call install2.sh as non-root Prognosis user with an answer file.

installauto.sh must be run as root; it runs install.sh and install2.sh as the nominated user. Type 'installauto.sh -h' for usage instructions.

installautononroot.sh, on the other hand, must be run as the non-root user who will own Prognosis; it runs install.sh and install2.sh as this user and uses the 'sudo' command to run installroot.sh without requiring the root password to be known. installautononroot.sh is perhaps cleaner, but requires that you have installed the 'sudo' command as described in the next section.

Answer File

Both installauto.sh and installautononroot.sh require an 'answer' file. When a manual install is run, an answer file, namely PROGNOSIS_HOME/server/answer.txt, is automatically created containing the answers entered.

For unattended upgrades, use upgradeauto.sh or upgradeautononroot.sh. These scripts function in a similar fashion to the installauto scripts, described above.

Installation

Example Unattended Install

Step 1 Login as non-root user, for example 'fred'.

Step 2 mkdir /home/fred/Install

Step 3 cd /home/fred/Install

Step 4 Copy the following files from the installation CD to /home/fred/Install: install.sh upgrade.sh (only required if you upgrading existing Prognosis systems) gzip (only required if your system does not have the 'gzip' command) plin22.gz (Use the appropriate tarball for your system, for example Linux 2.2)

Step 5 Copy the license keys to /home/fred/Install The license key information is normally sent via an email. The attached license file should be saved to the install directory.

Step 6 chmod +x *.sh chmod +x gzip

Step 7 ./install.sh Complete the questions. For install directory, answer /home/fred/prognosis. Answer 'n' to starting Prognosis after install.

Step 8 After install has finished successfully: cd /home/fred/install cp /home/fred/prognosis/server/installauto.sh . cp /home/fred/prognosis/server/answer.txt . cp /home/fred/prognosis/server/irrunas . (only required if installing as a user without a login shell) chmod +x installauto.sh Check and edit, if desired, the file answer.txt.

Step 9 su Use the 'su' command to becomer superuser. Enter the root password when prompted.

Step 10 ./installauto.sh -i /home/fred/prognosis2 -a answer.txt -u fred This should auto-install a new Prognosis in directory /home/fred/prognosis2 using the answers from file answer.txt.

Step 11 exit Become user 'fred' again.

Prognosis 11.0

Uninstalling - UNIX/Linux The uninstall.sh shell script is used to uninstall IR Prognosis and it must be run from outside the PROGNOSIS_HOME directory, as this directory will be deleted during the uninstall process.

The uninstall script requires super-user permissions to run and as PROGNOSIS_HOME/server is unlikely to be on the super-user's PATH it is recommended to carry out the uninstall as follows;

Step 1 Log in as the user who owns Prognosis.

Step 2 cd (no parameters required to move to the users home directory)

Step 3 su root -c $PROGNOSIS_HOME/server/uninstall.sh

Installation

Unattended Uninstall Unattended uninstall is not available for IR Prognosis on UNIX/Linux.

Prognosis 11.0

Server on HP NonStop This chapter provides the procedures for installing the IR Prognosis Management and/or Monitoring Server on a machine running the HP NonStop operating system.




Installation Subvolume Requirements (page 163)

UNPACK Command (page 164)




Associated topics:




Installation

Installation Subvolume Requirements

Terminology

Install Subvolume

The Install Subvolume is the main volume.subvolume where Prognosis is installed. It is specified using the DEST option of UNPACK. If it is not specified, UNPACK will prompt for the Install Subvolume.

Due to an SQL/MP limitation, Prognosis should be installed in a volume name that has six characters or less if it is intended to collect Prognosis data to an SQL/MP format database.

Install Prefix

The Install Prefix is derived from the Install Subvolume by taking the volume portion and adding the first four characters of the subvolume portion. If the subvolume portion is four characters or less, the Install Prefix will be identical to the Install Subvolume.

Install Subvolume Set

Prognosis reserves a set of subvolumes within the Install Prefix. The subvolume names are derived from the Install Prefix by adding a set of suffixes. The currently defined suffixes are:

CSV DAY HIST MIBS PRIM PTCH PTMP PKG

The Install Subvolume Set is the set of subvolumes reserved for use by a Prognosis installation. It includes the Install Subvolume and all other reserved subvolumes.

Examples:

Install Subvolume: $PHYS42.PRGNOSIS

Install Prefix: $PHYS42.PRGN

Install Subvolume Set: $PHYS42.PRGNOSIS

$PHYS42.PRGNDAY

$PHYS42.PRGNMIBS

$PHYS42.PRGNPTCH

$PHYS42.PRGNCSV

$PHYS42.PRGNHIST

$PHYS42.PRGNPRIM

$PHYS42.PRGNPTMP

Install Subvolume: $PHYS42.PRG

Install Prefix: $PHYS42.PRG

Install Subvolume Set: $PHYS42.PRG

$PHYS42.PRGDAY

$PHYS42.PRGMIBS

$PHYS42.PRGPTCH

$PHYS42.PRGCSV

$PHYS42.PRGHIST

$PHYS42.PRGPRIM

$PHYS42.PRGPTMP

Requirements for Install Subvolume

Valid Subvolume

The Install Subvolume must be a valid Guardian volume.subvolume. The volume portion must specify an existing disk volume.

Empty Install Subvolume Set

For a new Installation, the Install Subvolume Set must be 'empty', i.e. the subvolumes that make up the Install Subvolume Set must not contain any files.

For an in-place upgrade installation, the 'PKG' subvolume (for example, $DISK.PRGNPKG) should be empty.

Prognosis 11.0

UNPACK Command The UNPACK command is used to complete the IR Prognosis server installation on HP NonStop. The following are the full range of options that are available with the UNPACK command:

RUN UNPACK [ <option> ... ]

Where <option> is one of:

UPGRADE <upgrade-svol>

Upgrade Prognosis in specified subvolume. See Upgrading the Prognosis Server on HP NonStop (page 172) for further details.

DEST <svol> Specifies the destination subvolume for install/upgrade.

Default for upgrade is to upgrade in place.

Default for new install is to prompt for the destination.

BUILDMODE Create sample ANSWERS file based on install input. See Unattended Install for further details.

BUILDONLY Create sample ANSWERS file, but do not install. See Unattended Install for further details.

VERBOSE Verbose output. Gives full UNPAK output.

DEBUG Turn on debug trace output.

ENABLE <feature> Enable available features. Currently these features are:

BASE - Enable normal Prognosis product/feature set.

TSV - Enable Prognosis Transaction Surveillance

ALL - Enable all products/features

If ENABLE is not specified the default will be to ENABLE BASE.

KEEP Do not delete install files (optional). If this option is not specified, the installation files transferred from the CD will be purged, this saves disk space. If the KEEP option is specified, the installation files are preserved in the temporary subvolume, allowing Prognosis to be installed again from the same temporary location.

<patch> Pre-selects the nominated patch, service pack or feature pack for install. Only the patches, service packs and feature packs selected on the command line will be installed. See Patch Installation (page 219) for further details.

Installation

New Installation The following topics will provide details for a new installation of the IR Prognosis server component on to a HP NonStop machine.





Prognosis 11.0

Installation Checklist Checklist for installing the IR Prognosis Server on HP NonStop.

Installation Checklist - HP NonStop

1. Release Notes




Ensure that you have the Prognosis for HP NonStop installation files. These will either be provided by CD/DVD or can be downloaded from the Prognosis Online web site:



Save the new Prognosis license files ('license' and 'licext') to a convenient location on an MS Windows machine that has FTP access to the HP NonStop Server. If the license files have not been received, please contact your Prognosis account manager.



See: Server Requirements - HP NonStop.


Obtain the DNS hostname or IP address of the HP NonStop server on which Prognosis is to be installed. This will be required during the installation procedure.

6. Username/Password

Choose a userid for Prognosis. This userid will own the Prognosis files and processes. If no suitable userid exists, one must be setup before installing Prognosis.

Some Payments products require the Prognosis user to have read access to various components of the Payments application. For instance; Transaction Insight, ATM Manager and XPNET Manager all have security considerations around the Prognosis user. These may affect the choice of Prognosis user. See the relevant product section in the Online

Help for more details.

7. Temporary subvolume

Choose an empty subvolume as a temporary location for storing the Prognosis installation files. The installation files will be transferred to this location in preparation for the UNPACK script. The UNPACK script uses the installation files in this temporary subvolume to install Prognosis. For example, if the installation subvolume is $DATA.PRGNOSIS then a temporary subvolume might be $DATA.PRGNTMP. Do not use the subvolume where Prognosis will be finally installed.

This temporary subvolume location cannot be on an SMF virtual disk.



Installation


8. super.super password for the TACL session

Once the Prognosis files have been transferred to the HP NonStop server, a TACL session will need to be opened using the super.super credentials in order to run the UNPACK command. However, some environments do not permit entering super.super into a macro due to security concerns, therefore logon as super.super before running the install macro.

9. Destination Install subvolume

Select the location where Prognosis will be installed.

See: Installation Subvolume Requirements (page 163) for further details.

Prompts about the following items will be shown during the UNPACK, so it is recommended to have the answers ready in advance for these questions:

10. Record definitions - file location

Prognosis uses an OSS folder to store record definitions in folders designated by the product or solution that they are part of. This arrangement makes it easier to deploy solutions delivered by the Integrated Research Consulting Group as well as custom ADI solutions, and will be further utilized in later releases. The base folder needs to be chosen at install time. The default location is /etc/prognosis/<version_number>/solutions. If it is not possible to use OSS on this system, there is an option store record definitions in the base Prognosis folder.

11. Prognosis Process Manager - process name

Process name for Prognosis Process Manager or use the default $STM if it is not already allocated.

12. Prognosis Process Manager - priority

Priority for Prognosis Process Manager. The default setting of 180 is recommended.

13. Prognosis Process Manager - CPU

CPU where the Prognosis Process Manager will run. The default is the CPU in which the install TACL is running. This default can be used in most cases as the Process Manager has a minimal impact on the CPU. Remaining Prognosis processes are distributed among all CPUs.

14. STATIC home terminal name

Select the Home terminal name for Prognosis. This must be a terminal that is always present, e.g. not a Telnet terminal. The default is the system console.

15. TCP/IP process name

This is the TCP/IP process that Prognosis uses to connect to other Prognosis servers and user interfaces. Ideally, a TCPIP process should be selected that is able to connect to all other systems that will run the Prognosis server or Windows Client. If this is not possible, select a TCPIP process that is able to connect to the system that will run the Prognosis Windows Client. The NETWORK Configuration can be manually altered later to specify more than one TCPIP process.

16. Multicast IP address

If the selected TCP/IP process has more than one physical interface associated with it, it will be necessary to specify the IP address of the interface to be used. Select this as per the TCP/IP process name as shown above. If the TCP/IP process has only one physical interface, it will not be necessary to supply an IP address.

Prognosis 11.0


17. TCP/IP Port number (The default setting is 1960.)

This is the port number used by Prognosis for TCP/IP communication. Prognosis reserves the use of a number of ports, starting from the port number specified through to that port number plus six. For example, if port 1960 is chosen, ports 1960 through 1966 inclusive are reserved. The default value of 1960 is recommended unless this port is used by another application.

18. Troubleshooting/Capacity Planning databases

Prognosis comes pre-configured with troubleshooting and capacity planning databases. Decide if this data is to be collected on this system. If it is decided not to collect these databases, it will not be possible to use some of the reports included with Prognosis. The databases require up to 300MB of disk space on the HP NonStop system.

19. Configure IN Manager

Where the Prognosis license includes IN Manager monitoring, a prompt will be shown during the installation for the IN environment configuration. To complete this it will be necessary to know the location of the IN data subvolumes that are to be monitored.

20. BASE24 resource nodes (XPNET Manager only)

Where the Prognosis license includes XPNET Manager, a prompt will be shown during the installation for the BASE24 XPNET environment configuration. To complete this it will be necessary to know the following for each resource node to be monitored:

As many XPNET resource nodes can be entered as required.

a) Name of the XPNET resource node. b) Name of the Pathway process (pathmon) controlling this resource node. c) Name of the NCP serverclass servicing NCP requests. (default SERVER-NCP). d) XPNET userid with read access to the resource node. e) Password for the XPNET userid.

21. BASE24 Transaction log file locations (ATM Transaction Manager only)

Where the Prognosis license includes ATM Transaction Manager, a prompt will be shown during the installation for the BASE24 ATM environment configuration. To complete this it will be necessary to know the filename prefix used for the TLF log files. The Prognosis installation can search for these log files and those required can be selected, or the log file locations can be manually entered.

22. BASE24 POS log file locations (POS Transaction Manager only)

Where the Prognosis license includes POS Transaction Manager, a prompt will be shown during the installation for the BASE24 POS environment configuration. To complete this it will be necessary to know the filename prefix used for the PTLF log files. The Prognosis installation can search for these log files and those required can be selected, or the log file locations can be manually entered.

23. BASE24 Terminal Definition file locations (ATM Manager only)

Where the Prognosis license includes ATM Manager, a prompt will be shown during the installation for the BASE24 environment configuration. To complete this the Prognosis installation can search for the Terminal Definition (TDF) files and those required can be selected, or the file locations to monitor can be manually entered.

24. Connex Transaction Log File locations

Where the Prognosis license includes Connex Transaction Manager, a prompt will be shown during the installation for the Connex environment configuration. To complete this the Prognosis installation can search for log files and those required can be selected, or the LGWARM file location(s) and related logger process names can be entered manually.

Installation


25. Transaction Surveillance Log File locations

Where the ENABLE TSV or ENABLE ALL UNPACK option has been used and the Prognosis license includes Transaction Surveillance, a prompt will be shown during the installation for the BASE24 or Connex environment configuration. To complete this the Prognosis installation can search for log files and those required can be selected, or the log file locations can be manually entered.

26. ATM Manager - Email In/Out

Where the Prognosis license includes ATM Manager the installation can create a sample set up for the 'Email-In' functionality. During the installation a prompt will be shown for an originating email address, an SMTP server name or IP Address, POP server port number and a mailbox name and password. This can also be completed or amended later through the various configuration files (see the ATM Manager section of the Prognosis for Payments User Guide).

27. Is MQSeries monitoring required?

Where the Prognosis license includes MQ Manager, a prompt will be shown during the installation asking if WebSphere MQSeries data is required to be collected.

28. Is TMF/RDF monitoring required?

Where the Prognosis license includes Transaction Manager,a prompt will be shown during the installation asking if TMF and/or RDF data is required to be collected.

29. Are Dispatch Manager Threshold/Analyst email notifications required?

Where the Prognosis license includes Automated Operations, a prompt will be shown during the installation asking if Dispatch Manager should to be enabled to send email notifications. The IP Address or DNS Name of a mail server which accepts message delivery via SMTP will need to be supplied. It will also be required to supply an email address to send the notifications to. One server and one email address can be configured at install time and additional servers and addresses can be configured later.

30. Is Pathmon monitoring required?

Where the Prognosis license includes the TP Manager product, a prompt will be shown during the installation asking if Prognosis should be configured to monitor Pathmon environments on the system. The install will automatically find any Pathmon processes running and it will be necessary to know which of these environments, if any, is to be monitored. Additional Pathmon processes that are not currently running can also be specified.


Prognosis 11.0

Installation Procedure The following installation procedure needs to be carried out from an MS Windows machine that has access to the HP NonStop server via FTP.

Procedure

Step 1 Place the IR Prognosis installation CD into a CD drive on the MS Windows machine. The installation program will run and the 'Welcome to Prognosis' screen will be displayed.


Step 3 On the FTP Details screen complete the details of the HP NonStop server where Prognosis is to be installed.

- Hostname (page 166) DNS hostname or IP address of the HP NonStop server on which Prognosis is to be installed

- Username/Password (page 166) Userid (username and password) for Prognosis. This userid will own the Prognosis files, and processes.

- Temporary Subvolume (page 166) Specify an empty subvolume to be used as a temporary location for storing the Prognosis installation files.


Step 4 On the next dialog box, specify/select the location of the Prognosis license files (page 166).




Step 6 When the transfer is complete start a TACL session on the HP NonStop server.

Step 7 Logon to the HP Nonstop server as the user that will own the Prognosis files and processes.

LOGON <userid>

During the installation the setup may prompt for 'super.super' credentials where required.

Installation

Step 8 Change to the temporary subvolume where the Prognosis Installation files have been stored.

VOLUME <temp subvol> e.g. VOLUME $DATA.PRGNTMP

Step 9 Input the following UNPACK command and follow the prompts to complete the installation of the Prognosis server component.

RUN UNPACK DEST <svol>

Where:

DEST <svol> Installation subvolume. This subvolume must be empty, for further details see the Installation Subvolume Requirements topic (page 163). If <svol> is not specified, a prompt will be displayed for an installation location.

Examples

In these examples, the installation files have been transferred to the temporary subvolume $DATA.TEMP.

1) Install Prognosis to the installation location $DATA.PRGNOSIS:

VOLUME $DATA.TEMP

RUN UNPACK DEST $DATA.PRGNOSIS

2) Install Prognosis without specifying the installation Location (UNPACK will prompt for the installation location):

VOLUME $DATA.TEMP

RUN UNPACK

Step 10 Complete the questions as they are displayed (see the Installation Checklist topic (page 166))

Step 11 Answer 'y' to start Prognosis after the installation has been completed.

Prognosis 11.0


Prognosis 9.1 SP4

Prognosis 10.0 SP1

Prognosis 10.1










Upgrade Procedure (page 178)

Installation

Upgrade Information Prior to carrying out an upgrade to the Prognosis Server on a HP NonStop machine, please take note of the following points:

Upgrading Prognosis is done by using the UPGRADE option of the UNPACK script to specify the Prognosis installation to be upgraded. See Upgrade Instructions (page 178) for further details.

The upgrade can be done either 'in place' or to a different location. In either case, a full back-up is required of all files in all sub-volumes. For example, if the Prognosis sub-volume is $DATA.PRGNOSIS then backup all files matching $DATA.PRGN*.*.

The destination installation subvolume (page 163) for the upgrade can be chosen using the DEST option of UNPACK. If the destination is different to the upgrade subvolume, Prognosis will be copied to the destination as part of the upgrade. Since the same process name, port number, etc will configured for both the original and upgraded copies of Prognosis, only one can be running at a time. If you try to start both, you will get a 'process name in use' error.

If it is required to run both versions of Prognosis in parallel, install a new copy of Prognosis to a new Installation subvolume, rather than upgrading. A different name for the process manager, and a different port number will need to be used. Once satisfied with the operation of the new version the previous one can be removed.

When upgrading Prognosis only the 'core' components such as executables and start-up script files will be upgraded. In an 'in-place' upgrade, custom files will be overwritten and lost. If the IR Consulting Group has installed custom solutions, contact them before commencing the upgrade. Custom solutions will not work after the upgrade.

Both the Troubleshooting database and DBSUMM Analyst are known as 'core packaging', that is, they are crucial for the correct operation of Prognosis. By design, both of these files are overwritten with the latest version when an upgrade takes place. Therefore, if any modifications have been made to the standard DB* files, it is strongly recommended that these be backed-up so that they can be subsequently be restored, if required. Other Prognosis packaging that is considered 'non-core' is unpacked with the 'KEEP' option, meaning that if the file already exists in the sub volume, it will not be overwritten.

The upgrade must be run as super.super or an alias of super.super. This is due to the fact that some environments do not permit entering super.super into a macro due to security concerns, therefore this will avoid having to use the super.super user with the upgrade macro.




Prognosis 11.0

Upgrade Order



If the IR Prognosis installation to be upgraded does not reside in a subvolume that meets the installation subvolume requirements (page 163), you will be prompted for a destination, if it has not already been specified with the DEST option.

Prognosis is stopped if it is running.

If the selected installation subvolume is different to the upgrade location, a copy of Prognosis is made to the installation subvolume.

Existing core static configurations are maintained. Existing custom static configurations are lost.

New static configurations are added.

Prognosis log file (wvlog) is deleted.

Prognosis core databases are maintained.

Prognosis database data files should be maintained but the databases will need to be restarted manually to resume collecting new data.


- Availability


- Problem Logs

Prognosis is restarted if it was running prior to upgrade.

Installation

What DOES NOT happen on Upgrade?

Availability Logs are NOT maintained. However, any availability data recorded in Prognosis databases is maintained. Fields such as 'Mean Time Between Failure'(MTBF) are reset.

Custom collector solutions will not work in the upgraded version (effective from Prognosis 10).

Requestors are not restarted automatically and will need to be started manually using the document files saved before the upgrade.

All customized Database Collections, Thresholds and Analysts will be lost. These files will need to be backed up manually prior to the upgrade and then added back into the new version and restarted.

Prognosis 11.0

Upgrade Checklist Checklist for upgrading the IR Prognosis server on a HP NonStop machine.

Upgrade Checklist - HP NonStop

1. Release Notes




Ensure that you have the Prognosis for HP NonStop installation files. These will either be provided by CD/DVD or can be downloaded from the Prognosis Online web site:



Save the new Prognosis license files ('license' and 'licext') to a convenient location on an MS Windows machine that has FTP access to the HP NonStop Server. If the license files have not been received, please contact your Prognosis account manager.



The upgrade facility is only available from certain Prognosis versions. For details see the HP NonStop Upgrade Installation topic (page 172).




See: Prognosis for Infrastructure - HP NonStop Server Requirements (page 35)

or Prognosis for Payments - HP NonStop Server Requirements (page 45).





Current Prognosis 9.1 customized solutions will not work on Prognosis 10+.


Back-up all files in all subvolumes of the previous Prognosis installation. For example, if the Prognosis subvolume is $DATA.PRGNOSIS then all files matching $DATA.PRGN*.* should be backed-up.





Installation

Upgrade Checklist - HP NonStop

10. Save document files for all running requesters.

Save the document files for all running requestors that need to be manually restarted after the upgrade. This includes: Threshold (.thr), Analyst (.aa), Database Collection (.dbc) and Database Summary (.dbs) files.

11. Create an IRFAX


12. Run 'RUN STOPPRG' and check that no processes are running.

To check this, run 'STATUS *, PROG *' in the Prognosis subvolume. Manually STOP any remaining processes to avoid an upgrade failure due to open files.


Obtain the DNS hostname or IP address of the HP NonStop server on which Prognosis is to be upgraded. This will be required during the upgrade procedure.

14. Username/Password

Choose a userid for Prognosis. This userid will own the Prognosis files and processes. If no suitable userid exists, one must be setup before installing Prognosis.

Some Payments products require the Prognosis user to have read access to various components of the Payments application. For instance; Transaction Insight, ATM Manager and XPNET Manager all have security considerations around the Prognosis user. These may affect the choice of Prognosis user. See the relevant product section in the Online Help for more details.

15. Temporary subvolume

Choose an empty subvolume as a temporary location for storing the Prognosis installation files. The installation files will be transferred to this location in preparation for the UNPACK script. The UNPACK script uses the installation files in this temporary subvolume to upgrade the existing Prognosis installation. For example, if the installation subvolume is $DATA.PRGNOSIS then a temporary subvolume might be $DATA.PRGNTMP. Do not use the installation subvolume of the Prognosis version being upgraded.

This temporary subvolume location cannot be on an SMF virtual disk.

16. super.super password for the TACL session

Once the Prognosis files have been transferred to the HP NonStop server, a TACL session will need to be opened using the super.super credentials in order to run the UNPACK command. However, some environments do not permit entering super.super into a macro due to security concerns, therefore logon as super.super before running the upgrade macro.

17. Record definitions - file location

Prognosis uses an OSS folder to store record definitions in folders designated by the product or solution that they are part of. This arrangement makes it easier to deploy solutions delivered by the Integrated Research Consulting Group as well as custom ADI solutions, and will be further utilized in later releases. The base folder needs to be chosen at upgrade time. The default location is /etc/prognosis/<version_number>/solutions. If it is not possible to use OSS on this system, there is an option store record definitions in the base Prognosis folder.

Once the checklist has been completed, proceed with the Prognosis upgrade. For details see, Upgrade Procedure (page 178).

Prognosis 11.0

Upgrade Procedure The following upgrade procedure needs to be initiated from an MS Windows machine that has access to the HP NonStop server via FTP.

Procedure

Step 1 Place the IR Prognosis installation CD into a CD drive on the MS Windows machine. The installation program will run and the 'Welcome to Prognosis' screen will be displayed.


Step 3 On the FTP Details screen complete the details of the HP NonStop server where Prognosis is to be upgraded.

- Hostname (page 177) DNS hostname or IP address of the HP NonStop server on which Prognosis is to be upgraded

- Username/Password (page 177) Userid (username and password) for Prognosis. This userid will own the Prognosis files, and processes.

- Temporary Subvolume (page 177) Specify an empty subvolume to be used as a temporary location for storing the Prognosis upgrade files.


Step 5 On the next dialog box, specify/select the location of the Prognosis license files (page 176).




Step 7 When the transfer is complete start a TACL session on the HP NonStop server.

Step 8 Logon to the HP Nonstop server as the user that will own the Prognosis files and processes.

LOGON <userid>

During the installation the setup may prompt for 'super.super' credentials where required.

Installation

Step 9 Change to the temporary subvolume where the Prognosis installation files have been stored.

VOLUME <temp subvol> e.g. VOLUME $DATA.PRGNTMP

Step 10 Use either of the following UNPACK commands depending upon whether a 'roll-back' option is required or not. Follow the prompts to complete the installation of the Prognosis server component.

a) Upgrade 'in-place' (no rollback option)

This option will upgrade the existing copy of Prognosis in its current location.

RUN UNPACK UPGRADE <upgrade-svol>

Where:

UPGRADE <upgrade-svol> Subvolume containing the existing copy of Prognosis that is to be upgraded.

Example

Upgrade the Prognosis installation in $DATA.PRGNOSIS 'in-place'

VOLUME $DATA.TEMP

RUN UNPACK UPGRADE $DATA.PRGNOSIS

b) Preserve existing installation and place upgrade into a new location (allows rollback)

This option will preserve the existing Prognosis installation which can then used for a 'post-upgrade rollback' if in need.

RUN UNPACK UPGRADE <upgrade-svol> DEST <svol>

Where:

UPGRADE <upgrade-svol> Subvolume containing the existing copy of Prognosis which will be preserved.

DEST <svol> Destination subvolume for the upgrade installation. See the Installation Subvolume Requirements (page 163) section for details. If <svol> is not specified, the upgrade will be done 'in-place' (i.e. <loc> = <upgrade-loc>) if possible, otherwise you will be prompted for a new install location.

Example:

Upgrade the Prognosis installation in $DATA.PRGNOSIS with the upgraded Prognosis installed in $DATA.PRG10.

VOLUME $DATA.TEMP

RUN UNPACK UPGRADE $DATA.PR91 DEST $DATA.PR10

Step 11 The unpack will prompt for a directory to store Record Definitions using OSS (page 177). If OSS is not available, type 'N' at the prompt and the record definitions will be stored in the Prognosis subvolume.

Step 12 Answer 'y' to start Prognosis after the upgrade has been completed.

Prognosis 11.0

Unattended Installation Unattended installation is an automated process for installing IR Prognosis with minimal user intervention. This feature is most useful when the standard installation needs to be performed on a number of separate machines. It works in two parts:

1. Create an 'Answer File'. The 'Answer File' is a simple text document that contains the answers to all of the questions asked during a standard installation. See Creating an Answer File (page 181).

2. Run the 'Unattended Installation' command. This command runs the installation process and makes use of the 'Answer File' to provide all the information required to complete the installation without any user intervention.

Because unattended installation uses an 'Answer File' to install Prognosis there is little interaction required by system administrators during the installation process. This reduces the risk of errors that may be introduced during the setup process and provides consistency in the configuration of multiple machines.


Creating an Answer File (page 181)

Answer File Format (page 182)

Question Ids - General (page 183)

Question Ids - Application Configuration (page 187)

Question Ids - Payments (page 188)

Installation

Creating an Answer File - HP NonStop HP NonStop unattended install is controlled by a configuration file named 'ANSWERS', which is located in the installation subvolume. This is an edit file that contains responses to each of the questions asked by the IR Prognosis installation process.

To create an ANSWERS file, run UNPACK with the BUILDMODE or BUILDONLY options.

e.g. RUN UNPACK BUILDMODE, or RUN UNPACK BUILDONLY

BUILDMODE will perform a normal install, and in addition, record all responses to install questions in the ANSWERS file. If an answers file exists, it will be deleted.

BUILDONLY will not perform an install, but will prompt with all install questions relevant for the system running UNPACK. All responses will be saved in the ANSWERS file. If an answers file exists, it will be deleted.

To run an unattended install:

Ensure that a fully populated answers file is present in the install subvolume. This can either be the result of a previous BUILDMODE or BUILDONLY unpack session, or custom built by setting answers to each of the questions. (see the following section).

Make sure the UNPACK file is owned by the correct userid. This should be the user who is to 'own' Prognosis.

Logon to the super.super userid or an alias of super.super. This will allow unpack to install and secure Prognosis without prompting for the super.super password.

Run UNPACK as normal. UNPACK will take input for each prompt from the ANSWERS file. Each prompt will still appear on the terminal for reference with the applicable answer also displayed.

The ANSWERS file can also be used to automate some responses to the Prognosis install without running a full automated install. This is done by setting responses only to the questions that need to be automated, and leaving the remaining questions absent from the file. The Prognosis install will accept input from the ANSWERS file where it finds a response, and will prompt when no response exists.

Prognosis 11.0

Answer File Format The ANSWER file is an edit file (code 101) which contains a series of entries in the format Question=Answer. Each question that the IR Prognosis installation can prompt for has a question ID assigned. The ANSWER file is scanned from top to bottom, therefore a matching answer at the start of the file will take precedence over a matching answer at the bottom. This is important when using wildcarding.

For example, the following line sets Prognosis to start after install

UnpPrgStart=Y

Wildcarding

Question IDs can accept the wildcards '*' and '?'. * replaces 0 or more characters of the question ID. ? replaces exactly 1 character of the question ID. This can be used to give a common answer to more than one question.

For example, the following entry answers 'Y' (yes) to all database questions:

DB_*=Y

Numbered Lists

Some of the install prompts allow the entry of multiple values. These are represented in the answer file by Numbered Lists. Each numbered list consists of two types of entries. The first entry gives the number of items in the list, and takes the form <id>#, where <id> is the question ID. The second and subsequent entries list the items, and take the form <id><num>, where <id> is the question ID, and <num> is the entry number. Entry numbers must start from 0 and be consecutive.

For example, the following entries specify a list of three TCPIP processes named $ZB018, $ZB019 and $ZB01A:

NetTCPProc#=3

NetTCPProc0=$ZB018

NetTCPProc1=$ZB019

NetTCPProc2=$ZB01A

Wildcarding can be used for the question IDs in numbered lists, but care should be taken that the resulting expansion still follows the rules for a numbered list.

For example, the following entries specify a list of 4 server classes for Prognosis XPNET Manager, all with the name 'SERVER-NCP'.

B24AppServerClass#=4

B24AppServerClass?=SERVER-NCP

Defaults

The asterisk ('*') can be used as the answer to any question to indicate that the default value should be used. Not all questions have default values (see the list of question IDs that follow). If the question does not have a default value, the '*' will be ignored, and the question will be prompted.

For example, the following entry accepts the default priority for the process manager:

INIProPri=*

The following entries accept the default for all questions, except that Prognosis for ATM/POS will not be configured:

B24GenConfig=N

*=*

Installation

Question Ids - General

Install

UnpEulaRead Type: Y/N

Default: Y

Selects whether the End User License Agreement (EULA) should be displayed.

UnpEulaAccept Type: Y/N

Default: N

Specifies whether the End User License Agreement (EULA) has been accepted.

UnpInsFile<file> Type: Y/N

Default: Y

Install patch file <file>? Where <file> is the full filename of a patch.

Value 'Y' will install the patch. Value 'N' will ignore the patch.

There will be one UnpInsFile prompt for each patch present in the install subvolume.

Use UnpInsFile*=Y to install all patches present.

UnpInsNonPrgn Type: Y/N

Default: N

Continue the install if Non Prognosis programs are discovered running in the Prognosis install subvolume?

Value 'Y' will continue the install. Value 'N' will halt the install.

UnpInsUpgrade Type: Y/N

Default: Y

Upgrade the existing Prognosis installation?

Value 'Y' upgrades the existing installation. Value 'N' will halt the install.

UnpLicAltLoc Type: Subvolume

Default: -

Specifies an alternate subvolume to copy license files from if no valid license is found in the install subvolume.

You must also specify UnpLicCopyFiles=Y to enable copying licenses from an alternate location

UnpLicCopyFiles Type: Y/N

Default: Y

Copy license files from an alternate location if no valid license is found, or abandon the installation?

A value of 'Y' will copy license files from an alternate subvolume if no valid license is found. In this case UnpLicAltLoc should also be set to a suitable value.

UnpPrgStart Type: Y/N

Default: Y

Start Prognosis on completion of the installation?

Value 'Y' will start Prognosis. Value 'N' will leave Prognosis stopped.

Prognosis 11.0

UnpPrgStop Type: Y/N

Default: Y

Stop an existing Prognosis installation on upgrade. (see also UnpInsUpgrade)?

A value of 'Y' will stop the existing Prognosis installation prior to upgrade. A value of 'N' will halt the installation if there is an existing Prognosis system running.

UnpInsDest Type: Volume/

Subvol prefix

Default: -

Destination installation subvolume for Prognosis. See Installation Subvolume Requirements (page 163) for further details. Specifies where Prognosis will be installed or upgraded.

Installation

Environment

INISolutionsDirectory Type: OSS Directory

Default: /etc/prognosis/<version_number>/solutions

Selects the location of the OSS solutions directory where record definitions are stored.

INIProCPU Type: Number 0 - 15

Default: The primary CPU of the TACL running the

install.

CPU the Prognosis Process Manager will run in.

INIProName Type: Process Name

Default: $STM

Process name used by the Prognosis Process Manager.

INIProPri Type: Number 1 - 199

Default: 180

Priority for the Prognosis Process Manager.

INIProTerm Type: device

Default: $ZHOME or console

Sets the Prognosis home terminal.

UsrChgAction Type: Keyword List - L / G / Q

Default: L

The action to take if Prognosis is started by a userid other than the Prognosis owner or SUPER.SUPER.

'L' specifies that the install process will log on to the Prognosis owner userid before proceeding.

'G' specifies that the install will change the Prognosis owner to user who started the install, and secure all files accordingly. (this will prompt for the SUPER.SUPER password).

'Q' specifies that the install will halt if it is not started by the Prognosis owner or SUPER.SUPER

Prognosis 11.0

Network

See the NETWORK Configuration Syntax section in the System Guide for further details on these settings.

NetTCPMultIFAddr Type: IP address

Default: IP address of the first

subnet (as listed by SCF) for the TCP/IPprocess specified by the NetTCPProc0

Sets the MULT-IF-ADDR parameter in the Network Configuration.

NetTCPPort Type: number

Default: 1960

Sets the TCPIP-PORT parameter in the Network Configuration.

NetTCPProc# NetTCPProc<n>

Type: processname

Default: NetTCPProc#=1

NetTCPProc0= The value of the =TCPIP^PROCESS^NAME define if it exists, otherwise $ZTC0

Sets the TCPIP-NAMES parameter in the Network Configuration.

Database

DB_HstConvert Type: Y/N

Default: Y

Selects whether to convert the 6.01 PRGNYEAR database to the PRGNHIST (Capacity Planning) database upon upgrade.

'Y' converts the PRGNHIST database if found. 'N' does not convert the PRGNHIST database.

DB_StdEnable Type: Y/N

Default: Y

Enables the Trouble Shooting and Capacity Planning databases.

'Y' enables the databases. 'N' disables the databases.

Dispatch Manager

DspEnable Type: Y/N

Default: N

Selects whether dispatch manager is configured with an SMTP server location and email address.

DspSMTP Type: IP Address/DNS Name

Default: 127.0.0.1

IP Address or DNS Name of SMTP server to be used to send Dispatch Manager emails.

DspSmtpPort Type: number

Default: 25

SMTP Port number

DspEmail Type: Email Address

Default: [email protected]

Email Address to send Dispatch Manager emails to.

Installation

Question Ids - Application Configuration

Batch Manager

BM_GenEnable Type: Y/N

Default: Y

Enable Batch Manager data collection?

'Y' (Yes) or 'N' (No)

IN Manager

HLRGenConfig Type: Y/N

Default: Y

Configure and enable HLR Manager data collection?


With 'N' the HLRGenNSDB and HLRGenStat setting will not be used.

HLRGenSubvol#

HLRGenSubvol<n>

Numbered List

Type: Subvolume

Default: -

Specifies the subvolume location of the NSDB file to be read by HLR Manager.

Only used if HLRGenConfig is set to 'Y'.

HLRStaSubvol#

HLRStaSubvol<n>

Numbered List

Type: Subvolume

Default: -

Specifies the subvolume location of the statistics file to be read by HLR Manager.

Only used if HLRGenConfig is set to 'Y'

MQSeries

MQ_GenEnable Type: Y/N

Default: Y

Enable MQSeries Manager data collection?


TMF Manager

TM_RDFEnable Type: Y/N

Default: Y

Enable collection of RDF data for TMF Manager?


TM_TMFEnable Type: Y/N

Default: N

Enable collection of TMF data for TMF Manager?


TP Manager

PthEnable Type: Y/N

Default: Y

Configure TP Manager to collect Pathway data?

PthProc#

PthProc<n>

Numbered List

Type: Process Name

Default: -

Pathmon process name to be monitored by TP Manager.

Prognosis 11.0

Question Ids - Prognosis for Payments

General

B24GenConfig Type: Y/N

Default: N

Is the Prognosis for Payments configuration process to be run?

'Y' runs the configuration process to configure Prognosis to manage BASE24.

'N' leaves Prognosis for Payments disabled. In this case, none of the BASE24 settings (the remaining settings in this section) will take effect.

Prognosis XPNET Manager

These settings are used to configure a list of BASE24 resource nodes to monitor. Therefore, each of the settings, except for B24AppConfig, is a numbered list. This allows multiple resource nodes to be specified. A resource node is specified by the entries in each list with a particular number, i.e. the first resource node is specified by the entry numbered 0 in each list. All lists should have the same number of entries.

The resource node information is used to build the BASEMAN static configuration.

B24AppConfig Type: Y/N

Default: N

Is the Prognosis XPNET Manager configuration to be run?

'Y' runs the configuration

'N' bypasses the configuration, no further XPNET Manager questions will be raised.

B24AppPass#

B24AppPass<n>

Numbered List

Type: Password

Default: -

Password for the BASE24 userid specified in B24AppUserID<n>.

B24AppPathway#

B24AppPathway<n>

Numbered List

Type: processname

Default: $PWY1

Pathway process for B24AppResNode<n>.

B24AppResNode#

B24AppResNode<n>

Numbered List

Type: resource node name

Default: P1A^GATE

Base24 resource node to monitor.

B24AppServerClass#

B24AppServerClass<n>

Numbered List

Type: pathway serverclass

Default: SERVER-NCP

Serverclass for B24AppResNode<n>.

B24AppUserID#

B24AppUserID<n>

Numbered List

Type: Base24 userid

Default: -

BASE24 userid for B24AppResNode<n>.

Installation

Prognosis ATM Status Manager

B24MonConfig Type: Y/N

Default: Y

Is the Prognosis ATM Status Manager configuration to be run?

'Y' runs the configuration.

'N' bypasses the configuration. No further ATM Status Manager questions will be processed.

B24MonSubvol#

B24MonSubvol<n>

Numbered List

Type: subvolume

Default: -

Subvolume containing terminal definition files to be monitored by Prognosis ATM Status Manager.

Prognosis ATM Transaction Manager

B24ATMConfig Type: Y/N

Default: Y

Is the Prognosis ATM Transaction Manager configuration to be run?


'N' bypasses the configuration. No further ATM Transaction Manager questions will be processed.

B24ATMPrefix Type: log file prefix

Default: TL

Filename prefix for transaction log files monitored by Prognosis ATM Transaction Manager.

B24ATMSubvol#

B24ATMSubvol<n>

Numbered List

Type: subvolume

Default: -

Subvolume containing transaction log files to be monitored by Prognosis ATM Transaction Manager.

Prognosis POS Transaction Manager

B24POSConfig Type: Y/N

Default: Y

Is the Prognosis POS Transaction Manager configuration to be run?


'N' bypasses the configuration. No further POS Transaction Manager questions will be processed.

B24POSPrefix Type: log file prefix

Default: PL

Filename prefix for POS log files monitored by Prognosis POS Transaction Manager.

B24POSSubvol#

B24POSSubvol<n>

Numbered List

Type: subvolume

Default: --

Subvolume containing POS log files to be monitored by Prognosis POS Transaction Manager.

Prognosis 11.0

Prognosis Transaction Surveillance

B24TktConfig Type: Y/N

Default: Y

Is the Prognosis Transaction Surveillance configuration to be run?


'N' bypasses the configuration. No further Transaction Surveillance questions will be processed.

Prognosis ATM Manager

Prognosis ATM Manager includes email messaging. This facility allows Trouble tickets to be dispatched to field operators by way of email messages and for field operators to respond and automatically update the corresponding Trouble tickets through pre-configured commands.

EMIEnable Type:#160; Y/N

Default: Y

Is the Prognosis email-in configuration to be run?


'N' bypasses the configuration. No further Email-in questions will be processed.

EMIEmail Type: Email Address

Default: [email protected]

Email in allows emails to be sent from a pre-designated address, use this field to input the originating email address to be used.

EMIServer Type: SMTP server name or IP

Address

Default: The domain name

specified in the EMIEmail option. For example, if the default Email address is used, then the EMIServer default would be example.com

SMTP server name or IP Address of the POP server to be used to send emails.

EMIPopPort Type: number

Default: 110

POP Server Port number.

EMIMailBox Type: mailbox name

Default: Using the example email

address, prognosis@ example.com, the default mailbox name will be 'prognosis'

A mailbox needs to be setup on the POP server specified for the exclusive use of Prognosis ATM Manager. Input the POP Mailbox name here.

EMIPassWord Type: Password

Default: The password is in base

64 encrypted format, so it cannot be seen as a default. However, the encrypted password will be stored in the Answer file and will be used as it is.

The password for the mailbox specified in the previous question.

Installation

Connex Transaction Manager

CnxGenConfig Type: Y/N

Default: Y

Is the Prognosis for Connex configuration process to be run?

'Y' runs the configuration process to configure Prognosis to manage Connex.

'N' leaves Prognosis for Connex disabled. In this case, none of the Connex settings will take effect.

CnxAtmPosConfig Type: Y/N

Default: Y

Is the Prognosis Transaction Manager for Connex configuration to be run?

'Y' runs the configuration

'N' bypasses the configuration. No further ATM Transaction Manager questions will be processed.

CnxAtmPosLocation#

CnxAtmPosLocation<n>

Numbered List

Type: <lgwarm-

location>:<logger-name>

Location of LGWARM file and logger name that are to be monitored.

Prognosis 11.0

Uninstalling from HP NonStop To uninstall the IR Prognosis Server component from a HP NonStop machine use the following procedure.

Procedure

Step 1 Stop the Prognosis Server application.

Step 2 Purge all Prognosis files in the Install Subvolume Set.

Installation

Unattended Uninstall Unattended uninstall is not available for IR Prognosis on HP NonStop.

Prognosis 11.0

Web Application The IR Prognosis Web Application component is optional and, if required, needs to be installed with a Prognosis Server component on to an MS Windows machine which is running IIS.

See the following section for installation details:

Installing the Server on MS Windows (page 81)




System Requirements (page 195)

Optional Split Deployment (page 196)

Important Notes (page 197)

Installation

System Requirements - Web Application The IR Prognosis Web Application must be installed together with a Prognosis MS Windows Server component. See the MS Windows Server topic (page 35) for specific details of the system requirements.


Platform Internet Information Services (IIS) version 7 or later

Operating System: Microsoft Windows Server 2008 (64 bit) or later

Supported Web Browsers: Microsoft Internet Explorer 10 +

Microsoft Edge 25+

Google Chrome 48 +

Mozilla Firefox 44 +

Safari 5.7+

Android 3+

iPhone 3GS + with at least iOS 5.1

iPad - all versions

Other iOS - version 5.1 +

Browser Support: For operation of the Web Application, the selected web browser must support:

- Javascript

- CSS

Prognosis 11.0

Optional Split Deployment - Web Application The IR Prognosis Web Application is normally installed on to the same machine as the Prognosis server component, this is a requirement of the Prognosis install. For a standard deployment, this automatically configures the Web Application to obtain data from the associated Prognosis server on the same machine. However, in some circumstances it may be required to have the Web Application obtain data from a remote Prognosis server. To do this a manual configuration needs to be carried out as shown below.

Procedure

Step 1 Install the Prognosis server and Web Application components on to the required MS Windows machine (such as in a web farm environment).

Step 2 If the Prognosis Server component is not required to operate on this machine, the Prognosis service should be stopped and the 'start up' type changed to 'manual' or 'disabled'. This will avoid the server component being restarted automatically. This can be done through the Control Panel > Administrative Services > View Local Services facility of the MS Windows operating system.

Step 3 On the Prognosis server go to the following folder path and open the web.config file in a text editor.

/Prognosis/WebUI/IIS/web.config

Step 4 In the <appSettings> section add the following:

<add key="ServerName" value="<PrognosisIp>" />

<add key="ServerPort" value="<PortNumber>" />

Where:

<PrognosisIp> IP address of a remote Prognosis server.

<PortNumber> By default port 6767 is used between the IIS web server and the Prognosis server. If for some reason port 6767 cannot be used, then this additional 'add key' statement needs to be included specifying the port number to be used. If port 6767 is being used then this statement is not required.

Example:

<appSettings>

...

<add key="ServerName" value="172.255.255.1" />

<add key="ServerPort" value="3535" />

</appSettings>

Step 5 Save and close the configuration file.

Step 6 If a port other than 6767 is being used between the web server and the Prognosis server, then the following addition will also need to be made to the irpqlsrv.ini file. This file can be found in the following folder path of the Prognosis server. If port 6767 is being used, then this step is not required.

/Prognosis/Server/Configuration/irpqlsrv.ini

Add the following:

[PQL]

Port=<PortNumber>


Step 8 Refresh/reopen the Prognosis Web Application.

See the Security Recommendation topic (page 201) for details of port security in such a split deployment.

Installation

Important Notes Before starting the initial installation please pay particular attention to the following requirements:

Microsoft IIS

By default, the IR Prognosis installer will setup Internet Information Services (IIS) automatically to enable the minimum requirements for the Prognosis Web Application to function. This includes creating an

application pool "PrognosisAppPool" and a website "IrPrognosisSite", plus an application named

"Prognosis" which will be created in IIS under "IrPrognosisSite" using "PrognosisAppPool".

However, when installing the Prognosis Web Application on a Microsoft Windows Server 2008 SP2 platform, it will be necessary to manually ensure that a number of Microsoft IIS settings have been enabled before installation. Please refer to the Microsoft IIS Settings topic (page 198) for details.

For Microsoft Windows Server 2008 SP1 machines the Web Application requires a 'hotfix' for IIS 7.0 to

support .NET Framework 4.0. To download the 'hotfix' go to http://support.microsoft.com/kb/958854.

Port Requirements

Port 443 is the default port that is used between the Web Browser and the Prognosis Web Application on the IIS Web Server. If the Prognosis installation detects that an existing website is listening to port 443 (https) then the installer will try to find an alternative port starting from 8080 and incrementing by 1 up to 8089. In this case the installer will show a dialog box with the selected port number, this can be manually changed if required. If no alternative port in the range 8080 to 8089 is found the installer will show a dialog box where a user specified port can be input.

When a secure website, that is using port 443 (https), is turned off and nothing is listening to this port, the Prognosis Web Application will proceed to use port 443. This will result in no Prognosis website being created (only the Prognosis application pool and Prognosis application); the Prognosis application will use the web site that is using port 443. When the installer has finished, the website has to be turned on in order for the Prognosis Web Application to function.

Port 6767 is the default port that is used between the Prognosis Web Application on the IIS Web Server and the Prognosis server. If it is not possible to use this port, please refer to the Changing Port 6767 topic (page 200).

Security Recommendations

See the Security Recommendations topic (page 201) for recommended firewall settings that can prevent potential external access to Prognosis data.

SSL Certificate

Initial use of the Prognosis Web application may cause certificate errors to be shown by way of message pop-ups or warnings in the URL. These messages indicate that the HTTPS certificate is not signed by a trusted source. Please refer to the SSL Certificate topic (page 202) for details of how to setup a certificate.

Windows Server IE Enhanced Security

When viewing the Web Application using Internet Explorer 9, or later, from any supported Windows operating system, it is possible that some screen buttons may be unresponsive. This is due to Server Manager IE Enhanced Security Settings on the Windows Server being turned 'on'. With this option turned on 'onclick' events in Javascript are disabled. Therefore in order to rectify the unresponsive buttons in the Web Application, this setting needs to be turned 'off'.

MS Windows Updates

On MS Windows 8, Windows Server 2012 and above, the Prognosis Web Application Installation may fail unless all pending Windows updates have been applied. It is therefore strongly recommended that the Windows Update facility be manually run before attempting to install Prognosis in order to ensure that the system is completely up to date.

http://support.microsoft.com/kb/958854

Prognosis 11.0

Microsoft IIS Settings When installing the IR Prognosis Web Application on a Microsoft Windows Server 2008 SP2 platform, it will be necessary to ensure that the following Microsoft IIS settings have been enabled before installation.

For Microsoft Windows Server 2008 R2, Windows 7 and Windows Server 2012 installations these settings will be automatically enabled by the Prognosis installation.

Minimum Web Server IIS Settings

The minimum Web Server IIS settings are:

Web Server (on MS Windows Server) or World Wide Web Services (on MS Windows Workstation)

Common HTTP Features

Static Content (enabled)

Default Document (enabled)

HTTP Errors (enabled)

Application Development

.NET Extensibility 4.5 (enabled)

ASP.NET 4.5 (enabled) Microsoft IIS Manager 8

.NET Extensibility (enabled)

ASP.NET (enabled) Microsoft IIS Manager 7

ISAPI Extensions (enabled)

ISAPI Filters (enabled)

Health and Diagnostics

Request Monitor (enabled)

Security

Request Filtering (enabled)

Performance

Static Content Compression (enabled)

Dynamic Content Compression (enabled)

Management Tools

IIS Management Console (enabled)

IIS Management Scripts and Tools (enabled)

Installation

To enable any of these IIS settings use the following procedure.

Procedure

Step 1 From the Windows Start menu select:

Control Panel > Programs > Programs and Features > Turn Windows Features On or Off

This will open the Windows 'Server Manager' window.

Step 2 In the 'Server Manager' window, move down to the 'Roles Summary' section:

If the 'Roles Summary' section already includes a Web Server (IIS) item, then proceed with the following 'Update an Existing Server Role' steps.

If the 'Roles Summary' section does not show an existing Web Server (IIS) item, then proceed with the 'New Server Role' steps.

Update an Existing Server Role

Step 3 Click on the Web Server (IIS) item. This will open the Web Server IIS page.

Step 4 In the 'Role Services' section click on Add Role Services.

Step 5 From the list of Role services ensure that at least all of the items shown in the 'Minimum Web Server IIS settings (page 198)' list are checked.

Step 6 When complete, click the Next button. This will open the 'Confirm Installation Selections' page.

Step 7 Check that all the required items have been selected and if everything is correct click on the Install

button.

Step 8 The Installation Result page will open verifying that the role services have been installed successfully.

New Server Role

Step 3 Click on the Add Roles option on the right side. This will open the 'Add Roles Wizard'.

Step 4 If the wizard opens at the 'Before you Begin' page, click the Next button to open the 'Select Server

Roles' page. Otherwise the wizard will open directly to the 'Select Server Roles' page.

Step 5 From the 'Roles' list, select Web Server (IIS). This will display the 'Add features required for Web

Server (IIS)' dialog box.

Step 6 On the dialog box click the Add Required Features button. This will return the 'Select Server Roles'

page.

Step 7 From the Navigation panel on the left of the 'Select Server Roles' page, click on Role Services.

Step 8 From the list of Role services ensure that at least all of the items shown in the 'Minimum Web Server IIS settings (page 198)' list are checked.

Step 9 When complete, click the Next button. This will open the 'Confirm Installation Selections' page.

Step 10 Check that all the required items have been selected and if everything is correct click on the Install

button.

Step 11 The Installation Result page will open verifying that the role and role services have been installed successfully.

Prognosis 11.0

Changing Port 6767 By default the IR Prognosis Web Application is set to use port 6767 between the IIS Web Server and the Prognosis server, either locally or in a remote setup. If port 6767 cannot be used, the following procedure should be followed to configure an alternative port.

Procedure

Step 1 On the Prognosis server machine go to the following folder path and open the web.config file in a text editor.

/Prognosis/WebUI/IIS/web.config

Step 2 In the <appSettings> section add the following:

<add key="ServerPort" value="<PortNumber>" />

Where:

<PortNumber> Input the alternative port number to be used

Example:

<configuration>

<appSettings>

...

<add key="ServerPort" value="3535" />

</appSettings>


Step 4 The following addition will also need to be made to the irpqlsrv.ini file. This file can be found in the following folder path of the Prognosis server.

/Prognosis/Server/Configuration/irpqlsrv.ini

Add the following:

[PQL]

Port=<PortNumber>


Step 6 Restart the Prognosis service and then refresh/reopen the Prognosis Web Application.

Installation

Security Recommendations IR Prognosis makes use of port 6767 between the IIS Web Server and the Prognosis server.

The following security recommendations can prevent potential access to Prognosis data by external users:

1. For standard installations of the Prognosis Web Application, where the Management Server and Web Application are running on the same machine, it is recommended to block external access to port 6767 using Windows Firewall.

2. For customized split deployments (page 196) (e.g. where the Web Application is running in a web farm connecting to a remote Prognosis Management Server) it is recommended to only allow access to Port 6767 from the remote IIS server(s).

Where an alternative port number has been configured (see Changing Port 6767 (page 200)), the same security precautions should be applied.

Prognosis 11.0

SSL Certificate Initial use of the IR Prognosis Web application may cause certificate errors to be shown by way of message pop-up windows or warnings in the URL. These messages indicate that the HTTPS certificate is not signed by a trusted source.

To remove these certificate errors the following steps should be taken on the MS Windows machine that is hosting the Prognosis Web Application:

There are two parts to the process:

Part 1 – Obtain and install the certificate provided by organization. Note that different certificate types may require different installation steps. See steps 1 through 7.

Part 2 – Bind the certificate to the website. See steps 8 through 14.

Part 1 - Obtain the Certificate

Step 1 Obtain a trusted signed certificated for the Prognosis server name. The procedures for purchasing a real SSL certificate depend upon the specific provider.

Step 2 From the MS Windows Start screen, click or search for Internet Information Services (IIS) Manager and open it.

Step 3 In the panel on the left side, click on the server name.

Step 4 In the IIS section in the center panel, click on 'Server Certificates'.

If you received a PFX certificate:

Step 5 Right-click in the central window and select 'Import...'.

Step 6 In the first field browse to the .pfx file that was provided. In the second field, enter the password associated with the certificate.

Step 7 When complete click the OK button.

If you received a CER certificate:

Step 5 From the Actions menu in the panel on the right side, click on 'Complete Certificate Request...'.

This will open the 'Complete Certificate Request' wizard.

Step 6 In the first field browse to the .cer file that was provided by the certificate vendor. In the second field enter a 'user friendly' name which can be used by the server administrator to easily distinguish the certificate.

Step 7 When complete click the OK button.

Installation

Part 2 - Bind the Certificate

Step 8 Once the SSL Certificate has been successfully installed to the server, it will be necessary to assign the certificate to the appropriate website using IIS.

Step 9 From the 'Connections' menu on the left side of the main Internet Information Services (IIS) Manager window, expand the name of the server to which the certificate was installed.

Step 10 Under 'Sites' select 'IrPrognosisSite'.

Step 11 From the 'Actions' menu on the right, click on 'Bindings...'. This will open the 'Site Bindings'

window.

Step 12 In the 'Site Bindings' window, select https and click 'Edit…'. This will open the 'Edit Site Binding' window.

Step 13 From the 'SSL certificate' field, select the certificate that has been added.

Step 14 Click the OK button.

The SSL Certificate is now installed and the website configured to accept secure connections.

The Prognosis upgrade process may overwrite an existing SSL certificate that has been assigned to the

Prognosis Web Application. Therefore, it is recommended that any applicable SSL certificate be backed up before attempting an upgrade and then re-assigned (re-bind) after the upgrade is completed. This does not apply for Self-signed Certificates'.

Prognosis 11.0

Windows Client The IR Prognosis Windows Client should be installed on at least one MS Windows machine within the monitored environment, more copies can be installed onto other machines if required.

This section describes installing the Windows Client on a separate machine as a standalone component. If the Windows Client is to be installed with a server component, please refer to the Prognosis Server on Windows Installation section (page 81).




Important Notes (page 206)

When ready to start the installation please refer to the following topic:


Installation

System Requirements - Windows Client The IR Prognosis Windows Client can be installed in either of two ways:

1) On an MS Windows machine together with the Prognosis Server component. For details of the system requirements for this installation option please see the MS Windows Server topic (page 35).

or,

2) As a standalone installation. With this option the Windows Client may be installed on a machine that is already running other applications. In this case, the Windows Client system specifications given here are in addition to the requirements of any other applications installed on the machine.


Processor (CPU): Intel® Pentium® III

Average CPU usage should be less than 50% and peak CPU usage less than 60% (CPU usage captured with all other applications operating in typical usage scenarios).

Operating System: Microsoft Windows 7 (x86 and x64)

Microsoft Windows 8 (x64)

Microsoft Windows Server 2008 (x86 and x64)

Microsoft Windows Server 2008 R2 (x64)

Microsoft Windows Server 2012 (x64)

Microsoft Windows Server 2012 R2 (x64)

System Memory (RAM): 512 MB in addition to the needs of other applications operating in typical usage scenarios.

Installation Hard Drive Space: 800 MB

Prognosis 11.0

Important Notes - Windows Client Prior to carrying out a new installation or an upgrade of the IR Prognosis Windows Client, please take note of the following points:

Microsoft Visual C++

When installing the Windows Client as a standalone installation, the following software will be required on the destination machine:

MS Windows 32-bit operating system: Microsoft Visual C++ 2013 SP1 Redistributable Package (x86)

MS Windows 64-bit operating system: Microsoft Visual C++ 2013 SP1 Redistributable Package (x86)

and

Microsoft Visual C++ 2013 SP1 Redistributable Package (x64)

Effective with Prognosis 10 SP1, if the installer does not find this software on the destination machine it will automatically install it.

Server Connections

A Prognosis version 11 Windows Client can only connect to a Prognosis version 11 server. However, previous versions of Prognosis servers can still be managed by connecting the version 11 Windows Client to a version 11 Management Server. The version 11 Management server is able to “see” any configured Monitoring Servers that are running any of the previous three Prognosis server installation versions.

Document Upgrades

Documents from earlier Prognosis versions that are OPENED in the latest Windows Client may no longer be able to be opened again in the original version. For example if a version 9 Display document is opened in a version 11 Windows Client, this document may no longer function in the original version 9 Windows Client. This rule applies even if the document is not SAVED in the new version as the document format is automatically converted to the new format as soon as it is opened and NOT when it is saved. For this reason, it is advisable to keep a separate back-up copy of all customized Displays before and after an upgrade and keep these until such time as it is determined that the need to revert back to the previous version is longer required.

Installation

Installation Procedure - Windows Client To install the Windows Client without a IR Prognosis server component carry out the following procedure.

Procedure


or






- Setup.exe





Prognosis 11.0


The next step in the installation is the acceptance of the End User License Agreement.





If you do not wish to accept the license agreement, click the Cancel button and the installation

will be aborted.

Installation

Step 3 License


When installing only the Prognosis Windows Client, this field can be left blank.


Prognosis 11.0


This dialog box offers the option of installing the various Prognosis components (page 31). However, if no license details were added in the previous 'License' dialog box the only option available here will be the 'Windows Client', no other components will be available for selection.

To install the Windows Client as a standalone component, check the 'Windows Client' option and ensure that all other options are unchecked.


Installation


This dialog box is used to assign the folder path where the Prognosis user interface components will be installed.






Prognosis cannot be installed into an existing folder. A new folder must be created.

Absolute file name length cannot exceed 258 characters. As the relative path and field names of the Prognosis packaging can reach up to 210 characters, it is strongly recommended to limit the absolute path for the Prognosis Windows Client home installation folder to 45 characters.


new folder.

Prognosis 11.0


This dialog box confirms that all the installation settings that have been made. If any changes are required select the Back button to return the required dialog and make the necessary adjustments.



Installation

Step 7 When the installation is finished the 'Complete' message box will be shown.

Click the Finish button to close the message box.

After installation a connection can be made to the required Prognosis server by opening the Prognosis Client and completing the Server Logon dialog with the server name and logon credentials.

Prognosis 11.0

UC Reporter The IR Prognosis UC Reporter component is installed with the Management Server component on to an MS Windows machine. Its use is optional and, if required, will need to be configured.

Before starting the initial installation the UC Reporter application will require the following pre-requisites:

Microsoft SQL Database:

- TCP/IP protocols need to be enabled prior to the installation of UC Reporter in order for it to use the SQL database.

- The database should be able to accept SQL authenticated logins ('mixed' authentication mode).

- If using a remote database an SQL authenticated user login should be created with specific rights. See the UC Reporter section in the online help for details.

The SMTP mail server must be configured to allow outgoing emails from the server machine, if email distribution of reports and/or error alerting via email is required.

Any anti-virus program on the server machine should allow outgoing emails on port 25 if email distribution of reports and/or error alerting via email is required.

Any firewalls should allow internal TCP traffic on the nominated Reporting Server and Logger ports.

The UC Reporter application must be installed on the same machine as the Prognosis Management Server.

Setup

Following the Reporter installation, a setup script will need to be run in order to configure the application. For details please see the Setting up UC Reporter topic in the Prognosis UC Reporter section of the Online WebHelp


System Requirements (page 215)


Installation

System Requirements - UC Reporter The IR Prognosis UC Reporter component is installed with the Management Server component on to an MS Windows machine. See the MS Windows Server topic (page 35) for specific details of the system requirements.

The following table shows details of the additional requirements for UC Reporter.

It is recommended that Prognosis UC Reporter plus the Prognosis for Unified Communications server be installed on a dedicated machine.


Processor (CPU): See the Prognosis Server on MS Windows Server Requirements (page 35).

System Memory (RAM): See the Prognosis Server on MS Windows Server Requirements (page 35).

Installation Hard Drive Space:

An additional 40 MB on top of the Prognosis Management Server and any other required Prognosis components.

Hard Drive Space for Databases:

Up to 180GB for reporter database storage, estimated as 9GB for each of up to 20 PBXs.

If a remote database is used then the Hard Drive space required on the Reporter server can be reduced.

Required Applications: Prognosis 10

Microsoft® Word 2003, 2007, 2010, 2013, or Microsoft Office 2003, 2007, 2010, 2013 (+)

Microsoft .Net V2.0

Microsoft Windows Installer 3.1 (++)

Microsoft SQL Server (tested on SQL 2005, 2008, 2008 R2, 2012 and 2014)

SMTP Server (+++)

(+) Ensure that no other versions of Word or Office are installed.

(++) If necessary, Windows Installer 3.1 will be installed from the CD. However, this will require a machine reboot.

(+++) Access to an SMTP Mail Server (e.g. MS Exchange) is required if email distribution of reports and/or error alerting via email is required. The SMTP server does not need to be on the same machine.

Report Recipients

Each report recipient must have a machine that is set up as an email client in order to receive the reports. The machine must also have Microsoft® Word 2003 or later installed in order to read the reports.

Prognosis 11.0

Upgrade Installation Upgrading from UC Reporter version 10.x (page 216)

Upgrading from Prognosis IPTM Reporter (page 217)

DCOM Setting (page 218)

Upgrading from UC Reporter version 10.x

To upgrade a copy of UC Reporter version 10.x to the latest version, please use the following procedure.

Procedure

Step 1 Run the Prognosis 10 Upgrade

On running the upgrade the following processes will take place:

a) The previous Prognosis version will be backed up.

b) The previous Prognosis version will be upgraded to Prognosis 11.

c) Prognosis 11 UC Reporter will be installed into the '<install_path>\Prognosis\Reporter' folder.

Step 2 Copy the 'registry.txt' file

After the upgrade has been run, copy the 'registry.txt' file from the \Prognosis\Backup_restore\PreviousLogs\ folder to the \Prognosis folder.

e.g. copy "C:\Prognosis\Backup_restore\PreviousLogs\registry.txt" to "C:\Prognosis\".

Step 3 Run the Setup Command

Once the upgrade has been completed, open an administrator command window in Prognosis\Reporter\Bin and run the following command

setupucreporter –b=<dir> -A=<reporter_server_account> –

P=<reporter_server_account_password>

Where <dir> is the Prognosis folder path, e.g. C:\Prognosis\

The parameters from the backup will be used to setup Prognosis 10 UC Reporter. Extra optional parameters can also be specified on the command line that will overwrite the ones stored in the backup directory, these include:

-a=<sql authentication user name> The database user for SQL authentication

-p=<sql authentication user password> The database user password for SQL authentication.

-l=<log port> The log port (default: 5998)

-r=<service port> The service port (default: 5999)

-i=<database instance> The database instance (format: server\instance).

For the default instance: use machine name only, for local machine.

-s=<paper size> Papersize (A4 or Letter, default: Letter)

Any parameters supplied on the command line will override the parameters that were previously backed up.

Please also refer to the DCOM Setting section below

Step 4 After the setup command has been run, the whole upgrade process will be complete.

Installation

Upgrading from Prognosis IPTM Reporter

When upgrading from IR Prognosis IP Telephony Management Reporter 9.6.1 to Prognosis11 UC Reporter, use the following procedure:

Procedure

Step 1 Run the Prognosis 11 Upgrade

On running the upgrade the following processes will take place:

a) The previous Prognosis version will be backed up.

b) The previous Prognosis version will be upgraded to Prognosis 11. At this point, IP Telephony Management Reporter will be backed-up to the 'Prognosis 11 Reporter\Backup' folder.

c) Prognosis 11 UC Reporter will be installed into the '<install_path>\Prognosis\Reporter' folder.

Step 2 Manually Uninstall IP Telephony Management Reporter 9.6.1

The Prognosis 10 upgrade will leave the previous IP Telephony Management Reporter version in place, this will now need to be manually uninstalled.

a) The uninstall can be done through the MS Windows Control Panel by selecting 'Uninstall a program'.

b) In the 'Programs and Features' window, locate and then right click on 'IP Telephony Management Reporter'. Select Uninstall.

c) During the uninstall of IP Telephony Management Reporter, when the 'Keep Reporter Databases' dialog box is displayed, it is important to click 'Yes' in order to preserve the existing

SQL server instance name and databases for the upgrade (IPTM_Device, Location and Exception).

Step 3 Run the Setup Command

Once the upgrade has been completed and the old IP Telephony Management Reporter 9.6.1 has been uninstalled, open an administrator command window in Prognosis\Reporter\Bin and run the following command

setupucreporter –b=<backup dir> -A=<reporter_server_account> –

P=<reporter_server_account_password>

Where <backup dir> is the backup folder under the Prognosis 11 Reporter directory named ‘Backup’, e.g. C:\Prognosis\Reporter\Backup

The parameters from the backup will be used to setup Prognosis 10 UC Reporter. Extra optional parameters can also be specified on the command line that will overwrite the ones stored in the backup directory, these include:

-a=<sql authentication user name> The database user for SQL authentication

-p=<sql authentication user password> The database user password for SQL authentication.

-l=<log port> The log port (default: 5998)

-r=<service port> The service port (default: 5999)

-i=<database instance> The database instance (format: server\instance).

For the default instance: use machine name only, for local machine.

-s=<paper size> Papersize (A4 or Letter, default: Letter)

Any parameters supplied on the command line will override the parameters that were previously backed up.

Prognosis 11.0

Please also refer to the DCOM Setting section below

Step 4 After the setup command has been run, the whole upgrade process will be complete. However, it may be necessary to manually delete the former 'PROGNOSIS IP Telephony Management Reporter' folder and any sub-folders that it contains in order to clean-up the system.

DCOM Setting

The abovementioned 'setupucreporter' command may fail if the DCOM 'Identity' setting for Microsoft Word has been previously changed to a specific user in order for Reporter to work. If this is the case, please ensure that the DCOM setting is changed back to 'The launching user' by using the following steps:

Step 1 Run 'dcomcnfg' from the Windows Start->Run menu

Step 2 Navigate to Microsoft Word Document under Console Root -> Component Services -> computer -> My Computer -> DCOM config

Step 3 Select the Identity tab under Properties and check 'The launching user'

Step 4 Save the changes and exit.

After the UC Reporter setup command has been completed, it will be necessary to change the setting back to the original user.

Installation

Service Packs and Patches From time to time IR Prognosis service packs and individual patch files will become available.

Service Packs These are cumulative sets of all product updates. A service pack will include patches issued since the initial release of the product (current version), it may also contain new features and design changes. Please refer to the 'release notes.pdf' document that is supplied with each service pack for details of what has been included.

Patch Files These normally contain updates and/or fixes to correct reported problems for individual features. Please refer to the 'read me.txt' file that is supplied with each patch for specific details of what is included.

For installation purposes service packs are treated in the same manner as patch files.

Obtaining Service Packs and Patch Files

Service pack and patch files can be obtained from the Prognosis Support Web Portal:

Prognosis Technical Support

A user id and password are required to access this site. If you do not have these please contact your

Prognosis Account Manager.

After logging on to the site, select the 'Content' tab in the Toolbar and then navigate to the required product line, version number and platform.

For details see the following topics:

Patch Naming Conventions (page 220)

Patch Installation Order (page 221)

Patch Installation on MS Windows (page 222)

Patch Installation on UNIX/Linux (page 223)

Patch Installation on HP NonStop (page 224)

Patch Installation Support Files (page 225)

Uninstalling a Patch (page 226)

IRPATCH Syntax (page 228)

https://na4.salesforce.com/secur/login_portal.jsp?orgId=00D600000006qg0&portalId=060600000008qrc

Prognosis 11.0

Patch Naming Conventions The convention used for patch file names is, 'z' followed by the Prognosis version number, followed by 'p' for patch, the patch issue number, then finally the system type such as WIN, UNIX or AIX43.

A patch file is only valid for a specific version of Prognosis.

All patches have a patch number. This may not be the same number in a different version.

A patch file is only for a specific target Operating System platform.

On Windows, the patch is wrapped in a self-extracting installer.

The files shown below are examples of patch files for a number of the supported Prognosis platforms.

z110p005-aix5364.gz z110p005-hp1164.gz z110p005-lin26.gz z110p005-nskh.gz z110p005-sol10.gz z110p005-win.exe

'z110' - specifies Prognosis version 11.0. 'p005' - specifies patch number 5. 'aix5132' - specifies it is for aix version 5.1 , 32 bit version, 'hp' is HP-UX, 'lin'=Linux, 'nsk'=HP NonStop, 'sol'=Solaris, ’'win'=Windows.

The Windows patch has an .exe extension instead of .gz as it is a self-extracting executable.

- Newer patches that are dependent on older patches will include files and/or scripts from the older patch. - The patch system will not overwrite newer files with older ones. - Patches can be installed in any order without causing functional regression.

Installation

Patch Installation Order Patch files should be installed top/down from the IR Prognosis Windows Client, the highest level Management Server and the UC Reporter server to any lower-level Management Servers and then the Monitoring servers:

1. Patch Prognosis on the Windows Client, top-level Management Server and, if applicable, the UC Reporter server.

2. Patch any mid-level Management Servers.

3. Patch Prognosis on the lower-level Management Servers and the Monitoring Servers.

Prognosis 11.0

Patch Installation - MS Windows To install an IR Prognosis patch file onto an MS Windows server carry out the following procedure.

Procedure

Step 1 From the Support Web Portal navigate to the required patch folder and then click on the patch file name.

Step 2 A dialog box will be displayed. Select Save and then copy the file to a temporary folder on the

Windows server (e.g. C:\Prognosis-Temp).

It is recommended that this temporary folder be a new folder that contains no other files except for the patch being installed.

Step 3 Go to the folder and double-click on the patch file name or icon.

Step 4 The installation process will commence and the 'Welcome' dialog will be displayed. Select the Next > button and follow the screen prompts to complete the installation.

Patch Installation on Multiple Servers

In many cases Prognosis patches will need to be installed on multiple servers within the monitored environment. Also, it may be necessary to perform certain command executions, such as shutting-down Prognosis prior to the patch installation, followed by a restart and also a check that the patch has been correctly installed. In order to do this as simply as possible, Prognosis includes an application that can assist, please refer to the File Transfer and Execution section in the Prognosis System Guide for details.


Installation

Patch Installation - UNIX To install an IR Prognosis patch file onto a UNIX server carry out the following procedure.

Procedure


Step 2 A dialog box will be displayed, select Save to download the file.

Step 3 Transfer the patch file to the patch directory on the UNIX server. This is named 'patches' and is located directly under $Prognosis_Home, i.e. $Prognosis_Home/patches.

Ensure that 'binary' mode is used to transfer the file.

Step 4 Change directory to the patch directory.

cd $Prognosis_Home/patches

Step 5 Check if the patch needs root permissions to install with the -l option of irpatch:

./irpatch -l <patch file name> | grep "root access"

where <patch file name> is the file name of the patch file.

e.g. ./irpatch -l z999p001-aix5164.gz | grep "root access"

If the patch requires root permissions you will see a line similar to:

- Requires root access

Step 6 Install the patch using the -i option of the irpatch command. If the patch requires root permissions, this will need to be run from the root user.

./irpatch -i <patch file name>

Examples:

If the patch doesn’t require root permissions:

./irpatch -i z999p001-aix5165.gz

If the patch requires root permissions:

su root -c "./irpatch -i z999p001-aix5165.gz"

You will need to respond 'Y' to confirm the installation but this can be avoided by using the optional '-n' command line switch if you want to automate this task.




Prognosis 11.0

Patch Installation - HP NonStop To install an IR Prognosispatch file onto a HP NonStop server carry out the following procedure. In most cases the patch installation will not need to shut-down the Prognosis server, but this will not apply to all patches as it will depend upon the functionality that the patch is addressing.

Procedure


Step 2 A dialog box will be displayed, select Save to download the file.

Step 3 Transfer the patch file to the HP NonStop target system, placing it into the Patch subvolume.

The Patch subvolume is named using the Install volume name plus the first four characters of the Install subvolume name with 'PTCH' appended.

e.g. if the Install subvolume is $DATA.PRGNOSIS, the Patch subvolume is $DATA.PRGNPTCH.

Ensure that 'binary' mode is used to transfer the file to the HP NonStop system.

By default the HP NonStop FTP Server creates files that can grow to approximately 53MB. If the patch is larger than 53MB, the HP NonStop FTP Server may require a special PUT command to ensure that the destination file is large enough. To specify the destination file size, a destination filename should be used with the string ",0,500,500,978" appended. This will create a file that can grow to approximately 955MB. See the HP NonStop manual "TCP/IP Applications and Utilities User Guide" for further details of the special syntax used in the HP NonStop FTP Server 'put' command. For example, to transfer the patch z999p001-nskh.gz to a HP NonStop system using a standard command line FTP client, use the following command:

put z999p001-nskh.gz z999p001,0,500,500,978

Step 4 Logon to SUPER.SUPER or an alias to SUPER.SUPER:

LOGON SUPER.SUPER

Step 5 Change to the Patch subvolume:

VOLUME <Patch subvolume>

e.g. VOLUME $DATA.PRGNPTCH

Step 6 Install the patch using the -i option of the irpatch command:

RUN IRPATCH -p <Install subvolume> -i <patch>

Where <patch> is the file name of the patch to be installed.

e.g. RUN IRPATCH -p $DATA.PRGNOSIS -i Z999P001

You will need to respond 'Y' to confirm the installation but this can be avoided by using the optional '-n' command line switch if you want to automate this task.




Installation

Patch Installation Support Files Upon installation of an IR Prognosis patch file two log files will be created. These files can be useful to refer to in case of any unexpected problems with the patch installation or to determine which patches have already been installed.

Windows and UNIX

The following files will be created in the Patches folder:

Patchlog-P<patch issue number> (e.g. Patchlog-P001)

This file provides a detailed log of the installation of each individual patch.

Audit.log

This file provides a single audit trail of each Prognosis patch that has been installed.

HP NonStop

The following files will be created in the Patch subvolume:

PlogP<patch issue number> (e.g. PlogP001)

This file provides a detailed log of the installation of each individual patch.

Auditlog

This file provides a single audit trail of each Prognosis patch that has been installed.

Prognosis 11.0

Uninstalling a Patch This procedure will always uninstall the last IR Prognosis patch that was installed. The procedure may be repeated to uninstall more than one patch but it will only ever uninstall in the reverse order of installation. There is no option to specify which patch is to be uninstalled.

Stop the Prognosis Service before attempting to uninstall a patch.

MS Windows Server

To uninstall a Prognosis patch file from a Windows machine carry out the following procedure.

Procedure

Step 1 Start a command shell (cmd.exe)

Step 2 Change directory to the patches directory directly underneath the Prognosis install directory.

e.g. if Prognosis is installed in c:\program files\prognosis, issue the commands:

c:

cd “\program files\prognosis\patches”

Step 3 Uninstall the patch using the -u option of irpatch:

irpatch -u

You will need to respond 'Y' to confirm the uninstall but this can be avoided by using the optional ‘-n’ command line switch if you want to automate this task.

The last installed patch will now be uninstalled.

UNIX/Linux Server

To uninstall a Prognosis patch file from a UNIX machine carry out the following procedure.

Procedure

Step 1 Change directory to the patch directory. This is named ‘patches’ and is located directly under $Prognosis_Home.

Step 2 Uninstall the patch using the -u option of the irpatch command:

./irpatch -u



Installation

HP NonStop Server

To uninstall a Prognosis patch file from a HP NonStop machine carry out the following procedure.

Procedure

Step 1 Change to the Patch Subvolume:

VOLUME <Patch subvolume>

e.g. VOLUME $DATA.PRGNPTCH

Step 2 Logon to SUPER.SUPER or an alias to SUPER.SUPER:

LOGON SUPER.SUPER

Step 3 Uninstall the patch using the -u option of the irpatch command:

RUN IRPATCH -p <Install subvolume> -u



Prognosis 11.0

IRPATCH Syntax IRPATCH syntax help output.

irpatch –h

Usage: irpatch [-n] [-p prognosis] [-o omitfile] -i [-a|patches...]

Usage: irpatch [-n] [-p prognosis] –u

Usage: irpatch [-p prognosis] -L [1..3] -l [patches...]

-i Install patches

-u Uninstall most recent patch

-L level Patch information detail level when listing

patches. The higher the level number, the more

details are displayed.

-l List patches (displays a summary of installed patches

if no patch names/filenames are specified),

-n Do not ask questions (non interactive)

-o omitfile Do not install files matching paths in omitfile

-a Select all patches in the current directory

-p PROGNOSIS installation directory

Configuration

Configuration

Prognosis 11.0

Configuration Once the IR Prognosis installation has been completed, some configuration procedures may now need to be carried out. The procedures required will depend upon the Prognosis deployment (page 30) that has been used in the environment. The following provides a summary of what may be needed.

Management Server


Setting up a Management Server (page 231)

Monitoring Server(s)

A number of configuration steps may be required on each Prognosis Monitoring Server in order to enable the monitoring of certain systems and vendor products. Details of any necessary configurations are contained in the product sections of the Prognosis Online Help Center.

Configuration

Setting up a Management Server A separate additional server installation, known as a Management Server, is required if more than one IR Prognosis Monitoring Server is included in the deployment. The Management Server is used to combine the collected data for the Web Application and/or Windows Client. An example deployment is shown below.

After installing the Prognosis Monitoring Server component on to the required machines and then installing the Management Server component onto a separate machine, the NETWORK Configuration on the Management Server will need to be updated with a MANAGED-NODES statement for each Monitoring Server. This statement allows the Management Server to 'see' each 'Monitoring Server.

Using the Web Application

Step 1 From a web browser open the login screen using the following URL, where <machine_name> is the name or IP address of the Management Server.

https://<machine_name>/Prognosis/Admin

Step 2 Complete the login credentials and check that the 'Login to' box has 'Administration' selected.

Step 3 Click the Login button.

Step 4 In the second panel from the left, the 'Servers panel', ensure that the Management Server is shown and is highlighted.

Step 5 In the main display area of the screen, scroll down to the 'Static Configurations' section and click on the NETWORK item.

Step 6 on the 'Update Static Configuration NETWORK' page add a MANAGED-NODES statement for each Monitoring Server (this can use the server name or IP address).

MANAGED-NODES (<monitoring_server>[:<port>])

Example:

MANAGED-NODES (SERVER_1:11791)

MANAGED-NODES (10.1.1.190)


Step 7 When finished click the Start button, wait a few moments and once running correctly the

NETWORK item will show with a green indicator.

Step 8 In the 'Servers panel' check that each Monitoring Server is now shown. If not, try refreshing the browser or recheck the configuration steps on the Management Server.

Prognosis 11.0

Using the Windows Client

Step 1 From the Windows Start menu, open the Windows Client

Step 2 Go to the Nodes Navigator and locate the Prognosis Management Server.

Step 3 Expand the Configuration folder of the Management Server.

Step 4 Right click on NETWORK Configuration item and select 'Properties' from the shortcut menu.

Step 5 In the 'Properties' dialog box add a MANAGED-NODES statement for each Monitoring Server (this can use the server name or IP address).

MANAGED-NODES (<monitoring_server>[:<port>])

Example:

MANAGED-NODES (SERVER_1:11791)



Step 6 When finished, restart the NETWORK Configuration.

Step 7 Wait a few moments and then in the Node Navigator expand the Entire Network folder and check that each Monitoring Server is now shown. If not recheck the configuration steps on the Management Server.

Using the MANAGED-NODES statement will allow each named machine to see all other named machines. If this is not suitable for the particular environment, then the alternative is to add a MANAGING-NODES statement with the name or IP address of the Management server to each Monitoring server. This will allow the Management server to see all Monitoring servers, whilst each individual Monitoring server can

only view itself.

Index

Index

A

About this Guide ................................................. 6

ACI BASE24 ................................... 48, 50, 51, 53

ACI MTS ..................................................... 55, 56

ACI Postilion ............................................... 57, 59

ACI Proactive Risk Manager ....................... 60, 61

Answer File ..................................... 158, 181, 182

Creating ....................................................... 181

Creating - HP NonStop ................................ 181

Creating UNIX/Linux .................................... 158

Format ......................................................... 182

Answer File Format ......................................... 182

Application Configuration ................................ 187

B

Backup ............................................................ 112

Backup/Rollback Previous Version ................. 112

C

Changing Port 6767 ........................................ 200

Components...................................................... 31

Configuration#Configure-ManagementServer 230

Configure - MonitoringServer .......................... 230

Connectivity ........................................................ 9

CopSSH .................................................... 86, 137

Manual Uninstall .......................................... 137

Creating .......................................................... 181

Answer File.................................................. 181

Creating an Answer File .................................. 181

HP NonStop ................................................ 181

UNIX/Linux .................................................. 158

D

DCOM_Setting ................................................ 216

Default Tarball ................................................. 141

Overriding .................................................... 141

Deployment .. 5, 30, 33, 37, 38, 39, 41, 43, 48, 50, 51, 53, 55, 56, 57, 59, 60, 61, 62, 63, 64, 65, 66, 73, 75, 76

Multi Vendor Network .................................... 75

Multiple Management Servers ....................... 41

Multiple Monitoring Servers ........................... 76

Prognosis for Infrastructure ........................... 33

Prognosis for Payments ................................ 33

Prognosis for Unified Communications .......... 66

Separate Monitoring Server ........................... 38

Single Machine .............................................. 37

Single Management Server ........................... 39

Single Vendor Network .................................. 73

Deployment Steps ......... 50, 53, 56, 59, 61, 63, 65

E

Eps .............................................................. 51, 53

F

FIPS Encryption .............................................. 102

Firewalls ............................................................ 11

FIS Connex ................................................. 62, 63

FIS IST ........................................................ 64, 65

Format - Answer File ....................................... 182

Prognosis 11.0

G

General ........................................................... 183

General Installation Information .......................... 8

General Question Ids ...................................... 183

H

Hostname ....................................................... 166

HP NonStop ... 162, 163, 164, 165, 166, 170, 172, 173, 176, 178, 180, 181, 182, 183, 187, 188, 192, 193, 224

Installation Procedure .................................. 170

New Installation ........................................... 165

Patch Installation ......................................... 224

Question Ids - Application Configuration ..... 187

Question Ids - General ................................ 183

Question Ids - Payments ............................. 188

Subvolume Requirements ........................... 163

Unattended Installation ................................ 180

Unattended Uninstall ................................... 193

Uninstalling .................................................. 192

UNPACK Command .................................... 164

Upgrade Information .................................... 173

Upgrade Installation .................................... 172

Upgrade Procedure ..................................... 178

I

Important Installation Notes ............................ 143

Web Application .......................................... 197

Important Notes ...................................... 197, 206

Infrastructure ......................................... 33, 34, 35

Install .97, 148, 166, 183, 187, 188, 194, 204, 214

Install Hostname ............................................. 166

Install License ................................................. 166

Install TempDirectory ...................................... 144

Install Username ..................................... 144, 166

Install_TempDirectory ..................................... 144

Installation .... 5, 8, 80, 83, 89, 144, 146, 163, 166, 170, 207

Installation Checklist ......................... 83, 144, 166

Installation General Information .......................... 8

Installation Procedure ............... 89, 146, 170, 207

HP NonStop Server ..................................... 170

MS Windows Client ..................................... 207

MS Windows Server ...................................... 89

UNIX/Linux Server ....................................... 146

Installation Subvolume Requirements ............. 163

Installing




Prognosis with Oracle on UNIX ................... 148

Prognosis with Oracle on Windows ............... 97

UC Reporter ................................................ 214


Web Application ........................................... 194

Introduction ............................................. 5, 30, 80

IRPATCH Syntax ............................................ 228

L

License .............................................................. 13

License File ....................................................... 13

Linux140, 141, 142, 143, 144, 146, 150, 151, 153, 155, 157, 158, 160, 161, 223

Creating an Answer File .............................. 158

Installation Procdure .................................... 146


Overriding the Default Tarball ...................... 141




Uninstalling .................................................. 160


Upgrade Installation ..................................... 150


Linux Server .................................................... 141

M

Management Server ........................................ 231

Management Server - Configuration ............... 230

Manual Steps .................................................. 135

Uninstall ....................................................... 135

Manual Uninstall .............................................. 137

CopSSH ...................................................... 137

MS Windows Server .................................... 135

Manual Upgrade Procedure ............................ 128

Manually Running the Restore Utility .............. 109

Manually_Running_the_Restore_Utility .......... 109

Microsoft IIS Settings ...................................... 198

Middleware .................................................. 34, 44

MinimumWebServerIISSettings ...................... 198

MS Windows34, 81, 82, 83, 89, 99, 100, 102, 104, 107, 109, 112, 115, 120, 128, 130, 133, 135, 139, 222

Client Installation ......................................... 204


Server Installation .......................................... 82

MS Windows - Server

Backup/Rollback Previous Version .............. 112

Index

CopSSH ........................................................ 86

Installation Checklist ...................................... 89

Installation with Oracle .................................. 97

Manual Steps to Uninstall ............................ 135

Manual Upgrade Procedure ........................ 128

New Installation ............................................. 82

Proxy Server Settings .................................... 88

System Requirements ................................... 35



Uninstalling .................................................. 133


Upgrade Installation ...................................... 99


Upgrade Process ......................................... 107

Multi Vendor Network ........................................ 75

Multi VendorNetwork ......................................... 75

Multiple Management Servers .......................... 41

Multiple Monitoring Servers .............................. 76

N

New Installation ................................. 82, 142, 165





O

Online Help Center ........................................... 15

Optional .......................................................... 196

Oracle on UNIX ............................................... 148

Oracle on Windows ........................................... 97

Overriding ....................................................... 141

Default Tarball ............................................. 141

Overriding the Default Tarball ......................... 141

P

Patch ....... 219, 220, 221, 222, 223, 224, 225, 226

Uninstalling .................................................. 226

Patch - Uninstall .............................................. 226

Patch Installation ..... 219, 221, 222, 223, 224, 225



Order ........................................................... 221

Support Files ............................................... 225


Patch Installation Order .................................. 221

Patch Installation Support Files....................... 225

Patch Naming Conventions ............................ 220

Payments43, 44, 45, 48, 50, 51, 53, 55, 56, 57, 59, 60, 61, 62, 63, 64, 65, 188

Deployment ................................................... 33

Question Ids - Unattended Install ................ 188

Port 6767 - Changing ...................................... 200

Port Requirements ............................................ 16

Pre .................................................. 104, 120, 206

Prereqisite_Software ......................................... 83

Prognosis31, 33, 37, 38, 39, 41, 43, 66, 68, 71, 81, 97, 140, 148, 162

Deployment ................................................... 30

Installation ..................................................... 80

Prognosis Components ..................................... 31

Prognosis Server ..................................... 140, 162

HP NonStop................................................. 162

MS Windows.................................................. 81

UNIX/Linux .................................................. 140

Prognosis Sever ................................................ 81

Proxy Server Settings ....................................... 88

Q

Question Ids - Unattended Install

Application Configuration ............................. 187

General ........................................................ 183

Payments..................................................... 188

R

Red_Hat_Enterprise_64_bit__AMD64_or_x86_64 .................................................................... 143

Reporting ........................................................ 214

Requisite_Software_Client .............................. 206

Requisite_Software_Upgrade ......................... 104

Rollback .......................................................... 112

S

Scalability .......................................................... 71

Security Recommendations ............................ 201

Separate Monitoring Server .............................. 38

Server Requirements ............................ 35, 45, 69

Service Pack ................................................... 219

Single Machine.................................................. 37

Single Management Server ............................... 39

Single Vendor Network ..................................... 73

Software Security Recommendations ............... 26

Split Deployment ............................................. 196

SSL Certificate ................................................ 202

Subvolume Requirements ............................... 163

Support Files ................................................... 225

Supported Platforms ............................. 34, 44, 68

Prognosis 11.0

Switch ......................................................... 64, 65

System Requirements ..................... 195, 205, 215



UC Reporter ................................................ 215

Web Application .......................................... 195

T

TempSubvolume ............................................. 166

Time Synchronization ....................................... 27

Troubleshooting Backup Issues ...................... 110

U

UC ..................... 68, 71, 73, 75, 76, 214, 215, 216

UC Reporter .................................... 214, 215, 216

Installing ...................................................... 214

System Requirements ................................. 215

Unattended Install Question Ids ...... 183, 187, 188

Unattended Installation ................... 130, 157, 180




Unattended Uninstall ....................... 139, 161, 193

Unified Communications ............................. 66, 69

Deployment ................................................... 66

Prognosis ...................................................... 66

Scalability ...................................................... 71

UC Reporter ................................................ 214

Uninstall .......................................................... 135

Manual Steps .............................................. 135

Uninstalling ..................... 133, 134, 160, 192, 226


Manual Steps - MS Windows ...................... 135

Manual Unistall CopSSH ............................. 137


Patch ........................................................... 226


Uninstalling Using ........................................... 134

UNIX140, 141, 142, 143, 144, 146, 150, 151, 153, 155, 157, 158, 160, 161, 223

Creating an Answer File .............................. 158


Overriding the Default Tarball...................... 141




Uninstalling .................................................. 160


Upgrade Installation .................................... 150


UNPACK Command ........................................ 164

Upgrade ... 99, 100, 102, 104, 107, 109, 115, 120, 150, 151, 153, 155, 172, 173, 176, 178, 216

Backup/Rollback-MS Windows Server ........ 112

Manual - MS Windows Server ..................... 128

Procedure - HP NonStop Server ................. 178

Procedure - MS Windows Server ................ 120

Procedure - UNIX/Linux Server ................... 155

Process - MS Windows Server .................... 107

Upgrade Checklist ........................... 104, 153, 176

Upgrade Information ....................... 100, 151, 173




Upgrade Installation .................. 99, 150, 172, 216




Upgrade License ..................................... 153, 176

Upgrade Procedure ................. 115, 120, 155, 178




Upgrade Process ............................................ 107

Upgrade TempDirectory .......................... 153, 154

Upgrade Troubleshooting ................................ 109

Upgrade Username ................................. 154, 177

Upgrade_TempDirectory ................................. 153

Using ....................................................... 134, 158

V

Vendors ............................................................. 68

Virtualization Support ........................................ 28

W

Web Application194, 195, 196, 197, 198, 200, 201, 202

Changing Port 6767 ..................................... 200

Important Notes ........................................... 197

Installation ................................................... 194

Security Recommendations ......................... 201

Split Deployment ......................................... 196

SSL Certificate ............................................. 202


Windows Client ....................... 204, 205, 206, 207

Installation ................................................... 204

Installation Procedure .................................. 207


Index

Windows Control Panel ................................... 134

Deployment and Installation Guide -...

Documents

Transcript of Deployment and Installation Guide -...