High-usage Production Environment
(Manual and Server Scheduling)

Notes: These requirements are for a system configuration capable of handling approximately 400 users who use the system for both Manual run and Server scheduling - with those users submitting a total of 220 or fewer new files daily.

If any parameter extends beyond what is noted in the high-usage production environment example, please contact the Winshuttle Customer Support team for consideration of your specific case.

If you are working through a VPN and/or accessing Evolve from a remote location, we recommend an internet speed of at least 10 Mbps (for both download and upload speeds). We also recommend that any latency between your browser and the Evolve server be less than 100 milliseconds. Slower internet connections can cause performance issues and in some cases timeout errors.

The performance of the application on On-Premise and On-Cloud (private cloud) systems will be same, provided the system resources are same and network latency is not a bottle-neck.

Database details:

  • SQL Server on Azure Virtual Machines allows a customer to run SQL Server inside a virtual machine in the Azure cloud. It is supported with all versions of Evolve, from the first version (20.0) to the most current version.

  • Azure SQL Managed Instance is a collection of system and user databases with a shared set of resources that is lift-and-shift ready. It is supported with Evolve 20.2 and all subsequent versions.

  • Azure SQL Database is built on standardized hardware and software that is owned, hosted, and maintained by Microsoft. Winshuttle does not support it and currently has no plans to support it.

  • If the Evolve DB is on cloud (using Amazon RDS or Azure SQL Managed Instance or SQL Server on Azure Virtual Machines), then we recommend to have Server and Worker machines also on cloud. This will help in reduction of the network latency and improve performance.

Note: The Winshuttle Third-party-product support policy states that when Microsoft or SAP products are in limited/extended support or end-of-life, then Winshuttle products are also in limited support. Hence, customers will not get any code fixes on these product versions from Winshuttle. Customers who need code fixes, will have to upgrade their third-party products and if applicable Winshuttle products (in the case of Foundation 12.x customers will migrate to Evolve) to get code fixes. For more information, see also the Product Availability Matrix and system requirements below.

Component Studio Manager Server Studio Manager Worker SQL Server
Processor 64 bit 64 bit 64 bit
Core 4 4 8
RAM 16 GB 16 GB 32 GB
Storage

100 GB (Free space on the application drive)

100 GB (Free space on the application drive) 500 GB (For application data, log and temporary databases)
OS Windows Server 2019
Windows Server 2016

Windows Server 2019
Windows Server 2016

 Windows Server 2019
Windows Server 2016
Network IPV4 IPV4 IPV4
Network Latency between servers less than 1 MS less than 1 MS less than 1 MS
Network Speed (LAN) 1 GBPS 1 GBPS 1 GBPS
Number of Machines
 2

2

Each machine should have 4 instances of Worker services.

1
Database NA NA

Amazon RDS

Azure SQL Managed Instance

SQL Server on Azure Virtual Machines

SQL Server 2019 (64 bit)
SQL Server 2017 (64 bit)

Supported with SQL Server Always On
IIS 10.0 NA NA
SAP GUI

770 - patches 1,2,3,4, and 5

760 - patches 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10

750 – patch 10 (Not supported from 20.2.8 onwards)

See Which SAP GUI versions are supported by Winshuttle? for details

770 - patches 1,2,3,4, and 5

760 - patches 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10

750 – patch 10 (Not supported from 20.2.8 onwards)

See Which SAP GUI versions are supported by Winshuttle? for details

 NA
.NET Framework 4.8.x 4.8.x NA
Networking TLS 1.0, 1.1, 1.2 TLS 1.0, 1.1, 1.2 TLS 1.0, 1.1, 1.2

Note: A High Availability setup can be created for this application by adding additional nodes and using a network load balancer. We have tested the F5 load balancer and it was successful; other load balancers should also work. We also support the SQL Always On capability of Microsoft SQL Server.

Considerations

  1. If the number of users or the load increases, the system requirements will also increase.

  2. The storage requirements will increase based on the document size (the size of the file and supporting documents).

  3. SQL server data must be purged or archived at regular intervals to avoid application issues. Based on your usage data, you can determine the frequency with which the SQL server data needs to be purged or archived.

Note: Please contact Winshuttle Customer Support with any questions.

Account Requirements

Accounts Studio Manager Server
Installation
Accounts		 SQL Server Roles: DB Creator, Security Admin
Application DB: DB Owner
Server Machine Admin
Application
Pool Account		 Supported: Application Pool Identity, Network System, Custom Account

Permissions provided by the installer:

Application Folder -- Read and Execute
Application Log Folder -- Read and write
Application MSMQ -- Receive Message, Peak Message,
Receive Journal Message, Get Queue Properties, Set Queue Properties,
Get Queue Permissions, Change Queue Permissions, Take Queue Ownership, Write Message.
Full Control permission is provided to the local machine Administrators group.

Application DB -- WSDBAccessRole and WSDBReportRole

