https://community.qlik.com/t5/Management-Governance/Best-Practice-with-Multiple-Environments/m-p/1555803#M12917 <P>Hello,&nbsp;</P> <P>Based on the process you have built, I would definitely recommend a multi-node environment.</P> <P>With multi-node, you will be able to dedicate specific Qlik Sense Engine(s) to load the applications published to the staging stream and to load the application published to the Production Stream. This way you will ensure that if an application hasn't been very well developed and is consuming lots of resources the user working on the production stream are not affected in any way because the load will take place on the Qlik Sense Engine(s) dedicated to staging.&nbsp;</P> <P>You can apply the same idea to the Qlik Sense Scheduler to reload tasks so basically having Staging Qlik Sense Scheduler(s) to reload the staging applications and having Production Qlik Sense Scheduler(s) to reload the production applications.&nbsp;</P> <P>Hope this helps!</P> <P>&nbsp;</P> Wed, 13 Mar 2019 08:51:28 GMT Bastien_Laugiero 2019-03-13T08:51:28Z https://community.qlik.com/t5/Management-Governance/Best-Practice-with-Multiple-Environments/m-p/1554896#M12888 <P>Hello all and thank you for viewing,</P><P>&nbsp;</P><P>I am somewhat new to the Qlik space, however; I have been a Sys Admin / Engineer for a number of years.</P><P>What I am looking for is best practices when setting up a Qlik environment.<BR /><BR />At the moment we have a production server that we are developing processes and what not. Is it best practice to have multiple environments? Or just have one?<BR /><BR />My idea in setting up processes is as follows:</P><P>&nbsp;</P><OL><LI>A user requests a new application</LI><LI>Data Connection is made and shared with app developers / qvd developers</LI><LI>QVD Dev creates the QVD and shares with app developers</LI><LI>App developer develops that application</LI><LI>App is published to staging stream validation</LI><LI>App is validated</LI><LI>App is published to production stream<BR /><BR /></LI></OL><P>I know this is a lot of steps and there are a few more for our organization and how it has to handle things due to SEC and Federal Regulations.</P><P>&nbsp;</P><P>Any thoughts and or guidance is much appreciated.</P> Mon, 11 Mar 2019 14:22:05 GMT https://community.qlik.com/t5/Management-Governance/Best-Practice-with-Multiple-Environments/m-p/1554896#M12888 hmnathanstotts 2019-03-11T14:22:05Z https://community.qlik.com/t5/Management-Governance/Best-Practice-with-Multiple-Environments/m-p/1555803#M12917 <P>Hello,&nbsp;</P> <P>Based on the process you have built, I would definitely recommend a multi-node environment.</P> <P>With multi-node, you will be able to dedicate specific Qlik Sense Engine(s) to load the applications published to the staging stream and to load the application published to the Production Stream. This way you will ensure that if an application hasn't been very well developed and is consuming lots of resources the user working on the production stream are not affected in any way because the load will take place on the Qlik Sense Engine(s) dedicated to staging.&nbsp;</P> <P>You can apply the same idea to the Qlik Sense Scheduler to reload tasks so basically having Staging Qlik Sense Scheduler(s) to reload the staging applications and having Production Qlik Sense Scheduler(s) to reload the production applications.&nbsp;</P> <P>Hope this helps!</P> <P>&nbsp;</P> Wed, 13 Mar 2019 08:51:28 GMT https://community.qlik.com/t5/Management-Governance/Best-Practice-with-Multiple-Environments/m-p/1555803#M12917 Bastien_Laugiero 2019-03-13T08:51:28Z