Placement of MicroStrategy Engine Components And Architecture

The three engine components ( SQL/Query/Analytical Engine) are objects that can be invoked as needed to perform their tasks.

All the 3 engines are physically stored on both the client machine & Intelligence Server(IS) machine. The use of this component is dictated by the configurations of the system ( 2 tier / 3 tier / higher ).

2 Tier Configuration System:
In this system, the client connects directly to the DWH & MD databases and the MicroStrategy engine components are invoked on the clients side. The SQL Engine can be loaded on demand on either the client side ( in 2 tier ) or on Intelligence Server ( in 3 tier ).

For eg: if we run a report in MicroStrategy Desktop ( 2- tier ) , the SQL Engine component in MicroStrategy Desktop is invoked to perform the SQL generation. Similarly, in a 2 tier configuration, the Analytical engine component on MicroStrategy(MSTR) Desktop is invoked to perform the formatting.

3 Tier / 4 Tier Configuration System:
In this systems, the client establishes the connectivity to the DWH & MD Databases through Intelligence Server, so the MicroStrategy engine components are invoked on the IS Side.

For eg: if we are running a report in MSTR web in a 4 tier environment, the SQL engine component on IServer is invoked to perform the SQL generation and the Analytical engine component on IServer is invoked to format the required results.

To get in-Depth knowledge on Microstrategy you can enroll for a live demo on Microstrategy Training

MicroStrategy Architecture

Generally MicroStrategy follows 3 kinds of architectures.
- 2 - Tier Architecture
- 3 - Tier Architecture
- N - Tier Architecture

2 Tier Architecture :

This involves connecting the MicroStrategy Desktop / DWH / MD together.

So, if you look at the above picture - it clearly shows about the 2 tier architecture involved in MicroStrategy.Whatever objects that you create inside the MicroStrategy layer gets stored in their Metadata database. So by default, when you start work/create a project - you would require a metadata database created ( empty shell ) and then start your new project creation on top of it. So this can be done either in 2 tier / 3 tier / n tier based applications. Here we talk about the 2 tier architecture and hence the Metadata database connection needs to be established between your Project Source first ( 2 Tier Project is also called as Direct connection - which connects directly to the Metadata and DWH ). Then you might need to establish the connection to the DWH / ODS / Datamart required to fetch data for the reports/dashboards/documents that your going to develop with the help of MicroStrategy.

All the connections between the MicroStrategy Desktop --> MD & DWH happens through the ODBC connection.


MicroStrategy Desktop --> Primary Developer interface used to develop the objects required for the reports/dashboards/documents.

Take your career to new heights of success with Microstrategy Courses

3 Tier Architecture

This is the major achievement from MicroStrategy which no other BI application has made it to be as like this sort of functionality coupled with it. Its none other than the MicroStrategy Intelligence server which is treated as the Heart of the MicroStrategy.

So, the new componet IS ( Intelligence Server ) is added in between your Microstrategy Desktop & MD/DWH. So the MD connection & DWH connections happen through ODBC DSN is first setup with Intelligence Server configurations and then there after you create a project source in your MicroStrategy Desktop configured to connect to IS ( Also called as Server Connection based where as 2 tier is referred as Direct Connection ). This would be through TCP/IP connections while the db connections are happened through ODBC Connections.

Read Here For More Information Microstrategy Online Training

N - Tier Architecture

This is the key architecture used by Many clients who are using the MicroStrategy as BI tool. The main purpose of BI is to make better decisions through the RAW DATA that we extract from source and provide the useful informations from it to the end users. The end users should be happy to see the reports on first look and also the quality of data is must to make a better decisions. Here N - tier architecure involves Web Server added to the top of Intelligence Server. Also it will have the NCS ( Narrowcast Server) , Mobile Server attached on top of it. So the intelligence Server communicates to every other component as and when there are request coming from different perspective. It could come from MicroStrategy Desktop or Web based application ( IE/Safari/Chrome/Firefox/etc) or Mobile applications ( iPad/iPhone/Smartphones).

One another thing i would like to highlight here is that NCS is been replaced by Distribution Services to send the alert notification to end users which was previously handled by NCS separately.