MicroStrategy Enterprise Manager is just a project on top of MicroStrategy server that includes its own schema and lots of reports in order to monitor and analyze Intelligence Server statistics. Let's install Enterprise Manager:
CREATE USER MSTREM IDENTIFIED BY HAPPY2016 default tablespace USERS;
GRANT UNLIMITED TABLESPACE TO MSTREM;
GRANT ALL PRIVILEGES to MSTREM;
We can go to SQL Developer after some time to see how it is going. For example, let's look at one of the tables with statistics:
SELECT * from
MSTREM.STG_IS_SESSION_STATS;
We should see data in this table. In MicroStrategy, we collect statistics in one table and then load them to another table. Running this script, we can see when MicroStrategy last loaded the data to the Enterprise Manager tables:
SELECT
max(is_win_end),max(is_proc_begin),max(is_proc_end)
FROM EM_IS_LAST_UPDATE;
This script didn't return us a new date for the data load.
Enterprise Manager is comprised of three major parts: Statistics, Enterprise Manager Warehouse, and the Enterprise Manager Project. Activity within MicroStrategy is logged into the Statistics tables (these tables typically end in _STATS
; for example, IS_SESSION_STATS
records user session data) by the Intelligence Server. A majority of the out-of-the-box reports available in the Enterprise Manager project are sourced from Enterprise Manager Warehouse tables (these tables typically end with _FACT
). In order for the reports to reflect the current data, a data load needs to be performed to move the data from Statistics tables into the Enterprise Manager tables.
MicroStrategy provides best practices for configuring Enterprise Manager at https://community.microstrategy.com/t5/Server/TN273206-Best-practices-for-configuration-of-MicroStrategy/ta-p/273206.
If the data load is not working, we should use MicroStrategy Command Manager in order to create a schedule for the load. Let's look at Command Manager and understand why it is important to use it. Command Manager gives us the opportunity of different admin tasks using script language or procedures such as:
There is detailed information about Command Manager available in the Administrator System Guide.
Let's create a script that will set up a data load to the Enterprise Manager project:
CONNECT TO ENTERPRISE MANAGER "LOCALHOST.LOCALDOMAIN" IN
PORT 9999;
We should open port 9999
on Linux by modifying iptables as we did in Chapter 1, Getting Started with MicroStrategy.
START MONITORING SERVER " LOCALHOST.LOCALDOMAIN" IN PORT34952 USING
USERNAME "ADMINISTRATOR" PASSWORD "" FOR ENTERPRISEMANAGER
"MSTR101.TEST.MICROSTRATEGY.COM" IN PORT 9999;
CREATE DATA LOAD "DATALOAD" FOR ENVIRONMENT " LOCALHOST.LOCALDOMAIN"
AND PROJECT "MASTERINGBI", ENVIRONMENT " LOCALHOST.LOCALDOMAIN» DO
ACTION UPDATEWAREHOUSE CLOSESESSIONS UPDATEOBJECTDELETIONS BEGIN DATE
"10/22/2015 22:00:00 +0000" TO "10/25/2025 22:00:00 +0000" FREQUENCY
WEEKLY ON SATURDAY SUNDAY FROM 02:00:00 TO 06:00:00 EVERY 2 HOURS
ENABLED IN ENTERPRISE MANAGER " LOCALHOST.LOCALDOMAIN" IN PORT 9999;
LIST ALL DATA LOADS IN ENTERPRISE MANAGER " LOCALHOST.LOCALDOMAIN"
IN PORT 9999;
EXECUTE DATA LOAD "DATALOAD" IN ENTERPRISE MANAGER
" LOCALHOST.LOCALDOMAIN" IN
PORT 9999;
The following screenshot shows the Command Manager interface:
As a result, we will see data in Enterprise Manager tables as well as in Enterprise Manager reports. Moreover, we can connect Operations Manager to Enterprise Manager.
In order to start collecting statistics about the projects, we should set up a statistics database on Database Instance if there isn't one yet and set collection statistics for every project by going to the settings in MicroStrategy Developer:
Before we go to another part of the chapter, it is good to learn one more use case of using Command Manager - creating procedures that will disable the schedules. Let's imagine that we copy metadata and run it on another machine. We will meet one issue - all schedules will continue to work and business users will get their reports twice. We can write procedures that will return us a list of schedules and update the start date: