Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

Highlighted
Not applicable

EDX - Task Completion

I have been able to put the code together to send the EDX request to start a Publisher job in QlikView 9.0 SR1. I need help getting a response back when the task has finished. Is there another request to the EDX that needs to be made, and if so, what is the XML tag that I need to look for.

Thanks for your help.

11 Replies
Not applicable

EDX - Task Completion

Check out the recently released SR2 where you can request the status of the task via EDX.

Not applicable

EDX - Task Completion

I have downloaded and installed 9.0 SR2. I looked through the documentation that is along with SR2 and the only information I see on triggering the EDX is starting the process. Is the request to the EDX the same to get the status of the task as it is to start the task?

Not applicable

EDX - Task Completion

Leave it with me a few days - I'm working on 'extracting' the missing documentation from the R&D team ...

Not applicable

EDX - Task Completion

Does anyone have any code or documentation on how to monitor a task triggered by an EDX request for its completion?

Not applicable

EDX - Task Completion

Rough notes, but hopefully this should help:


The call to get the taskstatus looks like this:
<Global method="GetTaskStatus" key="%timelimitedkey% >
<TaskNameOrId>Notepad, EDX triggered</TaskNameOrId> </Global>

answer could look like this:

HTTP/1.1 200 OK
Connection: close
Content-Length: 694
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Date: Thu, 29 Oct 2009 11:42:55 GMT
Server: Microsoft-HTTPAPI/2.0

<GetTaskStatus>
<GetTaskStatusResult>
<TaskStatus>
<DocumentPath />
<ID>55a4d924-f7bc-4027-9204-4c00711e001a</ID>
<LastLogMsg>Executing c:\windows\notepad.exe Executing commandline: "c:\windows\notepad.exe" in folder "c:\windows".
Process exited with exit code: 0 at 2009-10-29 12:31:31 Process exited with exit code: 0 at 2009-10-29 12:31:31 The task "Notepad, EDX triggered" finished successfully</LastLogMsg>
<Name>Notepad, EDX triggered</Name>
<Server />
<Start>On EDX</Start>
<LastExec>2009-10-29 12:31:34</LastExec>
<Status>Waiting</Status>
<DoAlert>False</DoAlert>
<TaskType>ExternalProgramTask</TaskType>
<Summary />
<Category>Default</Category>
</TaskStatus>
</GetTaskStatusResult>
</GetTaskStatus>

One important thing though:
If you only want to fire of EDX then membership in Qlikview EDX is enough but if you also want to get status of a task you need to be member of Qlikview Administrator.


douglaac
New Contributor

EDX - Task Completion

I was able to get a sample C# program (unsupported) from support that has an example of startign and monitoring a task (see attachment). However the issue I still have with this is that it only monitors the original tasks and does not demonstate a way to monitor dependent tasks that may be triggered by the initiated task.

In our 8.5 environment we had jobs that would run several tasks and we could monitor the status of the entire job (includign all tasks) using the EDX WebService. With the changes in v9.0 so far I have not found a way to repicate this functionality and be able to monitor the status of all triggered tasks.

if anyone has an example of being able to monitor dependent tasks that would be very helpful.

Not applicable

EDX - Task Completion

Hi Chris,

since we switched from 8.5 to 9.0 I miss the EDX set-up starting page w/ the test-option for URL. In the past we created a dumb webpage on the local server which started a QV-job on that server. I learned that isn't supported anymore... Any docu avail. now how to set a EDX using URL's ?

Thks, Tom

Employee
Employee

EDX - Task Completion

TomTom > EDX tasks have to be triggered via HTTP Post in version 9. You cannot launch an EDX with URL/querystring (HTTP GET) anymore.

Not applicable

EDX - Task Completion

Any news on this topic?

Currently we can not put QV V9 into production environment because we have no way to monitor a job status (=chain of tasks).

I need a way to connect the result of a job execution triggered by an external trigger (via HTTP POST) back to the monitoring system.