Oracle 9i Application Server Using the PL/SQL Gateway Release 1 (v1.0.2.2) Part Number A90099-01 |
|
The following are the recommended and minimum requirements for installing and running the PL/SQL Gateway:
Operating Systems
Oracle Database
Web Listener
Web Browsers
Before you install the PL/SQL Gateway using the Oracle9i Application Server v1.0 Oracle Universal Installer, satisfy the following requirements:
To begin the Oracle Universal Installer, execute the runInstaller application located on your product CD or stage area. Follow the installation instructions, including choosing a directory where you want to install Oracle9i Application Server v1.0.2. This install directory is referred to as <ORACLE_HOME>.
After installation, manually install additional required packages using the owaload.sql script.
@owaload.sql log_file
If you were previously running Oracle9i Application Server or WebDB Listener 2.5 and below:
The PL/SQL Web Toolkit packages shipped with Oracle 8.1.7 and Oracle9i Application Server v1.0 are recommended for installation.
If the new PL/SQL Web Toolkit packages have been installed (either automatically or manually) and you were previously running OAS, note that the 8.1.7 install/upgrade or manual install for mod_plsql installs new PL/SQL Web Toolkit packages in the SYS schema. It also recreates PL/SQL Web Toolkit public synonyms to reference these new packages.
However, if you face problems while running the OAS PL/SQL Cartridge, recreate the older public PL/SQL Web Toolkit package synonyms.
To recreate the old public synonyms do the following:
drop public synonym OWA_CUSTOM; drop public synonym OWA_GLOBAL; drop public synonym OWA; drop public synonym HTF; drop public synonym HTP; drop public synonym OWA_COOKIE; drop public synonym OWA_IMAGE; drop public synonym OWA_OPT_LOCK; drop public synonym OWA_PATTERN; drop public synonym OWA_SEC; drop public synonym OWA_TEXT; drop public synonym OWA_UTIL; drop public synonym OWA_INIT; drop public synonym OWA_CACHE; drop public synonym WPG_DOCLOAD;
create public synonym OWA_CUSTOM for OWA_CUSTOM; create public synonym OWA_GLOBAL for OWA_CUSTOM; create public synonym OWA for OWA; create public synonym HTF for HTF; create public synonym HTP for HTP; create public synonym OWA_COOKIE for OWA_COOKIE; create public synonym OWA_IMAGE for OWA_IMAGE; create public synonym OWA_OPT_LOCK for OWA_OPT_LOCK; create public synonym OWA_PATTERN for OWA_PATTERN; create public synonym OWA_SEC for OWA_SEC; create public synonym OWA_TEXT for OWA_TEXT; create public synonym OWA_UTIL for OWA_UTIL; create public synonym OWA_INIT for OWA_CUSTOM; create public synonym OWA_CACHE for OWA_CACHE; create public synonym WPG_DOCLOAD for WPG_DOCLOAD;
If you have an OAS installation in which the new PL/SQL Web Toolkit packages were never installed and you use Oracle9i Application Server, it is recommended that you install the new PL/SQL Web Toolkit packages. If you continue using the older PL/SQL Web Toolkit packages, in order to use Oracle9i Application Server mod_plsql, you must run the following SQL statements
wpiutl.sql
wpgdocs.sql
wpgdocb.sql
These steps install the required packages needed to run mod_plsql with an older PL/SQL Web Toolkit package installation. In this configuration, you cannot use some of the new features in the PL/SQL Web Toolkit packages.
The Oracle9i Application Server installation creates configuration files that you can edit, including the following that affect the PL/SQL Gateway.
The apachectl starts and stops the Oracle HTTP Server. For UNIX, it is located at:
<ORACLE_HOME>/Apache/Apache/bin/apachectl
Inside this file, there are three parameters that affect the PL/SQL Gateway:
Note: To run the PL/SQL Gateway in another Oracle Home:
For UNIX platforms, change both the ORACLE_HOME and LD_LIBRARY_PATH settings. (For HP-UX, change SHLIB_PATH and for IBM, change LIBPATH settings.) For NT, change the PATH environment setting to <ORACLE_HOME>\bin.
This configuration file defines the behavior of Oracle HTTP Server (powered by Apache). You can set your port number as well as other server settings. It is located at:
<ORACLE_HOME>/Apache/Apache/conf/httpd.conf
This configuration file describes settings for the PL/SQL Gateway module. It is located at:
<ORACLE_HOME>/Apache/modplsql/cfg/plsql.conf
There settings are configurable:
This main configuration file describes settings for the PL/SQL Gateway module. For UNIX, it is located at:
<ORACLE_HOME>/Apache/modplsql/cfg/wdbsvr.app
For NT, it is located at:
<ORACLE_HOME>\Apache\modplsql\cfg\wdbsvr.app
It contains all the DAD information. Most of the settings can be edited by using the PL/SQL Gateway Configuration page, which you can access through your browser as shown "Accessing the PL/SQL Gateway Configuration page".
This section describes several Oracle HTTP Server powered by Apache settings to improve performance.
For all static files served by the server (images, static pages, etc.), use mod_expires to cache in the browser. This improves performance by having the browser retrieve the files from the cache, avoiding contacting the server for static files which do not change often.
Mod_expires uses expires-based caching technique. You set the time period that the files are valid for. Do this by using the ExpiresActive, ExpiresDefault, and ExpiresByType directives. Refer to www.apache.org to search for these directives and their usage.
For example:
To have a directory of static files cached by the browser when they are served, the directives would be:
Alias /images/ "/iAS/staic_images/" <Directory "/iAS/static_images/"> AllowOverride None Order allow, deny Allow from all ExpiresActive On ExpiresDefault "access plus 8 hours" </Directory>
The browser will cache the material for 8 hours if any of the content in the /iAS/static_images directory is served.
Another family of directives you can use to fine tune performance are the KeepAlive, MaxKeepAliveRequests, and KeepAliveTimeout directives.
These directives tells the server when to destroy a connection between itself and the browser. Since connection establishment is time consuming, this can improve response time if the connection is already established. The default settings are:
Directive | Default |
---|---|
KeepAlive |
On |
MaxKeepAliveRequests |
100 |
KeepAliveTimeout |
15 seconds |
Adjust these settings to achieve better performance. Refer to www.apache.org for more information.
For all errors generated by the PL/SQL Gateway, you can customize them to have the same look and feel of your application.
ErrorDocument 500 /error_500.html
This tells the Oracle HTTP Server to serve the error_500.html file when it encounters a 500 HTTP status code from the PL/SQL Gateway.
ErrorDocument 403 /error_403.html
ErrorDocument 403 /cgi-bin/gen_error.pl
This tells the Oracle HTTP Server to execute the perl script called gen_error.pl under the virtual path cgi-bin. For example:
<Location /pls> SetHandler pls_handler Order deny, allow Allow from all ErrorDocument 500 /error_500.html ErrorDocument 403 /cgi-bin/gen_error.pl </Location>
In this example, any 500 errors from the PL/SQL Gateway will be handled by serving the error_500.html located in the root virtual path. Any 403 errors will be handled by executing the gen_error.pl perl script in the cgi-bin virtual path. For more information about the ErrorDocument directive, refer to Apache's website www.apache.org.
To access to the PL/SQL Gateway Configuration page, enter the following URL in your Web browser:
http://<hostname>:<port>/pls/DAD/<admin_path>/gateway.htm
Parameter | Description |
---|---|
hostname |
The machine where the application server is running. |
port |
The port where the application server is listening. If omitted, port 80 is assumed. |
admin_path |
The URL path element that identifies an admin page. The default is admin_. For example, if you use the default of admin_, the following URL invokes the PL/SQL Gateway configuration page if the invoking user is listed in the administrators configuration setting: http://www.myserver.com/pls/admin_/gateway.htm Configuration settings are protected by the Administrators setting of the configuration file. Refer to "Configuring the PL/SQL Gateway" for more information. |
The Oracle HTTP Listener configuration file includes the modplsql configuration file plsql.conf. The contents of plsql.conf are:
# Directives added for the PL/SQL Gateway
For UNIX:
LoadModule plsql_module <ORACLE_HOME>/Apache/modplsql/bin/modplsql.so
For HP-UX:
LoadModule plsql_module <ORACLE_HOME>/Apache/modplsql/bin/modplsql.sl
For NT:
LoadModule plsql_module<ORACLE_HOME>\bin\modplsql.dll
For all:
# Enable handling of all virtual paths beginning with "/pls" by mod-plsql # <Location /pls> SetHandler pls_handler Order deny,allow Allow from all </Location>
To start the Apache listener, type:
<ORACLE_HOME>/Apache/Apache/bin/apachectl start
To start the Apache listener with SSL support, type:
<ORACLE_HOME>/Apache/Apache/bin/apachectl startssl
To stop the Apache listener, type:
<ORACLE_HOME>/Apache/Apache/bin/apachectl stop
On Windows NT, the Oracle HTTP Server is installed as a service. To start the Oracle HTTP Server with SSL support:
To stop the Oracle HTTP Server:
|
![]() Copyright © 2001 Oracle Corporation. All Rights Reserved. |
|