Differences

This shows you the differences between two versions of the page.

--- versago3:environment_requirements [2021/06/07 09:46]
dlee [Supported Browser Platforms]
+++ versago3:environment_requirements [2025/05/16 16:32] (current)
afernandes
@@ Line 1: / Line 1: @@
-====== Versago 3 Environment Requirements ======
+====== Versago Environment Requirements ======
 Review the following requirements for your Versago environment.
@@ Line 8: / Line 8: @@
   * CPU: x64 processor (1.4 GHz or faster)
   * RAM: 12GB or greater
-  * Disk: The Versago installation package requires approximately 285 MB of disk space. The installed Versago application footprint is approximately 140 MB of disk space
+  * Disk: The Versago installation package requires approximately 500 MB of disk space. The installed Versago application footprint is approximately 300 MB of disk space
 ===== Software Requirements =====
@@ Line 14: / Line 14: @@
 Third Wave recommends that Versago be installed on a dedicated server. If possible, avoid installing Versago on the **same server as that of SAP Business One**.
-  * Windows Server 2012 or higher
+  * Windows Server 2016 or higher
-  * MS SQL Server or MS SQL Server Express 2012 or above
+  * MS SQL Server or MS SQL Server Express 2019 or above
-  * Microsoft IIS (Internet Information Services) 7 or higher
+  * Microsoft IIS (Internet Information Services) 10 or higher
-  * %%URL%% Rewrite extension for IIS 7
+  * %%URL%% Rewrite extension for IIS
-  * Microsoft .Net Framework,v3.5 <color #ed1c24>AND</color> v4.7.2 or higher
+  * SAP Crystal Reports Runtime Engine 13.0.33 or later (Versago's installation file will update your CR runtime to v13.0.33)
+  * SQL Server Native Client (used by Crystal Reports)
+  * HANA client to access the SAP on HANA database
+  * Microsoft ODBC Driver
+Due to constraints imposed by Microsoft Internet Explorer and Microsoft Edge the name of the any server hosting a Versago web component should not have an underscore in the server name. For example, Server_1 would not be acceptable whereas Server1 or Server-1 would be fine.
-<WRAP center round tip 80%>
+===== Install & Configure IIS =====
-Install .Net Framework v3.5 from the Windows Server installation disk.  Download the current version of v4.x.x from Microsoft and install independently.
+Go to the //**[[versago3:installation|Installation Instructions]]**// for instructions on how to configure IIS for Versago
+===== Security Requirements =====
+==== HTTPS ====
+HTTPS with SSL is mandatory for Versago.
+You will need to acquire an **SSL Certificate** from a third party provider.
+=== Creating a Self-Signed SSL Certificate ===
+<WRAP center round important 80%>
+The use of a certificate issued by a proper authority is highly recommended. Self-sign certificates will cause an unsecured connection warning by browsers.
 </WRAP>
+The following shows how to create a self-signed SSL certificate.
+  - Open the Windows IIS Manager (Administrative Tools > IIS Manager)
+  - Select the server under the Connections pane
+  - Double click the “Server Certificates” icon in the IIS section of the page \\ \\ {{:versago:selfssl1.png?600|}} \\ \\
+  - Click on “Create Self-Service Certificates” in the Actions pane
+  - Name the certificate and store it under Personal \\ \\ {{:versago:selfssl2.png?600|}}
+----
+==== TLS Versions ====
+We recommend that protocols TLS 1.0 and 1.1 be disabled
+<WRAP center round important 80%>
+A server reboot is required after disabling these protocols.
+The protocols can remain active if other applications running on the Versago server require them
+</WRAP>
+Follow these step to **manually** disable the protocols:
+  - Open the registry editor
+  - Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client
+  - Set the DisabledByDefault entry DWORD value to 1
+  - Set the Enabled entry DWORD value to 0
+  - Navigate to \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server
+  - Set the DisabledByDefault entry DWORD value to 1
+  - Set the Enabled entry DWORD value to 0
+  - Repeat for TLS 1.1
+  - Reboot server
+{{ :versago:app_security01.png?600 |}}
+----
+==== Require Server Name Indication ====
+Define a host name and set 'Require Server name Indication' in the bindings settings for the Versago site.
+  - Open IIS Manager
+  - Select the Versago Site on the left pane
+  - Go to the Actions pane to the right and select and edit Bindings
+  - set Hostname to your site's name and select Require Server Name Indication as shown below
+{{ :versago:app_security02.png?600 |}}
-Due to constraints imposed by Microsoft Internet Explorer and Microsoft Edge the name of the any server hosting a Versago web component should not have an underscore in the server name. For example, Server_1 would not be acceptable whereas Server1 or Server-1 would be fine.
 ===== Supported Browser Platforms =====
+<WRAP center round important 80%>
+Ad blocking extensions or add-ons installed in your browser may affect some functions within the Administration Console. Disable such extensions for the Versago %%URL%%.
+</WRAP>
 The following platforms are supported for Versago clients.
@@ Line 52: / Line 115: @@
 | Phone  | Microsoft Edge  | iOS|
-<WRAP center round important 80%>
-Ad blocking extensions or add-ons installed in your browser may affect some functions within the Administration Console. Disable such extensions for the Versago %%URL%%.
-</WRAP>
 ----
 **[[versago3:Home|Home]]**

Wiki

User Tools

Site Tools

Differences

Page Tools