We currently have two Qlik Sense environments in place: Production and Development. Each environment has its own dedicated file share on the local server.
As we plan to move towards a multimode setup, I would like to clarify a few points before proceeding:
Qlik Sense Version:
both environments running the same version of Qlik Sense.
PostgreSQL Installation:
Production uses an unbundled PostgreSQL installation, while Development is using the bundled PostgreSQL. Will this cause any compatibility or migration issues? How can we handle this?
Shared File Structure:
How can we create a shared file structure between the two environments?
Once this is established, what is the recommended process to move apps from Development to Production?
App File Naming:
Currently, both environments store applications using the AppID as the file name (e.g., AppID.qvf).
Is there a way to configure the system to save the app using the App Name instead of the AppID?
Environment Synchronization:
Is it necessary to synchronize both environments?
If yes, what is the best approach or recommended tools for keeping them in sync?
I appreciate your input on these points to help ensure a smooth transition to a multimode architecture.
Maybe I don't understand the case but multinode is single cluster with rim-nodes, it means you have for example 3 VM's with Qlik Sense: - Central - Production - Development
Central is creating new cluster, Production and Development are joined nodes to Central and added in QMC. Then you swap between Dev and Prod in QMC, so you duplicate app go to QMC select Run Engine as Dev and you are working on Dev enviroment if new version is ready you just publish app and the app swaps with existing app in stream cuz your apps store at Central.
1. Same version is must have 2. Second node should be connected to Main node as join to claster 3. It's one QlikShare folder 4. Your developer app is a duplicate of published application and when you publish the app to stream it swaps with old version
The problem will likely occur with versions if the PostgreSQL versions are different. I haven't encountered your situation, so I'm just guessing, but I think you won't be able to merge two repositories into one, and you'll have to rebuild the development version. With repositories fails occure even in updates so you never know make couple backups.
