>I have an app called Foo running on our web server (solaris)...it's live
its
>been deployed. I want to run the same app on another machine (winnt), but
>it's a development version, I don't want it to be accessible when a user
>requests Foo on the solaris box.
>
>In the old days, you could specify the name for the app...for example if I
>had Foo (and the executable was named Foo), I could have the adaptor know
the
>FooDev would go to Foo.
Monitor in 4.0 is not good for this. Monitor uses the name of the
application and appends it to the path to compute the path to the
executable. You could work around this in a couple of ways - neither of
which are elegant:
1) You could rename the executable in development mode and create a separate
entry in Monitor with that name. You might want to automate this in your
build/make process.
2) Use a second copy of Monitor. This would work as long as you don't use
the same web server. The critical piece is the 'WebObjects.conf' that gets
written. You don't want the 2nd Monitor to overwrite the one on your
solaris box.
- Eric
