workflow.xml

This file is the definition of the workflow application. It is created when you input and save the workflow parameters. The file is saved to whatever location you specify in HDFS. The default file name is workflow.xml, but you can provide an alternative name when you initially save the file.

workflow.wfdraft

This is a draft file created when you save a non-validated workflow. The file is saved to the same location in HDFS as the associated workflow.xml file. The default file name is workflow.wfdraft, but you can provide an alternative name when you initially save the file.

/appdir/config-default.xml

This file is in HDFS. It is optional and contains properties shared by all workflows.

/appdir/lib/files.jar

In HDFS

Each workflow can also have a job.properties file (not put into HDFS) for job-specific properties.

coordinator.xml

This file is the definition of the coordinator application. It is created when you input and save the coordinator parameters. The file is saved to whatever location you specify in HDFS. The default file name is coordinator.xml, but you can provide an alternative name when you initially save the file.

coordinator.wfdraft

This is a draft file created when you save a non-validated coordinator. The file is saved to the same location in HDFS as the associated coordinator.xml file. The default file name is coordinator.wfdraft, but you can provide an alternative name when you initially save the file.

coordinator.properties

For defining the job’s properties.

bundle.xml

This file is the definition of the bundle application. It is created when you input and save the bundle parameters. The file is saved to whatever location you specify in HDFS. The default file name is bundle.xml, but you can provide an alternative name when you initially save the file.

bundle.wfdraft

This is a draft file created when you save a non-validated bundle. The file is saved to the same location in HDFS as the associated bundle.xml file. The default file name is bundle.wfdraft, but you can provide an alternative name when you initially save the file.

The wfmanager-view.log found under the ambari-server log directory.

Jobs successfully submitted to WFM so they have a job ID will have logs displayed in the WFM details tabs. The wfmanager-view.log provides additional information.

Oozie logs, which are located at /var/log/oozie by default.

The location of the log file can be changed. If an exception occurs before successfully submitting a workflow, coordinator, or bundle job, a good place to debug is the Oozie logs.