Re: Moving tomcat logs to a location readable by developers
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Eric, On 6/1/15 9:16 AM, Eric Wood wrote: I want to be able to move tomcat log file to a location readable by developers so they do not have to log into the server and read them from there. I'm looking for recommended best practices. What processes are others using for this purpose? logrotate can execute scripts (e.g. scp-to-another-location) if you want . Or, you could modify your logging configuration to use some kind of remote logging, such as syslog-style logging to a single logging server. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v2 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJVbF3wAAoJEBzwKT+lPKRY99EP/0rmlO/qMyz52ZqH5GDpSqOJ LidR4/PgyXvG6h84/ACaeIO+Lsj5KjINRFp5Gj+E62v7qs47XsKQqt2M6sgt10rt oI/wPn+qR2bY8zCnSITx2ldoba0nzatlXSPZ3HGN7rGY1rlJlET3XH00kBXnkIyY 6oQmlRvxszwNoVEywKMMgqTSzk1cJNvXpbv3uMsu1B+uZpSn+SK4w4WXZUDBnEfd PC0RE4XkqJ01tb/pPJ6uuuZX54F8ZK0Q4L2J8G+xokWaOp7jV/nNfZ0OAeg4fDdZ k/Vlhat8mUr3TDe6tVuh2XHdaKysvxSwzyEBf/oR0XkpHOAyEQOYiKj9eRlcweP8 1NfS9OkLT94GqPGMUy8R7fPDaVP8YQ8uAuEsS1zJJqALTsClNVsV3ERIrNwxrUoL aWoEAGS3D8OstEyPn5yVUJCF4RmaNyR3+XcbGnMF//o4m3K7LIOFqWvDfz8be5Tt 5CmJxzn8wCKHiQtRdCoSette6i+gJX5DRhxzm8GMZTC8fUjuUZBor5nsqaWCCY3w 3y2M+6+UIv0KY9rno9Bd/EcMUa2HPrvQO5v5EBrMF4yPAMb6bphH2iN4V/Ld28Ws Qpn4xmmaN6BEkkoGLVRSxzAmial5bVGLvrH7GwzVuHchOoWajQDOoPqPpU70Fhyp /o6ux7tIRwTL7ERxIJHj =6Y6v -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Moving tomcat Ver 6.0
From: Nick Wall [mailto:nick.w...@mvtcanada.com] Subject: RE: Moving tomcat Ver 6.0 You mention - Install the java sdk, set the %JAVA_HOME% system environment variable? Which SDK should I use ? and from where from? I downloaded the latest SDK from the oracle site jave_ee_sdk-7u1 is this the correct one ? No, for several reasons: 1) You don't need an SDK or JDK; a JRE is all that's necessary to run Tomcat. 2) You definitely don't want the EE version (an SDK), since that comes with a lot of junk that can conflict with Tomcat classes if you're not careful. 3) Java 7 will only be available until April, so you're looking at a dead end there. Undo whatever you did, and go here to get a more appropriate JVM: http://java.com/en/download/manual.jsp You normally do not need to set JAVA_HOME or JRE_HOME, as long as the JVM is properly installed and not just copied into a directory somewhere. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Moving tomcat Ver 6.0
Hi All New year so happy new year and im back at the install Thanks Leo for your step by step You mention - Install the java sdk, set the %JAVA_HOME% system environment variable? Which SDK should I use ? and from where from? I downloaded the latest SDK from the oracle site “jave_ee_sdk-7u1” is this the correct one ? Cheers for now – Nick -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 1:31 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 2:53 PM, Nick Wall nick.w...@mvtcanada.com wrote: -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] I kinda wonder though if there is a windows service associated with this Tomcat. Do you see anything called Tomcat6 in the windows services panel? Leo Yes I just checked and there is a service running called Apache Tomcat As you can tell I have no clue to this installation :) Nick Generic steps: First step would be to decide whether you want to deploy a 32bit or 64bit version of Tomcat. 1. Download the latest Tomcat (32bit or 64bit, your decision) 1.b Determine whether you want to download the zip or windows installer version of that architecture. In your case, probably the later. 2. Download the latest java sdk (same architecture as you picked above). 3. Install the java sdk, set the %JAVA_HOME% system environment variable. if you need help, ask. 4. Install Tomcat using the windows service installer. If you used a specific windows user account to run the previous service, make sure you set that in in the service properties. 5. In your previous Tomcat installation, you need to take note of all of the settings and apply them to your new install. This is the hard part. You will want to compare the following files in the old and new installs: tomcat-install-directory/conf: context.xml server.xml tomcat-users.xml web.xml tomcat-install-directory/bin run tomcat6w.exe you are looking for any custom settings for memory and other options... (trying to recall the exact names of the tabs at the moment, where I am now we block Tomcat because we use a different web server, can't even install it here.. sorry list) 6. Copy your webapps from the Tomcat6 webapps dir to Tomcat8 web apps dir. I would also investigate any custom settings to the webapps/manager/META-INF/context.xml in the previous Tomcat6. You don't know if there was a custom valve or something applied in there other than the default. 6.b (Optional) Get rid of the docs and examples directories in your new Tomcat, or move them somewhere else if you want to keep them. 7. Make sure you copy the old ROOT web app directory to the new Tomcat. 8. Hard to say, but you might also have had custom jar files in the previous tomcat6-install-directory/lib Only way to know is to compare what was in there. This sucks that you have no documentation on the previous install, makes your life a little harder. I'm sure others will chime in with things I have forgotten. leo
Re: Moving tomcat Ver 6.0
On Wed, Nov 5, 2014 at 1:48 PM, Nick Wall nick.w...@mvtcanada.com wrote: Hi All Sorry new user to this We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. Or if you are familiar with this and can assist setting up and moving could look at that possibility as well Nick Wall AScT IT Manager nick.w...@mvtcanada.com You might as well consider getting the latest version of Tomcat while you're at it, and then moving your webapps to that new installation. You will want to check the customizations (if you made any) in web.xml, server.xml, tomcat-users.xml and anything under conf/Catalina/localhost that you placed there intentionally in the 2003 Tomcat installation. Don't forget to use the same service account, if you created one. You will also want to check the 2003 tomcat7w.exe for any custom options you used there, like memory settings, etc. leo
RE: Moving tomcat Ver 6.0
-Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 12:32 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 1:48 PM, Nick Wall nick.w...@mvtcanada.com wrote: Hi All Sorry new user to this We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. Or if you are familiar with this and can assist setting up and moving could look at that possibility as well Nick Wall AScT IT Manager nick.w...@mvtcanada.com You might as well consider getting the latest version of Tomcat while you're at it, and then moving your webapps to that new installation. You will want to check the customizations (if you made any) in web.xml, server.xml, tomcat-users.xml and anything under conf/Catalina/localhost that you placed there intentionally in the 2003 Tomcat installation. Don't forget to use the same service account, if you created one. You will also want to check the 2003 tomcat7w.exe for any custom options you used there, like memory settings, etc. Leo HI Leo Thanks for the reply and info :) Can I just copy the folder/files you mention and put in the new installation on the 2008 server ? As for a service account I have no idea if one exists as this was installed about 5 yrs ago and no one is left in the company that knows anything about it - Hence why I'm on this :) lol Nick
Re: Moving tomcat Ver 6.0
On Wed, Nov 5, 2014 at 2:36 PM, Nick Wall nick.w...@mvtcanada.com wrote: -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 12:32 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 1:48 PM, Nick Wall nick.w...@mvtcanada.com wrote: Hi All Sorry new user to this We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. Or if you are familiar with this and can assist setting up and moving could look at that possibility as well Nick Wall AScT IT Manager nick.w...@mvtcanada.com You might as well consider getting the latest version of Tomcat while you're at it, and then moving your webapps to that new installation. You will want to check the customizations (if you made any) in web.xml, server.xml, tomcat-users.xml and anything under conf/Catalina/localhost that you placed there intentionally in the 2003 Tomcat installation. Don't forget to use the same service account, if you created one. You will also want to check the 2003 tomcat7w.exe for any custom options you used there, like memory settings, etc. Leo HI Leo Thanks for the reply and info :) Can I just copy the folder/files you mention and put in the new installation on the 2008 server ? If the installation was done using the Tomcat zip version and it is not running as a windows service, yes, you should be able to do that. Don't put all your eggs in this basket for the moment, you need more info. As for a service account I have no idea if one exists as this was installed about 5 yrs ago and no one is left in the company that knows anything about it - Hence why I'm on this :) lol Nick I kinda wonder though if there is a windows service associated with this Tomcat. Do you see anything called Tomcat6 in the windows services panel?
RE: Moving tomcat Ver 6.0
-Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 12:47 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 2:36 PM, Nick Wall nick.w...@mvtcanada.com wrote: -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 12:32 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 1:48 PM, Nick Wall nick.w...@mvtcanada.com wrote: Hi All Sorry new user to this We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. Or if you are familiar with this and can assist setting up and moving could look at that possibility as well Nick Wall AScT IT Manager nick.w...@mvtcanada.com You might as well consider getting the latest version of Tomcat while you're at it, and then moving your webapps to that new installation. You will want to check the customizations (if you made any) in web.xml, server.xml, tomcat-users.xml and anything under conf/Catalina/localhost that you placed there intentionally in the 2003 Tomcat installation. Don't forget to use the same service account, if you created one. You will also want to check the 2003 tomcat7w.exe for any custom options you used there, like memory settings, etc. Leo HI Leo Thanks for the reply and info :) Can I just copy the folder/files you mention and put in the new installation on the 2008 server ? If the installation was done using the Tomcat zip version and it is not running as a windows service, yes, you should be able to do that. Don't put all your eggs in this basket for the moment, you need more info. As for a service account I have no idea if one exists as this was installed about 5 yrs ago and no one is left in the company that knows anything about it - Hence why I'm on this :) lol Nick I kinda wonder though if there is a windows service associated with this Tomcat. Do you see anything called Tomcat6 in the windows services panel? Leo Yes I just checked and there is a service running called Apache Tomcat As you can tell I have no clue to this installation :) Nick
Re: Moving tomcat Ver 6.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nick, On 11/5/14 2:48 PM, Nick Wall wrote: We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. It depends upon how you have everything set up. If you have a mostly default configuration and all your web applications are deployed into Tomcat's webapps/ directory, then you should be able to just copy the whole Tomcat directory from one machine to another. There are a few caveats: 1. If you are switching architectures (e.g. 32-bit to 64-bit, IA64 to x86_64, etc.) and you are using the tcnative library, then you'll have to make sure you place the library that matches your destination architecture into the right place (usually Tomcat's bin/ directory). 2. If you are running Tomcat as a Windows Service, then you'll have to re-register the service on the target machine once you've moved the files over. You can get a lot of mileage out of running the following on the command-line of the destination server: C:\ SET CATALINA_HOME=C:\Path\To\Tomcat C:\ SET CATALINA_BASE=C:\Path\To\Tomcat C:\ %CATALINA_HOME%\bin\service.bat install You might want to run CATALINA_HOME\bin\tomcat6w.exe on the old machine and make sure all your settings are copied-over to the new one. 3. You may have net networking components of services on the destination machine, so make sure you don't have any port conflicts. The easiest way to check for this is to start Tomcat and look at the catalina.out log file in Tomcat's logs/ directory. If it doesn't say anything about not being able to bind to a port, then you should be okay. Or if you are familiar with this and can assist setting up and moving could look at that possibility as well You can contact folks off-list if they invite you to do so. I'm not a great resource for Windows deployments, but I'll happily take your money and help you out ;) - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAEBCAAGBQJUWo7CAAoJEBzwKT+lPKRYZsMP/jIK+bNJpQ+YFMXXxBkXQloc JZonapaGyQhMx9sfYph/vjMwYhfEIAHktbyHqL962hpzSOfDf5bP11HX5UuJY66V PswNQNXhnyZbPHFVvItjBLv18+UwBClGxzgjjrcQXuzInLmyPdine6gzLxrWmPRL N00qCrKgWQh0bXT3C61xnmMTtj40aRGehZKwH1MiuMHTrnr0Ass5feqzMwO4JEgy u/BKzm8qcg36OCR8dvZ4XSl6TeDcDGakQWai25SXZUnNix/dmfBiMdsLXEBdAsCY LZyyqKj0d1G3iVBqqw1E+4qdKtCv5dXgBNz6qkQFpV9Z2isNGNvSezxympvX8VxD WV8CeYpuSJ5nOW2ukWjpuq+tJw3RF7HvR1uqJpkyQSJ85smc16Vri8H2PudjZN3/ hMyLlTWwEBOotFB4nHaJfSVQ0PfwuZxngk4PWjhi7mhOkSIsKX9FoghtJ/zWJCjR 5X5s2BwaytE9zxlsiyhM/C9cMdW2bxeQ5wbb5ROCrE97V1yvNZRyOvfd4UCE+POd Ora6NHbyh07rQJDmin7nBcYVTtLU9wtEfEvnMJH4/63zWN5xjzmlK0by9eBn9vbE Climj9nyVNquC1rj12bP6bZi57QXrRUUyyc/RPd3WKY/9z45Z94xAtu/Vn/d/4EN FFg8R/OQcTXO3kPQMjJw =22/F -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Moving tomcat Ver 6.0
From: Nick Wall [mailto:nick.w...@mvtcanada.com] Subject: RE: Moving tomcat Ver 6.0 Can I just copy the folder/files you mention and put in the new installation on the 2008 server ? Never, never, never copy configuration files from one version of Tomcat to another. The properties change drastically between levels, as do some of the defaults. You need to examine each .xml file in your current installation, read the documentation for that level and the new level, and then create the appropriate equivalent for the new one. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Moving tomcat Ver 6.0
Nick, On Wed, Nov 5, 2014 at 2:55 PM, Christopher Schultz ch...@christopherschultz.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Nick, On 11/5/14 2:48 PM, Nick Wall wrote: We have a Win server 2003 running Tomcat and our software I need to move this to a new win 2008 R2 server Is there an easy way to move everything over etc. Looking at easiest way to move everything over. It depends upon how you have everything set up. If you have a mostly default configuration and all your web applications are deployed into Tomcat's webapps/ directory, then you should be able to just copy the whole Tomcat directory from one machine to another. There are a few caveats: 1. If you are switching architectures (e.g. 32-bit to 64-bit, IA64 to x86_64, etc.) and you are using the tcnative library, then you'll have to make sure you place the library that matches your destination architecture into the right place (usually Tomcat's bin/ directory). 2. If you are running Tomcat as a Windows Service, then you'll have to re-register the service on the target machine once you've moved the files over. You can get a lot of mileage out of running the following on the command-line of the destination server: C:\ SET CATALINA_HOME=C:\Path\To\Tomcat C:\ SET CATALINA_BASE=C:\Path\To\Tomcat C:\ %CATALINA_HOME%\bin\service.bat install You might want to run CATALINA_HOME\bin\tomcat6w.exe on the old machine and make sure all your settings are copied-over to the new one. Yes. I think I told you to check tomcat7w.exe. Chris is correct, it would be tomcat6w.exe, since you are on version 6 something. 3. You may have net networking components of services on the destination machine, so make sure you don't have any port conflicts. The easiest way to check for this is to start Tomcat and look at the catalina.out log file in Tomcat's logs/ directory. If it doesn't say anything about not being able to bind to a port, then you should be okay. You can also run at the command prompt: netstat -ano to see what ports are being used and by what process.
Re: Moving tomcat Ver 6.0
On Wed, Nov 5, 2014 at 2:53 PM, Nick Wall nick.w...@mvtcanada.com wrote: -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] I kinda wonder though if there is a windows service associated with this Tomcat. Do you see anything called Tomcat6 in the windows services panel? Leo Yes I just checked and there is a service running called Apache Tomcat As you can tell I have no clue to this installation :) Nick Generic steps: First step would be to decide whether you want to deploy a 32bit or 64bit version of Tomcat. 1. Download the latest Tomcat (32bit or 64bit, your decision) 1.b Determine whether you want to download the zip or windows installer version of that architecture. In your case, probably the later. 2. Download the latest java sdk (same architecture as you picked above). 3. Install the java sdk, set the %JAVA_HOME% system environment variable. if you need help, ask. 4. Install Tomcat using the windows service installer. If you used a specific windows user account to run the previous service, make sure you set that in in the service properties. 5. In your previous Tomcat installation, you need to take note of all of the settings and apply them to your new install. This is the hard part. You will want to compare the following files in the old and new installs: tomcat-install-directory/conf: context.xml server.xml tomcat-users.xml web.xml tomcat-install-directory/bin run tomcat6w.exe you are looking for any custom settings for memory and other options... (trying to recall the exact names of the tabs at the moment, where I am now we block Tomcat because we use a different web server, can't even install it here.. sorry list) 6. Copy your webapps from the Tomcat6 webapps dir to Tomcat8 web apps dir. I would also investigate any custom settings to the webapps/manager/META-INF/context.xml in the previous Tomcat6. You don't know if there was a custom valve or something applied in there other than the default. 6.b (Optional) Get rid of the docs and examples directories in your new Tomcat, or move them somewhere else if you want to keep them. 7. Make sure you copy the old ROOT web app directory to the new Tomcat. 8. Hard to say, but you might also have had custom jar files in the previous tomcat6-install-directory/lib Only way to know is to compare what was in there. This sucks that you have no documentation on the previous install, makes your life a little harder. I'm sure others will chime in with things I have forgotten. leo
RE: Moving tomcat Ver 6.0
Thanks all so far I will take a look at this again tomorrow and see what I can figure out Nick -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] Sent: November-05-14 1:31 PM To: Tomcat Users List Subject: Re: Moving tomcat Ver 6.0 On Wed, Nov 5, 2014 at 2:53 PM, Nick Wall nick.w...@mvtcanada.com wrote: -Original Message- From: Leo Donahue [mailto:donahu...@gmail.com] I kinda wonder though if there is a windows service associated with this Tomcat. Do you see anything called Tomcat6 in the windows services panel? Leo Yes I just checked and there is a service running called Apache Tomcat As you can tell I have no clue to this installation :) Nick Generic steps: First step would be to decide whether you want to deploy a 32bit or 64bit version of Tomcat. 1. Download the latest Tomcat (32bit or 64bit, your decision) 1.b Determine whether you want to download the zip or windows installer version of that architecture. In your case, probably the later. 2. Download the latest java sdk (same architecture as you picked above). 3. Install the java sdk, set the %JAVA_HOME% system environment variable. if you need help, ask. 4. Install Tomcat using the windows service installer. If you used a specific windows user account to run the previous service, make sure you set that in in the service properties. 5. In your previous Tomcat installation, you need to take note of all of the settings and apply them to your new install. This is the hard part. You will want to compare the following files in the old and new installs: tomcat-install-directory/conf: context.xml server.xml tomcat-users.xml web.xml tomcat-install-directory/bin run tomcat6w.exe you are looking for any custom settings for memory and other options... (trying to recall the exact names of the tabs at the moment, where I am now we block Tomcat because we use a different web server, can't even install it here.. sorry list) 6. Copy your webapps from the Tomcat6 webapps dir to Tomcat8 web apps dir. I would also investigate any custom settings to the webapps/manager/META-INF/context.xml in the previous Tomcat6. You don't know if there was a custom valve or something applied in there other than the default. 6.b (Optional) Get rid of the docs and examples directories in your new Tomcat, or move them somewhere else if you want to keep them. 7. Make sure you copy the old ROOT web app directory to the new Tomcat. 8. Hard to say, but you might also have had custom jar files in the previous tomcat6-install-directory/lib Only way to know is to compare what was in there. This sucks that you have no documentation on the previous install, makes your life a little harder. I'm sure others will chime in with things I have forgotten. leo
Re: Moving Tomcat to work externally.
On 7/12/2013 10:52 AM, Terence M. Bandoian wrote: On 7/11/2013 6:46 PM, Mark Eggers wrote: Comments mostly inline. Lots at the end - channeling James Fenimore Cooper. On 7/11/2013 3:26 PM, Mark Eggers wrote: On 7/11/2013 3:06 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re: Moving Tomcat to work externally. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's what the ROOT webapp is for - it's the default webapp. If the application is packaged as a .war file, just copy it to webapps/ROOT.war, and delete the existing ROOT directory. That's a couple of hundred pages and several sub-directories just for the main application. Why is that relevant? And I have to move another half dozen applications to Tomcat as well. Define applications. From my quick reading of the railo documentation, you can different scenarios 1. one railo administrator and one application (site ?) per administrator 2. one railo administrator and multiple applications (sites ?) The first is easy to set up, but it will probably be memory-expensive. The second is more complex to set up, and once again the railo documentation really advocates some practices that not good practices. Never mind. Railo sets up each application in its own Host (at least from the examples). You could run multiple railo applications in one Host. You would just copy railo.war to appname.war and place it in your webapps directory. If your applications are organized properly, that is each in their own subdirectory under a common directory, with nothing but the webapps under the common directory, then just change the appBase attribute in the Host element to point there. Your default webapp must still be named ROOT (case sensitive). Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. You're definitely reading garbage somewhere. If that were the case, there would be no reason to have anything other than a standard web server, such as httpd. A .war file will normally contain a collection of servlets, JSPs, static pages, configuration files, and any other resources needed by the webapp. These are all in ColdFusion. This is almost exactly but not quite like JSF. It's more like PHP, or various tag libraries with JSP. In short, WAR files can happily serve dynamic content. Actually, the files get processed on the server and the resulting HTML gets sent to the client. How a .war file or webapp was created is also not relevant, once it exists. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? It looks like railo manages its own database connections. So if the railo infrastructure is there, the connections should work. I have no idea about Railo, but Mark E did a pretty good job of explaining how to make it work. Thanks. With the latest message (I'm writing a reply to it as well), there are some wrinkles. These are all due to the way railo is written. For multiple web applications using the same railo administrator, set up and configuration will get a bit messy (as in not best practices messy). What URL did you try to use? www.books-on-line.com It looks like the current site isn't running. That's not a complete URL, since you're missing the scheme (usually http). Assuming you are using http (not https), you'll be sending a request for the default webapp's welcome page to port 80 at whatever IP address the client machine evaluates www.books-on-line.com as. Verify that the client can resolve www.books-on-line.com into the IP address you expect. Since you have nothing after the domain name, you must have a ROOT webapp deployed in order to get a response. What port is specified in server.xml? 80 -- localhost:80 works, localhost:8080 doesn't. Ok, that's good. Is there a firewall blocking that port? There's a hole in the firewall to let page requests through to the on-line server. Register the DNS name for your server with your DNS providers. This site is about 17 years old with several million home page hits. I think it is registered. But it sounds like you're expecting requests to magically appear at the new server when the old one is still running. If that's not the case, you need to tell us how they're differentiated. - Chuck . . . . more later /mde/ There are several other fun issues involved. A. Railo applications expect a file system. Railo writes logs to a subdirectory within the application (by default). It writes configuration files to a subdirectory within the application (by default). You must run
Re: Moving Tomcat to work externally.
On 7/11/2013 6:46 PM, Mark Eggers wrote: Comments mostly inline. Lots at the end - channeling James Fenimore Cooper. On 7/11/2013 3:26 PM, Mark Eggers wrote: On 7/11/2013 3:06 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re: Moving Tomcat to work externally. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's what the ROOT webapp is for - it's the default webapp. If the application is packaged as a .war file, just copy it to webapps/ROOT.war, and delete the existing ROOT directory. That's a couple of hundred pages and several sub-directories just for the main application. Why is that relevant? And I have to move another half dozen applications to Tomcat as well. Define applications. From my quick reading of the railo documentation, you can different scenarios 1. one railo administrator and one application (site ?) per administrator 2. one railo administrator and multiple applications (sites ?) The first is easy to set up, but it will probably be memory-expensive. The second is more complex to set up, and once again the railo documentation really advocates some practices that not good practices. Never mind. Railo sets up each application in its own Host (at least from the examples). You could run multiple railo applications in one Host. You would just copy railo.war to appname.war and place it in your webapps directory. If your applications are organized properly, that is each in their own subdirectory under a common directory, with nothing but the webapps under the common directory, then just change the appBase attribute in the Host element to point there. Your default webapp must still be named ROOT (case sensitive). Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. You're definitely reading garbage somewhere. If that were the case, there would be no reason to have anything other than a standard web server, such as httpd. A .war file will normally contain a collection of servlets, JSPs, static pages, configuration files, and any other resources needed by the webapp. These are all in ColdFusion. This is almost exactly but not quite like JSF. It's more like PHP, or various tag libraries with JSP. In short, WAR files can happily serve dynamic content. Actually, the files get processed on the server and the resulting HTML gets sent to the client. How a .war file or webapp was created is also not relevant, once it exists. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? It looks like railo manages its own database connections. So if the railo infrastructure is there, the connections should work. I have no idea about Railo, but Mark E did a pretty good job of explaining how to make it work. Thanks. With the latest message (I'm writing a reply to it as well), there are some wrinkles. These are all due to the way railo is written. For multiple web applications using the same railo administrator, set up and configuration will get a bit messy (as in not best practices messy). What URL did you try to use? www.books-on-line.com It looks like the current site isn't running. That's not a complete URL, since you're missing the scheme (usually http). Assuming you are using http (not https), you'll be sending a request for the default webapp's welcome page to port 80 at whatever IP address the client machine evaluates www.books-on-line.com as. Verify that the client can resolve www.books-on-line.com into the IP address you expect. Since you have nothing after the domain name, you must have a ROOT webapp deployed in order to get a response. What port is specified in server.xml? 80 -- localhost:80 works, localhost:8080 doesn't. Ok, that's good. Is there a firewall blocking that port? There's a hole in the firewall to let page requests through to the on-line server. Register the DNS name for your server with your DNS providers. This site is about 17 years old with several million home page hits. I think it is registered. But it sounds like you're expecting requests to magically appear at the new server when the old one is still running. If that's not the case, you need to tell us how they're differentiated. - Chuck . . . . more later /mde/ There are several other fun issues involved. A. Railo applications expect a file system. Railo writes logs to a subdirectory within the application (by default). It writes configuration files to a subdirectory within the application (by default). You must run with unPackWARs set to true
Re: Moving Tomcat to work externally.
On Fri, Jul 12, 2013 at 11:52 AM, Terence M. Bandoian tere...@tmbsw.comwrote: Really generous responses. That's very normal on this list. I have found Apache user lists to be very (user) friendly. :)
Re: Moving Tomcat to work externally.
You say: Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's a couple of hundred pages and several sub-directories just for the main application. And I have to move another half dozen applications to Tomcat as well. Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. These are all in ColdFusion. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? You then ask: What URL did you try to use? -- www.books-on-line.com Where is the other machine located relative to the one Tomcat is running on? -- I'm in a room with the on-line server, the new server and a half dozen other machines. The on-line server is about six and a half inches from the new server. I used one of the other machines to browse to www.books-on-line.com. It was 8 or ten feet away. What port is specified in server.xml? -- 80 -- localhost:80 works, localhost:8080 doesn't. Is there a firewall blocking that port? -- There's a hole in the firewall to let page requests through to the on-line server. Be specific when reporting problems. -- I thought I had been. Register the DNS name for your server with your DNS providers. -- This site is about 17 years old with several million home page hits. I think it is registered. I asked and you answered: Did I do something stupid? -- Not terribly, other than not reading the real Tomcat doc before making changes. -- I've tried to read the real Tomcat doc without success. I've worked in a dozen or so languages, but the Java world is new to me and it uses a lot of jargon making trying to get anything out of it very difficult. On Wed, Jul 10, 2013 at 7:09 PM, Mark Eggers its_toas...@yahoo.com wrote: On 7/10/2013 6:08 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com**] Subject: Moving Tomcat to work externally. Following instructions found in various places I added the following to the server.xml file and restarted Tomcat: If you followed something that said to put a Context element in server.xml, you need to stop going to those places and read the real Tomcat doc. Sadly, the three documents I read concerning Railo and Tomcat all have this same exact syntax. The rest of the instructions concerning integrating Tomcat and Railo are pretty much on par with this. users@tomcat.apache.org The above has no business being anywhere in a config file. Host name=books-on-line.com appBase=webapps Context path' docBase=C:\inetpub\wwwroot\ / Aliaswww.books-on-line.org/**Alias Aliaswww.books-on-line.net/**Alias /Host Take out all of the above; none of it is needed or desirable. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Chrome, Firefox and even tried IE from another machine -- all say they can't connect. What URL did you try to use? Where is the other machine located relative to the one Tomcat is running on? What port is specified in server.xml? Is there a firewall blocking that port? Be specific when reporting problems. Tomcat version: Whatever comes with Railo 4 It comes with some (undefined) version of Tomcat 7. If you don't know what it is, remove it, and install a real one from tomcat.apache.org; otherwise, you're just shooting in the dark. Is there something else I'm supposed to do? Register the DNS name for your server with your DNS providers. Did I do something stupid? Not terribly, other than not reading the real Tomcat doc before making changes. - Chuck In the original author's defense, the railo documentation is . . . unpleasant. Here's what I did to get it running quickly: 1. Download a copy of Tomcat from tomcat.apache.org Grab the zip file and unpack it somewhere. Right now you don't need to run it as a service, nor do you need to even use the manager application. 2. Download the WAR file for railo I believe the current production version is 4.0.4. The WAR file will be named railo-4.0.4.001.war 3. Copy it as railo.war to the webapps directory You'll find that directory in apache-tomcat-7.0.42\webapps, wherever you've unpacked the zip file. 4. Double-click on startup.bat You'll find that in apache-tomcat-7.0.42\bin, wherever you've unpacked the zip file. 5. Browse to localhost:8080/railo and confirm that it works. 6. Remote machine access Now, either update DNS to point to your machine as books-on-line.com, or go and edit a remote machine's host file to have books-on-line.com with your IP address. Make sure
RE: Moving Tomcat to work externally.
From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re: Moving Tomcat to work externally. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's what the ROOT webapp is for - it's the default webapp. If the application is packaged as a .war file, just copy it to webapps/ROOT.war, and delete the existing ROOT directory. That's a couple of hundred pages and several sub-directories just for the main application. Why is that relevant? And I have to move another half dozen applications to Tomcat as well. If your applications are organized properly, that is each in their own subdirectory under a common directory, with nothing but the webapps under the common directory, then just change the appBase attribute in the Host element to point there. Your default webapp must still be named ROOT (case sensitive). Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. You're definitely reading garbage somewhere. If that were the case, there would be no reason to have anything other than a standard web server, such as httpd. A .war file will normally contain a collection of servlets, JSPs, static pages, configuration files, and any other resources needed by the webapp. These are all in ColdFusion. How a .war file or webapp was created is also not relevant, once it exists. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? I have no idea about Railo, but Mark E did a pretty good job of explaining how to make it work. What URL did you try to use? www.books-on-line.com That's not a complete URL, since you're missing the scheme (usually http). Assuming you are using http (not https), you'll be sending a request for the default webapp's welcome page to port 80 at whatever IP address the client machine evaluates www.books-on-line.com as. Verify that the client can resolve www.books-on-line.com into the IP address you expect. Since you have nothing after the domain name, you must have a ROOT webapp deployed in order to get a response. What port is specified in server.xml? 80 -- localhost:80 works, localhost:8080 doesn't. Ok, that's good. Is there a firewall blocking that port? There's a hole in the firewall to let page requests through to the on-line server. Register the DNS name for your server with your DNS providers. This site is about 17 years old with several million home page hits. I think it is registered. But it sounds like you're expecting requests to magically appear at the new server when the old one is still running. If that's not the case, you need to tell us how they're differentiated. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Moving Tomcat to work externally.
On 7/11/2013 3:06 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re: Moving Tomcat to work externally. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's what the ROOT webapp is for - it's the default webapp. If the application is packaged as a .war file, just copy it to webapps/ROOT.war, and delete the existing ROOT directory. That's a couple of hundred pages and several sub-directories just for the main application. Why is that relevant? And I have to move another half dozen applications to Tomcat as well. Define applications. From my quick reading of the railo documentation, you can different scenarios 1. one railo administrator and one application (site ?) per administrator 2. one railo administrator and multiple applications (sites ?) The first is easy to set up, but it will probably be memory-expensive. The second is more complex to set up, and once again the railo documentation really advocates some practices that not good practices. If your applications are organized properly, that is each in their own subdirectory under a common directory, with nothing but the webapps under the common directory, then just change the appBase attribute in the Host element to point there. Your default webapp must still be named ROOT (case sensitive). Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. You're definitely reading garbage somewhere. If that were the case, there would be no reason to have anything other than a standard web server, such as httpd. A .war file will normally contain a collection of servlets, JSPs, static pages, configuration files, and any other resources needed by the webapp. These are all in ColdFusion. How a .war file or webapp was created is also not relevant, once it exists. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? It looks like railo manages its own database connections. So if the railo infrastructure is there, the connections should work. I have no idea about Railo, but Mark E did a pretty good job of explaining how to make it work. Thanks. With the latest message (I'm writing a reply to it as well), there are some wrinkles. These are all due to the way railo is written. For multiple web applications using the same railo administrator, set up and configuration will get a bit messy (as in not best practices messy). What URL did you try to use? www.books-on-line.com It looks like the current site isn't running. That's not a complete URL, since you're missing the scheme (usually http). Assuming you are using http (not https), you'll be sending a request for the default webapp's welcome page to port 80 at whatever IP address the client machine evaluates www.books-on-line.com as. Verify that the client can resolve www.books-on-line.com into the IP address you expect. Since you have nothing after the domain name, you must have a ROOT webapp deployed in order to get a response. What port is specified in server.xml? 80 -- localhost:80 works, localhost:8080 doesn't. Ok, that's good. Is there a firewall blocking that port? There's a hole in the firewall to let page requests through to the on-line server. Register the DNS name for your server with your DNS providers. This site is about 17 years old with several million home page hits. I think it is registered. But it sounds like you're expecting requests to magically appear at the new server when the old one is still running. If that's not the case, you need to tell us how they're differentiated. - Chuck . . . . more later /mde/ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Moving Tomcat to work externally.
Comments mostly inline. Lots at the end - channeling James Fenimore Cooper. On 7/11/2013 3:26 PM, Mark Eggers wrote: On 7/11/2013 3:06 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Re: Moving Tomcat to work externally. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Do I understand that you are telling me to put the whole web application into the webapps/ROOT directory? That's what the ROOT webapp is for - it's the default webapp. If the application is packaged as a .war file, just copy it to webapps/ROOT.war, and delete the existing ROOT directory. That's a couple of hundred pages and several sub-directories just for the main application. Why is that relevant? And I have to move another half dozen applications to Tomcat as well. Define applications. From my quick reading of the railo documentation, you can different scenarios 1. one railo administrator and one application (site ?) per administrator 2. one railo administrator and multiple applications (sites ?) The first is easy to set up, but it will probably be memory-expensive. The second is more complex to set up, and once again the railo documentation really advocates some practices that not good practices. Never mind. Railo sets up each application in its own Host (at least from the examples). You could run multiple railo applications in one Host. You would just copy railo.war to appname.war and place it in your webapps directory. If your applications are organized properly, that is each in their own subdirectory under a common directory, with nothing but the webapps under the common directory, then just change the appBase attribute in the Host element to point there. Your default webapp must still be named ROOT (case sensitive). Further these are almost all dynamic pages, and I may be incorrect, but I've read that .war files can only contain static web pages. You're definitely reading garbage somewhere. If that were the case, there would be no reason to have anything other than a standard web server, such as httpd. A .war file will normally contain a collection of servlets, JSPs, static pages, configuration files, and any other resources needed by the webapp. These are all in ColdFusion. This is almost exactly but not quite like JSF. It's more like PHP, or various tag libraries with JSP. In short, WAR files can happily serve dynamic content. Actually, the files get processed on the server and the resulting HTML gets sent to the client. How a .war file or webapp was created is also not relevant, once it exists. Is my understanding incorrect, and somehow this can connect to Railo to handle the database interaction? It looks like railo manages its own database connections. So if the railo infrastructure is there, the connections should work. I have no idea about Railo, but Mark E did a pretty good job of explaining how to make it work. Thanks. With the latest message (I'm writing a reply to it as well), there are some wrinkles. These are all due to the way railo is written. For multiple web applications using the same railo administrator, set up and configuration will get a bit messy (as in not best practices messy). What URL did you try to use? www.books-on-line.com It looks like the current site isn't running. That's not a complete URL, since you're missing the scheme (usually http). Assuming you are using http (not https), you'll be sending a request for the default webapp's welcome page to port 80 at whatever IP address the client machine evaluates www.books-on-line.com as. Verify that the client can resolve www.books-on-line.com into the IP address you expect. Since you have nothing after the domain name, you must have a ROOT webapp deployed in order to get a response. What port is specified in server.xml? 80 -- localhost:80 works, localhost:8080 doesn't. Ok, that's good. Is there a firewall blocking that port? There's a hole in the firewall to let page requests through to the on-line server. Register the DNS name for your server with your DNS providers. This site is about 17 years old with several million home page hits. I think it is registered. But it sounds like you're expecting requests to magically appear at the new server when the old one is still running. If that's not the case, you need to tell us how they're differentiated. - Chuck . . . . more later /mde/ There are several other fun issues involved. A. Railo applications expect a file system. Railo writes logs to a subdirectory within the application (by default). It writes configuration files to a subdirectory within the application (by default). You must run with unPackWARs set to true (this is the default). B. Lots of JARs If you run multiple Railo applications on one server
RE: Moving Tomcat to work externally.
From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Moving Tomcat to work externally. Following instructions found in various places I added the following to the server.xml file and restarted Tomcat: If you followed something that said to put a Context element in server.xml, you need to stop going to those places and read the real Tomcat doc. users@tomcat.apache.org The above has no business being anywhere in a config file. Host name=books-on-line.com appBase=webapps Context path' docBase=C:\inetpub\wwwroot\ / Aliaswww.books-on-line.org/Alias Aliaswww.books-on-line.net/Alias /Host Take out all of the above; none of it is needed or desirable. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Chrome, Firefox and even tried IE from another machine -- all say they can't connect. What URL did you try to use? Where is the other machine located relative to the one Tomcat is running on? What port is specified in server.xml? Is there a firewall blocking that port? Be specific when reporting problems. Tomcat version: Whatever comes with Railo 4 If you don't know what it is, remove it, and install a real one from tomcat.apache.org; otherwise, you're just shooting in the dark. Is there something else I'm supposed to do? Register the DNS name for your server with your DNS providers. Did I do something stupid? Not terribly, other than not reading the real Tomcat doc before making changes. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Moving Tomcat to work externally.
On 7/10/2013 6:08 PM, Caldarale, Charles R wrote: From: john Matlock [mailto:johndmatl...@gmail.com] Subject: Moving Tomcat to work externally. Following instructions found in various places I added the following to the server.xml file and restarted Tomcat: If you followed something that said to put a Context element in server.xml, you need to stop going to those places and read the real Tomcat doc. Sadly, the three documents I read concerning Railo and Tomcat all have this same exact syntax. The rest of the instructions concerning integrating Tomcat and Railo are pretty much on par with this. users@tomcat.apache.org The above has no business being anywhere in a config file. Host name=books-on-line.com appBase=webapps Context path' docBase=C:\inetpub\wwwroot\ / Aliaswww.books-on-line.org/Alias Aliaswww.books-on-line.net/Alias /Host Take out all of the above; none of it is needed or desirable. Remove the ROOT directory from Tomcat's webapps directory, replacing it with your webapp renamed to ROOT.war (or, if it's already an expanded .war file, put it in the ROOT directory under webapps). Chrome, Firefox and even tried IE from another machine -- all say they can't connect. What URL did you try to use? Where is the other machine located relative to the one Tomcat is running on? What port is specified in server.xml? Is there a firewall blocking that port? Be specific when reporting problems. Tomcat version: Whatever comes with Railo 4 It comes with some (undefined) version of Tomcat 7. If you don't know what it is, remove it, and install a real one from tomcat.apache.org; otherwise, you're just shooting in the dark. Is there something else I'm supposed to do? Register the DNS name for your server with your DNS providers. Did I do something stupid? Not terribly, other than not reading the real Tomcat doc before making changes. - Chuck In the original author's defense, the railo documentation is . . . unpleasant. Here's what I did to get it running quickly: 1. Download a copy of Tomcat from tomcat.apache.org Grab the zip file and unpack it somewhere. Right now you don't need to run it as a service, nor do you need to even use the manager application. 2. Download the WAR file for railo I believe the current production version is 4.0.4. The WAR file will be named railo-4.0.4.001.war 3. Copy it as railo.war to the webapps directory You'll find that directory in apache-tomcat-7.0.42\webapps, wherever you've unpacked the zip file. 4. Double-click on startup.bat You'll find that in apache-tomcat-7.0.42\bin, wherever you've unpacked the zip file. 5. Browse to localhost:8080/railo and confirm that it works. 6. Remote machine access Now, either update DNS to point to your machine as books-on-line.com, or go and edit a remote machine's host file to have books-on-line.com with your IP address. Make sure your machine's firewall allows port 8080. Now browse to books-on-line.com:8080/railo and make sure you can connect. Now to make the Railo environment the default application: -- 1. Stop Tomcat Double-click on shutdown.bat found in apache-tomcat-7.0.42\bin, wherever you've unpacked the Tomcat zip file. 2. Back up Tomcat's original ROOT application It's found in apache-tomcat-7.0.42\webapps, wherever you've unpacked the Tomcat zip file. 3. Rename railo.war to ROOT.war Please note that case is important, even on Windows 4. Delete the railo directory that was created It's found in apache-tomcat-7.0.42\webapps, wherever you've unpacked the Tomcat zip file. 5. Start up Tomcat 6. Browse to localhost:8080/ You should see the railo application 7. From a remote machine, browse to books-on-line.com:8080 You should see the railo application Added Feature 1 - Run on Port 80 1. Stop Tomcat Double-click on shutdown.bat found in apache-tomcat-7.0.42\bin, wherever you've unpacked the Tomcat zip file. 2. Edit server.xml - changing port 8080 to port 80 The file is found in apache-tomcat-7.0.42\conf, wherever you've unpacked the Tomcat zip file You're looking for the following entry to change: Connector port=8080 protocol=HTTP/1.1 connectionTimeout=2 redirectPort=8443 / 3. Make sure port 80 is not being used This is usually means that IIS or Apache HTTPD is running. Stop them. You can open up a cmd.exe and type the following: netstat -ano This will list all of the ports, and the process ID accessing the ports. If there's 0.0.0.0:80 or [::]:80, find the process and stop it. 4. Start up Tomcat 5. Browse to localhost/ You should see the railo application 6. From a remote machine, browse to books-on-line.com You should see the railo application Added Feature 2 - Run as a service -- Repeat the above exercise, with the following exceptions. 1. Install the service
RE: Moving Tomcat
I want to thank everyone for the insightful information yesterday on my query about moving Tomcat. I have not moved anything at this time but I have made a copy onto CD of everything that resides on the /usr/local/src directory. This does include the jakarta-tomcat-5.5.9 directory and all of its content. Again, as far as I can determine everything associated with our website does reside in this directory. Martin, there is a lib and a classes directory in the /shared directory but there are no files in those directories. However, there are lib and classes directories with files in the /usr/local/src/jakarta-tomcat-5.5.9/common directory. I have read through the link you provided below. There are a few .jar files that reside in the folder that the howto article does not discuss. Here is a list of the .jar files in /usr/local/src/jakarta-tomcat-5.5.9/common/lib: Commons-el.jar Jasper-compiler.jar Jasper-compiler-jdt.jar Jasper-runtime.jar Jsp-api.jar Naming-factory.jar Naming-factory-dbcp.jar Naming-resources.jar Servlet-api.jar There is one file in /usr/local/src/jakarta-tomcat-5.5.9/common/classes/: Logging.properties Here are the files in /usr/local/src/jakarta-tomcat-5.5.9/server/lib/: Catalina.jar Catalina-ant.jar Catalina-cluster.jar Catalina-optional.jar Commons-modeler.jar Servlets-cgi.renametojar Servlets-default.jar Servlets-invoker.jar Servlets-ssi.renametojar Servlets-webdav.jar Tomcat-ajp.jar Tomcat-coyote.jar Tomcat-http.jar Tomcat-util.jar There are no files in the /usr/local/src/jakarta-tomcat-5.5.9/server/classes directory. I do not see a .war file in the /usr/local/src/jakarta-tomcat-5.5.9/webapps directory or any other directories. I do believe that all the web site content does reside in the webapps/online directory. There are several files and folders in the online directory. I have not seen anything that indicates the content resides anywhere else. If it is not obvious that there would be any files outside of the /usr/local/src directory except the JDK which I see resides at /usr/java/jdk1.5.0 can I then assume everything needed is going to be found in the /usr/local/src/ directory under the various appropriate directories? Other questions, could I download tomcat and java fresh onto the new server that I am moving the web site onto? If I download updated versions of these programs would the web site function normally if I just copy the content files from /webapps/online on the old server into the same directories on the new server? Or, would I have some additional configuring to do? Thanks, Steve I'm glad to hear that Steve! to recap-- Get same version JVM installed on new tomcat Get same version Tomcat installed (with manager and admin working) on new Tomcat copy over jars from $CATALINA_BASE/shared/lib/*.* copy over class files from $CATALINA_BASE/shared/classes/*.* if you see extra jars or class files located in either $CATALINA_HOME/common/lib or $CATALINA_HOME/common/classes read this http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html once you feel you grasp the implications of what jars should be located in the common folder then copy jars and classes only on a as-needed basis All of your webapps live in a self contained package called WebAppName.war (confirm by viewing folders located at $CATALINA_BASE/webapps and all war files located at $CATALINA_BASE/webapps/*.war) you should use the manager of the new server to open each war file and carefully note any error messages at top of manager screen If the top of the manager screen displays errors then view the tail end of the log file located at $CATALINA_BASE/logs/HostName.-MM-DD.log As always we are here to help HTH M- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: EDMOND KEMOKAI [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, January 03, 2007 1:52 PM Subject: Re: Moving Tomcat If you have the second server setup then you can install tomcat and copy the webapps folder over and see what happens. Once you start
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat Here is a list of the .jar files in /usr/local/src/jakarta-tomcat-5.5.9/common/lib: The noted jars are all part of the standard Tomcat distribution. There is one file in /usr/local/src/jakarta-tomcat-5.5.9/common/classes/: Logging.properties The above is not part of the standard distribution (at least not the current one). It would be there to define a standard logging configuration for all of your webapps. You will need it in the new server installation. Here are the files in /usr/local/src/jakarta-tomcat-5.5.9/server/lib/: Again, these are all part of the standard distribution. There are no files in the /usr/local/src/jakarta-tomcat-5.5.9/server/classes directory. That's normal. That directory is typically used only to override a class in a server/lib jar with a patched version. can I then assume everything needed is going to be found in the /usr/local/src/ directory under the various appropriate directories? Assumptions are always suspect, but in this case the app environment seems to be relatively straightforward, so that's probably safe. Other questions, could I download tomcat and java fresh onto the new server that I am moving the web site onto? I would, but it does open up the potential for introducing incompatibilities that you may not have the experience to deal with handily. You could try it, test everything you can, and fall back to the older Tomcat and JRE versions if something breaks and it's not readily fixable. If I download updated versions of these programs would the web site function normally if I just copy the content files from /webapps/online on the old server into the same directories on the new server? Or, would I have some additional configuring to do? You would need to compare all the .xml files in the conf directory tree to look for differences and apply them when appropriate. Tomcat comes in a rather development-oriented configuration, and several properties should be changed in a production environment. This may or may not have been done on the current server. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
Thanks Chuck for the info. I appreciate your and everyone else's replies. I will be continuing on with resolving this problem and may have some other questions but you guys have answered a lot for me already. Thanks, Steve -- From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat Here is a list of the .jar files in /usr/local/src/jakarta-tomcat-5.5.9/common/lib: The noted jars are all part of the standard Tomcat distribution. There is one file in /usr/local/src/jakarta-tomcat-5.5.9/common/classes/: Logging.properties The above is not part of the standard distribution (at least not the current one). It would be there to define a standard logging configuration for all of your webapps. You will need it in the new server installation. Here are the files in /usr/local/src/jakarta-tomcat-5.5.9/server/lib/: Again, these are all part of the standard distribution. There are no files in the /usr/local/src/jakarta-tomcat-5.5.9/server/classes directory. That's normal. That directory is typically used only to override a class in a server/lib jar with a patched version. can I then assume everything needed is going to be found in the /usr/local/src/ directory under the various appropriate directories? Assumptions are always suspect, but in this case the app environment seems to be relatively straightforward, so that's probably safe. Other questions, could I download tomcat and java fresh onto the new server that I am moving the web site onto? I would, but it does open up the potential for introducing incompatibilities that you may not have the experience to deal with handily. You could try it, test everything you can, and fall back to the older Tomcat and JRE versions if something breaks and it's not readily fixable. If I download updated versions of these programs would the web site function normally if I just copy the content files from /webapps/online on the old server into the same directories on the new server? Or, would I have some additional configuring to do? You would need to compare all the .xml files in the conf directory tree to look for differences and apply them when appropriate. Tomcat comes in a rather development-oriented configuration, and several properties should be changed in a production environment. This may or may not have been done on the current server. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
you can also install Tomcat from the .tar.gz (on apache's website), that creates a location independent layout for you Filip Steve Ingraham wrote: I have a website running with jakarta-tomcat-5.5.9. The server this website resides on is going to have to be rebuilt so I am needing to move everything off of it onto another server. I know very little about tomcat, ok, I really know nothing about tomcat. This website was created before I started managing this network so I was not involved in its construction. My question is this. I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. If I copy everything from /usr/local/src from the old server onto the new server will this capture everything needed for the website? Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? Any information would be appreciated. Steve No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.16.3/614 - Release Date: 1/2/2007 2:58 PM - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
Steve Ingraham wrote: I have a website running with jakarta-tomcat-5.5.9. The server this website resides on is going to have to be rebuilt so I am needing to move everything off of it onto another server. I know very little about tomcat, ok, I really know nothing about tomcat. This website was created before I started managing this network so I was not involved in its construction. My question is this. I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. If I copy everything from /usr/local/src from the old server onto the new server will this capture everything needed for the website? Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? Do not forget about JRE/JDK. Are you sure your webapps does not access any files outside /usr/local/src/jakarta-tomcat-5.5.9 ? -- Mikolaj Rydzewski [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: Moving Tomcat
First I'll suggest you backup your entire server, it is possible for instance if your server is running Linux that the webapps folder only contain the links to the actual webapp folders residing somewhere else on the filesystem..So again BACKUP before doing anything. About a month ago someone on this mailing list in your position deleted stuff on a server they were managing, I have the feeling they don't have a job anymore. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: I have a website running with jakarta-tomcat-5.5.9. The server this website resides on is going to have to be rebuilt so I am needing to move everything off of it onto another server. I know very little about tomcat, ok, I really know nothing about tomcat. This website was created before I started managing this network so I was not involved in its construction. My question is this. I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. If I copy everything from /usr/local/src from the old server onto the new server will this capture everything needed for the website? Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? Any information would be appreciated. Steve -- talk trash and carry a small stick. PAUL KRUGMAN (NYT)
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: Moving Tomcat I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. That's where they are by default. However, apps can be deployed outside of the Tomcat directory tree by placing [appName].xml files in conf/[engine]/[host] (usually conf/Catalina/localhost, although you may have more than one host defined in conf/server.xml). Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? DNS entries may need to be changed to point to the new box, of course. If you have multiple Host entries defined in your conf/server.xml, you may need to examine them for changed IP addresses. The same applies to any filters or valves you have configured. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
Hmm Interesting, the person was from Oklahoma Court, is that you again? On 1/3/07, EDMOND KEMOKAI [EMAIL PROTECTED] wrote: First I'll suggest you backup your entire server, it is possible for instance if your server is running Linux that the webapps folder only contain the links to the actual webapp folders residing somewhere else on the filesystem..So again BACKUP before doing anything. About a month ago someone on this mailing list in your position deleted stuff on a server they were managing, I have the feeling they don't have a job anymore. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: I have a website running with jakarta-tomcat-5.5.9. The server this website resides on is going to have to be rebuilt so I am needing to move everything off of it onto another server. I know very little about tomcat, ok, I really know nothing about tomcat. This website was created before I started managing this network so I was not involved in its construction. My question is this. I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9 /webapps. If I copy everything from /usr/local/src from the old server onto the new server will this capture everything needed for the website? Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? Any information would be appreciated. Steve -- talk trash and carry a small stick. PAUL KRUGMAN (NYT) -- talk trash and carry a small stick. PAUL KRUGMAN (NYT)
RE: Moving Tomcat
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: Moving Tomcat I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. That's where they are by default. However, apps can be deployed outside of the Tomcat directory tree by placing [appName].xml files in conf/[engine]/[host] That was incomplete. Within each such .xml file will be a Context element with an appBase attribute giving the actual deployment location of the webapp. Make sure you copy those as well. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9/webapps. Lots of good answers already, but here's some others: First, use `ps -auxww | grep tomcat` to confirm the directory that Tomcat is running from (referred to as $CATALINA_HOME). If that is /usr/local/src/jakarta-tomcat-5.5.9/, OK, good so far. :-) Next check $CATALINA_HOME/conf/server.xml for any Host entries with an appBase that points to a directory *outside* of /webapps; you'll need to copy those directories, too. There's probably a startup script, e.g. /etc/init.d/tomcat, that will also provide some insight into Tomcat's running config, and you'll want to copy that. (It'll tell you where Tomcat's JRE/JDK should be found, as well.) You may have iptables/ipchains entries that affect the ports and addresses that Tomcat's using -- check those. HTH, and good luck! -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
I believe you are talking about my post. I still have my job thank you. That particular issue was with another server and dealt with a .war file that was moved. I was successful in getting the file in question back onto the server. I do have a backup of this server. In reference to my posted question, I appreciate everyone's quick input. You all are responding in the manner that I thought you would in that there seems to be a myriad of files to worry about with this move. As I posted, I am looking to copy everything in the /usr/local/src directory. So far I have not been able to see where anything associated with our website resides outside the /src directory. So, if that turns out to be the case could I be confident that everything for the website resides inside the /usr/local/src directory? Chuck mentioned the .xml files. From everything I can determine the catalina directory resides in /usr/local/src/jakarta-tomcat-5.5.9/conf. Mikolaj also mentioned JRE/JDK. Hassan mentioned that there could be a startup script in /etc/init.d that may nave information on where the JRE/JDK is. There is not a startup script. I have to manually startup tomcat whenever this server is rebooted. What and where is the JRE/JDK? Hassan mentioned running ps -auxww | grep tomcat. Below is the return from that command. Is there anything anyone can see that I should be copying that would not get copied when I copy /usr/local/src? What is the /usr/local/java/. . . referring to? Is this needed for the website? [EMAIL PROTECTED] /]# ps -auxww | grep tomcat root 13104 0.0 3.6 293716 37904 pts/2 S 2006 8:45 /usr/local/java/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/local/tomcat/common/endorsed -classpath :/usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/commons-loggi ng-api.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start root 18753 0.0 0.1 26836 1756 ?S 2006 0:11 gedit file:///usr/local/src/jakarta-tomcat-5.5.9/webapps/online/calendar.jsp root 10820 1.0 0.0 3700 668 pts/2S09:43 0:00 grep tomcat [EMAIL PROTECTED] /]# Thanks for all the input. Steve -Original Message- From: EDMOND KEMOKAI [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 03, 2007 9:27 AM To: Tomcat Users List Subject: Re: Moving Tomcat Hmm Interesting, the person was from Oklahoma Court, is that you again? On 1/3/07, EDMOND KEMOKAI [EMAIL PROTECTED] wrote: First I'll suggest you backup your entire server, it is possible for instance if your server is running Linux that the webapps folder only contain the links to the actual webapp folders residing somewhere else on the filesystem..So again BACKUP before doing anything. About a month ago someone on this mailing list in your position deleted stuff on a server they were managing, I have the feeling they don't have a job anymore. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: I have a website running with jakarta-tomcat-5.5.9. The server this website resides on is going to have to be rebuilt so I am needing to move everything off of it onto another server. I know very little about tomcat, ok, I really know nothing about tomcat. This website was created before I started managing this network so I was not involved in its construction. My question is this. I believe that all of the content for the webpage(s) reside in /usr/local/src/jakarta-tomcat-5.5.9 /webapps. If I copy everything from /usr/local/src from the old server onto the new server will this capture everything needed for the website? Is there anything else I need to know about or that needs moved in order for the website to be accessible from the new server? Any information would be appreciated. Steve -- talk trash and carry a small stick. PAUL KRUGMAN (NYT) -- talk trash and carry a small stick. PAUL KRUGMAN (NYT) - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: . I am looking to copy everything in the /usr/local/src directory. So far I have not been able to see where anything associated with our website resides outside the /src directory. So, if that turns out to be the case could I be confident that everything for the website resides inside the /usr/local/src directory? The running instance of Tomcat indicates that it's in /usr/local/tomcat, not /usr/local/src/... -Dcatalina.home=/usr/local/tomcat Mikolaj also mentioned JRE/JDK. Hassan mentioned that there could be a startup script in /etc/init.d that may nave information on where the JRE/JDK is. There is not a startup script. I have to manually startup tomcat whenever this server is rebooted. That's, mmm, wierd. And awkward. :-) Is that a policy thing, or just something no one's ever fixed? What is the /usr/local/java/. . . referring to? Is this needed for the website? Absolutely; that's the JDK referred to above. `java -version` will tell you which one; if it's 1.5.something you may want to just download and install the latest 1.5.x, rather than just copy. -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] So far I have not been able to see where anything associated with our website resides outside the /src directory. So, if that turns out to be the case could I be confident that everything for the website resides inside the /usr/local/src directory? Yes - if that turns out to be the case :-). However, it looks like the version of Tomcat that's running is in /usr/local/tomcat, not /usr/local/src - so something odd is going on. You may want to run a 'find /usr/local/src/jakarta-tomcat-5.5.9 -type l -print' (check that l is the correct type for symlinks, I'm working from very old memory) to be certain there are no unexpected symbolic links under the Tomcat directories if you've not already checked. You may want to do the same with /usr/local/tomcat, as that may be linked to the source tree or something more complex may be happening. What and where is the JRE/JDK? This is your Java installation - Java Runtime Environment / Java Development Kit. Looks like it's in /usr/local/java from the output below. What is the /usr/local/java/. . . referring to? Is this needed for the website? Yep :-). Without that, or its equivalent somewhere on the new server, you won't be starting Tomcat any time soon. root 13104 0.0 3.6 293716 37904 pts/2 S 2006 8:45 /usr/local/java/bin/java -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djava.endorsed.dirs=/usr/local/tomcat/common/endorsed -classpath :/usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/com mons-loggi ng-api.jar -Dcatalina.base=/usr/local/tomcat -Dcatalina.home=/usr/local/tomcat -Djava.io.tmpdir=/usr/local/tomcat/temp org.apache.catalina.startup.Bootstrap start So that's the Tomcat that's running... root 18753 0.0 0.1 26836 1756 ?S 2006 0:11 gedit file:///usr/local/src/jakarta-tomcat-5.5.9/webapps/online/calendar.jsp ... that's someone editing a JSP... root 10820 1.0 0.0 3700 668 pts/2S09:43 0:00 grep tomcat ... and that's your grep. - Peter - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
. I am looking to copy everything in the /usr/local/src directory. So far I have not been able to see where anything associated with our website resides outside the /src directory. So, if that turns out to be the case could I be confident that everything for the website resides inside the /usr/local/src directory? The running instance of Tomcat indicates that it's in /usr/local/tomcat, not /usr/local/src/... -Dcatalina.home=/usr/local/tomcat There is a link in /usr/local for tomcat that directs to /usr/local/src/jakarta-tomcat-5.5.9. Is it important to have the tomcat link set up this same way on the new server? Is there a specific reason why it would have been set up this way? Mikolaj also mentioned JRE/JDK. Hassan mentioned that there could be a startup script in /etc/init.d that may nave information on where the JRE/JDK is. There is not a startup script. I have to manually startup tomcat whenever this server is rebooted. That's, mmm, wierd. And awkward. :-) Is that a policy thing, or just something no one's ever fixed? It is not a policy issue. I believe it is something no one setup. Since I am the local tomcat novice I have not done anything about it either. I just have to remember to manually start tomcat when I reboot the server (which I have had occasion to forget to do before). What is the /usr/local/java/. . . referring to? Is this needed for the website? Absolutely; that's the JDK referred to above. `java -version` will tell you which one; if it's 1.5.something you may want to just download and install the latest 1.5.x, rather than just copy. Ok, well that resides in /usr/java/jdk-1.5.0. Where can I download a new version? Is the download straightforward for a novice like me? Or do I need to read up on a thing or two before downloading? The machine I am attempting to move this to is running CentOS 4.0. Thanks, Steve -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat Chuck mentioned the .xml files. From everything I can determine the catalina directory resides in /usr/local/src/jakarta-tomcat-5.5.9/conf. Yes, but the [appName].xml files may have docBase attributes in Context entries that point to app locations outside of /usr/local/src; those must be individually checked and the targets copied if they reside elsewhere. It's also possible that you might have Context elements inside conf/server.xml as well; these are strongly discouraged in 5.5, but not prohibited. And now you have the confusion of /usr/local/src/jakarta-tomcat-5.5.9 vs. /usr/local/tomcat; will the real Tomcat please stand up? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
If your running fedora/redhat, it usually creates many symlinks and places the actual files into different folders. The only reason this is done I think is for flexibility. For instance with the server running my site now, I have my webapp in a different home directory and created a symlink called ROOT to point to my webapp. This allows my app to become the deault app without having to do anything else. If you have ssh server running, I'll be willing to login to your machine to provide some guidiance. Currently I use not much more than but nautilus to administer my server. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: . I am looking to copy everything in the /usr/local/src directory. So far I have not been able to see where anything associated with our website resides outside the /src directory. So, if that turns out to be the case could I be confident that everything for the website resides inside the /usr/local/src directory? The running instance of Tomcat indicates that it's in /usr/local/tomcat, not /usr/local/src/... -Dcatalina.home=/usr/local/tomcat There is a link in /usr/local for tomcat that directs to /usr/local/src/jakarta-tomcat-5.5.9. Is it important to have the tomcat link set up this same way on the new server? Is there a specific reason why it would have been set up this way? Mikolaj also mentioned JRE/JDK. Hassan mentioned that there could be a startup script in /etc/init.d that may nave information on where the JRE/JDK is. There is not a startup script. I have to manually startup tomcat whenever this server is rebooted. That's, mmm, wierd. And awkward. :-) Is that a policy thing, or just something no one's ever fixed? It is not a policy issue. I believe it is something no one setup. Since I am the local tomcat novice I have not done anything about it either. I just have to remember to manually start tomcat when I reboot the server (which I have had occasion to forget to do before). What is the /usr/local/java/. . . referring to? Is this needed for the website? Absolutely; that's the JDK referred to above. `java -version` will tell you which one; if it's 1.5.something you may want to just download and install the latest 1.5.x, rather than just copy. Ok, well that resides in /usr/java/jdk-1.5.0. Where can I download a new version? Is the download straightforward for a novice like me? Or do I need to read up on a thing or two before downloading? The machine I am attempting to move this to is running CentOS 4.0. Thanks, Steve -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- talk trash and carry a small stick. PAUL KRUGMAN (NYT)
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat There is a link in /usr/local for tomcat that directs to /usr/local/src/jakarta-tomcat-5.5.9. Is it important to have the tomcat link set up this same way on the new server? Is there a specific reason why it would have been set up this way? Probably to avoid having to change startup scripts, procedures, etc., when Tomcat is upgraded. Ok, well that resides in /usr/java/jdk-1.5.0. Where can I download a new version? From Sun's web site: http://java.sun.com/javase/downloads/index_jdk5.jsp Do not download and install the version with Java EE - that will result in problems you don't want to deal with; just use the plain JDK 5.0 Update 10. It's pretty straightforward. You could download JDK 6 instead, but that's brand new, and I wouldn't risk it. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: There is a link in /usr/local for tomcat that directs to /usr/local/src/jakarta-tomcat-5.5.9. Is it important to have the tomcat link set up this same way on the new server? Is there a specific reason why it would have been set up this way? Every admin has her/his own installation style :-) If that seems to be the site standard -- i.e., other things in /usr/local are symlinks to installation packages under /usr/local/src -- stick with it. But it's a policy point, not a technical requirement. Ok, well that resides in /usr/java/jdk-1.5.0. Where can I download a new version? Is the download straightforward for a novice like me? Easy enough, I'd think: http://java.sun.com/ but not necessary. For your own edification, I'd suggest trying to install Java and Tomcat from scratch on the new machine, get it running, e.g. the example apps work, and then copy over the current production apps. FWIW! -- Hassan Schroeder [EMAIL PROTECTED] - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
Chuck mentioned the .xml files. From everything I can determine the catalina directory resides in /usr/local/src/jakarta-tomcat-5.5.9/conf. Yes, but the [appName].xml files may have docBase attributes in Context entries that point to app locations outside of /usr/local/src; those must be individually checked and the targets copied if they reside elsewhere. It's also possible that you might have Context elements inside conf/server.xml as well; these are strongly discouraged in 5.5, but not prohibited. Well now I am indeed thoroughly confused. Here is the website in question: http://www.okcca.net/online/ I have been looking at the various pages and links on this site and so far I believe that they all are linking to the /usr/local/src/jakarta-tomcat-5.5.9/webapps directory. And now you have the confusion of /usr/local/src/jakarta-tomcat-5.5.9 vs. /usr/local/tomcat; will the real Tomcat please stand up? I do believe the real tomcat resides in the /usr/local/src/jakarta-tomcat-5.5.9 directory and the /usr/local/tomcat is a link to that directory. FYI, there also is a link in /usr/local/ titled java that redirects to the /usr/java/jdk-1.5.0 directory. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat Yes, but the [appName].xml files may have docBase attributes in Context entries that point to app locations outside of /usr/local/src; those must be individually checked and the targets copied if they reside elsewhere. It's also possible that you might have Context elements inside conf/server.xml as well; these are strongly discouraged in 5.5, but not prohibited. Well now I am indeed thoroughly confused. Note that the above are _possibilities_, not mandatory aspects of a Tomcat installation. Your particular environment may well have everying under the regular webapps directory. Here is the website in question: http://www.okcca.net/online/ You can't tell where things are by looking from the outside; the URLs used to access the web site can be easily mapped to various locations in the file system by servlet-mappings, appBase and docBase attributes, filters, symbolic links, etc. A well-designed and well-managed web site will have such things documented, but unfortunately many just seem to evolve. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Moving Tomcat
Here is the website in question: http://www.okcca.net/online/ You can't tell where things are by looking from the outside; the URLs used to access the web site can be easily mapped to various locations in the file system by servlet-mappings, appBase and docBase attributes, filters, symbolic links, etc. A well-designed and well-managed web site will have such things documented, but unfortunately many just seem to evolve. Ok, I understand what you are saying about not seeing the location from the outside. However, am I wrong in thinking that I can track down the location if I know where everything is residing? For example, if I click on the judges for retention link on the left side of the main webpage the browser is directed to an address of: http://www.okcca.net/online/JudgeVote.2006.jsp I know that the online directory resides in the /usr/local/src/jakarta-tomcat-5.5.9/webapps/ directory and therefore the JudgeVote.2006.jsp file should be in that online directory. When I navigate to that directory on the server I can see that file. Therefore, I have been looking at each page/link in this manner. I look at the address location in the web browser and then navigating to the appropriate directory in the /usr/local/src/. . . directory I believe it is on the server to verify that the file in question is there. So far this has worked in showing me the exact directory location for each page/link I have looked at. Is this a legitimate way to go about this or am I going to overlook something in using this method? As far as your comment about documentation, I am afraid I have not come across any documentation detailing any of the website design. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
If you have the second server setup then you can install tomcat and copy the webapps folder over and see what happens. Once you start getting errors from the new server then you can troubleshoot until everything is fixed. It will be difficult to know if everything will work without testing. So I'll suggest to build the new server first, unless of course you'll be using the same hardware then you can't do that. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: Here is the website in question: http://www.okcca.net/online/ You can't tell where things are by looking from the outside; the URLs used to access the web site can be easily mapped to various locations in the file system by servlet-mappings, appBase and docBase attributes, filters, symbolic links, etc. A well-designed and well-managed web site will have such things documented, but unfortunately many just seem to evolve. Ok, I understand what you are saying about not seeing the location from the outside. However, am I wrong in thinking that I can track down the location if I know where everything is residing? For example, if I click on the judges for retention link on the left side of the main webpage the browser is directed to an address of: http://www.okcca.net/online/JudgeVote.2006.jsp I know that the online directory resides in the /usr/local/src/jakarta-tomcat-5.5.9/webapps/ directory and therefore the JudgeVote.2006.jsp file should be in that online directory. When I navigate to that directory on the server I can see that file. Therefore, I have been looking at each page/link in this manner. I look at the address location in the web browser and then navigating to the appropriate directory in the /usr/local/src/. . . directory I believe it is on the server to verify that the file in question is there. So far this has worked in showing me the exact directory location for each page/link I have looked at. Is this a legitimate way to go about this or am I going to overlook something in using this method? As far as your comment about documentation, I am afraid I have not come across any documentation detailing any of the website design. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- talk trash and carry a small stick. PAUL KRUGMAN (NYT)
RE: Moving Tomcat
From: Steve Ingraham [mailto:[EMAIL PROTECTED] Subject: RE: Moving Tomcat However, am I wrong in thinking that I can track down the location if I know where everything is residing? If you want an absolute answer, it's yes - you are wrong, at least if you're assuming that URL paths always correspond to file system paths. However, having said that, most apps are straightforward and do conform to the idea of one-to-one mapping of URL paths to directories. (For an example of one that doesn't, just look at Tomcat's manager app. As you click on various links in it, you'll see things like manager/html/list - but there's no such directory structure under server/webapps/manager; it's all done with servlet mappings in its WEB-INF/web.xml file.) The only real way to be _absolutely_ sure you have found everything is to go through the Tomcat and app configuration, and the source code of each app. (Painful, at best.) It's possible to discover direct file system references in an app that don't appear as links on any page. As far as your comment about documentation, I am afraid I have not come across any documentation detailing any of the website design. Not at all surprising that it doesn't exist. It's tough when you inherit responsibilities. - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Moving Tomcat
I'm glad to hear that Steve! to recap-- Get same version JVM installed on new tomcat Get same version Tomcat installed (with manager and admin working) on new Tomcat copy over jars from $CATALINA_BASE/shared/lib/*.* copy over class files from $CATALINA_BASE/shared/classes/*.* if you see extra jars or class files located in either $CATALINA_HOME/common/lib or $CATALINA_HOME/common/classes read this http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html once you feel you grasp the implications of what jars should be located in the common folder then copy jars and classes only on a as-needed basis All of your webapps live in a self contained package called WebAppName.war (confirm by viewing folders located at $CATALINA_BASE/webapps and all war files located at $CATALINA_BASE/webapps/*.war) you should use the manager of the new server to open each war file and carefully note any error messages at top of manager screen If the top of the manager screen displays errors then view the tail end of the log file located at $CATALINA_BASE/logs/HostName.-MM-DD.log As always we are here to help HTH M- --- This e-mail message (including attachments, if any) is intended for the use of the individual or entity to which it is addressed and may contain information that is privileged, proprietary , confidential and exempt from disclosure. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this communication is strictly prohibited. --- Le présent message électronique (y compris les pièces qui y sont annexées, le cas échéant) s'adresse au destinataire indiqué et peut contenir des renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le destinataire de ce document, nous vous signalons qu'il est strictement interdit de le diffuser, de le distribuer ou de le reproduire. - Original Message - From: EDMOND KEMOKAI [EMAIL PROTECTED] To: Tomcat Users List users@tomcat.apache.org Sent: Wednesday, January 03, 2007 1:52 PM Subject: Re: Moving Tomcat If you have the second server setup then you can install tomcat and copy the webapps folder over and see what happens. Once you start getting errors from the new server then you can troubleshoot until everything is fixed. It will be difficult to know if everything will work without testing. So I'll suggest to build the new server first, unless of course you'll be using the same hardware then you can't do that. On 1/3/07, Steve Ingraham [EMAIL PROTECTED] wrote: Here is the website in question: http://www.okcca.net/online/ You can't tell where things are by looking from the outside; the URLs used to access the web site can be easily mapped to various locations in the file system by servlet-mappings, appBase and docBase attributes, filters, symbolic links, etc. A well-designed and well-managed web site will have such things documented, but unfortunately many just seem to evolve. Ok, I understand what you are saying about not seeing the location from the outside. However, am I wrong in thinking that I can track down the location if I know where everything is residing? For example, if I click on the judges for retention link on the left side of the main webpage the browser is directed to an address of: http://www.okcca.net/online/JudgeVote.2006.jsp I know that the online directory resides in the /usr/local/src/jakarta-tomcat-5.5.9/webapps/ directory and therefore the JudgeVote.2006.jsp file should be in that online directory. When I navigate to that directory on the server I can see that file. Therefore, I have been looking at each page/link in this manner. I look at the address location in the web browser and then navigating to the appropriate directory in the /usr/local/src/. . . directory I believe it is on the server to verify that the file in question is there. So far this has worked in showing me the exact directory location for each page/link I have looked at. Is this a legitimate way to go about this or am I going to overlook something in using this method? As far as your comment about documentation, I am afraid I have not come across any documentation detailing any of the website design. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- talk trash and carry a small stick. PAUL KRUGMAN (NYT)
