In the current deployment configuration, OME is running within
mod_perl. This process is created by the Apache httpd process in
order to take care of execution of HTTP requests that are handled
by Perl scripts via CGI. Apache and mod_perl are configured so that
they have access to the OME Perl scripts and modules. Apache is
also made aware of some HTML static pages and JavaScript libraries
that are needed to support dynamic content provided through mod_perl.
Web browsers access the system through an URL similar to the following:
http://your.ome.site/perl/serve.pl?Page=OME::Web::Home
Apache dispatches the request to mod_perl that executes the serve.pl
script, which, in turn, instantiates an appropriate module (depending
on the Page parameter) to handle the request. Depending on the request,
the module may interact with the OME database, which is managed
by the PostreSQL server process, postmaster. However, the actual
identity of the DBMS is transparent to OME, as access is through
the Perl DBI interface.
OME makes use of a directory in the file system to store the Image
Repository. Imported image files are stored in this area. The import
process takes care of converting proprietary image formats into
the OME image file standard. The disk space needed by the repository
is roughly equivalent to the amount of storage taken up by the native
format image files.
Apache, mod_perl and PostreSQL run on the same node where OME is
deployed. Web browsers typically run on a different node across
an IP network.
The current deployment configuration of OME is summarized by the
following UML deployment diagram:
|