Qlik Community

QlikView Publisher

Discussion Board for collaboration on QlikView Publisher.

nicktodd
New Contributor III

How to document the tasks we've got set up on our server?

Is there a way to list out details of the various tasks we have set up on our Qlikview server?

This would be useful to see when the various tasks are triggered, and as a backup should we need to re-created the tasks in the future (e.g. for disaster recovery).

Thanks

5 Replies
manojkulkarni
Valued Contributor II

Re: How to document the tasks we've got set up on our server?

Refer below link, might give some idea

QlikTip #37: Retrieve all EDX tasks from QMSAPi

Not applicable

Re: How to document the tasks we've got set up on our server?

Nick, Generally we use the publisher to create the tasks. & trigger on demand. All these tasks info was stored into QVPR (QV Publisher Repository). So you can back up your QVPR at any time.

Re: How to document the tasks we've got set up on our server?

Hi,

Nick there is no proper one I guess you have to create your own in excel.

Even I do that for my projects.

Regards

ASHFAQ

Arjunarao
Honored Contributor II

Re: How to document the tasks we've got set up on our server?

Hi nicktodd

As per my knowledge it is better to document manually.

Please follow ashfaq_haseeb 's advise.

datanibbler
Esteemed Contributor

Re: How to document the tasks we've got set up on our server?

Hi,

there is a possibility. We have done it.

There are various log files stored on the QlikView_Server, among them details on all the tasks running. I will have a look to see if I can find it.

I think we used HIERARCHY somewhere to display which tasks are dependent on others and the result is a very practical overview, showing all tasks and whether they are dependent on another task or scheduled for a specific time.

HTH

Best regards,

DataNibbler

P.S.: Yep, I have found it. There is a series of xml files for all the tasks in the subdirectory >> DistributionService\Tasks <<

I can attach that part of the app incl. the frontend, it's not a secret and there is no sensitive data.

You will just have to adapt the paths.

Community Browser