Discussion board where members can learn more about Integration, Extensions and API’s for Qlik Sense.
We are going to call qrs/api through PDI (pentaho data integration) but we faced a problem. PDI says success but without any result in body. (a "200" response from PDI and a "403" result for "HTTP status code")
we can call qrs/api through other applications like "QlikSense desktop>rest-client" or "PowerShell". we are going to see what is the response in the Qlik server log but we can't find it. Do you know where is error log for calling a qrs/api (probably related to certificate)?
Furthermore, any clue about calling qrs/api through PDI is helpful.
It's the repository that logs that contain that type of information. I think it will log errors by default, but to see requests that complete successfully, you will have to enable debug logs. You can either set the system log level to debug or (for the latest patches) you can set the performance log level to debug and get some additional information.
As for locating the files on disc, you'll find the local log files at this location:
The files fond there are per node, and they are the ones that are actively written to by Qlik Sense. From time to time those log files will be moved to the "ArchivedLogs" folder of the shared content folder used by Qlik Sense.
I found these for correct and the one which has the problem. but the information is not enough. I can't find what is going on.
|145 20200131T095853.166-0500 DEBUG CRP-BISB-02 System.Repository.Qlik.Sense.Common.Communication.Server.HttpConnectionHandler 35 8e5bb5dd-7bed-4f10-aa9d-f60d99b47fa6 CQQQ\administrator Handling request /qrs/app/full?xrfkey=3333333333333333 8e5bb5dd-7bed-4f10-aa9d-f60d99b47fa6|
|146 20200131T095853.168-0500 DEBUG CRP-BISB-02 System.Repository.Qlik.Sense.Common.Communication.REST.Server.RESTEngine 35 ba7b5eae-a799-41e9-a9ae-6f8649b2bda9 CQQQ\administrator User CQQQ\user33333333 called GET on /qrs/app/full?xrfkey=3333333333333333 0 ba7b5eae-a799-41e9-a9ae-6f8649b2bda9|
The one with problem:
|1189 20200131T101749.411-0500 DEBUG CRP-BISB-02 System.Repository.Qlik.Sense.Common.Communication.Server.HttpConnectionHandler 36 92c059a3-41dc-4cda-858b-333ad060696c CQQQ\administrator Handling request /qrs/app/count?xrfkey=1234567890123999 92c059a3-41dc-4cda-858b-333ad060696c|
|1224 20200131T101826.841-0500 DEBUG CRP-BISB-02 System.Repository.Qlik.Sense.Common.Communication.Server.HttpConnectionHandler 35 53e509fb-9a41-4786-883e-a7f94a2a09a9 CQQQ\administrator Handling request /qrs/app/count?xrfkey=1234567890123999 53e509fb-9a41-4786-883e-a7f94a2a09a9|
sorry, I didn't notice. I brought the wrong lines. Both of them were qrs/app/full. so maybe there isn't any record for the call with PDI.
Somewhere should be a line for that 403 response, shouldn't?
I couldn't use rest api in pdi, so I wrote a python program to call qrs api and then call that by "execut shell" node in pdi.
(I wrote this for the person who want to call qrs/api with pdi)