1
Using mod_plsql

1.1 Oracle Database Requirements

The following are the recommended and minimum requirements for the Oracle database when using mod_plsql:

• Oracle8i or higher

  Note: mod_plsql requires the Oracle 9.0.1.2 client libraries to be installed in the same Oracle Home as mod_plsql. If these libraries are installed, you can still run mod_plsql against remote Oracle 8i or above databases.

• For 8i databases, verify you are on the correct path set.

• For Solaris, the database must have the following patch sets:
  • 8.1.6.3 or higher for 8.1.6 databases

  • 8.1.7.2 or higher for 8.1.7 databases

• For Windows NT, you need:
  • 8.1.6.3.1 or higher for 8.1.6 databases

  • 8.1.7.1.1 or higher for 8.1.7 databases

1.2 Before you begin

Before you install mod_plsql using the Oracle9i Application Server Oracle Universal Installer, satisfy the following requirements:

• You must have a SYS user password on the database where you plan to load PL/SQL Web Toolkit packages required by mod_plsql.

• The database to which you plan to connect mod_plsql must be up and running.

• You must have enough disk space on the machine where you plan to run the Oracle Universal Installer.

• You must have write permissions to the directory where the Oracle Universal Installer is writing its oraInventory data.

1.3 Installing Required Packages

After installation, manually install additional required packages using the owaload.sql script.

Note: Even if a full database export is made with the Export utility you still must reinstall mod_plsql in the new target instance via running the OWALOAD.SQL script as SYS. Objects in SYS are not imported with the Import/Export mechanism, and the PL/SQL toolkit has to be installed in SYS.

1. Navigate to the directory where the owaload.sql file is located. This directory is <ORACLE_HOME>/Apache/modpsql/owa.

2. Using SQL*Plus, log into the Oracle database as the SYS user.

3. If you think other OWA packages exist in SYS, run the following query to produce a list of all instances of the OWA packages

   'select object_name, owner from all_objects where object_name like HTP%'; 
   

   If multiple instances are detected in other schemas, deinstall other versions before installing the OWA packages.

4. At a SQL prompt, run the following command:

   @owaload.sql log_file  
   

   Table 1-1 Installing Required Packages Parameters

   Elements	Description
   owaload.sql	Installs the PL/SQL Web Toolkit packages into the SYS schema. It also creates public synonyms and makes the packages public so that all users in the database have access to them. Therefore, only one installation per database is needed.
   log_file	The installation log file. Make sure that you have write permissions to create the log file

5. Scan the log file for any errors.

   Note: The owaload script checks the existing version of the owa packages in the database and installs a new version only if: No OWA package exists or, Older OWA packages were detected. If your database already has the latest OWA packages or has a newer version installed, the owaload script does nothing and reports this in the log file.

6. Do a manual recompile.

   Note: Installing the OWA packages invalidates all dependent objects. These packages automatically recompile on first access, but a manual recompile is recommended after the reinstallation.

7. After the install, check the version of the OWA packages by running "Select owa_util.get_version". Confirm that the version shown is 9.0.2.1.0 or above.

1.3.1 Upgrading from Oracle9i Application Server or WebDB Listener

If you were previously running Oracle9i Application Server or WebDB Listener 2.5 and below:

1. Verify there is no user data (other than the PL/SQL Web Toolkit packages) in the schema.

2. Drop the schema where the old PL/SQL Web Toolkit packages were installed.

3. Install the new PL/SQL Web Toolkit as per "Installing Required Packages" .

1.4 Accessing the mod_plsql Configuration page

All monitoring and configuration takes place through the Oracle Enterprise Manager (OEM) tool. The mod_plsql monitoring and configuration is accessible through links within the HTTP Server components and the Portal.

Note: Refer also to the Online Help available through the Oracle Enterprise Manager tool for mod_plsql and DAD Configuration.

To get to the mod_plsql configuration pages navigate to the applicable Application Server through OEM. You can access the pages either through a portal instance or through the link in the HTTP server instance.

1.4.1 Access the DAD Configuration pages through OEM

1. Enter the following URL in the web browser:
   http://<hostname>:<port_number>

   Note: 1810 is the default port.

2. Enter the Oracle9i Application Server administrator username and password. The default username for administrator user is ias_admin. The default password is defined during the installation of Oracle9iAS.

3. Click OK.

4. Select Oracle9i Application Server instance with the mod_plsql that needs configuring.

5. Select the HTTP Server link or the Portal instance.

6. Select mod_plsql component or link.

7. Scroll down to DAD Status section.

8. Click Create to set up a new DAD or select the DAD you are interested in and click Edit.

1.4.2 Access the DAD Configuration pages through Portal

1. Log on to Portal.

2. Click the Builder icon.

3. Access the Administrator tab.

4. Click Portal Service Monitoring link in the Services portlet.

5. Click mod_plsql Services in the Portal Components section.

6. Scroll down to DAD Status section.

7. Click Create to set up a new DAD or select the DAD you are interested in and click Edit.