Analyzing FOCUS Database Server Activity

In this section:

x

FOCUS Database Server (FDS) is a listener that enables multiple users (or multiple agents) to update central a FOCUS database simultaneously. Database transaction events are logged to the HLIPRINT log file (hliprint.log), which is created in the server directory.

You can view the first 50,000 lines of the log file from the Web Console. If you wish to view lines beyond 50,000, you can open or save the file in a text editor.

x


Top of page

x
Controlling the HLIPRINT Transaction Log

How to:

You can control the size of the HLIPRINT transaction log by using the hliprint_max_lines parameter in the configuration file, edaserve.cfg. The parameter defines the maximum number of lines to be included in hliprint.log before it is archived and a new hliprint log is started.

Each time the line limit is reached, the current HLIPRINT log file is archived to HLIPRI01 and the new file starts with an additional identification line. This line indicates that the file was truncated and looks like the following:

continued from hlipri01

Archiving also takes place the first time the FDS listener is activated and the HLIPRINT log from the previous run is found in the server directory.



x
Procedure: How to Control the Size of the HLIPRINT Log From the Web Console
  1. From the menu bar, select Workspace.
  2. Expand the Special Service and Listeners folder in the navigation pane.
  3. Right-click FDS, and select Properties.

    The Special Services Configuration page opens.

  4. Expand the Advanced section by clicking the arrow.

  5. Enter a value for:
    hliprint_max_lines

    Is the maximum number of lines to include in the hliprint.log before it is archived and a new hliprint log is started. You can limit the size of the log file by setting the maximum number of lines to a value other than zero. (0 means an unlimited number of lines can be included in the file.)

    There is no minimum, but the recommended value is at least 1000 lines. If the limit is too low, the FDS listener may experience performance problems due to excessive archiving.

  6. To register this setting, click Save.

Top of page

x
Controlling HLIPRINT Output

The Server Administrator can control hliprint.log output by manually adding the EDAHLIP variable, with a value, to the edaserv.cfg file, in the form edahlip=value where valid values are:

Setting

Description

none

No hliprint.log is created. Turning logging off will increase performance, however, this is not recommended, because it makes it harder to diagnose problems.

echo

The hliprint.log is created and contains basic transaction information (one line per transaction; line length 80 characters).

stat

The hliprint.log is created and contains basic transaction plus timing information (one line per transaction; line length is 133-characters).

The default value is stat.


iWay Software