Qlik Community

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
Now Live: Qlik Sense SaaS Simplified Authoring – Analytics Creation for Everyone: READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
jpjust
Specialist
Specialist

Qliksense Installation and Configuration - Best Practice

All,

I am trying to install and configure Qliksense on multi node.

I wanted to know what is the best practice.

Is it recommended to install and configure dev and prod on the same cluster (Development Node within a Production Site) OR  Dev and Prod on different servers?

Please let me know your experience.

Thank you

6 Replies
Bastien_Laugiero

Hi,

I believe the recommended approach that also provide the easiest way to maintain the environment is to run Prod and Dev within the same Qlik Sense Deployment but on dedicated nodes.

So basically having dedicated Dev engine server(s) and dedicated Prod engine servers.

This will make the promotion of applications easier and avoid the potential loss of User Objects.

Such deployment can be found here:

https://help.qlik.com/en-US/sense-admin/May2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

Hope this helps! 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
jpjust
Specialist
Specialist
Author

Thank you Bastien.

If I keep the Dev and Prod as different environment then the only difference would be promoting the apps and other objects between environments, correct? Eg., Export and Import of qvf's between Dev and Prod.

If keeping dev and prod within the same deployment, then promotion of app's might happen with out the SDLC process. And anyone after completing the development can publish to Prod and incase bad queries can hamper the prod environment. How would we handle such situations?

Can you please provide me some more information about Pros and Cons of both type of deployments?

Thanks

Bastien_Laugiero

Hello, 

From a functional perspective yes this will be the main impact. But there are other component to consider such as the amount of servers required to have two separated environment. It is very likely that you will need more servers to run two environments than just one. 

Regarding the process of promoting application, this can be integrated with security rules and load balancing rule to ensure a clean separation between DEV and PROD apps and to make sure that before the application is getting promoted to PROD, a specific user or set of users will need to review and approve it. 

When running DEV/PROD under the same deployment, I would usually recommend to also have a separated test environment to test upgrades or major configurations changes because obviously you cannot test this in DEV since it will also affect PROD. 

 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
jpjust
Specialist
Specialist
Author

Thanks Bastien for the comments.

Talking about the amount of server, for instance, if go with the concept of "run Prod and Dev within the same Qlik Sense Deployment", we are still going for 2 servers to run the engine servers (dev and Prod) on dedicated servers.

Which approach we follow should be able to save server counts? Can you please provide me an  example of saving server counts when running Prod and Dev within the same Qlik Sense Deployment

Thanks

Bastien_Laugiero

Hi, 

So depending on the size of your environment, we can imagine the following setup (Not taking load balancing nor failover into account)

  • 1 Central node
  • 1 Scheduler node
  • 1 Engine nodes
  • 1 Proxy node
  • Optionally 1 dedicated Postgres + File Share server

So with this scenario you will need at least 5 servers for DEV and 5 servers for PROD while if you combine DEV and PROD on the same environment you could do a similar setup with 6-7 servers

  • 1 Central node
  • 1 or 2 Scheduler (One to reload PROD apps and one to reload DEV apps)
  • 2 Engine servers (One for PROD and one for DEV)
  • 1 Proxy server 
  • Optionally 1 dedicated Postgres + File Share server

Once again this is just an example where I am not taking into account any sort of failover nor load balancing possibilities. 

Hope this helps! 

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
jpjust
Specialist
Specialist
Author

OK Bastien. Make sense. absolutely some savings... Thanks for the suggestions.

Do you recommend an separate proxy server and can you please let me know the reason behind it?

Do you suggest an dedicated consumer node?

In addition to this , I do have an question on Licensing.

If I have an mashup, hosting few visualizations from qvf and displaying that on 5 monitors (windows OS), does it require licenses?

Thanks