[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Monitor as NT service - Which port?



[ David Neumann ]

> Sounds like you don't have your web server configured properly. If you
> are using IIS or PWS,those tend to default to using a 'Scripts' key
> instead of 'cgi-bin' in the URL.  

I'm using Apache and there is no problem whith the webserver setup. If
I start Monitor from command line my webbrowser is automaticly started
and the Monitor application works. Applications also works fine when
launching them from Project Builder.

The problem is when I start Monitor and Monitor as  _NT service_.
Which port is the default? Do I have to specify a portnumber when
accessing the _NT service_ Monitor?

OK, so the scenario is this:

The NT service "Monitor" is started automaticly at boot, and is now
running.
The NT service "Monitor Proxy" is started automaticly at boot, and is
now running.

I open my web browser and try the following URL:
http://localhost/cgi-bin/WebObjects.exe/Monitor

The result is: 404 - The file was not found.

Why?

> OR, you could type this in a shell:
> 
> defaults write Monitor WOPort 7777
> 
> And now the app named 'Monitor' will use port 7777 any time it is
> launched (in your case by the NT Service stuff). And so you can just use
> DirectConnect to access the app:
> 
> http://localhost:7777/

I havent tried to specify the portnumber my self, but I'm sure it
works, but I don't want to start Monitor from a shell. I want to use
the NT service.


-- 
Lars Preben