Log Configuration 'axrptcfg.exe'

During installation of enaio®, the configuration tool axrptcfg.exe and a configuration file (oxrpt.cfg) are installed in every directory containing enaio® applications.

To change the logging settings for applications contained in this directory, use the oxrpt.cfg configuration file in the same directory or create new channels for applications.

Every application reads its logging settings from the oxrpt.cfg configuration file in its directory when the program is launched.

The applications must be restarted after making changes to the oxrpt.cfg configuration file.

The 'axrptcfg.exe' Configuration Tool

Access to axrptcfg.exe und oxrpt.cfg is not incorporated in the enaio® rights system. Secure access via the operating system.

When the application starts, open the installed configuration file oxrpt.cfg located in the application directory. The data from this configuration file is used for logging all applications from the directory. The path and file name are shown in the title bar and the status bar.

You can change the log path for default logs, activate or deactivate flow, SQL, error, job call, ODBC, and HTTP logging, and select other levels.

A higher level for flow logging can lead to longer response times or an increased system load. Error messages are always included in a flow log.

Changes apply to all applications in the directory for which no individual channel has been set up.

Channels are created in the Channels area, while the Aliases area allows you to assign channels to applications and activate these assignments.

Channels

A channel accepts messages with the same action ID from one or more applications and can store the messages in the internal log format, in OXMISC format, or in TEXT format.

Logs in the internal log format (*.evn) can be opened using enaio® protocol-viewer; logs found in the OXMISC and text format can be opened with any editor.

We recommend the internal log format, since logs in enaio® protocol-viewer can be displayed in a highly structured manner.

Internal EVN Log

Channels in the internal log format have the following properties:

Parameter	Default value	Range of values
Action	15	15 = Flow 11 = Memory 9 = SQL 8 = Error 7 = Job call 2 = HTTP 14 = ODBC
Level	1	0 = Only error log 1 = Application initialization 2 = Function entry points 3 = Function exit points 4 = Significant function points 5 = Detailed log 6 = Debug log
Suspended/ Stopped	NO	NO=0 / YES=1 'YES': Logging is suspended; no log entries are written.
FilterName	-	Filter for logs.
LogLongTerm / permanently opened file	NO	NO=0 / YES=1 Fast logging via a permanently opened file (YES=1) or by logging multiple applications in a shared file (NO=0). Fast-logging files cannot be deleted as the application that is currently writing to the log holds a handle to the files.
LogRecreate / log file rolling	YES	NO=0 / YES=1 The running log file is closed at midnight (YES=1) and a new file is started at the beginning of the new day.
LogFileName	os%6%7%5.evn	Name of the log file. The name may contain the following parameters:
		%2	Name of the executed application
		%3	Name of the computer
		%4	User name of the Windows user who starts the application. For the server, the user under which the process is running.
		%5	Year in two-digit format
		%6	Day
		%7	Month
		Enter 'evn' as the file extension. The path specified in the configuration tool is valid for all logs.
LogMaxFileSize	128000	Maximum file size of the generated log files in kilobytes. A new log file is written when this limit is reached. The value in kB must be between 1024 and 524288.
LogSizeControlOn	1	The size of the log directory is governed by enaio®. 0 – disabled, 1 – enabled
LogHighWater	1024	Maximum allowable size of all log files per channel in MB.
LogLowWater	512	Minimum size of all log files per channel in MB.
LogExpirationDays / File age	2	Value in days. Files are not deleted until the low water mark is reached. Instead, the most recent files are still available after several days. If the value is 1, the files from the last 24 hours are kept at minimum.

OXMISC Log

Channels in OXMISC format have the following properties:

Property	Default value	Range of values
Action	15	15 = Flow 11 = Memory 9 = SQL 8 = Error 7 = Job call
Level	1	0 = Only error log 1 = Application initialization 2 = Function entry points 3 = Function exit points 4 = Significant function points 5 = Detailed log 6 = Debug log
Suspended	NO	NO/YES 'YES' turns off the channel.
MiscLogFormat	TDUXMJP	T = Time; D = Date; U = User; X = Station; M = Module; J = Job; P = Procedure
FilterName	-	Filter for logs.

OXMISC logs are always saved to the log path specified in the default settings. They are given the following names:

Flow logs	osddmmjj.flw
SQL logs	osddmmjj.sql
Error logs	osddmmjj.err
Job call logs	osddmmjj.log

An example of an OXMISC log entry:

BEGIN
TIME     : 12:55:50
DATE     : 02/29/03
USER     : THOMAS
STATION  : 11D3-080009FEC5ED
MODULE    : oxdbpipe
JOB      : DisConnect
STRING   : SQLFreeEnv(m_hEnv)
End

Text Log

Text logs are particularly useful for external log monitoring.

Output format:

date time : level : threadid : eventid : computer : user : application : module : function : sourcefile : codeline : message

The data is output line by line and separated by the colon with leading and trailing space. The date format is 'DD/MM/YYYY hh:mm:ss,ms'. The messages are composed in English regardless of the language setting. Messages can be longer than one line.

Channels in text format have the same properties as channels in the internal log format.

Aliases

You can use aliases to assign channels to applications or libraries.

Existing channel assignments are listed in this area and can be edited or deleted. Selected assignments (þ) are active.

Enter the name of an application as an alias. You can assign a channel to each executable file (*.exe) and each library (*.dll). Specify a name without an extension. The marked channels will be assigned.