Configuring Enterprise Manager

Once Enterprise Manager is installed, the data loader service is configured, and the projects are set up to log statistics, you can configure Enterprise Manager to process the statistics and load them into the Enterprise Manager repository. This involves connecting to Enterprise Manager using MicroStrategy Command Manager and creating one or more data loads.

Creating a data load

You can create a data load and specify which projects Enterprise Manager will monitor, select which maintenance tasks the data load performs, and set the schedule for when the data load runs.

Prerequisites

You must have Enterprise Manager installed on the same machine as Command Manager.
Before you can create a data load, you must be able to access Enterprise Manager using MicroStrategy Command Manager.
The projects must already be configured to log statistics.

For a description of what happens in the data load process, best practices to consider when setting it up, and maintenance tasks that can be done as part of the process, see Data loading.

To create a data load in Enterprise Manager

Open Command Manger and create a connected or connection-less session. For configuration purposes either will work.
Run the following command to connect the Enterprise Manager Data Loader service to a MicroStrategy environment by choosing an Intelligence Server from that environment

This command has to be called for every environment for which a data load needs to be created.

START MONITORING SERVER "<I-Server_machine_name>" IN PORT <port_number> USING USERNAME "<username>" PASSWORD "<password>" FOR ENTERPRISE MANAGER "<em_machine>" IN PORT <em_port>;

Field	Description
`<I-Server_machine_name>`	Name of one of the Intelligence Servers from the environment you want to monitor/run a data load for. If you have a cluster of Intelligence Servers, choose anyone and Enterprise Manager will automatically pick up all the Intelligence Servers in the cluster and save them. When a data load is triggered, Enterprise Manager does a load analysis for each Intelligence Server and chooses the Intelligence Server with the least load to help with the data load. Do not enter "IP" or "Localhost" in this field.
`<port_number>`	First `<port_number>` field is related to the port number where Intelligence Server is running. (Default Intelligence Server port is 34952)
`<username>`	Metadata Username
`<password>`	Metadata Password for the Username above. Note: If password is empty (not recommended), simply enter this field as PASSWORD ""
`<em_machine>`	Name of the machine where Enterprise Manager is running. Do not enter "IP" or "Localhost" in this field.
`<port_number>`	Second `<port_number>` field is related to the port number where Enterprise Manager is running. (Default Enterprise Manager port is 9999) Note: If you would like to change the port number where Enterprise Manager is running, please use MicroStrategy Service Manager on the machine where Enterprise Manager is installed and select 'Enterprise Manager Data Loader' service, click Options > Enterprise Manager Options.

Select the projects you want to monitor with the following command:

CREATE DATA LOAD "<name>" FOR ENVIRONMENT "<server_name>" AND PROJECT "<project_name>" [, ENVIRONMENT "<server_name>" AND PROJECT "<project_name>" ...] DO ACTION [UPDATEWAREHOUSE] [CLOSESESSIONS] [REPOPULATETABLES] [UPDATESTATS] [UPDATEOBJECTDELETIONS] BEGIN DATE <date> [TO <date>] FREQUENCY (DAILY | WEEKLY ON [MONDAY] [TUESDAY] [WEDNESDAY] [THURSDAY] [FRIDAY] [SATURDAY] [SUNDAY] | MONTHLY ON DAY <number>) (AT <time> | FROM <time> TO <time> EVERY <number> (MINUTES | HOURS))(ENABLED | DISABLED) IN ENTERPRISE MANAGER "<em_machine>" IN PORT <port>;

