IBM 51 manual Logs for data collection and decision making, Automation package logs

Logs for data collection and decision making

Log files for the policy engine component (data acquisition engine, application controllers, global resource manager) are stored in the %TIO_LOGS%\policyengine directory.

Table 8. Policy engine logs

File name	Location	Description
console.log	Windows	This log file stores all
		event logs for the
	%TIO_LOGS%\policyengine
		policy engine
	UNIX or Linux	component including
	$TIO_LOGS/policyengine	messages, traces, and
		debugging
		information.
msg.log	Windows	This log file stores the
		globalized event
	%TIO_LOGS%\policyengine
		messages for the policy
	UNIX or Linux	engine component.
	$TIO_LOGS/policyengine
trace.log	Windows	This log file stores
		error messages that can
	%TIO_LOGS%\policyengine
		be reviewed by Tivoli
	UNIX or Linux	Software Support.
	$TIO_LOGS/policyengine
cbe.log	Windows	This log file stores all
		event logs for the
	%TIO_LOGS%\policyengine
		policy engine
	UNIX or Linux	component in
	$TIO_LOGS/policyengine	Common Base Event
		standard format.
policyengine_start.log	Windows	This is the log file of
	%TIO_LOGS%\policyengine	the most recent startup
		of the policy engine.
	UNIX or Linux	This log is overwritten
	$TIO_LOGS/policyengine	each time the policy
		engine is started.

Automation package logs

Log files for orchestration packages are stored in the %TIO_LOGS%\tcdrivermanager directory.

Table 9. Automation package logs

File name	Location	Description
console.log	Windows	This log file stores all event
		logs for orchestration
	%TIO_LOGS%\tcdrivermanager
		packages including
	UNIX or Linux	messages, traces, and
	$TIO_LOGS/tcdrivermanager	debugging information.
msg.log	Windows	This log file stores the
		globalized event messages
	%TIO_LOGS%\tcdrivermanager
		for orchestration packages.
	UNIX or Linux
	$TIO_LOGS/tcdrivermanager

Chapter 5. Tivoli Intelligent Orchestrator log files 49