• Overview
• Install and Directions for Use
• Download Software

OWA Replacement Cartridge

• 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).

You can get more in depth information on the following topics as well:

• How this cartridge logs into the database using YOUR username/password
• How this cartridge resolves URLS. (eg: how it figures out whether to run a stored procedure, fetch a row from a BLOB table, or get an OS file), how it decideds to compress and OS file, how it decides to compress a database blob.
• How this cartridge does database Server Side Includes. Also known as the <ORACLE> tag.
• How this cartridge collects and processes detailed timing. statistics in the database for performance evaluation.