|iSQL*Plus User's Guide and Reference
Part Number A88826-01
Configuring iSQL*Plus, 5 of 8
The Oracle HTTP Server and the iSQL*Plus Server are installed on the middle tier during Oracle9i installation. This section discusses configuration options for the middle tier. Specific topics discussed are:
The iSQL*Plus Server is installed during Oracle9i installation on the middle tier. You can:
You can create new connection identifiers for use in iSQL*Plus. The new definitions are made in the tnsnames.ora file on the middle tier machine which is running the iSQL*Plus Server.
To create a new connection identifier for iSQL*Plus
See the Oracle Net Services Administrator's Guide for more information about defining connection identifiers.
Timing out iSQL*Plus sessions frees up resources for other users. The timeout settings determine whether sessions will timeout, and how long before they timeout. By default, an iSQL*Plus session times out after 60 minutes. You can edit the iSQL*Plus configuration file, isqlplus.conf, to change the lines affecting the timeout behavior. The syntax of the two lines to change in the configuration file is:
Where n is the number of whole minutes of inactivity until the session times out. The default is 60.
When a user tries to use a timed out iSQL*Plus session, the Log In screen is displayed and the user is prompted to log in again. The iSQL*Plus timeout feature is independent of the Oracle HTTP Server keep alive settings.
iSQL*Plus uses a cascading style sheet to control the format of the user interface. You can replace the default style sheet with your own style sheet. It is recommended that you do not delete the default style sheet, but rename it so that you can revert to it if necessary.
To replace the default cascading style sheet
You can edit the Oracle HTTP Server configuration file to disable iSQL*Plus.
To disable the Oracle HTTP Server
Where ORACLE_HOME is the hard-coded path of your Oracle home directory.
To re-enable iSQL*Plus, reverse the edit to uncomment the include line in oracle_apache.conf.
Additional iSQL*Plus configuration information must be included in the Oracle HTTP Server configuration file, httpd.conf, for the iSQL*Plus Server.
There are two levels of include:
Changes are usually only made to:
After making changes to isqlplus.conf, the top level Oracle HTTP Server configuration file, httpd.conf, should be checked, and then the Oracle HTTP Server stopped and started to implement the configuration file changes.
To check the Oracle HTTP Server configuration file, httpd.conf, and any included configuration files for errors
Any errors in the configuration file are displayed. If there are any errors, edit the included configuration files, oracle_apache.conf or isqlplus.conf, again to correct them and then test again. If there are no errors, the message "Syntax OK" is displayed.
For changes to the Oracle HTTP Server configuration file, httpd.conf, and any included configuration files to take affect, you must stop and restart the Oracle HTTP Server if it is running. There is no convenient way to know how many users are currently accessing the server, so it is important to have the server down for the shortest time. When making changes to configuration files, use the
apache -t command to parse the httpd.conf configuration file and report any errors before starting and stopping the Oracle HTTP Server.
To stop and start the Oracle HTTP Server