Change Tomcat after 2025.1 upgrade

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 

Info
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's bundled Tomcat

If you were already using 360Suite's 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

Alert
Please stop the Tomcat to make sure we are able to properly move files.
Warning
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.)


Info
Recommendation: by simply selecting the "Install Tomcat 10 for 360Suite 4.3" (or 4.2) and giving the path to the tomcat future location, you will be able to use 360Suite's bundled Tomcat. 
The other choice is to download a compatible version (we recommend the latest 10.1.x since lower versions may hold CVEs), and migrate to this one in the installer, by simply changing the provided path. 
All necessary files and folders will be moved by the installer.

Info
By moving to 360Suite shipped Tomcat, the application default port will be 5920, unless the "conf/server.xml" configuration file is edited to use another port number.

    • Related Articles

    • Read Tomcat Logs after 2025.1 upgrade

      Context 2025.1 made a lot of changes regarding log generation. Allowing users and support agent to be more efficient in the search of issues. The 360Suite Tomcat will now generate new files if old one are getting too large, this will only happen on ...

    • DB006 : Could not acquire change log lock

      Symptoms When saving the database configuration in the 360Suite Administration Console, the following error message appears: DB006 : Could not acquire change log lock Cause When the application is upgraded, the database structure is updated (new ...

    • 360Suite database configuration is not set when restarting Tomcat server

      Symptoms On application startup, a warning popup appears In the Administration console, the database configuration is empty even though is was setup previously Environment 360Suite Web Platform Linux server (all) Additional symptoms : tomcat logs In ...

    • How to enable AD authentication on the Web Platform

      Context You want 360Suite Web Platform to use AD authentication the same way Business Objects does. Procedure As part of the AD authentication configuration on the Business Objects server, two files will have been created and saved on “C:\Windows\” ...

    • Does Apache Tomcat belongs to Product Support scope?

      Context Does Apache Tomcat belong to Product Support scope? Answer Apache Tomcat, a free open-source third-party Web application server, is bundled with 360Suite (a Wiiisdom product) for convenience of use, but is not considered part of the ...