– MicroStrategy Desktop
– MicroStrategy Command Manager
– MicroStrategy Integrity Manager
– MicroStrategy Object Manager
– MicroStrategy License Manager
– MicroStrategy Configuration Wizard etc…
Today we’ll discuss about the key development interface –> MicroStrategy Desktop.
MicroStrategy Desktop enables you to design, create and maintain an entire BI system from a single interface by integration following components in it;
– Desktop
– Architect
– Administration
Desktop:
MicroStrategy Desktop is the only BI application in the market engineered to support the full requirements of very large databases without any complex coding. It includes over 200 predefined functions. We can even create our own functions and integrate them to use it in reports.
Architect:
MicroStrategy Architect is a convenient database reference utility lets you view column names and data types for any tables in the DWH and speeds application development by evaluation definitions in the logical model. It enables us to update the centralized metadata, there by reduces system maintenance.
Administration:
Most of the admin functions are found in the MicroStrategy Desktop itself. Few things to highlight here are like user management –> managing the users/user groups for a project/project source. Security roles to specify the role for a user ( Power Users / Architect / Report Designer / Desktop Analyst / Desktop Designer / Web Reporter / Web Professional / etc )
Also Deliveries containing the components involved for delivering the reports or dashboard through Email devices/transmitters and similarly file devices & transmitters.. etc.
Configuration managers are for setting up the project to connect to DWH –> Creation of DB Instances , then the schedules for subscriptions ( Time / Event based schedules ), then the Event to trigger , Security Roles & Subscriptions that are done by the users using the application.
System Monitors provided information about the running jobs ( reports/element request/schedules request/etc ), user connection to the projects , database connections to the project, then the caches involved for the reports/documents/ i cubes and then about the change journal to capture the change history by the users for further references to track the changes.
