Starting WLS from the console...

Question

Hello,
when trying to start the WL server from within the WL console on
my NT4, it seems like the console is trying to build a new classpath
rather than using the one it was started with.
This would be fine apart from the fact that it doesn't seem to
be doing this correctly. I have built my environment using wlconfig.exe
and the properties page in the console looks fine (i.e. all the
jars and other bits and bobs are in place). The registry also (obviously)
looks fine. However, the classpath used to start the server SHOULD
be prepended by the value of HKEY_LOCAL_MACHINE/SOFTWARE/BEA/WL5.1/CLASSPATH
but it isn't?? (As an aside, why call it classpath when it really
only the classpath_prefix?)
It also took me a while to find that there are two binaries used
for starting the console: wlconsolew.exe and wlconsole.exe. wlconsolew.exe
is what is run when you use the Start Menu and it blatantly ignores
any settings in the registry. wlconsole.exe does this right but
still manages to stuff up the building of the classpath for starting
the server. Any VM settings in the registry are also ignored.
Any comments? Has anyone managed to find a way around this (apart
from the obvious, i.e. using scripts instead?)
/Lars

Answer 1

A partial solution might be the following. Make shortcuts in your programs folder to target the batch files in %TOMCAT_HOME%\bin.
Then, all you need to do is select the shortcuts whenever you need to access the server.
The command prompt window will still be visible, but this method saves some typing time.
The next step is figuring out how to make Tomcat a Windows service so it runs in the background. I don't know how to do this.