riskose.blogg.se

Open Services and copy the Tomcat Service Name:.Navigate to \SAP BusinessObjects and rename tomcat to tomcat_old ( For Tomcat 6 it will be "Tomcat6" and for Tomcat 8 it will be "Tomcat8" ).Stop Tomcat from Central Configuration Manager (CCM) or Tomcat Configuration Manager.If Tomcat is successfully upgraded to a supported version respective to the BI Platform version in use, that version of Tomcat is then supported by SAP per the PAM as normally supported if bundled with the BI Platform installation.Refer to the supported version of Tomcat mentioned in the PAM Guide for your respective BI product version. In cases where the upgraded version is not stable or has other issues you may be required to downgrade or revert to the bundled version for product compatibility, or at the request of SAP Product Support in the course of troubleshooting.

NOTE: The process of upgrading Tomcat outside of the included BI Platform installation falls under Limited Support/Out of Scope of SAP Support.You can also find the list of bundled Tomcat and Java versions which are shipped with SAP BusinessObjects Business Intelligence 4.0/4.1 using KBA : 2112338 - List of Tomcat and JVM versions shipped with each (support pack) SP of SAP BusinessObjects 4.x).Please check the PAM (Supported Platforms) Guide for the relevant tomcat version which is supported with your product version using KBA : 2183884 - Master KBA: Supported Platforms Guide / Product Availability Matrix (PAM) document links.Make a backup of the Windows registry using KBA 1323322 - Editing the Windows Registry (For Detailed Information, check KBA : 1214052 - How to make changes to the Microsoft Windows Registry).Make a backup of Tomcat's Java Parameters from the Tomcat Configuration Manager.Make a backup of the entire current Tomcat directory.Before upgrading Tomcat ensure to take the necessary backup of the files and registry for safe side.All Supported Windows Operating Systems.