plsql.conf Configuration Files for mod_plsql

3-10 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server ■ PlsqlLogEnable ■ PlsqlLogDirectory ■ PlsqlIdleSessionCleanupInterval PlsqlDMSEnable Enables Dynamic Monitoring Service DMS for the mod_plsql module. PlsqlLogEnable Enables debug level logging for the mod_plsql module. Debug level logging is meant to be used for debugging purposes only. When logging is enabled, Oracle HTTP Server log files are typically created in the ORACLE_INSTANCE diagnosticslogsOHSohs_name directory. However, the location specified in PlsqlLogDirectory determines the final location. This parameter should be set to Off unless recommended by Oracle support to debug problems with the mod_plsql module. To view more details about the internal processing of the mod_plsql module, set this directive to On. This causes the mod_plsql module to start logging every request that is processed. The log files are generated as specified by the PlsqlLogDirectory directive. PlsqlLogDirectory Specifies the directory where debug level logs are written. 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. Category Value Syntax PlsqlDMSEnable {On | Off} Default On Example PlsqlDMSEnable On Category Value Syntax PlsqlLogEnable {On | Off} Default Off Example PlsqlLogEnable Off Category Value Syntax PlsqlLogDirectory directory Default None Example PlsqlLogDirectory ORACLE_ INSTANCEdiagnosticslogsOHSohs_name Understanding Oracle HTTP Server Modules 3-11 PlsqlIdleSessionCleanupInterval Specifies the time in minutes in which the idle database sessions should be closed and cleaned by the mod_plsql module. This directive is used in conjunction with connection pooling of database connections and sessions in the mod_plsql module. 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. If this number is too low, then this may adversely affect the performance benefits of connection pooling in the mod_plsql module. 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 value is adequate.

3.9.2.2 dads.conf

The dads.conf file contains the configuration parameters for the PLSQL database access descriptor. See Table 3–1 for the file location. A DAD is a set of values that specifies how the mod_plsql module connects to a database server to fulfill a HTTP request. The following parameters are used with the dads.conf file: ■ PlsqlAfterProcedure ■ PlsqlAlwaysDescribeProcedure ■ PlsqlAuthenticationMode ■ PlsqlBeforeProcedure ■ PlsqlBindBucketLengths ■ PlsqlBindBucketWidths ■ PlsqlCGIEnvironmentList ■ PlsqlConnectionTimeout ■ PlsqlConnectionValidation ■ PlsqlDatabaseConnectString ■ PlsqlDatabasePassword ■ PlsqlDatabaseUserName ■ PlsqlDefaultPage ■ PlsqlDocumentPath ■ PlsqlDocumentProcedure Category Value Syntax PlsqlIdleSessionCleanupInterval number Default 15 minutes Example PlsqlIdleSessionCleanupInterval 10 3-12 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server ■ PlsqlDocumentTablename ■ PlsqlErrorStyle ■ PlsqlExclusionList ■ PlsqlFetchBufferSize ■ PlsqlInfoLogging ■ PlsqlMaxRequestsPerSession ■ PlsqlNLSLanguage ■ PlsqlPathAlias ■ PlsqlPathAliasProcedure ■ PlsqlRequestValidationFunction ■ PlsqlSessionCookieName ■ PlsqlSessionStateManagement ■ PlsqlTransferMode ■ PlsqlUploadAsLongRaw PlsqlAfterProcedure Specifies the procedure to be invoked after calling the requested procedure. This enables you to put a hook point after the requested procedure is called. This is useful in doing SQLTracesSQL Profiles while debugging a problem with the requested procedure. This is also useful when you want to ensure that a specific call is made after running every procedure. ■ This parameter should only be used for debugging purposes. In addition, you could use this parameter to stop SQL traceSQL profiling. PlsqlAlwaysDescribeProcedure Specifies whether the mod_plsql module should describe a procedure before trying to run it. If this is set to On, then the mod_plsql module will always describe a procedure before invoking it. Otherwise, the mod_plsql module will only describe a procedure when its internal heuristics have interpreted a parameter type incorrectly. ■ This parameter should only be used for debugging purposes. Category Value Syntax PlsqlAfterProcedure string Default None Example PlsqlAfterProcedure portal.mypkg.myafterproc Category Value Syntax PlsqlAlwaysDescribeProcedure {On | Off} Default Off Example PlsqlAlwaysDescribeProcedure On