Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Configuring the TIBCO iProcess Objects Server : Disk Log Parameters

Disk Log Parameters
This dialog is from the Windows TIBCO iProcess Objects Server Configuration Utility. The configuration parameter names shown in the callouts are from the UNIX TIBCO iProcess Objects Server configuration file. This illustration provides a cross-reference to determine which fields to change when using the configuration utility.
TraceMsg
Flag (0 for no, 1 for yes) specifying if client request and response messages should be traced to the log file. Note that even if this parameter is set to “0” (No), messages will still be traced if LogLevel (see LogLevel) is set to “4” (Debug). In addition, only transactions that are specified through the LogCategories (see below) will be traced.
Values: 0 or 1
Default: 0
LogCategories
Specifies which categories of information to write to the log.
Values: Bit settings from 0x00000001 to 0xFFFFFFFF
Default: 0xFFFFFFFF (LOGCAT_ALL)
The following log categories are available (either alone or by combining the indicated hex values):
LogLevel
Level of detail to write to log file. Each level includes the levels numerically smaller (e.g., Informational includes Warnings and Errors). The level is specified using the corresponding number. Note that if the log level is set to 4 (Debug), messages are automatically traced to the log (even if the TraceMsg parameter is set to 0 — see TraceMsg above).
Errors: 1
Warnings: 2
Informational: 3
Debug: 4
Default: 2
WriteErrsToEventLog (Windows Only)
Flag that specifies whether or not TIBCO iProcess Objects Server errors should be written to the Windows Event Log.
The Write errors to Event Log check box is used to set this configuration parameter. Checking this box (the default) causes TIBCO iProcess Objects Server errors to be written to the Event Log. Unchecking this box disables the writing of most TIBCO iProcess Objects Server errors to the Event Log — note that the following errors are still written to the Event Log regardless of the setting of this parameter: errors opening, writing to, or archiving log files; errors reading configuration values in the Registry; errors starting the NT service; errors because of invalid configuration parameters.
LogFileMaxSize
Maximum size in MB of the log file before it is truncated (rolls over). Note that the log file will roll over when the maximum size is reached regardless of the LogLevel setting.
The swentobjsvXX.log file, which is located in the $SWDIR/logs.
The SWEntObjSvXX.log file, which is located in the SWDIR\logs.
The swentobjuaXX_timestamp.log file, which is located in the $SWDIR/logs.
The SWEntObjUaXX_timestamp.log file, which is located in the SWDIR\logs.
Lower Bound: 1
Upper Bound: none
Default: 15 MB
LogFileMaxArchives
This specifies the number of archive log files that will be saved when the log rolls over as a result of reaching the maximum size limit (LogFileMaxSize). This can be useful if you want to collect many MB of debug log, but don’t want to deal with a very large log file by setting LogFileMaxSize to a large value.
Windows Systems
The “non-archived” TIBCO iProcess Objects Server log file is named SWEntObjSvXX.log (see Name and Location of the TIBCO iProcess Objects Server Log). If the LogFileMaxArchives parameter is set to a value greater than 0, and the “non-archived” TIBCO iProcess Objects Server log file reaches the maximum size set by the LogFileMaxSize parameter, the log rolls over and “archived” log files are saved. The archived log files are named SWEntObjSvXX_timestamp_archive_xxx.log, where xxx is a counter that is incremented each time the log rolls over (starting at 1). For example, if this parameter is set to 2, the first time the log rolls over, it will be saved as SWEntObjSvXX_timestamp_archive_1.log. The next time it rolls over, it will be saved as SWEntObjSvXX_timestamp_archive_2.log. If it rolls over again, it will be saved as SWEntObjSvXX_timestamp_archive_3.log, but SWEntObjSvXX_timestamp_archive_1.log will be deleted because it is only saving two archives.
UNIX Systems
The “non-archived” TIBCO iProcess Objects Server log file is named swentobjsvXX.log (see Name and Location of the TIBCO iProcess Objects Server Log). If the LogFileMaxArchives parameter is set to a value greater than 0, and the “non-archived” TIBCO iProcess Objects Server log file reaches the maximum size set by the LogFileMaxSize parameter, the log rolls over and “archived” log files are saved. The archived log files are named swentobjsvXX_timestamp_archive_xxx.log, where xxx is a counter that is incremented each time the log rolls over (starting at 1). For example, if this parameter is set to 2, the first time the log rolls over, it is saved as swentobjsvXX_timestamp_archive_1.log. The next time it rolls over, it is saved as swentobjsvXX_timestamp_archive_2.log. If it rolls over again, it is saved as swentobjsvXX_timestamp_archive_3.log, but swentobjsvXX_timestamp_archive_1.log will be deleted because it is only saving two archives.
Whenever the TIBCO iProcess Objects Server is restarted, the archive log file name starts back at swentobjsvbXX_timestamp_archive_1.log. Therefore, if the system is set up for three archive log files, and the log rolls over eight times, the archive log files will be ..._6.log, ..._7.log, and ..._8.log. However, if the server is now shut down and restarted, the next three archive log files will be ..._1.log, ..._2.log, and ..._3.log (the ..._6.log, ..._7.log, and ..._8.log files will still exist).
Lower Bound: 0 (do not archive log files)
Upper Bound: none
Default: 0
UseSysLog (UNIX Only)
Flag (0 for no, 1 for yes) indicating whether all messages other than debug messages that are written to the TIBCO iProcess Objects Server message and audit logs are also written to the UNIX system log.
When the TIBCO iProcess Objects Server sends a message to the UNIX system log via the "syslogd" daemon, the facility or subsystem on the message is set to "local0". The syslogd priority levels are set as follows:
For more information about the UNIX System Log, see UNIX System Log
Values: 0 (No) or 1 (Yes)
Default: 0 (No)

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved