MicroStrategy 7 Administrator Guide

Report execution with caching
1. MicroStrategy Intelligence Server checks to see if there is a valid report cache
for this particular report. If a valid cache exists, MicroStrategy Intelligence Server
returns the results to the client application and the process ends. If a valid cache
does not exist because there is no cache or the cache is expired, MicroStrategy
Intelligence Server creates a new job with a report instance and an associated task
list.
Steps 3-9 are the same as a typical report execution.
2. The Job Executor passes the job to the Result Sender which sends the
complete report results back to the client and returns the job back to the Job
Executor. If there was no cache, MicroStrategy Intelligence Server creates a new
one. If there was a cache but it was expired, MicroStrategy Intelligence Server
updates the cache. The Job Executor officially closes the job and the process ends.
C
O
N
C
E
P
T
S
Report execution with a prompt
When processing a report that contains a prompt, job execution is delayed until
the user supplies the necessary filtering criteria. When this happens, job execution
is put into a sort of “sleep mode” while it waits for user input. In this case, the
report resolution task has a few additional steps:
3b
Job request
Client
Reply message
Network Dispatcher
3c
Result Sender
3a 10
Job Executor
3
3d
Resolution Server
Steps 4-9
Report execution with a prompt
1. The Job Executor sends the job to the Resolution Server. The Resolution
Server discovers that the report definition contains a prompt. It returns the job to
the Job Executor telling it to prompt the user for the necessary information.
Report execution 23