Field	Description
`<name>`	Name you would like to give to the data load
`<server_name>`	Name of the Intelligence Server used in the "START MONITORING SERVER" command above.
`<project_name>`	MicroStrategy Project you would like to monitor/run data loads for. Statistics needs to be enabled for the projects before you can include them in the `CREATE DATA LOAD` command. Parameterized inserts need to be enable in the DBInstance being used as the Statistics DBInstance for the project
`DO ACTION [UPDATEWAREHOUSE] [CLOSESESSIONS] [REPOPULATETABLES] [UPDATESTATS] [UPDATEOBJECTDELETIONS]`	These are the tasks the data load will carry out every time it is triggered. `UPDATEWAREHOUSE` is the task that populates the basic look up and fact tables in the Enterprise Manager warehouse and is mandatory. `CLOSESESSIONS` makes sure all incomplete sessions at the time when the data load is triggered are handled correctly. It is recommended to run `[CLOSE SESSIONS]` with every data load. `REPOPULATETABLES` populates all the Relationship tables in the Enterprise Manager Warehouse such as relationships between Users & User Groups, Reports and Attributes, Reports and Metrics etc. `UPDATESTATS` is a task that runs database specific commands to optimize the cost of each query that is run against the database. `UPDATEOBJECTDELETIONS` is a tasks that updates the current status of the objects by comparing with the metadata that is, whether they still exist or not. Specifically, it updates the `EM_EXISTS_ID` column in for each object look up table with a 0 if it is deleted from the metadata. `REPOPULATETABLES`, `[UPDATESTATS]` and `UPDATEOBJECTDELETIONS` are expensive tasks and can significantly increase the time of your data loads depending on the size of your metadata.
`BEGIN DATE <date> [TO <date>]`	Date at which the data load should begin executing and when it should end executing. The format required by the `<date>` field is "`dd/mm/yy 00:00:00 +0000`" where dd/mm/yy is the DATE, 00:00:00 is the time and +0000 is the offset. If you would like the data load to start executing from today till forever simply enter the first `<date>` as "`dd/mm/yy 00:00:00 +0000`" where dd/mm/yy is a date in the past and enter the second `<date>` as something many years in the future such as "12/31/2050 00:00:00 +0000". Note: Both <date> fields are mandatory. By default, all date times are saved in your machine's time zone. In most cases where a user wants data load to begin running from today and continue running till they delete it, this field should be set as "BEGIN DATE "01/01/1970 00:00:00 +0000" TO "12/31/2050 00:00:00 +0000"
`FREQUENCY (DAILY \| WEEKLY ON [MONDAY] [TUESDAY] [WEDNESDAY] [THURSDAY] [FRIDAY] [SATURDAY] [SUNDAY] \| MONTHLY ON DAY <number>)`	When the data loads should loads run that is, Daily, weekly, monthly. Note: This is a mandatory field. If you would like to run them Daily then please use "FREQUENCY DAILY ON MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY". If you would like them to run weekly on Saturday and Sunday only then please use "FREQUENCY WEEKLY ON SATURDAY SUNDAY"
`FROM <time> TO <time>`	This field tells Enterprise Manager what time the data load should run on a particular day. A user needs to account for the following two factors when filling in this field: Your machine's time zone where you are running Command Manager All times are saved in UTC time zone by the EM service. Note: This is a mandatory field. By default, all times are saved in UTC. Hence, (1) if the machine you are running Command Manager on in EST time zone and you want to run the data load at 23:00:00 EST, then please enter th field as 'FROM 04:00:00 TO 05:00:00'. This is because; 4 am UTC is 11 PM EST. (2) If the machine you are running Command Manager on is in PST time zone and you want to run the data load at 23:00:00 PST, then please enter this field as 'FROM 07:00:00 TO 08:00:00'. This is because; 7 am UTC is 11 PM PST. (3) If the machine you are running Command Manager on is in EST time zone and you want to run the data load at 23:00:00 PST, then please enter this field as 'FROM 07:00:00 TO 08:00:00'. This is because; 7 am UTC is 2 am EST which is is 11 PM PST.
`EVERY <number> (MINUTES \| HOURS))`	Frequency at which the data load should run. If you would like to run it every 2 hours, please use "EVERY 2 HOURS". This is a mandatory field.
(ENABLED \| DISABLED)	If this data load is enabled (will run) or disabled (will not run). This is useful in cases where you don't want the data load to run (as you may be troubleshooting an issue) but you do not want to delete it either.
<em_machine>	Name of the machine where the Enterprise Manager is running.
<port_number>	Second `<port_number>` field is related to the port number where Enterprise Manager is running. (Default Enterprise Manager port is 9999) If you would like to change the port number where Enterprise Manager is running, please use MicroStrategy Service Manager on the machine where Enterprise Manager is installed and select Enterprise Manager Data Loader service, click Options >Enterprise Manager Options tab.

Once a data load is created, you can verify when it will run next by running the following command:

LIST DATA LOADS IN ENTERPRISE MANAGER "<em_machine_name>" IN PORT <port>;.

The Next Execution field in the results will highlight when the next data load will be triggered.

Example

Below is a sample "CREATE DATA LOAD" scenario as entered into Command Manager

Time zone of Command Manager Machine: EST

Cadence: Daily

Time user would like to run a data load: 11 pm EST

Data Load Tasks: Only basic data load – sufficient for 80% of Enterprise Manager reporting.

CREATE DATA LOAD "Daily 11 pm" FOR ENVIRONMENT "<I-Server_machine_name>" AND PROJECT "<project_name>" DO ACTION UPDATEWAREHOUSE BEGIN DATE "01/01/1970 00:00:00 +0000" TO "12/31/2050 00:00:00 +0000" FREQUENCY DAILY ON MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY SUNDAY FROM 04:00:00 TO 05:00:00 EVERY 2 HOURS ENABLED IN ENTERPRISE MANAGER "<em_machine>"IN PORT <port>;

After you have configured Enterprise Manager and used it, you can maintain the data loads. For steps on how to disable and enable them, modify schedules, change what maintenance tasks are performed in the data load, and delete the data loads, see Maintaining Enterprise Manager.