Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
We have single node environments each for Dev and Production.
What should the Node Purpose value be for Prod and Dev environments in a single node architecture?
I read this article https://support.qlik.com/articles/000053760 but wasn't sure whether it makes a difference to set both of the environments to "Both" value.
What would be recommended drop-down option for each environment? My thinking is it should be "Production" for Prod, and "Development" for Dev server but I am wondering whether it makes any difference at all in a single node architecture.
Hi,
I guess it depends on whether you will allow self-service app creation on the Prod server. If yes, you should keep the Prod server as "Both".
As the Dev server is independent, you can keep it as "Both".
@fosuzuki it spot on. Prod = App Creation in the Hub is disabled. Both / Dev = App Creation in the Hub is possible given Security Rules. To be completely honest, there is no technical distinction between Both and Development. Conceptually you can (optionally) use them in load balancing rules. Otherwise there's no distinction whatsoever.
Hi @Levi_Turner,
Thanks for your input. This is something I get confused with. I still read manual (June 2019) that says:
Development: this server is intended to allow users to create apps but not serve the normal user
traffic for users consuming published apps. In this case, the create and edit capabilities are
enabled, but the server will not be considered when load balancing user traffic. Published apps
are never available on a development node.
Could you please help clarifying this?
I'm following up with some folks from that component since I have never seen the product work in that manner. It may have been a planned capability which never was shipped / developed / etc.
I have not been very exclusive into administration. So with my limited exposure to this world, I have also experienced the same..
@Levi_Turner wrote:...I have never seen the product work in that manner...
This has been submitted as a documentation bug. Help.qlik.com as well as the support articles which refer to this capability will be adjusted.