|
So far we have a working web server with a servlet engine - now lets discuss the
basic ideas and concepts before moving on to configuration
|
|
There's some documentation about zones on the apache pages. Basically each zone
gets mounted by jserv, each zone is a collection of servlets(or just one servlet).
The zones are configured to execute the servlet when a request is made and return
(at least in our case) html. Our zone will be configured to execute Prism, Prism
executes the pl/sql and returns the html generated by it. Easy? Prism also has a
configuration file.
- jserv, configured to mount zones
- zone, configured to execute Prism servlet
- Prism, configured to connect to database
At first it appears to be confusing, but the architecture if flexible and versatile.
We will configure each file as needed. Once you have been through a few configurations
it becomes much easier, as your understanding grows it becomes a breeze. Remember
when we started the instructions where written to get you up and running without
having to load OAS, (since you will probably need to buy more RAM or upgrade NT to
the correct service pack, or like many just give up).
|
|
|
When an http request is serviced, apache would normally return and html file, no
mystery here. When a request is made to access a servlet, apache passes the request
onto jserv (apache gets configured to do this) jserv accesses the servlet (jserv
is configured to do this). When the request is made for a pl/sql procedure, all the
above happens the servlet - prism - executes the pl/sql (prism is configured to do
this) and returns html. Voila!
Browser <--> Apache <--> Jserv <--> Prism <--> PL/SQL
|
|
