Download Release Notes | Previous Versions: << Sierra << Sierra HF01 << Sierra SP1 << Sierra SP1 HF01 << Sierra SP1 HF02 << Sierra SP1 HF03 << Denali << Denali HF01 << Denali HF02 << Denali HF03 << Denali HF04 << Denali HF05 << Denali HF06 << Denali HF07

What's New? | Customer Fixed Issues and Known Issues | Prerequisites | Installation, Configuration, and Upgrade | Security Best Practices for SummitAI Application Deployment

On this page:

Requirements

This section describes the hardware and software requirements for SummitAI IT Management Suite.

Note:

AI services need additional resources. For information, please contact the SummitAI Support team.

Application Server

Minimum Hardware Requirements

Intel Xeon Quad Core processor or equivalent
8 GB of RAM
250 GB Hard Disk (Minimum 100 GB)

Minimum Software Requirements

Windows 2008 R2 Enterprise edition or later
IIS 7.0 or above (Web Server)
Dot Net Framework version 4.6.2 and above
ASP.NET State Service start type with Automatic
Desktop Experience plugin (to generate Graphical reports for Push Report)

Mandatory Upgrades for SummitAI v5.6 or later Versions

To upgrade the SummitAI application to v5.6 or later version, upgrade all the SummitAI Data Collector and SummitAI Proxy Servers to v5.6 or later. Additionally, update the Agents as per the following details:

Agent	Required Version	Setup Size	Post Installation	Remarks
SAM Agent	v2.0.3.16	~8 MB	~20 - 25 MB	.NET Dependency
AVM Agent	v3.2.0.1	~6 MB	~13 - 15 MB	.NET Dependency (Framework version 4.6.2 and above)
SSI Agent	v3.0.1.17	~17 MB	~25 - 30 MB	-
MAC Agent	v2.1	~3 MB	~8 MB	-
Linux Agent	v1.3	~5 MB	~11 MB	-

Note:

The following AVM Agents will support the SummitAI application v5.6 onwards.

AVM Agent Versions	TLS Version	Remarks
AVM Agent v3.2.0.0		.NET Dependency (Framework version 3.5 or 4.0 and above)
AVM Agent v3.2.0.1		.NET Dependency (Framework version 3.5 or 4.0 and above)
AVM Agent v3.3.0.0	TLS 1.0,1.1	.NET Dependency (Framework version 4.5 and above)
AVM Agent v3.3.0.1	TLS 1.0,1.1,1.2	.NET Dependency (Framework version 4.5 and above)
AVM Agent v4.0.0.3	TLS 1.0,1.1,1.2	.NET Dependency (Framework version 4.5 and above)

Note:

Ensure that all the SummitAI Mobile applications are updated to the latest versions.

Proxy Server

Minimum Hardware Requirements

Intel Xeon Quad Core processor or equivalent
8 GB of RAM
250 GB Hard Disk (Minimum 100 GB)

Minimum Software Requirements

Windows 2008 R2 Enterprise edition or later
IIS 7.0 or above (Web Server)
Dot Net Framework 4.6.2 and above
ASP.NET State Service start type with Automatic

Browser Compatibility

Internet Explorer (IE) version - Windows 7 IE version- 8.0.7601.17514 or above.
Note:

With IE version 8 & 9, only End User screen for Service Management will be accessible. For all other roles, IE version 10 or above is required.
Microsoft Edge version 40.15063.674.0 or above

Firefox version 30 or above
Note:

While uploading the license information for SummitAI application using Mozilla Firefox version 42.0, an error message, “Incorrect License File!”, is displayed. This is a known issue reported by SummitAI QA team. This issue is fixed in the later versions of the Mozilla Firefox browser.
Chrome version 30 or above

Safari version 5.1.7

When viewing the Application, it is best to view at 1366 x 768 screen resolution.

Database Server

Minimum Hardware Requirements

Intel Xeon Quad Core processor or equivalent
8 GB of RAM
250 GB Hard Disk (Minimum 100 GB)

Minimum Software Requirements

Windows 2008 R2 or later
SQL Server 2008 R2 Standard/Enterprise

Additionally, the following SQL Server editions are supported:

SQL Server 2012 Standard/Enterprise
SQL Server 2014 Standard/Enterprise
SQL Server 2016 Standard/Enterprise