Permissions on these roles:
WSDB Access Role -- Connect, Select, Execute, Delete, Insert, Update, Create View, View Any Column Encryption Key Definition, View Any Column Master Key Definition

WSDBReportRole -- Connect, Select,View Any Column Encryption Key Definition,
View Any Column Master Key Definition
 
AccountsStudio Manager Worker
Installation
Accounts		SQL Server Roles: DB Creator, Security Admin
Application DB: DB Owner
Server Machine Admin
Application
Pool Account

Supported: Local Service, Network System, Custom Account

Permissions provided by the installer:
Application Folder -- Read and Execute
Application Log Folder -- Read and write
Application MSMQ -- Receive Message, Peak Message, Receive Journal
Message, Get Properties, Set Properties, Get Permissions, Set Permissions,
Take Ownership, and Send Message. Full Control permission is provided to
the local machine Administrators group.

Application DB -- WSDBAccessRole and WSDBReportRole

Additional Details

ComponentStudio Manager ServerStudio Manager WorkerSQL Server
Ports

443, 80:
By default, we use these ports for HTTPS and HTTP respectively. If we change these ports during the installation of Studio Manager Server, they must be valid and open.

25, 587:
If Exchange is Outlook 2010, 2013 or 2016,
we need port 25. If Exchange is Office 365 in the cloud, we need port 587. For Studio, if we use Custom Proxy Settings (Option->Proxy & Email), we will use the port specified there.

3300 – 3399:
Use these ports to connect Evolve Worker RFC calls to
the SAP server

135, 2101*, 2103*, 2105*:
MSMQ listen and receive messages on these ports

3300 – 3399:
Use these ports to connect Studio Manager Worker RFC calls to the SAP server.

135, 2101*, 2103*, 2105*:
MSMQ listen and receive messages on these ports.

1433, 1434:
Use these ports to connect to the Database Server from the Studio Manager Server and/or from the Studio Manager Worker.
IIS Authentication

For Windows Authentication -
Enable Window Authentication and Anonymous

For SAML 2.0 Authentication - Anonymous

For Windows Authentication -
Enable Windows Authentication and Anonymous

For SAML 2.0 Authentication - Anonymous

 
Certified SAML Types

The current version only supports Azure, Auth0, OKTA, ADFS IDPs.

Google Authentication - Supported from 20.2.8 onwards

The current version only supports Azure, Auth0, OKTA, ADFS IDPs.

Google Authentication - Supported from 20.2.8 onwards

 
Certified OAuth Types

The current version only supports Azure, Auth0, OKTA, ADFS IDPs.

Google Authentication - Supported from 20.2.8 onwards

The current version only supports Azure, Auth0, OKTA, ADFS IDPs.

Google Authentication - Supported from 20.2.8 onwards

 
SAP Authentication

SAP Credentials
SAP SSO

SAP Credentials
SAP SSO

 
Browsers

Edge*, Chrome, Firefox

*Added support for Chromium-based browsers

  
SSL Offloading SupportedSupported 
Server Roles and Features

.Net Framework 4.5/4.7/4.8
Features: ASP.NET 4.5/4.7/4.8

MSMQ Server Features:

  • MSMQ Server Core
  • MSMQ Active Directory Domain Services Integration

IIS Features - Web Management Tools:

  • IIS Management Console
  • IIS Management Scripts and Tools
  • IIS Management Services
  • World Wide Web Services

Application Development Features:

  • .NET Extensibility 4.5/4.7/4.8
  • Application Initialization
  • ASP.NET 4.5/4.7/4.8
  • ISAPI Extensions
  • ISAPI Filters

Common HTTP Features:

  • Default Document
  • Directory Browsing
  • HTTP Errors
  • HTTP Redirection
  • Static Content

Health and Diagnostics: 

  • Custom Logging
  • HTTP Logging
  • Logging Tools
  • ODBC Logging
  • Request Monitor
  • Tracing

Performance Features: 

  • Dynamic Content Compression
  • Static Content Compression

Security: 

  • Request Filtering
  • Windows Authentication

Note: We do not disable these features during the uninstall process.

Not applicable

 

 
Third-Party Software

Microsoft SQL Server 2012 Native client

VC++ redistributable.
If not already installed, the following VC++ redistribution libraries will be installed with this installer:

  • VC++ 2015-2019 (x64)
  • VC++ 2008 (x64)
  • VC++ 2010 (x64)
  • VC++ 2013 (x64)

Microsoft SQL Server 2012 Native client

VC++ redistributable.
If not already installed, the following VC++ redistribution libraries will be installed with this installer:

  • VC++ 2008 (x64)
  • VC++ 2010 (x64)
  • VC++ 2013 (x64)
 
PowerShell 5.1 5.1  
Certificates for HTTPSPersonal store and Web store certificates are supported.

Domain and Wild card types certificates are supported.		Personal store and Web store certificates are supported.

Domain and Wild card types certificates are supported.