Hi,
My approach for QAP is a bit different. Since we have Qlik sense and QAP in the same environment, the use for QAP is restricted to applications that we need to publish to users without any authentication, or embedding Qlik reporting inside some of the applications.
The QAP sits in the DMZ. Applications are developed on the Sense server. So, the design is as follows:
1- Loader applications on the sense server, these are simple apps that pull data from the databases, transpose tables , calculates aggregations, and applies maps as necessary, resulting in clean tables, and saving the resulting tables in QVD folder. The loading time for these applications is usually high, so they are triggered automatically via tasks.
2- User Applications: These are the applications that the users actually see, containing all the dashboards. These use only QVD folder connection.
3- Mashups: These are the applications containing the Mashups, and sheets to be embedded as frames in different applications. These also use exclusively QVD folder connection.
On QAP Server, I switch the license to Sense, add my user as a professional user. Import any application, then create a connection with the exact same name as the sense server, but instead, pointing to the shared QVD folder on the sense server. Then switch back to QAP license.
Moving the applications between Sense and QAP is now quite easy. Export the application without data from Sense server, then import it from the QAP server. Reload the application from the QAP server, and voila. Since the data connection name is the same in both Sense and QAP, QAP finds the QVD folder and reloads the data.
If I need to update the application, I just change it on Sense, export, then import back on QAP.
The added bonus with this approach is :
1- Database is accessed only once, from Sense.
2- Database is inaccessible from DMZ.
Hope that this helps
