Monthly Archives: July 2011

MicroStrategy Integration with Google Maps (Custom Visualizations)

Recently i tried the google maps integration with report/document and here are my inputs and some defintions with the help of MicroStrategy :)

Main Features :

  • Google Maps can viewed as regular maps
  • Threshold can be used
  • you can select single or multiple locations in the map and that can be used as filter

Prerequisites :

  • Need to get a license from Google (Google Maps API)
  • Configure the license with MicroStrategy WEB
  • Login to MSTR WEb –> Preferences –> Project Defaults –> General –> under Custom Visualizations –> Enable Custom Visualizations Editor

Configuration:

.Net Environment (Yet to try in J2EE)

To deploy the Map visualization plug-in to your MicroStrategy Web installation  and configure it, do the following:

  1. Navigate to GISConnectors in the MicroStrategy installation directory and open the folder that contains the Map visualization plug-in for your operating environment.

Open the ConnectorForGoogleMap_ASP  folder.

  1. From within the folder you just opened, copy the child ConnectorForGoogleMap folder to the plugins folder inside your MicroStrategy Web installation directory.
  2. Within the ConnectorForGoogleMap plug-in folder, navigate to WEB-INF/xml/config/google. Open the googleConfig.xml file
  3. Once you get the license key, paste the key in between <mk> and </mk>
  4. Add your API key between the <mk> and </mk> tags, in place of InvalidPremierKey shown in bold in the code sample below.– <gc>   <mk isPremier=true>InvalidPremierKey</mk>
  5. Restart your web server.
  6. Run the report
  7. Tools Menu –> Custom Visualizations –> Custom Visualizations Editor
  8. Enable this report to use Custom visualizations
  9. select AJAX — MAP (move to the right side)
  10. Enable –> Set view mode to custom visualizations and click ‘Visualizations Properties’
  11. In the editor;
    Select Locations –> Use attribute or form – Use attribute
    Select Locations –> Select data type – Latitude/Longtitude
    Select Locations –> Select Latitude – Store Latitude
    Select Location –> Select Longtitude – Store Longtitude form
  12. Click OK and Click OK on ‘Custom Visualizations’ editor
  13. Save the report

Intelligent Cube – Part-1

Intelligent Cubes: An Intelligent Cube is a set of data that can be shared as a single in-memory copy, among many different reports created by multiple users. Rather than returning data from the data warehouse for a single report,
you can return sets of data from your data warehouse and save them directly to Intelligence Server memory. The reports accessing Intelligent Cubes can use all of the OLAP Services features for analysis and reporting purposes.

Intelligent Cubes are created and published for use as a shared data source for the users to build reports from. Intelligent Cubes provide the fast response time and analytic calculations that are often associated with Multidimensional Online Analytic Processing (MOLAP) cubes, while also benefiting from the ability to use Relational Online Analytic Processing (ROLAP) by drilling into the full set of data outside of the Intelligent Cube. In addition, Intelligent Cubes are fully scalable, limiting excessive data consumption and redundant data by allowing you to build only the sets of data you require.
An intelligent cube is made up of two files – an info file (contains the structure of the cube) and a data file. Each one of them has a representation in memory and indicates different things:

  1. When the data file is not  updated with its representation from memory, the cube’s “dirty status flag”  is set to true.
  2. When the info file is different from its representation in memory, then the cube’s “monitoring information dirty status flag” is set to true.

While (1) indicates that the data of the cube is incorrect (2) indicates that the cube’s monitoring information is different on disk than it is in memory.

The following section discusses an example of the workflow and status change for MicroStrategy 9.x Intelligent Cube:
P = Processing, A = Active,  L = Loaded, D = Dirty, F = Filed, M = Monitoring Information Dirty

Coming soon on dynamic cube usage