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 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

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
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.

Info
By moving to 360Suite shipped Tomcat, you will now be using the port 5920 by default, if you do not change the server.xml

    • 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 ...

    • What are the proper steps to set up the Tomcat service account for Web Platform?

      Symptom How to configure 360Suite Web Platform to use a Windows domain service account to run the 360Suite Windows Service, if it is not an Administrator on the server, i.e. the Tomcat user? Environment 360Suite Web Platform Cause The issue is ...

    • Does Apache Tomcat belong to Product Support scope?

      Symptom Does Apache Tomcat belong to Product Support scope? Environment 360Suite Web Platform any version Tomcat 7 and above  Resolution Apache Tomcat, a free open-source third-party Web application server, is bundled with GB&Smith products (360Suite ...

    • Database Debug Mode (on Microsoft Windows)

      Condition Database issues arise and detailed logs are needed for debugging and fixing problems. Solution Cause The database may be corrupted or other technical issues arise. Remedy 1. Open a Windows command line or PowerShell prompt. 2. Access the ...

    • Configure 360Suite with SSL

      Context For many features, 360Suite needs to access the BOBJ RESTful API. The impacted modules are: - 360View - 360Eyes - 360Cast - 360Bind / WiiisdomOps for BusinessObjects In this situation, 360Suite takes the role of client to the BOBJ RESTful ...