topic Re: Steps to trigger QlikView task reload after the Informatica job is finished in QlikView

Steps to trigger QlikView task reload after the Informatica job is finished

Mon, 26 Jan 2026 18:19:17 GMT

Hi All,

Is there any way to trigger a QlikView task reload (on QMC) once the Informatica job is finished? Currently we are manually reloading the QlikView tasks and want to avoid that.

Also can someone give me the direct steps to set up EDX. The online material is confusing

Using EDX in QlikView 11 | Qlik Community

Using EDX in QlikView 11 - basic example | Qlik Community

These are the two discussions I referred to but couldn't understand it.

Appreciate the help.

Regards,

Janaki

Re: Steps to trigger QlikView task reload after the Informatica job is finished

Peter_Cammaert — Thu, 02 Apr 2015 22:19:29 GMT

Yes, there is and it is really using EDX to trigger a task from anywhere you want.

On average, a DB system has a sort of scheduling agent that allows you to execute queries-stored proedures-whatever database code at a specific point in time (see the first use case in the first document). You're probably using such a technique already. At the end of this batch job (run in the dark), you can send a trigger to the QlikView Management Service using a small command line executable called QMSEDX Enhanced‌‌. The command line tool doesn't need a lot to get going: the taskname (as defined by you in the QMC), the server where the QMS is operating and optionally a password if the QlikView task is password-protected.

If you don't know how to launch a command line tool from an Informatica job, you should probably visit an Informatica forum/blog or consult a specialist, as this is very DB-specific and entirely unrelated to QlikView.

Best,

Peter

Re: Steps to trigger QlikView task reload after the Informatica job is finished

Fri, 24 Apr 2015 21:06:17 GMT

I was able to get the EDX trigger working. But I am getting this error with EDX. Can someone provide me with some solution for this?

Failed to create a client to the specified Uri.
The HTTP request is unauthorized with client authentication scheme 'Ntlm'. The a
uthentication header received from the server was 'NTLM'.

Unhandled Exception: System.ServiceModel.Security.MessageSecurityException: The
HTTP request is unauthorized with client authentication scheme 'Ntlm'. The authe
ntication header received from the server was 'NTLM'. ---> System.Net.WebExcepti
on: The remote server returned an error: (401) Unauthorized.
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpC
hannelRequest.WaitForReply(TimeSpan timeout)
— End of inner exception stack trace —

Re: Steps to trigger QlikView task reload after the Informatica job is finished

Peter_Cammaert — Mon, 27 Apr 2015 09:43:21 GMT

Did you define the special local group for accounts that should get permission to send EDX-triggers? The group is called "QlikView EDX" and must be defined on the machine where the QMS is running. Add all accounts to this groups that should be able to run the QMSEDX tool.

Re: Steps to trigger QlikView task reload after the Informatica job is finished

Mon, 27 Apr 2015 18:21:48 GMT

Hi Peter,

Yes I did add all the users to QlikView EDX and QlikView Management API local groups. Do I need to restart the server for them to take affect.

Regards,

Janaki