3.13 Enabling Event Logging
If you want to enable event logging, you are required to include the <RDML TRACE> tag in either your process specific layout page (<process_name>_LAYOUT) or the default layout page (DEFAULT_LAYOUT). If you do not have a process specific layout page, it is suggested that you create your process specific layout page with a copy of the contents of the default layout page.
Enabling event logging using the layout pages permits you to have tracing over the entire application. By doing so, it is possible to tell how long a user has been using your application. Alternatively, you may enable logging over specific pages. This is done by putting <RDML TRACE> at the top of each your HTML pages.
The <RDML TRACE> tag is used to instruct LANSA for the Web to look up the trace page and determine which level of tracing is to be applied to your application. The appropriate tracing information will be written to the relevant files depending on the keywords specified in the trace file.
When determining the level of tracing, LANSA for the Web looks up either the process specific trace page (<proces_ name>_TRACE) or the default trace page, DEFAULT_TRACE. This trace file must only contain a single line with either TRACE_SUMMARY or TRACE_DETAILED as the keyword. Note that the keyword is in upper case.
The TRACE_SUMMARY keyword indicates that you only want to log summary information and the logging information is stored in the DC@W26 (summary) file. This is a default keyword in the DEFAULT_TRACE page. A new trace identifier is assigned for each process or procfun request made.
The TRACE_DETAILED keyword extends on the summary level tracing permitting you to log user defined fields. The detailed information is kept in the DC@W27 (detailed) file. This file contains information on how each of the pages was accessed for each trace identifier.