Hi,
Since we are having some issues with Tomcat 5.5 we are thing to upgrade it to Version 6.
My question is about the way how to do it. Is there a documentation to follow (tried Google already but no luck)?
Tomcat 5.5 we are using has been installed by BO itself (default settings).
XI3.1 fp2.
Win Server 2003 SP2.
Thank you for your help.
nlajka (BOB member since 2008-07-31)
I’d suggest upgrading to FP1.6 prior to doing a Tomcat upgrade …
I.e. I think the issue is with your application and local configuration as opposed to Tomcat 5.5 … unless yo have encountered a specific fault?
MikeD 
(BOB member since 2002-06-18)
Just an aside…
We’re trying to set up an install to 6.0.20, outside of the BOXI install dirs, and actually on a different drive.
This is not a “hey, let’s just use a new version and see if we can hose the installation”, but a “the organization requirements are for ver 6.0.20”. This is due to security alerts and configuration requirements. While we MIGHT be able to get a (temporary) waiver to allow us to install just using 5.5, every security audit would flag us as non-conforming, a security risk, and also risk getting our installation shut off the network.
It may seem stupid to many folks, but we have no control over what the security requirements are.
I have tried several different methods to effect the Tomcat 5.5 to 6.0 and upgrade and we’re not through trying, but my results are less than spectacular.
Tried a vanilla install, to TC 5.5, in the BOXI dir. Seemed to work, but we were out of spec (actually, I don’t REMEMBER if I tested all of the functionality – WebI is a critical app for us).
Tried a pre-install of TC 6.0.20 to the appropriate drive (build guidelines w/ security req’ts). Did an install of BOXI referencing an already installed app server (Tomcat 6.0) but TC 5.5 is what is listed in their install prog. Gave correct location for apps dir. Some of the services worked. I could get into CMC, Infoview, etc. WebI does not function (get 404).
Did a pre-install of TC, and during BOXI install, specified “will install web services at a later time”. Got whatever core code/services laid down. Tried a manual deploy from TC, and tried a bulk deploy using wdeploy. For the wdeploy, I edited the tomcat config and properties files in the “deploy” folder under BOXI’s dirs.
Results for 2 & 3 have been the same… some parts work (CMC, InfoView) and some turn 404’s. Investigation of the apps directories indicate that the main .jsps and htmls are missing.
This should not be these hard. Installing and deploying are not rocket science. Of course, I am ASSuMEing that I did everything correctly. 
Next attempt will be reverting to the vanilla install and TC 5.5, then trying two paths:
a) Upgrade TC 5.5 to 6.0.20, test
b) Move TC location to the appropriate drive, test
If either of the above work, then we’ll try the other.
Oh, and one last possibility… manually deploy, moving the WARs if necessary, and, I’m not above opening the things up and looking inside.
And, tech support is next to useless… the “self serve” website is next to useless. The best support I get is off of web forums.
Yo, SAP/BO/whoever… are you listening?
mvisconte (BOB member since 2008-01-17)
mvisconte,
have you successfully upgraded to Tomcat 6.0.20?
I am in the similar situation. We are testing the upgrade to BOE XI 3.1 and have been informed of the security IAVAs for Tomcat 5.5. So need to upgrade to Tomcat 6.0.20, but also need to upgrade BOE XI 3.1 to SP2 in order to be suppored by SAP/BO.
I have yet to perform this installation/upgrade to test the results, but what I was told is to install BOE XI 3.1 (along with packaged Tomcat 5.5) then install Tomcat 6.0.20 and copy the contents from the following directory:
“installdir”\Business Objects\Tomcat55\conf\Catalina\localhost to the new conf directory on the Tomcat 6.0 instance.
I will give this a try when I get a chance.
Did you succesfully upgrade Tomcat?
thanks,
Scott
Scott_at_Pax (BOB member since 2006-11-27)
Scott,
I am getting the same vulnerability from IAVA scans, were able to get tomcat upgraded?
shaley (BOB member since 2009-08-13)
Shaley,
No I have not had a chance to try and upgrade Tomcat to v6.0.20.
After working the BusObj Tech Support, I finally got BOEXI R3.1 SP2 installed, which they required to go to Tomcat 6.0.20.
Will try the upgrade, but may want to submit a message to BusObj Tech Support for assistance since Tomcat is currently installed and configured as part of the BOE XI 3.1 package.
Sorry, as soon as I get an update I will be sure to update this.
Scott
Scott_at_Pax (BOB member since 2006-11-27)
The upgrade is doable …
I’ve upgraded 3 different scenario’s to Tomcat 6.0.2 so as to determine what issues we could face in our development and production environments:
A vanilla (clean) install
A server that had a previous XI 3.x and Tomcat 5.5
A server that had a previous XI r2 Tomcat 5, and XI 3.x and Tomcat 5.5.
There were a few issues - like the drop down box for the web/app server only listing Tomcat 5.5 but this is an internal XI logic set that is trying to determine the typical install path etc for that particular web/app type.
Note: make sure you use the manual deployment option and de-select Tomcat - then select Tomcat 5.5 for your web/app server type and then just set the install directory to your Tomcat 6.0.2 directory.
Tomcat 6.x is also not listed in the CCM - and if you had a previous installation on this server, it still lists the Tomcat 5.5 entry.
Set the Initial and Max heap settings.
I don’t think the Admin module for Tomcat has been released yet - and there is some debate as to whether there will be one.
I have CCM and Infoview working on a basic level and will be loading up the systems and doing some benchmarks over the next few days.
MikeD (BOB member since 2002-06-18)
Hey. We had the same IAVA issues.
The upgrade is really easy. You need BO 3.1 SP2 to be officially supported, though I was able to do the upgrade with 3.1 base install using some files from a SP2 install. Check out the
BusinessObjects Enterprise XI 3.1 SP2 Web Application Deployment Guide for Windows
Install 6.0.20. Modify config.tomcat6 (don’t use double quotes in the file names). Use wdeploy to copy the BO WAR files into the new Tomcat. Shutdown your existing Tomcat. Configure the new Tomcat ports as you need them. Startup. You can do most of the work and testing while the existing app is up if you want.
To get the service to show up in the CCM, there’s a post about doing this for R2. Basically, the new Tomcat service needs to have an internal service name of BOE120Tomcat. So, remove the existing BOE120Tomcat service, remove the Tomcat6 service just installed by the Tomcat installer. Install the Tomcat 6.0.20 service manually using the BOE120Tomcat service name. Make sure to set any necessary parameters.
The only major problem we had was using BO 3.1SP2, Tomcat 6.0.20 configured to use JDK 1.6.0_07. Everything deployed ok, but the AnalyticalRepoting app, and one other, didn’t start, so our WebIs didn’t work. Configuring Tomcat 6.0.20 to use JDK 1.5.0_20 fixed this issue.
Good luck!
bluewaterjp (BOB member since 2009-09-11)
All,
Just after my previous post, we got pulled to a new project (and then another), so I never got that attempt going. I was glad to see that SP2 supported 6.0.20, and I am glad to see that folks have successfully gotten the upgrade to work.
I am back online with this, only we’ll be deploying to Solaris (as of this minute… in 15 minutes, then they might say *nix or even “stay on windows”). I will be happy to get it up and running.
As before, our deployment is complicated because of other infrastructure requirements (OS on separate partition, APPS on separate partition, DB on separate partition, Web components – Tomcat – on separate partition, etc.).
One more thing, during my wdeploy attempts, I also went into the BOXI deployment directories and copied the Tomcat 5.5 config files and hacked them to reflect the 6.0.20 install… it didn’t work, but it was fun.
I am hoping to get started back on this shortly. As I had to hack and burn the install, I will be repeating all steps (re-install). Adding to the mix is a requirement for web services, so I’ll be reading up on that, too.
Never a dull moment! 
mvisconte (BOB member since 2008-01-17)
I’ve been happily (and not-so-…) tinkering on Tomcat and BOXI.
My solution was to mod the Tomcat configuration files
(config.tomcat60, tomcat60.xml)
in the (boxi_install)[i]\deployment[/i] directory,
make copies of the tc55 files in the (boxi_install)\deployment\templates directory
(tomcat60_context.xsl, tomcat60_context_undeploy.xsl)
… changing the installation (tomcat) directory, changing the as_service_name, etc. Basically, substituting “tomcat60” for “tomcat55” and adjusting file names as necessary.
I used tomcat60 vs tomcat6) for consistency and because I had already done a version w/ “6”.
I saw some mentions on the forums that the service name “should be”
BOE120Tomcat specifically. My installation was “Tomcat6”, and due to some configuration and running problems, I’m going through and changing any references into BOE120Tomcat JIK (Just In Case).
I am having the standard “I can’t get XYZ to deploy / run” and “OutOfMemory: PermGen space” java errors… still researching.
mvisconte (BOB member since 2008-01-17)
Update: Tomcat/Java errors fixed – Tinkering w/ the memory seemed to be the secret (er, fixing the settings I had, I think… durn typos).
Under Windows on a local development system, it seems to be pretty stable. I don’t know how my settings would work if it were anything other than a local tinkering box.
Now we’re on to new challenges… Solaris deployment. Woohoo.
-m.
mvisconte (BOB member since 2008-01-17)
I am doing the Solaris 10 install. I wish I had paid much more attention to the highlighted statements above.
I will second (or third) the statement. BOXI 3.1 SP2 is supported up through Java (JDK) 1.5.0_21. I have been pulling my hair out for a while fighting the exact same issue.
For the record, some steps we took:
Tomcat:
Set -Xmx and -Xms higher than the default (in our case to 2G)
-Xms2048M -Xmx2048M
Set PermGen space to higher than the default,
-XX:PermSize=64m -XX:MaxPermSize=256m
Set Tomcat to use Java 1.5.0_21. In our case, I added a line to “catalina.sh” to EXPLICITLY reference
JAVA_HOME={our JDK 1.5.0_21 directory}
Stopped all BOXI processes, stopped Tomcat, clear out the deployed TC webapps directories and the TC work directory. Started BOXI and TC. Redeployed all BOXI wars (auto-deploy on TC startup). Also, noticed that my out-of-the-box(i) servers set up had everything except for CMS disabled (but running). Stopped disabled servers, manually configured to enable servers for products we have/need. Restarted servers.
Seems to work now.
I noticed that even after the CMC servers adjustment, I still have 36 BOXI-specific processes running.
mvisconte (BOB member since 2008-01-17)
Maybe this is the same thing, but this is what I did:
Copied all XML files from Tomcat 55:
C:\Program Files\Business Objects\Tomcat55\conf\Catalina\localhost*.xml
To Tomcat 6.0 new directory:
C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\Catalina\localhost
Opened Tomcat 6 parameters, Java tab, added java options:
-Dcatalina.home=C:\Program Files\Apache Software Foundation\Tomcat 6.0
-Dcatalina.base=C:\Program Files\Apache Software Foundation\Tomcat 6.0
-Djava.endorsed.dirs=C:\Program Files\Apache Software Foundation\Tomcat 6.0\endorsed
-Djava.io.tmpdir=C:\Program Files\Apache Software Foundation\Tomcat 6.0\temp
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.util.logging.config.file=C:\Program Files\Apache Software Foundation\Tomcat 6.0\conf\logging.properties
-Xrs
-XX:MaxPermSize=256M
-Dbusinessobjects.olap.bin=
-Dbusinessobjects.olap.stylesheets=C:/Program Files/Business Objects/OLAP Intelligence 12.0/stylesheets/
-Djava.awt.headless=true
-Daf.configdir=C:/Program Files/Business Objects/Dashboard and Analytics 12.0
Lastly made the service for Tomcat 55 start manually and tomcat 6 to start automatically. REbooted the box and everything worked.
Gabe
gorthous 
(BOB member since 2004-11-10)