DAD Section
This section describes DBPrism DAD parameters. Remember that DAD are sections into prism.xconf file starting with the reserved string DAD_
Here an example DAD:
<category name="DAD_java">
<property name="dbusername" value="scott"/>
<property name="dbpassword" value="tiger"/>
<property name="compat" value="java"/>
<property name="defaultPage" value="DEMOj.startup"/>
<property name="docAccessPath" value="download"/>
<property name="docAccessProcedure" value="DEMOj.download"/>
<property name="documentTable" value="wpg_document"/>
</category>
| Name | Values | Default | Explanation |
|---|---|---|---|
| dbusername/dbpassword/connectString | Oracle values | empy strings | Username, password and connect string used to connect to the database. If you want to use dynamic login, left username empty. Database connect string is a JDBC valid connect string for Oracle databases. |
| errorLevel | 0,1,2 | 0 |
|
| errorPage | a valid URL | empy string | URL to redirect if errorLevel is set to 0. |
| dynamicLoginRealm | any string | new DB Login | String that the browser showa to the users when ask for username and password. |
| toolkit | 3x,4x | 3x | Htp toolkit used, 3x => WAS 3.x, 4x => OAS 4.x, Web DB or IAS 1.0 mod_plsql |
| compat | a value listed on compatlist parameter | 7x | Compatibilty mode Value defined into general/compatlist. |
| dbcharset,clientcharset | a valid charset | iso-8859-1 | Charset used by DBPrism to enable non-ascii input JServ or JSDK needs this - they don't detect parameters charset. |
| StateLess | true,false | false | If false, DB Prism calls dbms_session.reset_package procedure before a client procedure to warranty reset all packages variables and global states (OWS 3.0 behaviour and OWSKiller) In Oracle Lite support you has to write StateFull code in com.prism.polite.DBMS_Session class If true, don't call to Reset Session, and then, global variables of packages, for example, persist across differents http calls, this no warranty same connection objects to the same client for this purpose use Transactions and leave this parameter with the default value. |
| documentTable | a valid [schema.]table | owa_public.wpg_document | This table is used by the upload/download functionality to store the content. |
| docAccessPath | a valid [[schema.]package.]procedure_name | owa_public.wpg_testdoc.process_download | This procedure is called by the DBPrism gateway in order to set up the file to be downloaded. This procedure is called without argument. |
| defaultPage | a valid [[schema.]package.]procedure_name | wwwIndex.html | Defines which procedure is called if a subdirectory is given. |
| alwaysCallDefaultPage | true,false | false | Ignore package.procedure in the url call, DBPrism will call always to the defaultPage . |
| customAuthentication | none,global,perPackage,custom | none | This parameters replaces the old style custom authentication seted by OWA_CUSTOM or OWA initialize procedures. |
| type_owner,type_name,type_subname | a valid PLSQL Type | owa_public,owa_util,ident_arr | Type used to pass multivaluaded input forms or with flexible
parameter support this data type is only used with oracle 7x
database because it doesn't include the information in
user_arguments view.
type_owner is the user which has installed the toolkit type_name is the package which defines the sample table type type_subname is the sample table type defined to pass multivalued infomation. |
| debugHost,debugPort | a valid hostname,port | localhost,4400 | hostname and port where Oracle JDeveloper 9i/10g is listening for remote debugging using JPDA protocol only works with Oracle 9.2.0+ and JDeveloper 9.0.3+ Uncomment the above two parameters if you want to enable server side debug information of your PLSQL or Java. |
| nls_lang | a valid Oracle NLS string | empy string | Overrides NLS_LANG enviroment setting at the level of the DAD
DBPrism will excecute for each request (previous to populate the
CGI env)
SQL> alter session set NLS_LANGUAGE='AMERICAN' NLS_TERRITORY='AMERICA'; |
| useProxyUser | true,false | false | Enable SSO/JAAS authentication using Oracle Proxy
user support, see
Demo Page to know how to activate/use
it.
DAD username and password will be used to connect to the database, then the proxy user extracted from req.getUserPrincipal().getName() or req.getRemoteUser() is passed to the Connection using: ((OracleConnection)sqlconn).openProxySession(OracleConnection.PROXYTYPE_USER_NAME,proxyUserInfo); Note: JTADBPrismConnectionCacheImpl is required as connection cache manager for using proxy user support |
| flexibleEscapeChar | Any valid URL character | ! (mod_plsql syntax) | Character or String used as escape value for flexible parameter behaviour |
| xformEscapeChar | Any valid URL character | ^ (hat/caret, DBPrism 2.1.1 syntax) | Character or String used as escape value for XForm Request Wrapper |
| xformParamName | Any valued parameter name | post_xml (DBPrism 2.1.1 syntax) | Parameter name used to pass the HTTP Request parameters encoded as XForms Instance or sent into the HTTP Post input string |
| Name | Values | Default | Explanation |
|---|---|---|---|
| MinLimit,MaxLimit,LoginTimeout,CacheScheme | a valid Oracle Connection Cache values | 0,20,60,FixedWait | Defines Min/Max number of connection for an specific DAD also
defines how many second wait for a login sucefull and which scheme
uses for getting a new connection. Possible values:
Positive integers for Min, Max and TimeOut Dynamic, FixedNoWait and FixedWait for CacheScheme |
This work is licensed under a
Creative Commons License
.


