Configuring Debug Settings for iProcess® Director

Note: This panel is active only if at least one instance of iProcess Director exists on any of the machines in a cluster. Otherwise, the panel is disabled.

To write a debug log file for iProcess Objects Director, perform the following steps:

1. On the iProcess Director panel, click the Add icon .
An Add New Debug Settings dialog box is displayed.
2. On the Add New DIRECTOR Debug Settings dialog box, enter the values for the following fields.

iProcess Director Debug Settings

Field

Description

Machine ID

The unique identifier of the server. Specify 0 to include all nodes in a node cluster.

Process Instance

The instance of the process for which you want to create a debug log file. Specify 0 to include all instances in the specified node or nodes.

DIRECTOR Debug Parameter

You can choose the parameters for which you want the debug information logged. For a list of debug parameters and their description, see iProcess Director Debug Parameters.

Debug Setting Value

This value indicates the level of detail that is included in the debug log.

iProcess Director Debug Parameters

Parameter

Description

LOG_FILE_MAX_SIZE

Maximum size in MB of TIBCO iProcess Objects Director log file before it is rolled over.

You can specify a file size in MB from 1 to 9999. The default is 15.

LOG_FILE_MAX_ARCHIVES

Maximum number of archived log files created if the log rolls over.

You can specify a file size in MB from 0 to 9999. The default is 0 which means archives are not logged.

LOG_LEVEL

Level of information written to TIBCO iProcess Objects Director log file.

The log levels are hierarchical, from the least amount of information to the most, with each higher level including the information from the levels following it. The default log level is Warning.

You can specify a value from one of the four values listed here:

• Value: 1
Log Level: Error
• Value: 2
Log Level: Warning
• Value: 3
Log Level: Informational
• Value: 4
Log Level: Debug

Warning: Unless directed by TIBCO Support, the log level should be specified as “Error” or “Warning.” Setting the level to “Debug” causes an extremely large number of messages to be written to the log file. This causes the performance and response time of iProcess Objects Server to be seriously degraded. It also causes the possibility of critical error messages being lost if the log file fills up and rolls over.

LOG_CATEGORIES

A set of bit flags to indicate which logging areas should be switched on. Note that request/response messages are written to the log, if the LOG_LEVEL attribute is set to 4 (Debug), regardless of the setting of this attribute.

You can select from one of the following values. The default is 0xFFFFFFF which means information from all categories is logged.

• 0xFFFFFFFF - LOGCAT_ALL
• 0x00000001 - LOGCAT_MAIN_THREAD
• 0x00000002 - LOGCAT_STATUS_UPDATE_THREAD
• 0x00000004 - LOGCAT_PERIODIC_STATS_THREAD
• 0x00000008 - LOGCAT_STATS_SEND_THREAD
• 0x00000010 - LOGCAT_STATS_RECV_THREAD
• 0x00000020 - LOGCAT_RECV_UDP_THREAD
• 0x00000040 - LOGCAT_MESSAGE_SEND_THREAD
• 0x00000080 - LOGCAT_MESSAGE_RECV_THREAD
• 0x00000100 - LOGCAT_GET_ONE_NODE
• 0x00000200 - LOGCAT_GET_ALL_NODES
• 0x00000400 - LOGCAT_LOAD_BALANCE_THREAD
• 0x01000000 - LOGCAT_LOG
• 0x02000000 - LOGCAT_SAL_TIMING

Warning: Do not change this parameter unless you are advised to do so by TIBCO Support.

For more information about iProcess Objects Server debug parameters, see TIBCO iProcess Objects Director Administrator’s Guide.

3. Click ADD to add the new debug settings.