Types of TIBCO iProcess Objects Server Logs

Copyright © Cloud Software Group, Inc. All rights reserved.

Chapter 3 TIBCO iProcess Objects Server Log : Types of TIBCO iProcess Objects Server Logs

Types of TIBCO iProcess Objects Server Logs

The TIBCO iProcess Objects Server log is available in two different formats: on-disk and in-memory. These are described below.

On-Disk Log File

This is the “standard” way of recording TIBCO iProcess Objects Server messages. The messages are written to a file on the hard disk and are available via a text editor.

The on-disk TIBCO iProcess Objects Server log is always “turned on” (as opposed to the in-memory log, which can be turned on or off — see below). The primary controller of the amount of information that is written to the on-disk TIBCO iProcess Objects Server log is the setting of the log level. The log level can be set so that only error-level messages (the fewest) are written to the log, or it can be set so that debug-level messages (the greatest amount) are written to the log. You can also control the size of the log file, the types of categories that are written to the log, etc. These are described in the following subsections.

In-Memory Log File

This method of storing log messages allows you to specify that they be stored in memory during server operations, rather than on disk; the log is written to disk if the server terminates abnormally (crashes). This method of TIBCO iProcess Objects Server logging can be used if the performance impact of using the “standard” on-disk logging is too great (especially when logging at the debug level).

In-memory logging is available only if your TIBCO iProcess Objects Server has CR 14205 implemented.

This method of logging is turned off by default. To turn it on, you must do the following:

•

Windows - Check the Enable Memory Logging check box on the Memory Log tab using the TIBCO iProcess Objects Server Configuration Utility. This then enables the rest of the selections on the tab so you can set the in-memory log level and categories.

•

UNIX - Set the MemLogLevel TIBCO iProcess Objects Server configuration parameter to a value from 1 (error level) to 4 (debug level). A setting of zero disables in-memory logging.

For more information, see the MemlogLevel parameter on MemLogLevel

Writing the In-Memory Log to Disk

The following describes the ways in which the in-memory log is written to disk (if in-memory logging is enabled):

•

If TIBCO iProcess Objects Server crashes, an attempt is made to automatically write the in-memory log to a file.

This only occurs if the "auto dump" feature has been turned on in the engine (using the PROCESS_AUTO_DUMPLOG process attribute). If auto dump is enabled (the default), the contents of the processes’ debug shared memory segment is written to disk when that process fails.

For more information, see TIBCO iProcess Engine Administrator’s Guide.

•

You can manually write the in-memory log to a file using the swsvrmgr DUMPLOG command (even when the server is still running). The syntax is:

swsvrmgr DUMPLOG [<MachineName>|<MachineID>[<ProcessName>[<ProcessInstance>]]]

Note that if the server crashes, and the log cannot be written to a file for some reason, the shared memory containing the log may still exist. If the shared memory still exists, you can manually write the in-memory log to a file using the swsvrmgr DUMPLOG command shown above.