Configuring DAD file and MODPLSQL on Oracle Application server 10g

mod_plsql DAD Configuration
This file contains documentation of all the Database Access Descriptor (DAD)level parameters that can be specified in the mod_plsql configuration file$ORACLE_HOME/Apache/modplsql/conf/dads.conf

A DAD is a set of values that specify how mod_plsql connects to a databaseserver to fulfill an HTTP request. Besides the connect details, a DAD containsimportant configuration parameters for various operations in the databaseand for mod_plsql in general. Any web-enabled PL/SQL application which makesuse of the PL/SQL Web ToolKit needs to create a DAD to invoke the application.
Some typical PL/SQL applications which would require DAD's are- Any PL/SQL Application written using the PL/SQL Web ToolKit- Oracle Application Server Portal- Oracle Application Server Single Sign-On

Creating a DAD------------------
If OHS/mod_plsql is part of the Oracle Application Server product, it isrecommended that you use Oracle Enterprise Manager to create a DAD. Otherwise,perform the following steps to create a DAD
1. Edit the DAD configuration file ORACLE_HOME/Apache/modplsql/conf/dads.conf.
2. Add a DAD where the DAD has the following format:
- The Oracle HTTP Server directive which defines a virtual path used to access the PL/SQL Web Application. This directive begins enclosing a group of directives that apply to the named Location.
For example, the directive defines a virtual path called "/myapp" that will be used to invoke a PL/SQL Web Application through a URL like http://host:port/myapp/.
Note: Older versions of mod_plsql were always mounted on a virtual path with a prefix of '/pls'. This restriction is removed in newer versions but might still be a restriction imposed by some older PL/SQL applications.
- The Oracle HTTP Server "SetHandler" directive which directs Oracle HTTP Server to enable mod_plsql to handle the request for the virtual path defined by the named Location
SetHandler pls_handler
- Additional Oracle HTTP Server directives that are allowed in the context of a directive. Typically, the following directives are used:
Order deny,allow Allow from all AllowOverride None
- One or more mod_plsql specific directives. For example:
PlsqlDatabaseUsername scott PlsqlDatabasePassword tiger PlsqlDatabaseConnectString orcl PlsqlAuthenticationMode Basic
- An Oracle HTTP Server directive which closes the group of directives for the named Location, and defines a single DAD.
3. Save the edits.
4. Obfuscate the DAD password by running the "dadTool.pl" script located in ORACLE_HOME/Apache/modplsql/conf. For instructions on performing the obfuscation, please refer to ORACLE_HOME/Apache/modplsql/conf/dadTool.README
If OHS/mod_plsql is part of the Oracle Application Server product, then issue $OH/dcm/bin/dcmctl updateConfig -ct ohs
5. Restart the Oracle HTTP Server for the configuration to take effect.
You can create additional DADs by defining other uniquely named Locations indads.conf.
Here is an example of a typical PLSQL application DAD
SetHandler pls_handler Order deny,allow Allow from all AllowOverride None PlsqlDatabaseUsername scott PlsqlDatabasePassword tiger PlsqlDatabaseConnectString orcl PlsqlAuthenticationMode Basic PlsqlDefaultPage scott.home PlsqlDocumentTablename scott.wwdoc_document PlsqlDocumentPath docs PlsqlDocumentProcedure scott.wwdoc_process.process_download
here is my example that I made it in my company



SetHandler pls_handler
Order deny,allow
Allow from all
AllowOverride None
PlsqlDatabaseUsername moi
PlsqlDatabasePassword moi
PlsqlDatabaseConnectString moidb
PlsqlAuthenticationMode Basic

Comments

Popular posts from this blog

Another user has changed the row with primary key oracle.jbo.Key[12 ].

Working With File Throgh WebUtill

weblogic windows JPS-01050: Opening of wallet based credential store failed. Reason java.io.IOException: Failed to lock cwallet.sso.lck