Change Tomcat after 2025.1 upgrade
Context
To prepare for BI 2025 moving away from Java 8, we migrated from Java 8 to Java 21.
This migration impacts everyone doing update from previous version, as the version used for Tomcat is not compatible anymore, as Java 21 requires a Tomcat 10 to work.
This change won't impact new installation, and depending on how
When migrating Tomcat, you will need to put back your user to run the service. You will also need to increase the Xmx parameter and any parameter you had added again.
Upgrade from 360Suite shipped Tomcat
If you were already on our Tomcat, the change will be seamless for you. You won't have anything to do, it will be like if we changed Tomcat version.
Upgrade from your Tomcat or SAP BusinessObjects
Please stop the Tomcat to make sure we are able to properly move files.
The way server.xml works in Tomcat 10 is a bit different and some options are not working, like APR connector. If you have such a configuration, please open a ticket so that we can assist you to get it working again.
If you are using another Tomcat than the 360Suite shipped one, you have two choice, when upgrading, you will have the following message (the message is the same for SAP BusinessObjects' Tomcat, except the path is different.)
Recommended : By simply, selecting the 'Install Tomcat 10 for 360Suite 4.3' (or 4.2), and giving the path to where we should install the tomcat, you will be able to use 360Suite embedded Tomcat.
The other choice it to download a version that is working (We are recommending 10.1.34 as version below this have CVEs), and migrate to this one in the installer, by simply changing the path given.
We will move all necessary files and folders.
By moving to 360Suite shipped Tomcat, you will now be using the port 5920 by default, if you do not change the server.xml
Last updated 4 days ago