Verj.io Version 5.11.0

Introduction

Welcome to Verj.io V5.11.0.

Prerequisites

For both the Verj.io Server and Verj.io Studio components, the minimum Java version is 1.8 at level 181. You are recommended to use the Java version contained in the distribution.

Downloads and Installation

Download the file(s) for your environment. Note that the Verj.io Studio (used for development) includes an embedded server – a separate Verj.io Server is not required.

Verj.io Studio

• Studio Windows installer (64 bit) – Download and run installer executable, then follow the installation instructions.
• Studio Linux bundle (64 bit) - To unpackage and install the Linux bundle, please click on the instructions here.
• Studio Mac installer (64 bit) - Download and double click the installer dmg, then follow the installation instructions.

Verj.io Server

• Server Windows installer (64 bit) - Download and run installer executable, then follow the installation instructions.
• Server Linux bundle (64 bit) - To unpackage and install the Linux bundle, please click on the instructions here.

Upgrade

It is only possible to upgrade to this release if your starting point is V5.6 or higher. V5.6 was a landmark release that introduced substantial changes to the file system layout for both the Verj.io Studio and Verj.io Server components.

To upgrade a V5.6+ system:

• Backup the file system
• Stop the system – either studio or server
• For Windows/Mac systems: run the installer as described above and select the option to upgrade an existing system
• For Linux systems:

· for the Studio follow the instructions here

· for the Server follow the instructions here

• Restart the system

To upgrade a system prior to V5.6:

You must first upgrade to V5.6.

Post Upgrade

The following instructions apply only to Verj.io Server installations.

Check and adjust the Tomcat server.xml file in /<userdata>/server/tomcat/conf/server.xml. The userdata folder location is selected as part of the installation/upgrade process. It’s usually named UserData and is located in parallel with the VerjioServer installation directory.

Background: This upgrade has installed a new version of Tomcat - 8.5.54 - which has introduced additional security parameters for the AJP connector used to connect to IIS or Apache. If your installation has previously modified the copy of server.xml in /<userdata>/server/tomcat/conf e.g. to change the HTTP port, the new configuration changes will not have been copied by the installer and will then cause the following error messages to be generated when the server is restarted after the upgrade; the Tomcat changes should be manually installed as described below. If you haven’t made any changes to server.xml, you don’t need to take any action.

Symptom: the server starts OK but connections using the AJP connector fail. The following error message is shown at startup in the tomcat log file in /<userdata>/server/tomcat/logs

“The AJP Connector is configured with secretRequired="true" but the secret attribute is either null or "". This combination is not valid.”

Correction: Edit file /<userdata>/server/tomcat/conf/server.xml and locate the AJP connector. It will look something like this:

<!-- Define an AJP 1.3 Connector on port 8009 -->

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" tomcatAuthentication="false" maxSwallowSize="50000000"/>

If the server is running in a trusted network and the additional security is not required or if you don’t use the AJP connector, add parameter: secretRequired=”false” e.g.

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" tomcatAuthentication="false" maxSwallowSize="50000000" secretRequired=”false”/>

Otherwise add parameters: secretRequired=”true” and secret=”xxxxxxxx” e.g.

<Connector port="8009" protocol="AJP/1.3" redirectPort="8443" tomcatAuthentication="false" maxSwallowSize="50000000" secretRequired=”true” secret=”xxxxxxxx”/>

..where xxxxxxx is a private secret key. The secret key must also be configured in the corresponding configuration file for IIS or Apache. See also the Tomcat AJP Connector Documentation.

Then restart the server.