CSP Gateway Configuration Guide - InterSystems Documentation

CSP Gateway Operation and Configuration
2.1.5 Viewing the Event Log
Use the View Event Log option from the Main Menu to read the contents of the Event Log.
Each log entry is marked with a header record which captures the date, time and additional information with respect to the
context in which the log entry was made.
Example:
>>> Time: Wed Jul 26 15:40:57 2006; RT Build: 664.896 (win32/isapi);
Log-Level: 9; Thread-Id: 2236; Connection-No: 0; Server: LOCAL;
Server-PID: 3028; Page: GET /csp/samples/menu.csp
Click Clear Log to clear all current entries from the Event Log.
The Log can be displayed in either ascending date/time order (the default) or descending date/time order. Click the hyperlink
at the top right-hand corner of the form to reverse the display order. This hyperlink acts as a toggle between the two modes.
Finally, most browsers are unable to render more than about 1MB of log data in a single form. Therefore, as the volume
of log data returned approaches 1MB the Gateway terminates the display and prompt for the next page of data (see the
More hyperlink at the bottom left-hand corner of the form). Additionally, a Top hyperlink is provided at the bottom righthand
corner of the form to allow you to quickly go back to the first form in the series.
2.1.6 Viewing HTTP Trace
The HTTP trace facility builds on the Event Log information already captured for log levels v9 (record raw HTTP request)
and v9r (record both HTTP request and response). The trace is accessed via the View HTTP Trace option.
The trace window consists of two main frames. The left-hand frame contains a list of HTTP requests processed by the
Gateway by time and a unique request ID (assigned by the Gateway). As each request is clicked, the request and response
data is shown in the right-hand frame. Hyperlinks allow easy navigation between the request and response message.
The request listing is automatically refreshed every few seconds (currently 7) so that the overall effect is of a real-time
monitor operating in much the same way as a proxy such as TCPTrace.
Note:
Note that the HTTP request headers reported by the Gateway are reconstituted because the hosting web server
always assumes responsibility for parsing the request headers. The Gateway reassembles the complete header
from the CGI environment variables supplied by the web server. However, if a request is passed directly through
the NSD component (that is, effectively by-passing the web server) then the request header recorded is byte-forbyte
the same as it was when dispatched from the client.
2.1.7 Configuring Default Parameters
The Default Parameters option on the CSP Web Management page menu provides you with a mechanism for maintaining
the global (system-wide) configuration parameters for the CSP Gateway. Note that you must be a system manager to use
this option.
When you configure access to a particular Caché Server, any unspecified optional parameters and/or custom system forms
are automatically inherited from the global configuration. For example, if you do not set a Server Response Timeout
parameter for a specific server, that server inherits the global Server Response Timeout setting.
The Default Parameters are made up of up to three components:
1. CSP Gateway
2. Security
3. Connections to Caché
16 CSP Gateway Configuration Guide