A lot of enterprise schedulers have an option to post to an HTTP endpoint. In the past I’ve used NiFi’s ListenHTTP processor to allow for remote triggering of a flow.
But really any of the Listen/Consume processors could potentially be used for remote triggering: * ListenHTTP or ListenWebSocket (might be a good way to trigger from some kind of Javascript front end, less helpful form an enterprise scheduler) * ConsumeJMSQueue/Topic * ConsumeMQTT * ListenTCP/ListenUDP You could also use a file as a trigger by writing an empty file to a directory and then using FetchFile to trigger the flow. You could even use this as a way to pass in a configuration file to a flow… ☺ all sorts of options. --Peter From: Jeremy Dyer [mailto:jdy...@gmail.com] Sent: Tuesday, November 14, 2017 02:24 To: users@nifi.apache.org Subject: [EXT] Re: Calling NIFI job from any Enterprise Scheduler Siva - I find the best way to trigger a NiFi workload from any sort of enterprise scheduler is to start the workflow you wish to trigger with a *ConsumeJMS processor and then have that enterprise scheduler fire the event to start the job to that configured endpoint. In this manner you can use your enterprise scheduler to invoke the flow without any major modifications. - Jeremy Dyer On Mon, Nov 13, 2017 at 1:20 PM, Sivakumar, S <sivakuma...@intuit.com<mailto:sivakuma...@intuit.com>> wrote: Hi Team, I have requirement to call NIFI job from any Enterprise Scheduler (for ex: tidal Enterprise Scheduler). What is the way to call nifi job from a command line so that it can triggered from external program? -Siva
