Upgrading the version of Galigeo consists in redeploying a new webapp in Tomcat. Since no configuration is stored in the web application (all the configurations are stored in the directory $GALIGEO_HOME), this action will not require any re-configuration.
There are multiple ways to re-deploy a webapp in Tomcat. Here we propose a simple solution.
This section will help choosing the right hardware for running Galigeo G20.
Galigeo is a J2EE application which means only the memory settings of the JVM matters. Usually the maximum memory allocated to Tomcat does not exceed half the memory of the server. For example, if a server has 16Go of RAM, the Java xmx won't exceed 8Go.The memory settings are highly dependent on the usage of the application. The following table helps understand the order of magnitude for several scenarios (assuming the map documents are compliant with the best practices).
|10 concurrent users
|20 concurrent users
|More than 20 concurrent users
|We recommand using multiple instances with a load balancer
Galigeo is divided in two parts on the disk: the Java webapp and the $GALIGEO_HOME directory. Usually we recommand using a machine with at least 600Go of hard disk.
The Java webapp unzipped is about 200Mo.
The $GALIGEO_HOME directory uses 100Mo of space on a fresh install. This directory will store all the resources used by the application (data, logs, cache, ...). The folder can grow to 1Go or 2Go according to the usage.
List of supported versions.
|Latest service pack
|End of support
This section concerns only the Galigeo Enteprise administrators
Galigeo Enterprise G20 is a major release which introduce lots of simplicity compared to the previous versions. The main change with this version is that the administration panel (based on Adobe Flash) is not used any more and all the administration is done through the Galigeo Manager common to all versions.
However, if you are using a version < G20 and you want to upgrade to a version >= G20, you will need to convert your documents to the new version. Galigeo provides a tool to help doing this conversion. Note that the migration creates a copy of the documents so the configuration will still work with the previous version (but the modifications won't be synchronized).
If you want to have both versions running in parallel, instead of step 3. you can install a new Tomcat server and install the new version on it. When you first open the application you will be asked to specify the location of the GALIGEO_HOME directory. During this step, make sure you specify the existing one.
The conversion tool will not be able to convert everything because some features are too different between the two versions. Here are the limitations:
Find below the steps to add Galigeo Rewrite Rule in IIS. These steps are only guidelines as it may differ depending on IIS version.
There is no support on IIS setup.
October 2022 - According to CVE-2022-42889 recommendation, Apache lib "commons-text" has been updated from commons-text-1.9.jar to commons-text-1.10.0.jar in Galigeo G22 SP1 and subsequent versions.
July 2022 - According to CVE-2021-4104 recommendation, Apache LOG4J1 has been updated to LOG4J2 (2.17.2) in Galigeo G22 SP0 and subsequent versions.
July 2022 - Spring vulnerability CVE-2022-22950 - No impact on Galigeo Platform, Cloud or On Premise:
April 2022 - Spring vulnerability CVE-2022-22965 - No impact on Galigeo Platform, Cloud or On Premise:
February 2022 - LOG4J-1 vulnerability CVE-2021-4104 - No impact on Galigeo Platform, Cloud or On Premise:
December 2021 - LOG4J-2 vulnerability CVE-2021-44228 - No impact on Galigeo Platform, Cloud or On Premise:
Important Notice 30 Sept. 2021 (updated on November 19, with 4.2 SP9 patch 4 notice):
SAP reported a critical issue affecting Custom Elements. See SAP Note 3103998.
In the BOE CMC, testing any Custom Element (Galigeo or other) always fails with the error: "Test has failed. [IllegalArgumentException] (Error: RWI 00011)". Therefore it is impossible to declare any Custom Element (Galigeo or other). The issue concerns the following patches releases:
January 2021 - Galigeo G21, Beta support of BI 4.3 SP1:
The support of BI 4.3 is still in Beta because of limitations in SAP 4.3 APIs (vs. 4.2). We are collaborating with SAP to overcome those limitations.
Features not yet supported with BI 4.3 are:
Important Notice 29 Sept. 2020:
SAP reported a critical bug affecting Custom Elements. See SAP Note 2966271.
There is a rendering problem with an empty custom element, not showing any content (Galigeo or other) in the following patches releases:
Important Notice 18 Dec. 2019:
For customers using Galigeo G19.5 or earlier
if you plan to update to SAP BI 4.2 SP6 patch11 (10/23/2019) or greater, SAP BI 4.2 SP7 patch5 (09/05/2019) or greater, SP8 (02/24/2020) or greater
Security rules to access the BOE APIs are continuously reinforced by SAP, which leads to changes starting in BI 4.2 SPs and/or patches released since 2019 September.
BOE APIs, used by Galigeo eXperience for WebI, are no more available by default in those SPs and/or patches and need a specific procedure to get activated.
The procedure is quite simple and does not need Tomcat service to be restarted. The necessary elements and the detailed procedure can be downloaded here.