The above mentioned minimum hardware and software requirements are for indicative purposes only. The application experience may not be the best on this minimum configuration. The performance and experience of the application depend on various factors including the customer environment. Please contact Symphony SummitAI Sales or Support Team to understand the implementation and deployment services provided to assess your specific needs.

Additional Configurations

Push Report E-mail ID Configuration at Database Level

The following data values should be changed for these fields: FromName and FromEmailID. They should be modified as per the SMTP configuration.

Select * from summit_ appconfigsettings

Push Notifications

Prerequisite

Ensure that the key for "FusionChartPath" is available in ServerMonitor.exe config file. For example: <add key="FusionChartPath" value="Iinstallation path\Jobfiles\bin\fusionchar\" />
Install/uninstall the Flash Player to execute the "FusionChartsImageSaver.dll" as follows:

For the 32-bit server environment follow the below steps:

1. To uninstall the flash, download and run the flash player uninstaller (32-bit) from http://download.macromedia.com/pub/flashplayer/current/uninstall_flash_player.exe.
2. Open Internet Explorer, download and install the Flash Player (32-bit) from http://www.adobe.com/go/getflash/

For the 64-bit server environment follow the below steps:

1. Download and install 64 Bit Flash Player from http://download.macromedia.com/pub/labs/flashplatformruntimes/flashplayer11/flashplayer11_b1_install_win_ax64_071311.exe link.

The following conditions should be considered for Push Notifications:

The Push Notifications work only with HTTPS having DNS Entry. However, it does not work with hosted server IP address.
To get the notifications in the browser, internet connection is required.
Push Notifications do not work in browser private window.

“Secure Origins” must have any of the following patterns:

(https, *, *)
(*, localhost, *)
Note:

Localhost (*, localhost, *) is only applicable to use Push Notifications functionality locally in the server.

Network Prerequisites

SummitAI Web Server

Application	Default Port
Web Server Port	80 or 443 (Configurable during installation)
Mail Server Ports Help Desk: POP/SMTP/SMTPS Monitoring: SMTP	110//25/465 25
SNMP	161, 162
SSH/Telnet	22/23
WMI – DCOM & RPC (If monitoring has to be done using WMI)	135, 445, 5000, 5001 & 5002 (Changing Dynamic WMI ports to a limited port involve registry changes in target endpoints)
Applications	Application-specific ports if applications are to be monitored.
MSSQL Database Server Port	1433 (Standard Port)
DNS/LDAP (In Domain controllers, to enable AD-SSO, ADIMPORT)	53/445 /389
Mail Server Port: SMTP (Cloud Instance)	SNMP Port No. 25 is blocked for cloud instances. User can use any custom port. However, it is recommended to use custom Port No. 587.

SummitAI Proxy Server

Application	Default Port
Web Server Port	80 or 443 (Configurable during installation)
SNMP	161, 162
SSH/Telnet	22/23
WMI – DCOM & RPC (If monitoring has to be done using WMI)	135, 445, 5000, 5001 & 5002 (Changing Dynamic WMI ports to a limited port involve registry changes in target endpoints)
Applications	Application-specific ports if applications are to be monitored.
Mail Server Port: SMTP (on Premise)	25

SummitAI Data Collector Server

Application	Default Port
Web Server Port	80 or 443 (Configurable during installation)
MSSQL Database Server Port to DB Server	1433 (Standard Port)

Ports to be Opened in Firewall

For SummitAI Web Server - SummitAI Proxy Server Communication (Registration and Replication):

SummitAI Role	Ports	Direction
SummitAI Web Server	80 or 443 (Default)	Inbound and Outbound
SummitAI Proxy to SummitAI Web Server	80 or 443 (Default)	Inbound and Outbound
SummitAI Data Collector to SummitAI DB	1433 (Standard Port)	Inbound and Outbound
SummitAI Agent	80 or 443 (Configurable during installation)	Inbound and Outbound
Advanced Remote Desktop Features (Paid Version)	Webserver Listen: 8040 Relay Listen: 8041	Inbound and Outbound
Basic Remote Desktop (OOB Available)	7900 (Default)	Inbound and Outbound

Note:

The ports mentioned above are the default ports. However, they are subject to change automatically based on the port availability. Please contact us, if you face any problem. The mode of communication between the SummitAI Web Server and SummitAI Proxy is, by default, HTTP and can be modified to HTTPS.