Change log
This document describes any technical changes made to Easit GO between releases.
2024.06
Easit GO have been migrated to Spring Boot and now, instead of a standalone Java application running in Apache Tomcat (installed as a Windows service), comes with an embedded Tomcat. This migration affects the components listed below in your Easit GO installation.
Spring Boot
At the release of Easit GO 2024.06, Spring Boot 3.2.2 is used.
Service container
Apache Tomcat
With the start of this release, as Spring Boot embeds Apache Tomcat with the application, we do not run Easit GO with Apache Tomcat as a Windows Service. Instead we leverage a service wrapper WinSW to install a Windows service that give you the possibility to start, stop and monitor the service as any other Windows Service. The embedded version of Apache Tomcat is at release 10.1.18.
Solution
Save the settings for Apache Tomcat, uninstall the service Apache Tomcat - Removing services and install Easit GO as a Spring Boot application.
Web traffic
IIS / ISAPI
The configuration of IIS, ISAPI filters and its settings have not been changed but the AJP connector settings, that corresponds to the ISAPI settings living in the Apache Tomcat file server.xml have been moved to the properties.xml file for Easit GO.
Solution
Add the AJP connector settings from server.xml to properties.xml and remember to add the property key ajp.enabled as true.
properties.xml
hibernate.dialect
With this release of Easit GO we have updated the dialect used for Hibernate to EasitMSSql2016Dialect.
Solution
Update the value for property key hibernate.dialect to com.easit.util.hibernate.EasitMSSql2016Dialect.
Database
Hibernate
We have updated the Hibernate (an Object/Relational Mapping (ORM) framework) version to 6.4.3, coming from 5.4.31. This update means that we introduced some breaking changes in what data types are used in the database and indexes added to different tables.
Solution
Contact our support for guidance when upgrading Easit GO from 2023.11 or earlier to 2024.06 and later.
Logging
Log4j2 - Lookups
In previous releases of Easit GO, Apache Tomcat added some system properties that was available in the log4j configuration. The most prominent one is sys:catalina.base that we used to know where to place all logs. These are no longer available, or correct.
Solution
Replace any system properties with these properties.
- sys:bpeBasePath (Path to directory where easitgo.jar exist)
- sys:bpeConfigPath (bpeBasePath\config)
- sys:bpeLogsPath (bpeBasePath\logs)
- sys:bpeAuditLogsPath (bpeLogsPath\audit)
Feedback
As always, please report any issue or problems to our support.
2023.11
No changes were made that affects the installation or its configuration.
2023.05
Database drivers
MSSQL
In this release we have updated the driver used for connecting to MSSQL databases to version 12.2, coming from version 8.2. Due to this update we are effected by changes made in 10.2 where the default value for the property encrypt was changed to true, previously false.
Solution
In order to keep the same behavior prior to 2023.05, please add the string encrypt=false to any connection string.
- properties.xml:
<entry key="dataSource.url">jdbc:sqlserver://localhost;databaseName=example;encrypt=false</entry>
- Data warehouse configuration: Add ;encrypt=false after the database name.
- ImportClient:
jdbc:sqlserver://SERVER;databaseName=DATABASE;encrypt=false;user=USER;password=PASSWORD
MariaDB / MySQL
We also updated the driver for connecting to MariaDB databases. Coming from version 2.2.0 and updating to 3.1.2. This means that if you are connecting to an MariaDB database you need to update the connection string as shown below.
Solution
- Connection string for 2.2.0:
jdbc:mysql://....
- Connection string for 3.1.2:
jdbc:mariadb://....