Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi.
For the last 2-3 years my project has been using the EDX command line component to trigger document reloads configured in our QMC. We use an external scheduler (Control-M) to trigger batch files on our QlikView servers and these bacth files in-turn trigger the EDX component and pass to it the task name of the document that we want to reload. (Nothing complicated, quite simple really.)
The EDX executable and associated config file are saved in a central location. Every batch file that is triggered uses this single central instance of the EDX component.
We have just started experiencing some intermittent failures where EDX is aborting in error but the task that it triggered continues to run in the QMC through to a successful completion.
As part of the investigation process we are asking ourselves if the EDX command line component is still the best approach to use for the version of QlikView that we are now running (v11.2 SR8)?
Can anyone on the community recommend a better or different alternative to EDX command line, something that can still be executed from a batch file triggered by Control-M?
We must still maintain the same overall approach of using Control-M to trigger our document reloads as Control-M is the standard for production systems in our organisation because it forms part of a wider incident management process.
I don't know about another ready-to-use application that allows you to trigger QDS tasks from anywhere at any time (except for the one that lets SAP trigger QDS tasks)
The best alternative I can suggest and that will perfectly integrate in your specific environment is to write your own application or service that uses the QMS API to control, start and track tasks.
A supported alternative from the Qlik Market:
Use cases:
1. Need to share data with QV application - upon arrival data, task needs to be triggered.
2. If we need to trigger QV task based on some external event then we can ask delegate/source system to create Zero KB (kind of token) so we can poll the folder and trigger the task
Used this approach for above use cases: Triggering task on QMC upon file arrival | QlikTab