18 Messages
QlikSense to Collibra Integration - can it be used for QlikSense SaaS
Can the Springboot application be used for QlikSense SaaS ?
- Does the QlikSense Solution use the same API?
- Can we use the Authorization?
TY in advance
@spring-team.collibra.com
springboot_team
368 Messages
2 years ago
Hi @rudolf.kunkel,
The latest version of the QlikSense to Collibra Spring Boot integration (i.e. v2.0.0) communicates directly with the Qlik Engine using the WebSocket protocol (https://help.qlik.com/en-US/sense-developer/May2022/Subsystems/EngineAPI/Content/Sense_EngineAPI/introducing-engine-API.htm).
To be able to do so, the integration makes use of the provided tenant URL (set using configuration property “qlik.api.url”) and a token (set using configuration property “qlik.api.token”). Thanks
1
0
springboot_team
368 Messages
2 years ago
Hi @rudolf.kunkel,
This QlikSense Spring Boot integration retrieves the metadata using the QlikSense Engine API which is a way of communication to QlikSense that exposes a specific set of endpoints.
The Spring Boot integration is capable of retrieving the metadata specified in the documentation (link below). Meanwhile, regarding whether the same metadata that is being retrieved from both the QlikSense SaaS API and QlikSense Engine API, it might be the case, however it would need to be tested. Would it be possible to try using the latest version of the QlikSense integration to confirm this please?. Thanks
1
0
springboot_team
368 Messages
2 years ago
Hi @rudolf.kunkel,
Thanks for the information provided.
We are looking into this and will keep you updated. Thanks
0
0
springboot_team
368 Messages
2 years ago
Hi @rudolf.kunkel,
Can you please try the following?
Ensure the property qlik.api.url has appropriate value (Secured WS connection to Tenant ID with no additional slash symbol at the end)
e.g. wss://xxxxxxxxx2yl94w.xx.qlikcloud.com
Open the source file src/main/java/com/collibra/marketplace/qliksense/engine/session/QSession.java and within the open Java method, update line 76 as follows:
From:
initConnection(url + docId);
To/Updated line:
initConnection(String.format("%s/app/%s", url, docId));
Recompile and run the updated integration using an IDE or Apache Maven (
mvn clean spring-boot:run
)Thanks
1
0
springboot_team
368 Messages
2 years ago
Hi @rudolf.kunkel,
Thanks for the information provided.
Once the QlikSense integration is deployed, can you please try making the following request:
where:
<qDocId>
should be replaced with the ID of an existing QlikSense application.As an example, when accessing QlikSense from a browser, the URL would have the following format:
https://xxxxx.xx.qlikcloud.com/sense/app/c36b9270-543f-11ed-bdc3-0242ac120002/overview
.the value that should be used is:
c36b9270-543f-11ed-bdc3-0242ac120002
.Also, if possible, it would be helpful to confirm whether the QlikSense account being used is a trial version, as the full integration would not work. Thanks
0
0
magdallavallol
2 Messages
2 years ago
Hi @spring-team.collibra.com Rudolf is OOO until November, 13th. We were testing with a Qlik cloud trial instance. Is there any way of confirming if this integration supports Qlik Cloud without needing Rudolf’s testing support?
Thanks,
Magda.
0
0
springboot_team
368 Messages
2 years ago
Hi @magda.llavallol,
Thanks for the update.
The full integration (i.e. getting all existing Document/App IDs and synchronizing them all) works only for Qlik Sense Enterprise users. Meanwhile, when using a trial account it is limited to only synchronize the specified Doc IDs. Thanks
3
0
springboot_team
368 Messages
2 years ago
Hi @roger.lockerbie.collibra.com,
Thanks for the update.
Regarding the minor code modification, just to let you know that the fix will be released as part of v2.0.1.
Meanwhile, yes, it might be related to the account type (i.e. an Enterprise account being required). This is due to the
/sync
endpoint that makes a request to retireve a list of documents, which is only available to Enterprise users.Currently, since a trial account is being used, you can try using the other endpoint that is exposed by the QlikSense integration. Thanks
Request:
where:
documentIds
should be set to a comma-separated list of document IDs that should be synchronized. (Example:5982f10f-0c40-40b2-bcd8-e602ba5352d9,5a2820bc-52b3-4d1c-92c8-22a8f4617b3a
)1
0
springboot_team
368 Messages
2 years ago
Hi @roger.lockerbie.collibra.com,
Thanks for the update.
It seems that respective IDs are set for the following properties, while the names are required.
Therefore, can you please try replacing the resource IDs with the respective community/domain name? Thanks
0
0
rogerlockerbie
6 Messages
2 years ago
Oh dear.
I’d got Asset Reference UUIDs in my head, and it clearly says, name, and after changing hem to name, I can confirm it works.
Thanks very much for your ongoing and prompt help
0
0
springboot_team
368 Messages
2 years ago
Hi @roger.lockerbie.collibra.com,
No worries and thanks for the update.
1
0
springboot_team
368 Messages
2 years ago
Hi @roger.lockerbie.collibra.com ,
The integration does not contain a relationship with the ‘Contains Business Dimension’ role/co-role. Is this a custom relation, or could it be a misconfiguration in the customconstants.java class file? Have you used the CMA file to import the correct IDs into your Collibra instance?
Regarding the modifications you mentioned, are the modifications only related to fixing the import bug, or did you add any additional logic to the current marketplace version?
The following are all of the relations that the integration uses:
The most similar relation is Dimension is part of report.
You can ensure that the correct IDs are set between your Collibra instance and the integration. Also, do you know the asset types of the ‘Licence Number’ asset?
Thanks
0
0