mod_plsql configuration file plsql.conf

Parameters in plsql.conf have to be configured manually

plsql.conf contains the LoadModule directive to load mod_plsql into the Oracle HTTP Server

The file specifies global settings for mod_plsql and include directives for dads.conf and cache.conf

The following parameters can be specified in plsql.conf:

PlsqlDMSEnable

Enables Dynamic Monitoring Service (DMS) in OEM for mod_plsql

Syntax:

PlsqlDMSEnable On

PlsqlDMSEnable Off

Default:

On

Example:

PlsqlDMSEnable On

PlsqlLogEnable

Enables debug level logging for mod_plsql

Debug level logging is meant to be used for debugging purposes only. When logging is enabled, log files are generated at:

Windows:

%ORACLE_HOME%\Apache\modplsql\logs\_DAD_name

UNIX:

%ORACLE_HOME%/Apache/modplsql/logs/_DAD_name

as configured by the PlsqlLogDirectory parameter in plsql.conf

This parameter should be set to "Off" unless recommended by Oracle support to debug problems with mod_plsql.

Syntax:

PlsqlLogEnable On

PlsqlLogEnable Off

Default:

Off

Example:

PlsqlLogEnable On

PlsqlLogDirectory

Specifies the directory where debug level logs are written out if PlsqlLogEnable is set to On

Set the directory name of the location where log files should be generated when logging is enabled. To avoid possible confusion about the location of this directory, an absolute path is recommended.

On UNIX, this directory must have write permissions by the owner of the child httpd processes.

Syntax:

PlsqlLogDirectory [directory]

Default:

None

Example:

PlsqlLogDirectory %ORACLE_HOME%/Apache/modplsql/logs

PlsqlIdleSessionCleanupInterval

Specifies the time (in minutes) in which the idle database sessions should be closed and cleaned by mod_plsql.

This directive is used in conjunction with connection pooling of database connections and sessions in mod_plsql. When a session is not used for the specified amount of time, it is closed, and freed. This is done so that unused sessions can be cleaned, and the memory is freed on the database side.

Setting this time to a low number helps in faster cleanup of unused database sessions. Be aware that if this number is too low, then this may adversely affect the performance benefits of connection pooling in mod_plsql

If the number of open database sessions is not a concern, you can increase the value of this parameter for best performance. In such a case, if the site is accessed frequently enough that the idle session cleanup interval is never reached for a session, then the DAD configuration parameter PlsqlMaxRequestsPerSession can be modified so that it is guaranteed that a pooled database session gets recycled on a regular basis.

For most installations, the default parameter value should suffice.

Syntax:

PlsqlIdleSessionCleanupInterval [number]

Default:

15 (minutes)

Example:

PlsqlIdleSessionCleanupInterval 15

Sample plsql.conf

LoadModule plsql_module %ORACLE_HOME%/Apache/modplsql/bin/modplsql.so
<IfModule mod_plsql.c>
  PlsqlLogEnable Off
  PlsqlLogDirectory %ORACLE_HOME%/Apache/modplsql/logs
  PlsqlIdleSessionCleanupInterval 15
  PlsqlDMSEnable On 
  include %ORACLE_HOME%/Apache/modplsql/conf/dads.conf
  include %ORACLE_HOME%/Apache/modplsql/conf/cache.conf
</IfModule>