oozie shell action

[#1]

I created a similar job as in : https://community.hortonworks.com/content/supportkb/48985/how-to-setup-oozie-shell-action.html

On execution the yarn log shows as success.

But I can't see the /tmp/output file being created anywhere. I checked on the local linux host as well as hdfs.

One question I have is in job.properties -

oozie.coord.application.path=${nameNode}/user/root/apps/shell

Should the configuration files (job.properties, coordinator.xml etc) reside in the above directory? I have them there.

Not sure what is happening.

Appreciate the insights.

[#2]

@Kuldeep Kulkarni , does your example : https://community.hortonworks.com/articles/27497/oozie-coordinator-and-based-on-input-data-events.ht...

set the job to run once a day?

If not, can you please let me know how to do that? I want to run a job once daily. Thanks.

[#3]

@n c
For some reason, I'm not able to add a comment in this post so replying as an answer:

For CDH, you can use Hue to design the submit the workflow.

For frequency - here is you can change the frequency of coordinator as per your requirement

 frequency="${coord:days(1)}"

[#4]

@Kuldeep Kulkarni, there are many lines with "input data" in the page you referred - not sure which ones to ignore.

Should I ignore the sections for datasets/input events/output events - that will leave only the workflow section.

Is that right?

Can't I use the coordinator from your shell action example?

But in that I don't see : "<app-path>${workflowAppUri}</app-path>"

Appreciate the clarification.