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:
- We should create a new database for Enterprise Manager. Now we should choose Oracle. MicroStrategy Enterprise Manager doesn't support PostgreSQL. Let's create a new Oracle schema using SQL Developer:
CREATE USER MSTREM IDENTIFIED BY HAPPY2016 default tablespace USERS; GRANT UNLIMITED TABLESPACE TO MSTREM; GRANT ALL PRIVILEGES to MSTREM; - Now we need to reconfigure Intelligence Server by adding an Enterprise Manager repository based on the MSTREM database that we just created. Enter all the information that we entered in Chapter 1, Getting Started with MicroStrategy and during the statistics configuration step, we should create a new DSN for the Enterprise Manager repository:
- Then we should choose this DSN (Enterprise Manager) and mark all rectangles:
- Click Next and Configuration Wizard will create tables in Oracle database. After this, we should click Finish and Configuration Wizard will do the rest of the work.
- The next step is deploying the Enterpise Manager project via Configuration Wizard. Click Create Enterprise Manager Project and choose our DSN from the previous step. As a result, we can open MicroStrategy Developer and find a new project - Enterprise Manager.
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:
- Modifying Intelligence Server and project settings
- Managing intelligent cubes
- Creating triggers for fire events and running schedule reports
- Managing security
- Managing administrative objects
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:
- Open Command Manager.
- Connect to Enterprise Manager using the following Command Manager outline:
CONNECT TO ENTERPRISE MANAGER "LOCALHOST.LOCALDOMAIN" IN PORT 9999;We should open port
9999on Linux by modifying iptables as we did in Chapter 1, Getting Started with MicroStrategy. - Once you have connected to Enterprise Manager, you have to create an environment (this step only needs to be done once). You can accomplish this by using the following Command Manager outline:
START MONITORING SERVER " LOCALHOST.LOCALDOMAIN" IN PORT34952 USING USERNAME "ADMINISTRATOR" PASSWORD "" FOR ENTERPRISEMANAGER "MSTR101.TEST.MICROSTRATEGY.COM" IN PORT 9999; - Once you have the environment configured, you can then use the following Command Manager outline to create a data load:
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; - Once you have the data load created, please run the following Command Manager outline to ensure that the data load was created successfully. The output should display all the parameters for your data load:
LIST ALL DATA LOADS IN ENTERPRISE MANAGER " LOCALHOST.LOCALDOMAIN" IN PORT 9999; - Once the data load has been verified, you can run the following command to trigger a manual data load:
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:
