mod_plsql provides a Web page for configuring Database Access Descriptors (DADs). A DAD is a set of values that specify how mod_plsql connects to a database server to fulfill an HTTP request.
|
Global Settings |
|
|
Default Database Access Descriptor (DAD) |
Specify a path that points to the default DAD. If the end user enters a URL without specifying the DAD name, the home page for the default DAD will be displayed.
Default = none You can change the DAD name by typing a new one in this field.
|
|
Administrators |
Specifies who can view the admin pages. By default, this is set to ALL which means anyone can view the admin pages. This should be changed to a comma separated list of users to enforce security on the admin pages, for example scott, mike where scott and mike are local database user names. Or, scott, mike@orcl where orcl is a connect string for a remote database.
Note This setting is accessible through the configuration file only, not through mod_plsql Web page.
|
|
Admin Path |
Specifies the URL path element that identifies an admin page. This should normally be left unchanged as /admin_/.
Note This setting is accessible through the configuration file only, not through mod_plsql Web page.
|
|
Database Access Descriptor Settings |
|
|
Database Access Descriptor Name |
Displays the name for this DAD. The name is set at installation time or during creation of new web sites. You can change the name by typing a new one in this field.
|
|
Oracle User Name |
Displays the Oracle database account user name. The user name is typically set at installation or during creation of new web sites. You can change it by typing a new name in this entry field.
|
|
Oracle Password |
Displays the Oracle database account password. The password is typically set at installation, but you change it by typing a new password in this entry field.
Notes The Oracle User Name and Password are the default user name and password for logging in to a Web site or page. If you leave the Oracle User Name and Oracle Password entry fields blank, the user will be prompted to enter a user name and password when first logging in.
|
|
Oracle Connect String |
Enter a SQL*Net alias if you are using a remote database. Leave this field blank if the database is local.
|
|
Authentication Mode |
This parameter can be set to one of the following values:
- Basic - authentication is performed using basic HTTP authentication. Most applications will use Basic authentication.
- Global Owa - authorization id performed in the OWA package schema.
- Custom Owa - authorization is performed using packages and procedures in the user's schema, or if not found, in the OWA package schema
- PerPackage - authentication is performed by packages and procedures in the user's schema
- Single Sign-On - authentication is performed using the Oracle Single Sign-On feature of the Login Server. You can use this mode only if your application is is set up to work with the Login Server.
|
|
Session Cookie Name |
Enter a session cookie name only for Oracle Portal 3.X installations that participate in a distributed environment. |
|
Create a Stateful Session? |
Choose Yes to preserve the database package/session state for each database request. Choose No to reset it after each request. For mod_plsql, this parameter must be set to No. |
|
Keep Database Connection Open Between Requests? |
Choose whether, after processing one URL request, the database connection should be kept open to process future requests. In most configurations, choose Yes for maximum performance.
The mod_plsql cleanup thread cleans up database sessions that have not been used for 15 minutes. |
|
Maximum Number of Open Connections |
Enter the size of the connection pool. This is the maximum number of database connections kept open at one time for this DAD. If a request for another connection comes in after the maximum number is reached, one of the connection is closed to serve this request.
Tip You'll need to adjust this number depending on your server, its capacity, and the number of connected users. As a rule of thumb, set this number at between 5 and 20 at a medium sized installation (approximately 200 users).
Notes
- This field is ignored when the Unix Oracle HTTP Server (powered by Apache) is used with mod_plsql. In a Unix configuration, each server process keeps one database connection pooled for each DAD. Thus, the maximum number of Oracle HTTP Server (powered by Apache) processes currently alive is the maximum size of the connection pool for each DAD. If the number of processes grows, the pool size grows, and the Gateway creates new connection. When a process dies, connections are closed. The maximum number of server processes can be configured through Oracle HTTP Server (powered by Apache) Configuration files.
- When NT Oracle HTTP Server (powered by Apache) Server is used with mod_plsql, configuration files govern the maximum number of threads that will simultaneously be serving requests. The Maximum Number of Open Connections field governs the maximum number of connection that can be kept open. Therefore, to ensure correct behavior on NT, specify a value that is equal to maximum number of threads specified in the Apache server configuration file. If this number is smaller, some requests may be rejected if threads are idle to serve but maximum connection limit has already been reached.
|
|
Keep Database Connection Open Between Requests
|
Choose whether, after processing one URL request, the database connection should be kept open to process future requests. In most configurations, specify Yes for maximum performance. |
|
Default (Home) Page |
Enter the PL/SQL procedure that will be invoked when none is specified as part of the URL itself. For example, if you specify a default home page of myapp.home and an end user enters this URL in a browser:
http://myapp.myserver.com:2000/pls/myapp/
will automatically update the URL to:
http://myapp.myserver.com:2000/pls/
myapp/myapp.home
|
|
Document Table |
Enter the name of the database table into which files uploaded to a web site created with will be stored. The default value in this entry field is based on the name of the schema in which you created the site.
|
|
Document Access Path |
Enter a path in the URL installation that is used to indicate a document is being referenced. In the following URL, for example:
http://myapp.myserver.com:2000/pls/my_site/
docs/folder1/presentation.htm
docs is the document access path.
|
|
Document Access Procedure |
Enter the procedure that will be used to upload and download documents.
|
|
Extensions to be Uploaded as LONGRAW
|
Specify extensions for files to be uploaded as LONGRAW. |
|
Path Alias |
To be used by PL/SQL applications for path aliasing.
WebDB 2.X Note You must leave this field blank if the DAD is for an existing WebDB 2.x Web site.
|
|
Path Alias Procedure |
To be used by PL/SQL applications for path aliasing.
WebDB 2.X Note You must leave this field blank if the DAD is for an existing WebDB 2.x Web site.
|
