Logging properties

The Transaction Server logs all messages as XML records to a file directory.

The following table shows the logging properties for Transaction Server.

Table 1. Logging properties
Property name	Default value	Range	Description
logFileSize	100,000	1000-10000000	Specifies an approximate maximum amount to write (in bytes) to any single log file. If this property is zero, no limit exists.
logFileCount	30	1-1000	Specifies how many output files to cycle through.
consoleLevel	info	N/A	Controls what messages are sent to the user interface for the operator. The following list shows the valid values. all info
consoleBufferSize	50	0-500	Specifies the number of console lines the Transaction Server retains for console buffer requests. This buffer allows external applications such as the Control Center to show up to this many lines of the current console state of the Transaction Server.

Pattern Characters

Pattern characters can be used to build the log file name and are useful for addressing logging issues, such as rotating log files. Typically, a log file name consists of a string that can include the following special characters that are replaced at run time.

/: The local path name separator.
%t: The system temporary directory.
%h: The value of the user.home system property.
%g: The generation number to distinguish rotated logs. If you don't specify the %g pattern, a dot and the generation number are automatically added to the end of the generated file name. This behavior is the same as ending a log file name specification with the .%g pattern.
%u: A unique number used to resolve conflicts.
%%: Converts to a single percent sign (%).

The %t, %h, %g, and %u patterns can appear in the log file name specification only one time. Also, since %t and %h are directory specifications, they must appear at the start of the log file name. For example, %h/logs/txlog%g.xml is valid, while mylogs/L%t.%g.xml is not. In addition, %t and %h are mutually exclusive. Only one of these patterns can be specified in a single log file name specification.

Using the Windows operating system as an example, %h resolves to the home directory of a user, such as C:\Documents and Settings\USERID. The %t pattern resolves to a temporary directory, such as C:\Documents and Settings\USERID\Local Settings\Temp. In these examples, USERID is the system ID that the user signed on with.

For example, the log file name specification of %u/txlog.xml generates the following log file names:

C:\Documents and Settings\USERID\txlog.xml.0
C:\Documents and Settings\USERID\txlog.xml.1
C:\Documents and Settings\USERID\txlog.xml.2
      .
      .
      .

A log file name specification of %t/java%g.log generates the following log file names:

C:\Documents and Settings\USERID\Local Settings\Temp\java0.log
C:\Documents and Settings\USERID\Local Settings\Temp\java1.log
C:\Documents and Settings\USERID\Local Settings\Temp\java2.log
      .
      .
      .

Note: The value of the logFileCount property must be greater than one for the %g pattern to be useful.