Re: wo processes and ssl wonderments
Re: wo processes and ssl wonderments
- Subject: Re: wo processes and ssl wonderments
- From: Denis Bredelet <email@hidden>
- Date: Mon, 27 Sep 2004 11:36:22 +0100
Hi Wes
I've been working a little with webobjects for a couple of months now
and I have some questions.
1. in the execution model for a wo app it appears that a web server
is in the mix. If this is so how does a wo app build then run when
there is no web server running? I notice that a custom port is
generated then the wo app runs on some type of webserver via:
http://ipaddress:port/cgi-bin/WebObjects/app.woa
Does this mean that a webserver is run during this build/run session
then the app/web server is shut down when the Red tasks button is
clicked in Xcode?
No. When launching the application in Xcode, the application opens in
"Direct Connect" mode. That means that it listens to HTTP requests on a
specific port without going through the web server.
Before deploying the application in production, make sure that you test
the application through the web server, as a few things change between
Direct Connect and deployment modes.
In deployment mode, the requests are delegated to a web server plugin,
the "WebObjects adaptor". You can find more about the WebObjects
adaptor here:
<http://developer.apple.com/documentation/WebObjects/Deployment/
Deploying_Applications/WebObjectsAdaptors/chapter_4_section_2.html#//
apple_ref/doc/uid/TP30000062/BBCGIBCI>
2. I have been looking at how wo works with ssl. I have had some help
via the apple osx server list regarding setting up certs so that the
apache server on osx server can run on https. But in working with
making a wo app live it appears that JavaMonitor manages the state of
apps on given ports. So it appears to me that JavaMonitor
starts/stops wo apps on given ports which means to me that wo apps run
on ports independent of say an apache installation running on port 80.
Monitor (really wotaskd) communicates with instances in Direct Connect
mode, even if Direct Connect is disabled. That is why wotaskd needs to
be running on the same host as the application.
To me this means that putting together certs for apache on port 443
is independent of any wo apps running. Since this seems to be the
case how does a wo app get set up to work on SSL. Where is SSL set up
for each instance of a wo app?
3. Are there any books, web docs, etc., that talk about 1 and 2
above? I have searched google, apple tech info and lists, but I can't
find much info on SSL and wo, except for a wo version 4 example that
is not even accessible from apple any more, just some other webs sites
that have it from past availability...
I was just looking through the wo overview pdf on the wo CD and It
always shows a web server in the mix. If I am using JavaMonitor to
start a wo app is this using the installed apache installation base to
start up an apache instance on a given port and then running the wo
app through the cgi-interface of the apache instance? If JavaMonitor
is just starting up an apache instance then I should be able to start
up an instance on port 443 and get wo working over https, right? I
tried this and it didn't work. I need some more pieces to this puzzle
:)......
thanks,
wj
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden