This is an old revision of the document!
Please review Versago's new Application Security requirements for version 2.5.6 and later
Do not use Microsoft Internet Explorer (IE) for the Versago installation process. IE is not longer supported for Versago. Download Chrome, Firefox, or any other HTML5-compatible browser and set it as the default on your Versago server.
Versago v2.3 and higher requires that Microsoft .Net Framework v4.7.2 or higher be installed before beginning an installation. The application can be downloaded from Microsoft. A restart of the server is required after installation.
Make sure there are no pending Windows Updates to help avoid a reboot during the Versago installation. If there are pending updates, install them first before installing Versago.
If you are using HTTPS Redirect to allow users to simply use the URL (e.g. https://versago.yourdomain.com) to access Versago, you should disable the redirect before beginning the upgrade.
For upgrades to v2.3 from earlier versions, note that the URL for Versago is different. The new URL is http://yourdomain/m.htm#. The previous URL was http://yourdomain/VSGUser/m.htm#. Users that have your Versago site bookmarked may need up update the bookmark to the new URL format.
SAP HANA Client should be installed on the machine where Versago is installed if you will be connecting to a HANA database to retrieve information. This application is automatically installed if SAP Business One for HANA is installed on the machine. An installation package is available from Third Wave Business Systems if it is not already installed.
HANA client change beginning with Versago 2.4.11.
Beginning with Versago v2.4.11, HANA Client v2.4.167 must be installed on the Versago server. You can download the installation package from https://portal.twbs.com. This client is also used for Bizweaver.
The installation process for this application is slightly different than “normal,” so please follow the instructions.
The installation package should remain in this folder. Removing it will cause issues with some Versago and Bizweaver functionality.
If you use a self-signed certificate, browsers will issue an unsecured connection warning. You will have to proceed beyond the warning to connect to Versago.