Hi Shaun,
[mto: Hi Mike, could you help Shaun by pointing this post to the other similar post with all discussion threads (I can't seem to find it and think it is in a different post section/category?).]
There were multiple threads and answers to this post, but I can't find them anymore. The "ideal" manner for a QAP deployment, is that developers check in the QAP QMC prior to building a QVF on desktop to get the name of the connection prior to building the script and prevent ending up with loads of different connection names/labels for the same connection. When the QVF gets pushed/imported from desktop to QAP, it will hold that (shared) connection name and therefore, since the connection name already exists, it will not create a new name for every instance. This does require the developer to look into the QMC and understand the content of the connection. I would believe that if you use account X for a connection Y and then a new developer uses account Z for connection Y, the connection Y will get overwritten with account Z credentials, affecting the prior instance. This could be problematic if an account is restricted on its table privileges (e.g. account Z cannot read tables needed by the script that was created using account X). The latter is my own "2 cents", I would be glad if someone could confirm/renege this claim.
This being said, I don't think there is any way of migrating a script from Sense Hub directly to QAP. I think the hub script would reference a connection into the QSR DB, rather than "hard-coding" it in the underlying file. I think the desktop version does "hard-code" the LIB connection (with hash-algo for security). [I acquiesce this is a bit pedestrian an explanation, but is the"best" I can give.] This is why a script developed in hub, would have to be exported to desktop, connection reset and then re-imported into QAP. This would be in a Sense "standard mode". If you choose to deploy in "legacy mode", you would be able to call for a connection somewhere on the server (e.g. a text file using an "INCLUDE", which would contain the credentials required to connect to DB). However, the Sense Help file defines this as a potential security risk. Hence, I asked Mike Tarallo if he could give more details (which he did on the other post I cannot find anymore). The only "security risk" is that the script does not have a true "LIB connection" which would effectively "hide" the connection string. That said, if only developers are given access to the Sense machine (if local domain security is effectively implemented), "legacy mode" and using text/include statements would not pose any further risk than doing this in a QlikView environment (like we have). However, please wait for Mike to re-direct you to the original post with discussion points to get the info from there, rather than just from me.
Hope the info helps. Please share your experience/thoughts also, as this could also be useful to me and others.
Kind regards,
Cheenu
