Updating Tomcat to 6.x after install

server administration XI Server Discussion
1

Greetings one and all!

My client had me install XI 3.1 and after completing the install their security team told them they HAD to use Tomcat 6 instead of Tomcat 5 due to vulnerabilities in 5.

I tried removing the Web Tier in Add/Remove Programs and then reinstalling it, but since 5.5 was not removed by the removal of the Web Tier (although it was unselected in that process, thanks BO), when I told it to reinstall the Web Tier it simply asked me what WAS I was installing to, and then installed back onto the 5.5 without asking what install of Tomcat to install into.

I am reading through the Web Application guide and it seems to me that the only way to move them to the newer Tomcat is to use wdeploy. Is this correct?

Any suggestions regarding how to do this?

A follow-on to that would be this, if we use wdeploy to push it to the newer Tomcat, will that have to be how the patches are applied as well?

aroche :us: (BOB member since 2006-06-06)

2

You will need to install Tomcat 6 yourself and deploy the war files as needed. wdeploy is one option or you can do them manually. What you are doing is pretty much the same as if you wanted to deploy to WebLogic or Websphere which are not part of the Bus Obj install.

As far as updating in the future…
I know the install has gotten smarter in the 3.x releases so it may allow you to point the install to your Tomcat 6 install and update the wars. If not, then you will need to use wdeploy or do it manually.

jwhite9 :us: (BOB member since 2006-07-28)

3

Thanks.

The 3.x install still talks about Tomcat 5.5 during the install, and you select 5.5 to install to 6 if it is there before you do the BOE install.

Since this was a case where the we installed befoire security said anything I had to get creative.

I went back and did a series of Google searches of the forums here and finally found a reference to this thread:

Basically, I just had to install Tomcat 6.x, copy the Catalina\localhost directory contents and the webapps directory contents from 5.5.

After that I stopped 5.5 and disabled it; started Tomcat 6.x and set it to automatic.

Onve I verified it was working I went back in and removed Tomcat from the Web Tier selections.

aroche :us: (BOB member since 2006-06-06)

4

Tomcat 6 startup is sluggish - suggest you get rid of everything not required … :yesnod:

MikeD :south_africa: (BOB member since 2002-06-18)

5

This article may be of some help, it talks about replacing 32bit Tomcat 5.5 with 64 bit Tomcat 6

http://wiki.sdn.sap.com/wiki/display/BOBJ/Quick+and+easy+tomcat+64+bits+configuration+with+BOE+XI3.1+on+Windows+64+Bits

HTH
Hayden

Hayden_Gill :australia: (BOB member since 2002-08-15)

6

Here are my java options for Tomcat 6, any feedback?

-Djava.library.path=C:/Windows/system32/;C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/win32_x86/
-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
-Dbobj.enterprise.home=C:/Program Files/Business Objects/BusinessObjects Enterprise 12.0/
-Xrs
-Xmx1024m
-Xms256m
-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
-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

gorthous :chile: (BOB member since 2004-11-10)

7

Hi All

We’re in the same postion - we have to fill some security holes before we’re allowed to open the ports up to the internet…

We’ve got BOXI 3.1, and I’ve installed tomcat 6.0.26 and it’s listening fine on the new port.
The machine is 64 bit, and so the Tomcat installation is 64 bit, and using a 64 bit JVM.

I have to have both the vanilla BO and the bespoke instances of tomcat running at the same time for a short while, and so I’ve allocated port 8081 for the new instance, and managed to get it started by changing the shutdown port from the default 8005 as well.

I can get the login screen up, and log in to the InfoView home page. However, I can’t get the directory listings to display.

I’ve copied over the webapps directory, and also the catalina\localhost directory, as described above.

I’ve even repeated the above using 5.5.29 and still get the same problem (this time on port 8082)

Any thoughts gratefully received…

Cheers

Ben

BenKentzer (BOB member since 2010-06-07)

8

Stop Tomcat, delete the work directory and restart tomcat. If this does not work then you need to redeploy the app.

gorthous :chile: (BOB member since 2004-11-10)