OWA Replacement Cartridge
Have you ever wanted to.....
-
Use Database Authentication over the web?
(as opposed to storing usernames and passwords in clear text in a plain
OS file). This lets you log into the database without using the username/password
stored in the owa.cfg file. The username/password you supply on the basic
authentication screen is used to log you in. The DCD information is used
only to find the oracle_home, oracle_sid, connect_string, and error logging
directory. The username and password are ignored.
-
Use the Database Authentication
to protect your regular OS files as well as database data?
-
Logoff (de-authenticate) yourself
without exiting the browser and restarting it. (Useful during development
when you want to test many accounts to see the different reactions each
user will get).
-
Allow your users to dynamically create their account and then
change
their passwords without having to rewrite a configuration file
or 'bounce' the web listener?
-
Upload files from your client to the
file system or directly
into long raw or blob column in the database?
-
Download files from your database to
your client?
-
Compress files as they are
downloaded either from the file system or from your database. Powerpoint
files are compressed 50% or more, Word Documents 60% or more...
-
Use an <ORACLE> tag to provide an easy
way to add a little bit of dynamic content to your existing static pages?
-
Have something equivalent to Timed statistics
to do performance tuning/tracking for your web applications?
-
Have a pre/post subroutine get invoked before
each web agent procedure call? This allows you to implement your own authorization
scheme in pl/sql, or audit activity, or time certain modules.
-
Have all of the above functionality in one integrated Oracle Web
Server cartridge? Or even in a CGI-BIN program (for use with WS 1.x or
2.0.1 to support database authentication).
Well, then look no further..... You are in luck.
You can get more in depth information on the following topics as well:
Sorry, compiled binaries are not available. Due to the sheer number
of OS versions (Solaris 2.4, .5, .6, ... NT 4sp3, 4sp4, 4sp5,
4sp6, ... ) and database versions (7.3, 8.0, 8.1) and OAS versions (2.1.1,
3.0.0.18, 3.0.1, 3.0.2, 4.0.....) it is just not possible to have a single
binary everyone could use. Source code and makefiles are provided