Whoops, for got that one,
thanks for adding it.
Lists wrote:
> I think that there is a further step required to make this work. The perl
> scripts that handle the tomcat config at startup build /conf/server.xml
> dynamically from server.xml.master. The path to tomcat is hard coded in this
> file:
>
> <ContextManager debug="0" workDir="work" showDebugInfo="true"
> home="/usr/java/jakarta-tomcat-3.2.1/" >
>
> Needs to be changed to jakarta-tomcat-3.2.3. Don't see why you couldn't use
> /usr/java/jakarta-tomcat which would make it easier to switch versions.
>
> regards,
> Peter Vines
> www.callido.com
>
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]]On Behalf Of O-S Inc.
>> Support
>> Sent: Thursday, August 23, 2001 10:56 PM
>> To: Cobalt Developers Group
>> Subject: [cobalt-developers] Upgrading Jakarta-Tomcat
>>
>>
>> To anyone interested,
>> We recently upgraded the Jakarta-Tomcat that comes with the
>> Java_Dev_Kit_Doc_v1.3, version 3.2.1 to 3.2.3. So far so good. At the
>> moment we are still using the cobalt perl scripts that came with the kit.
>>
>> So with that said, all we had to do was untar the new
>> Jakarta-Tomcat in
>> the dir that the current version was in. If you have not tweaked out
>> the install this will be the /usr/java dir. You will notice a symbolic
>> link that point jakarta-tomcat to jakarta-tomcat-3.2.1. To begin with
>> change that symbolic link to point to the new Jakarta-Tomcat dir which
>> should be jakarta-tomcat-3.2.3.
>>
>> Then I completely removed the conf dir in the new install,
>> as well as
>> deleting all default wepapps in the webapps dir. If you have backed up
>> the original install, then move the original conf dir to the new dir.
>>
>> So move jakarta-tomcat-3.2.1/conf to jakarta-tomcat.3.2.3/
>>
>> Replacing the deleted folder. Then grab the two perl scripts located in
>> the jakarta-tomcat-3.2.1/bin dir and move them to the new bin dir
>> jakarta-tomcat-3.2.3/bin.
>>
>> That should do it, and you should be able to start and run
>> jakarta-tomcat-3.2.3 from there. If everything works then you can toss
>> the old version, but you may want to keep the backup if any.
>>
>> If you do not make a backup and you simply copy the
>> jakarta-tomcat-3.2.1/conf to jakarta-tomcat.3.2.3/conf then you will
>> need to make sure all files have the proper permissions, based on the
>> original. You will have to look inside the old conf dir, and make sure
>> each file in the new conf dir, has the same permissions.
>>
>> Other than that you should be all set.
>>
>> Good luck.
>>
>>
>> --
>> Sincerely,
>> William L. Thomson Jr.
>> Support Group
>> Obsidian-Studios Inc.
>> 439 Amber Way
>> Petaluma, Ca. 94952
>> Phone/fax 707.766.9509
>> http://www.obsidian-studios.com
>>
>> _______________________________________________
>> cobalt-developers mailing list
>> [EMAIL PROTECTED]
>> http://list.cobalt.com/mailman/listinfo/cobalt-developers
>
>
> _______________________________________________
> cobalt-developers mailing list
> [EMAIL PROTECTED]
> http://list.cobalt.com/mailman/listinfo/cobalt-developers
--
Sincerely,
William L. Thomson Jr.
Obsidian-Studios Inc.
439 Amber Way
Petaluma, Ca. 94952
Phone/fax 707.766.9509
http://www.obsidian-studios.com
_______________________________________________
cobalt-developers mailing list
[EMAIL PROTECTED]
http://list.cobalt.com/mailman/listinfo/cobalt-developers
