Automating Cache Initializer after reload or recycling services.
I have both Cache Initializer and QSST working but not sure how to automate either one of them after a reload or after the services have been recycled.
Alternatively, you can schedule things outside of Qlik Sense Enterprise using something like the Qlik-Cli which then would allow you to chain it to the execution of the CacheIntiailizer.exe file.
> after services have been recycled
The easy mode answer would be just to schedule things using something like Windows Task Scheduler every X hours / minutes. That'll give you an approximation but not strictly speaking be exactly aligned with service restart.
For a closer approximation of 100% alignment, it'll be a much more complicated series of things. The method that seems the most straight-forward is something like this:
Script which checks the status of Engine(s). Example QRS API call: GET /qrs/servicestatus/full?filter=(serviceType eq 3)
This then writes the timestamp value (or serverNodeConfiguration > hostName & timestamp values for a multi-node environment)
Another script (or in the previous one): Checks the timestamp value against the prior row. If there's a difference then it executes CacheInitializer
This would be a fast reactive but still reactive method.
Alternatively, you can schedule things outside of Qlik Sense Enterprise using something like the Qlik-Cli which then would allow you to chain it to the execution of the CacheIntiailizer.exe file.
> after services have been recycled
The easy mode answer would be just to schedule things using something like Windows Task Scheduler every X hours / minutes. That'll give you an approximation but not strictly speaking be exactly aligned with service restart.
For a closer approximation of 100% alignment, it'll be a much more complicated series of things. The method that seems the most straight-forward is something like this:
Script which checks the status of Engine(s). Example QRS API call: GET /qrs/servicestatus/full?filter=(serviceType eq 3)
This then writes the timestamp value (or serverNodeConfiguration > hostName & timestamp values for a multi-node environment)
Another script (or in the previous one): Checks the timestamp value against the prior row. If there's a difference then it executes CacheInitializer
This would be a fast reactive but still reactive method.
