https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-Productionize-Nifi-and-schedule-it-to-run-every-hour/m-p/104196#M37996 <P>I think it depends what you mean by "schedule it to run every hour"... NiFi itself would always be running and different processors can be scheduled to run according to their needs. Every processor supports timer based scheduling or cron based scheduling, so using either of those you can set a source processor to run every hour. You could also use the REST API to start and stop processors as needed, anything you can do in the UI can be done through the REST API.</P><P>For best practices for upgrading NiFi see this wiki page:</P><P><A href="https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi">https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi</A></P><P>Deploying changes to production, there are a couple of approaches, one of them is based around templates:</P><P><A href="https://github.com/aperepel/nifi-api-deploy">https://github.com/aperepel/nifi-api-deploy</A></P><P>Some people also just move the flow.xml.gz from one environment to another, but this assumes you have parametized everything that is different between environments. </P> Tue, 16 Aug 2016 20:44:19 GMT bbende 2016-08-16T20:44:19Z https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-Productionize-Nifi-and-schedule-it-to-run-every-hour/m-p/104195#M37995 <P>What is the best practice to productionize nifi and schedule it to run every hour through a script? How do we upgrade nifi to a new version. How to deploy new workflows and modified workflows into production in EC2.</P><P>How do we deploy changes into nifi workflows thank you</P> Fri, 16 Sep 2022 10:35:09 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-Productionize-Nifi-and-schedule-it-to-run-every-hour/m-p/104195#M37995 bigspark 2022-09-16T10:35:09Z https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-Productionize-Nifi-and-schedule-it-to-run-every-hour/m-p/104196#M37996 <P>I think it depends what you mean by "schedule it to run every hour"... NiFi itself would always be running and different processors can be scheduled to run according to their needs. Every processor supports timer based scheduling or cron based scheduling, so using either of those you can set a source processor to run every hour. You could also use the REST API to start and stop processors as needed, anything you can do in the UI can be done through the REST API.</P><P>For best practices for upgrading NiFi see this wiki page:</P><P><A href="https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi">https://cwiki.apache.org/confluence/display/NIFI/Upgrading+NiFi</A></P><P>Deploying changes to production, there are a couple of approaches, one of them is based around templates:</P><P><A href="https://github.com/aperepel/nifi-api-deploy">https://github.com/aperepel/nifi-api-deploy</A></P><P>Some people also just move the flow.xml.gz from one environment to another, but this assumes you have parametized everything that is different between environments. </P> Tue, 16 Aug 2016 20:44:19 GMT https://community.cloudera.com/t5/Archives-of-Support-Questions/How-to-Productionize-Nifi-and-schedule-it-to-run-every-hour/m-p/104196#M37996 bbende 2016-08-16T20:44:19Z