Map Intelligence (MI) is deployed as a Client-Server system to provide the platform enabling communication between the BI / reporting tools, map providers and dynamic web services for data and specialised functions (primarily geographical and statistical).
The three MI components are shown in shades of blue in the following diagram:
The borders between the various sections of this diagram are intended to show how where the MI components conceptually fit together. Note: this conceptual view corresponds to the users’ impression of what is happening which does not necessarily correspond to the actual intercommunication between MI components. For example, there is no direct communication between the MI Viewer and the MI Builder components – the MI Server always acts as the intermediary.
The MI Server processes all the run-time information sent from the MI Client components, dynamically manages presentation of the various MI Builder screens and dynamically generates the MI Viewer GUI during a user session. The MI Server manages all interactions with map-servers. The MI Server has a number of administration tools that include license administration, global default settings and customization of various applications features such as pop-ups.
The MI Viewer is the application user interface for manipulating the MI Builder defined views of the mapped data. Application consumers (end users) interact with the dynamically generated MI application via the MI Viewer which is presented within a web browser.
The MI Client is used as a convenient description for the bundle of MI components which are purchased and installed within or alongside the BI environment – eg: the MI Client for Cognos. The MI Client also comprises a number of configuration ‘screens’ presented in a browser. These enable the design of the integrated mapping ‘application’ to be done without any programming. The configuration specified dictates how the MI Viewer appears within the BI application.
Using the MI Client Integration Kit (CIK), Integeo and its partners are progressively extending the range of software products integrated with MI.
Connection between the various components of a Map Intelligence deployment may break for external reasons such as security settings or network failure. As far as possible following good programming practices, Map Intelligence has been engineered to give meaningful reports when any code malfunctions. Since Map Intelligence is a reporting and analysis tool there are no vital rollback mechanisms required and any such mechanisms are the province of the involved BI tool and databases.
Map Intelligence deployments are usually configured to read from a central repository of spatial data - similarly on the BI side Map Intelligence pulls data from the BI tool using it as a data source. If Map Intelligence is deployed in this manner there are usually no data migration or load issues.