HPlogo HP Driver for JDBC User's Manual: HP 3000 MPE/iX Computer Systems > Appendix C HP JDBC Server

HP JDBC Server Configuration File

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Index

The following example shows the standard HP JDBC Default Server configuration file. This is a text file that resides on the server host in the same directory as the HP JDBC Server executable files and can be used to alter some of the server's behavior. On HP-UX the name of the default server configuration file is servcfg, and it is located in /opt/allbase/jdbc/bin. On MPE/iX the name of the default server configuration file is SERVCFG and it is located in JDBC.SYS.

LOGFILE /opt/allbase/jdbc/logs/servlogTIMEOUT 7200#LOGGING ERROR#LOGGING CONNECTION#LOGGING INFO#LOGGING WARNING#LOGGING FATAL#LOGGING IN#LOGGING OUT#LOGGING INHEX#LOGGING OUTHEX#LOGGING DEBUG#LOGGING TIMESTAMPLOGGING NONE# If LOGGING NONE is not commented out, it must be the# last line for it to have the desired effect.

The first configuration option LOGFILE refers to the path and filename for the HP JDBC Server log file. On HP-UX this is normally set to /opt/allbase/jdbc/logs/servlog. On MPE/iX this is normally set to SERVLOG.JDBC.SYS.

The second configuration option TIMEOUT specifies the number of seconds that the HP JDBC Server can remain idle before terminating. This idle time is the time between the returning of a result to the client and the submission of the next client request. It does not include database processing time. If this value is not provided, or is set to 0, the timeout will be set to an infinite value.

The next set of lines are the LOGGING levels used to determine the type of information to be logged to the server log file. The meanings of the various logging levels is discussed in the Troubleshooting section, under Server Logging. The logging levels can be turned on and off by either commenting the line out, or uncommenting the line. If the last line is LOGGING NONE, and the line is not commented out, all logging is turned off.

The server configuration file is read in anew each time a new server process is started. Thus once the file is edited and saved, the changes will take place beginning with the next server process. Existing server processes cannot be made to reread the configuration file.

NOTE: This is the default server configuration file, meaning that all server processes use the same configuration file. Thus, if logging is turned on in this file, it will be in effect for all subsequent server processes.
Feedback to webmaster