[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Monitor as NT service - Which port?
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. If you are using Netscape, I don't
even think that supports cgi programs with a .exe extension (that's why
WO always installs a 'WebObjects' and 'WebObjects.exe' into whatever
cgi-bin folder you specify on install.
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/
d
"Lars Preben S. Arnesen" wrote:
>
> [ Karsten D. Wolf ]
>
> > You should try this url instead
> > http://localhost/cgi-bin/WebObjects.exe
> > you should see a list of the WOApps on Your machine.
> > Click on the Monitor WOApp (and be sure to set a password for it).
>
> But what do I do when http://localhost/cgi-bin/WebObjects.exe returns
> the 404 error?
> (Then Monitor and MonitorProxy services are running!)
>
> Anyone...?
>
> --
> Lars Preben