MicroStrategy 7 Administrator Guide

3URGXFWLRQÃHQYLURQPHQWV
In a production environment, it does not make sense for you to manually trigger
events. Using the MicroStrategy utility FireEvent.exe (installed with the
MicroStrategy SDK), you can have external systems trigger events using a
command line and achieve true scheduling automation.
C
O
N
C
E
P
T
S
7LSÃThe following command line is an example of the syntax you must use to
trigger an event with FireEvent.exe:
FireEvent -fire Event1 -srv my_server -prt 34592
-uid Administrator -pwd Hello!
In this case, you are triggering an event called "Event1" on a server called
"my_server" through port "34592" using the "Administrator" login with a
password "Hello!".
For example, suppose you want to execute several reports immediately after a
database load occurs. You can have the database load routine open a remote shell
on the MicroStrategy Intelligence Server machine and execute FireEvent.exe. The
event you specify in the command line will be triggered just as if you manually
triggered it from the Event Viewer.
Cache refreshing
Sometimes, it is not important to deliver the results of a scheduled report to the
user. In some cases, it is more important to refresh a report cache, which can be
shared by several users.
To do this, you create and cache the reports and provide access to them. Then you
create the schedules to refresh those reports. The messages will be delivered to
your inbox. Users wishing to retrieve the results can access the cache by running
the shared, cached report.
Cache refreshing schedules are usually event-triggered since caches do not need
refreshing unless the underlying data changes from an event like a warehouse
load.
For example, suppose a set of standard weekly and monthly reports has been
developed in the system. These reports should be kept in cache because they are
frequently accessed. Certain tables in the database are refreshed on a weekly basis,
and other tables are refreshed on a monthly basis. Whenever these tables are
updated, the appropriate caches should be refreshed. Note that although the
refresh occurs on a weekly or monthly schedule, the refresh does not complete at
exactly the same time each week/month.
Cache refreshing 47