Notes from a Tomcat Install in Snow Leopard

I had to set up a Tomcat server to run on my MacBook Pro today. Here are the notes on what I did:

First, I downloaded Tomcat from the Apache site. Second, I used the sections labeled 'Install Apache Tomcat 6" and "Secure Tomcat" from this site to set up the server. Finally, I created two Automator scripts to start and stop the server without the need for any typing.

START TOMCAT SERVER:

Create a new shell script application in automator and enter the following commands in the script:

cd Library/Tomcat/Home/bin
./startup.sh

STOP TOMCAT SERVER:

Create another shell script application and enter the following commands in the script:

cd Library/Tomcat/Home/bin
./shutdown.sh

Next step on my current trek is the installation of Swing and maybe BlazeDS; I'll write on that too time permitting.

Trackback URL for this post:

http://www.stevenjbarnes.com/trackback/39

Virutalbox

You may want to consider using virualbox instead of poluting your host SO with server installs. I've asking the guys at work to start using VMs when working on new projects. There are some deltas, but the pluses out weigh them:

Pros:

* They keep the host OS clean (very important)
* You can move from one machine to another very quickly
* You can copy the OS to another developer and have them up and running immediately.
* Can have any number of OSes installed and running a number of different projects.
* You can keep a number of virgin os'es, copy them and then create a new project.

Cons:

* Can consume disk space and requires extra memory to run
* Needs to be maintained, patched, etc.
* If you are running SVN on the VM it can be a bit challenging to keep it up to date.
* Can be a bit hard to maintain the development files if they reside on your host OS. I tend to use samba and map to the VM and edit the files directly.

I'll take a look!

Thanks for the heads up Cary. Having a mess of servers on my computer has been a bit of concern.

http://www.virtualbox.org/

Update: If you are running 16.2 and considering virtualbox, you might want to wait for the next build. Not sure how prevalent the following issue is: http://forums.virtualbox.org/viewtopic.php?f=8&t=27936

stevenjbarnes