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 SQLManaged 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.
Upgrade policy for Automate products
- Upgrades between major releases, example upgrade from any version of 20.x to 21.0 – We do not allow customers to upgrade between the major releases on their own. They must reach out to Precisely professional services team or their partners to perform this upgrade. This policy is applicable in all the cases where the first number in the release version changes. Like upgrade from 20.2.8 to 21.1.
- Upgrades between minor releases, example upgrade from any version of 20.x to 20.3 – Customers can perform this upgrade on their own, but we require that if they face any challenges in upgrades related to their SSO configuration or high availability solution specific issue, they must reach out to Precisely professional services team or their partners to perform this upgrade.
- Upgrades between maintenance releases, example upgrade from 20.2.2 to 20.2.8 – Customers can perform this upgrade on their own, but we require that if they face any challenges in upgrades related to their SSO configuration or high availability solution specific issue, they must reach out to Precisely professional services team or their partners to perform this upgrade.
SAP NetWeaver RFC Library is required to connect Automate Evolve, Studio Manager (Server and Worker), and Studio with SAP. These products fail to connect to the SAP, if the library is not present on the system. Download this library from SAP marketplace: Steps to Download SAP NW RFC SDK files and place it at the required location. (Applicable from version 20.2.9 onwards)
Component | Studio Manager Server and Studio Manager Worker | SQL Server |
---|---|---|
Processor | 64 bit | 64 bit |
Core | 4 | 4 |
RAM | 8 GB | 8 GB |
Storage | 50 GB (free space on the application drive) | 100 GB (For application data, log and temporary databases) |
OS |
Windows Server 2022 Windows Server 2019 Windows Server 2016 |
Windows Server 2022 Windows Server 2019 Windows Server 2016 |
Network | IPV4 | IPV4 |
Network Latency between servers | less than 1 MS | less than 1 MS |
Network Speed (LAN) | 1 GBPS | 1 GBPS |
Database | NA |
Amazon RDS Azure SQL Managed Instance SQL Server on Azure Virtual Machines SQL Server 2019 (64 bit) Supported with SQL Server Always On |
IIS | 10.0 | NA |
SAP GUI |
770 - patches 1,2,3,4, 5, 6, 7, and 8 (patch 8 hotfix 1) |
NA |
.NET Framework | 4.8.x | NA |
Networking | TLS 1.0, 1.1, 1.2 | TLS 1.0, 1.1, 1.2 |
Considerations
-
If the number of users or the load increases, the system requirements will also increase.
-
The storage requirements will increase based on the document size (the size of the file and supporting documents).
-
If you are using the staging system for performance testing, we recommend a system configuration which is equivalent to that of the production setup.
-
For staging, the best practice is to use the same deployment architecture you use for the production setup (with lower system requirements).
-
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.
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 DefinitionWSDBReportRole -- Connect, Select,View Any Column Encryption Key Definition, View Any Column Master Key Definition |
Accounts | Studio 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
Component | Studio Manager Server | Studio Manager Worker | SQL 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 |
SSO authentication:
Non SSO authentication:
|
SSO authentication:
Non SSO authentication:
|
|
Browsers |
Edge*, Chrome, Firefox *Added support for Chromium-based browsers |
||
SSL Offloading | Supported | Supported | |
Server Roles and Features |
.Net Framework 4.5/4.7/4.8 Features: ASP.NET 4.5/4.7/4.8 MSMQ Server Features:
IIS Features - Web Management Tools:
Application Development Features:
Common HTTP Features:
Health and Diagnostics:
Performance Features:
Security:
Note: We do not disable these features during the uninstall process. |
Not applicable
|
|
Third-Party Software |
Microsoft SQL Server 2012 Native clientVC++ redistributable. If not already installed, the following VC++ redistribution libraries will be installed with this installer:
|
Microsoft SQL Server 2012 Native clientVC++ redistributable. If not already installed, the following VC++ redistribution libraries will be installed with this installer:
|
|
PowerShell | 5.1 | 5.1 | |
Certificates for HTTPS | Personal 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. |