Bookshelf v7.5: Configuring Server Logging Levels

You can specify the level of logging to the server hhsync.*.log files by setting the LoggingLevels parameter in the [PDA] section of the .cfg file. By default, the parameter is set to the following:

Generally, you should start with the default values. These values work for most customers and were selected to optimize performance. If you are experiencing problems with the application, change the logging levels to 77777 to capture additional diagnostic information. Performance degrades slightly as you increase the logging levels, but in most instances, this is not discernible. Once the problem is resolved, reset the logging levels to their default values.

The different types of log records are described in Table 17 and correspond to the following format: LoggingLevels = emdts.

Table 17. Types of Log Records
Log Record	Description
e	Transaction events captured and returned to the client application as error messages
m	Log records created by the metadata extractor
d	Log records created by the database extractor
t	Log records created by the transaction processor
s	Log records created by the mainline synchronization code

Each type of log record (emdts) can be set to one of the logging levels described in Table 18:

Table 18. Logging Levels
Logging Level	Description
0	Suppress all log records
1	Process Critical records only
2	Process Critical and Error records only
3	Process Critical, Error, and Warning records only
4	Process Critical, Error, Warning, and Information records only
5	Process Critical, Error, Warning, Information, and Debug records

Figure 8 shows the default settings for the LoggingLevels parameter. The parameter specifies both the type of log record and the logging level. The figure describes the logging levels for the default setting.

CAUTION: The maximum level for transaction events (e) is 2. It is recommended that you do not lower the value for logging transaction events. If the transaction events level is set to 0 or 1, transaction error messages are not sent to the client, and transactions will silently fail.

NOTE: The salesceqbe.txt that is shipped with the application does not include a [PDA] section. What this means is that the defaults for all PDA parameters apply. For example, the default setting of 23333 applies for the LoggingLevels parameter. If the LoggingLevels parameter or any other PDA parameter needs to be changed, administrators can add this section to the end of the file and manually enter the parameter.