The QlikView ODBC lasted until version 8.5 and then it disappeared in version 9 because of its multiple errors. What we've done is export the data from QlikView to a text o xml file using actions or a macro in order to make it available to other applications
Im an OBIEE developer so bear with me, I was hoping to utilize the Qlikview cube directly for performance benefits over hitting the star schema underneath it all.
XML or text kind of puts be back to square one, if not less effective because at least with my relational tables I have the option of creating aggregates and using OBIEE to navigate between aggregate / detail.
I think this is a very interesting thread. We are now implementing OBIEE 11g in our company, and have already some developments on QlikView. Integrating both worlds: QlikView and OBIEE sounds very interesting for me and am thinking on different architectures...
- Accessing QV data from OBIEE
- embedding QV in OBIEE, i.e. using QV as a new tool in a OBIEE portal
Maybe, we can share some experiences on this using this forum...