Hi, You should be able to point to a location in the local filesystem by starting the path with "file:///". For example: oozie.wf.application.path=file:///some/path/workflow.xml
You'll probably have to add "file" to the oozie.service.HadoopAccessorService.supported.filesystems property in oozie-site too. - Robert On Sun, Oct 5, 2014 at 9:39 PM, Srivastava Rachna - rasriv < [email protected]> wrote: > I am trying to find a way to run Oozie workflow outside Hadoop. After > researching I found that we can write our own custom action executor and by > making node as synchronous we can execute the Oozie workflow within the > Oozie execution context. I am trying to test following example of > extending Oozie http://www.infoq.com/articles/ExtendingOozie stand alone > on Tomcat. The example mentions that we can write custom action nodes and > execute directly inside Oozie execution context without using Hadoop. > > But when I looked at different ways of testing and deploying Oozie > workflow, I cannot find any way to run the workflow without deploying > workflow.xml on HDFS. > > I am looking at different ways to execute oozie workflow, all seems to > require workflow.xml file to be located in hdfs. > > 1. Command Line Interface: oozie job -oozie ...oozie -dryrun -config > job.properties To run oozie from CLI workflow application path must be > specified in the file with the oozie.wf.application.path property. The > specified path must be an HDFS path. > > 2. JavaClient: We have to specify the location of workflow.xml on hdfs > conf.setProperty(OozieClient.APP_PATH, " "), here app path needs to be hdfs > location of workflow.xml. > > 3. LocalOozieExample also needs location of workflow.xml on hdfs > > I want to know how to run workflow.xml under Oozie's execute context on > Tomcat without deploying workflow.xml on hdfs. > > Thanks, > > Rachana > > *************************************************************************** > The information contained in this communication is confidential, is > intended only for the use of the recipient named above, and may be legally > privileged. > > If the reader of this message is not the intended recipient, you are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited. > > If you have received this communication in error, please resend this > communication to the sender and delete the original message or any copy > of it from your computer system. > > Thank You. > > **************************************************************************** >
