Aha! I knew if I posted the question I'd figure it out.
IF you are running the startup and shutdown commands from the command
line in windows:
edit catalina.bat
set JAVA_OPTS=-D<key>="<value>"
IF you are running Tomcat 5 as a service:
Run %CATALINA_HOME%/bin/tomca5tw.exe
This opens a GUI and allows you to set a system property to the JVM.
> Aha! I knew if I posted the question I'd figure it out.
>
[quoted text clipped - 7 lines]
>
> This opens a GUI and allows you to set a system property to the JVM.
I typically use web.xml for this. A popular one I employ is
debug=true/false. I don't know if this is feasable in your situation though.

Signature
Tom Dyess
OraclePower.com
Brian Munroe - 22 Jun 2005 17:44 GMT
> I typically use web.xml for this. A popular one I employ is
> debug=true/false. I don't know if this is feasable in your situation though.
I second what Tom is suggesting. By placing your environment variables
in the deployment descriptor (<appname>/WEB-INF/web.xml), you can
restrict which applications will have access to these variables. If
you define them in the JVM, you won't.
If you need to have global variables defined, you can place them in
$CATALINA_HOME/conf/web.xml.
You define them in web.xml like:
<env-entry>
<env-entry-name>buildString</env-entry-name>
<env-entry-value>20050601-38</env-entry-value>
<env-entry-type>java.lang.String</env-entry-type>
</env-entry>
between the <web-app> </web-app> tag
and then you can access them in your code like:
<% Context env = (Context) new
InitialContext().lookup("java:comp/env"); %>
<%= "build: " + env.lookup("buildString") %>
Hope that helps.