I am using Xcelsius 2008 SP3 FP1 to build a dashboard with QaaWS queries running against BOE XI R2 providing the dashboard’s content.
The dashboard is showing Operational information and so is requiring as real-time data as is possible.
A number of QaaWS queries ‘pull’ data into the dashboard from a datamart that is being refreshed via ETL every 30 mins.
A flag is being written to the datamart when the ETL process successfully completes.
This flag is being polled by an Xcelisus QaaWS query that is scheduled to run every 2 mins.
When Xcelisus detects the flag has been updated another 9 QaaWS queries are triggered so as to repopulate the dashboard’s data.
It all works well enough, but this data ‘pull’ strategy results in a dashboard that shows stale information for up to 2 mins out of every 30 mins.
That is, the flag indicating that the ETL has completed is not being detected for up to 2 mins after it has been updated which means that the content-providing QaaWS queries are triggering up to 2 mins after the latest data is available.
If the required data could be ‘pushed’ from the datamart the instant the ETL was finished then dashboard users could get see the latest data without delay.
I’m interested in hearing from anyone with a similar concern, especially if you managed to resolve it! 
Is the only way of ‘pushing’ data into Xcelsius is via Adobe LCDS (Live Cycle Data Services)?
If yes, can anyone relate their experience using LCDS with Xcelsius and perhaps provide a pointer to some doco on how to do it?
Thanks in advance
wnissen (BOB member since 2008-01-30)