IBM 51 manual Workflow logs

Table 7. Deployment engine logs (continued)

File name	Location	Description
cbe.log	Windows	This log file stores
		all event logs for
	%TIO_LOGS%\deploymentengine
		the deployment
	UNIX or Linux	engine component
	$TIO_LOGS/deploymentengine	in Common Base
		Event standard
		format.
deploymentengine_start.log	Windows	This is the log file
	%TIO_LOGS%\deploymentengine	of the most recent
		startup of the
	UNIX or Linux	deployment
	$TIO_LOGS/deploymentengine	engine. This log is
		overwritten each
		time the
		deployment engine
		is started.

Workflow logs

If you want to determine why a particular workflow has failed, you can use the Web interface to display the run history for that workflow. You can also export the log files of your workflow history using the workflowLogExport command, as described below. The command script is located in the %TIO_HOME%\tools directory, where %TIO_HOME% is the Tivoli Intelligent Orchestrator home directory.

vOn a Windows platform, type the following command:

workflowLogExport.cmd (-n <workflow_name>* -r <request_id>) [-f <export_filename>] [-i <input_filename>]

vOn a UNIX or Linux platform, type the following command:

workflowLogExport.sh (-n <workflow_name>* -r <request_id>) [-f <export_filename>] [-i <input_filename>]

where:

–<workflow_name> is the name of the workflow whose run history you want to export to a log file;

–<request_id> indicates the deployment request identifier;

–[-f <export_filename>] specifies the fully qualified path and file name where the workflow log will be exported. By default, the file format for the exported log file is XML, and the default file name is workflowLogExport.xml. If you do not specify a different file format, the workflow log file will be exported by default to XML. Also, if no file location is specified, the log file will be exported by default to the %TIO_LOGS% directory.

–[-i <input_filename>] specifies the name of the file that lists the names of all workflows whose run history you want to export to the same log file.

48Tivoli Intelligent Orchestrator Problem Determination and Troubleshooting Guide