These are the system requirements for product update 250 of Exact Synergy Enterprise. Please be informed that third party software products like for example Microsoft Windows (Server), Microsoft Office, and Microsoft SQL Server have their own system requirements, which might be different from the system requirements of Exact Synergy Enterprise. For more information, see the following:
Please take into account that third party software products such as Microsoft Windows, Microsoft Office and Microsoft SQL Server have their own system requirements which might be different from the system requirements of Exact Globe. Moreover, please note that Exact follows the Microsoft support lifecycle policy. In this policy Microsoft provides guidelines for product support availability throughout a product lifecycle. For more information, see Microsoft Support Lifecycle Policy.
A complete overview of the system requirements per product update can be found at the Hardware and Software Requirements for Exact Synergy Enterprise Start page.
In addition, from product update 243 onwards, the SQL reporting services will be required in order for you to generate the Reporting Services Integration reports. From product update 249 onwards, SQL Server 2008 R2 Reporting Services is required to run the reports supplied with the PSA solution as well as Exact Globe Next Dashboards. For more details on the system requirements for Reporting Services Integration, see System Requirements Reporting Services Integration.
As of product update 244, Microsoft Exchange 2010 and the 32-bit version of Microsoft Office 2010 (locally installed), excluding the click-to-run suite are supported. For more information on 32-bit version and recommendation from Microsoft, see http://office.microsoft.com/en-us/word-help/choose-the-32-bit-or-64-bit-version-of-microsoft-office-HA010369476.aspx?CTT=1. In line with this, Synergy Office Integration (SOI) now works with Microsoft Office 2010. However, note that Office Add-in does not support Microsoft Office 2010.
For an overview of the system requirements for Synergy Office Integration and Office Add-in, see System Requirements - Synergy Office Integration and Office Add-in.
Operating system (Webserver + Databaseserver)
Microsoft Windows Server 2008R2 with IIS 7 and Microsoft .NET Framework 4.0 with latest Service Pack
The Internet, and all its related products, is commonly referred to as "insecure". This is directly related to the open nature of its technology which is in fact one of its greatest benefits. When implementing Exact Synergy Enterprise, a number of strict security policies must be maintained to protect both the application software and data against malicious acts. Total system security includes various types of safety measurements, each with their own characteristics and demands for maintenance. The necessary security policies are not limited to the Exact Synergy Enterprise application alone; the integrity of all elements of the entire system must be assured.
Exact Synergy Enterprise data traffic is vulnerable along the entire path between the Client and the Application Server (and even up to the Database Server). This means that all traffic paths, the data source, the data destination and data storage have to be protected. The best way to do this is to use data encryption (HTTPS) for the e-Synergy Application Server and install a firewall to separate the company's Local Area Network (LAN) from the Demilitarized Zone (DMZ) (with the public web servers) and the Internet. For more information about this issue, read security checklist of Exact Synergy Enterprise.
The application is installed as a program on the IIS web server and all data is stored in an SQL database, which is stored on a Microsoft SQL Database Server. Both the IIS web server and the SQL database can be installed on the same machine in small Exact Synergy Enterprise implementations (up to 50 concurrent connections).
When more connections are required or use of a large database can be expected, the IIS web server should be installed on a single separate machine (suitable for up to 150 connections). This results in a setup with an Application Server (IIS + Exact Synergy Enterprise) and a separate Database Server (MS SQL Server). Note that the Client only communicates with the Application Server (IIS).
When dealing with even more concurrent connections, the workload of the application server can be divided over several Application Servers. This results in a more reliable situation with better performance. A dedicated piece of hardware, the "load balancer", can divide all traffic among several (up to 50 or more concurrent connections) Application Servers which all connect to the same database server to store and retrieve data. A general guideline is that per web/application server 300 concurrent connections can be handled.
Regularly backup the administrations/databases and store the backup on a different media device (not the machine where the Microsoft SQL Server is installed).
Perform regular database maintenance.
For the core edition of supported Microsoft Operating System, Internet Explorer must be installed.
Use scalable hardware.
In a network environment a Microsoft Active Directory (domain) needs to be present. The workstations, the SQL Server, and the Windows Terminal Server need to be part of the same active directory.
For support in a WAN environment see document 10.287.204.
Exact Synergy Enterprise has been tested in a VMware environment. This test was conducted with VMware Server version 1.0.4 in combination with Windows Server 2003 and Microsoft Office 2003. For all other combinations, please see document 16.037.327.
The system requirements are based on the usage of Exact Synergy Enterprise only if other applications are used on the same machines the requirements should be increased.
Every new service pack is supported automatically by Exact, unless explicitly announced otherwise.
Exact follows the Microsoft support lifecycle policy. In this policy, guidelines are provided by Microsoft for product support availability throughout a product lifecycle. For more information, see Microsoft Support Lifecycle Policy.