Installing MicroStrategy on Ubuntu Linux

MicroStrategy is not yet supported or certified to be installed on Ubuntu Linux. But there is way to achieve it.

/etc/sysctl.conf

….and installed a lot of supporting packages :

…and tricked the installer into thinking it was a redhat environment :

But, if you want to install in a free linux version, you can try Fedora, CentOS or OpenSuse.

Report Data Options in version MicroStrategy 9

You know how, after you execute a report, every time you make a change to the Report Data Options the report gets re-executed in order to apply those changes?
Well, in version 9 (not sure about 9.01 yet) this doesn’t happen for the Metric Join Type and Attribute Join Type options. I don’t know if this is a bug or a feature, though the behaviour appears to be intended by the developers. If someone from MicroStrategy is reading this, please provide some background details.
The downside of this is, of course, that if you are debugging a report by modifying one of those options, you might get the idea that your change had no effect whatsoever. This is because you were used with automatic re-execution after you pressed OK, as in the previous versions.

MicroStrategy In CentOS

Recently I got an opportunity to work with one of the non certified or un supported OS for MicroStrategy. The task was to install MicroStrategy 931 on Cent OS 6.4

Though it was not supported or certified – I was able to install them with couple of workarounds

- First thing is, you would need to identify the required library to be install in OS ( either 32 bit or 64 bit libraries )

- If during the course of installation, you get some error stating the library is missed – then you just need to download that library for CentOS or Linux based libraries and then perform YUM install

- Then you should be able to proceed with the install successfully

- Similarly, during the process of configuring intelligence server/ DSN / Metadata setup – similar errors pop up and you should need to perform yum install of required libraries.

By this way, it works successful to install MicroStrategy on CentOS.

Hope MicroStrategy confirms it’s certification with CentOS soon !!

How to remove shine\bevel effects on mstr custom apps

The following simple addition will let you remove the shining effects(the white line) on your custom mstr apps that you either release it internally for your company or to the app store. In the case of app store release it also removes the shining and the bevel effect from the itunes and the app store icon.

Once when you have the mstr custom app(both iphone and ipad apps) to be compiled and ready for generating a compiled binary you do the following

In the info.plist file, right click on the UIPrerenderedIcon key, make the type “boolean” and then check the checkbox

MicroStrategy System Manager – Awesome Tool !!

Recently explored the ‘System Manager’ component in MicroStrategy 9.3.1 version. it’s a very helpful tool for those working as Admin, project designer, project lead/manager (who handles entire BI-MicroStrategy components). This reduces the pain and helps to automate the entire schedule process example, if the narrowcast service dependent on cube and cube is on depend on data load, then it can be automated using ‘System Manager’ work flow.

The document (PDF) provided by MicroStrategy is very clear to understand and very easy to create any work flow. Only important point is, whoever design the work flow should capture every success and failure possibilities and handle those success/failures in the work flow.

What is work flow?

System Manager, it’s like a ETL Job, where you can create a workflow visually, allowing you to see the step-by-step process that leads the workflow from one process to the next. This visual approach to creating a workflow can also help you to notice opportunities to troubleshoot and error check processes as part of a workflow.

Here are the few important points to be known before developing any work flow. There is no code, program required to develop a work flow. It’s all about drag & drop and set the properties. For each object you drag & drop, properties can be set.

Work flow components:

  1. Workflow – One Complete job is called Work flow (like in ETL tools, there can be one or more Workflow
  2. Parameters – For every step you can assign Name and values, which will make use of the values for the assigned job in the work flow
  3. Exit Codes – While defining the process (work flow), you can assign the exit codes, which says whether it’s success or failure and also description for the same. On the Properties pane, scroll down to the bottom and click Show Descriptions. Later we can see it in the example
  4. Connectors –

                           Success – If the current process is completed with an exit code that is defined as a successful status, the process that the success connector points to is the next process that is attempted.

If you use a success connector from a process, it is recommended that you also use a failure connector.

                           Failure – If the current process is completed with an exit code that is defined as a failure status, the process that the failure connector points to is the next process that is attempted.

If you use a failure connector from a process, it is recommended that you also use a success connector.

                          Continue – Regardless of the status of the exit code for the current process, the process that the continue connector points to is the next process that is attempted.

If you use the continue connector from a process, you cannot use any other connectors for that process.

  1. Decision – A decision process is created in the workflow, as shown in the image below. Decisions provide the ability to determine the next process in a workflow based on specific exit codes for the previous process, rather than just the simple success or failure of a process
  2. Toggle Entry Process – This enables or disables a process as an entry process for the workflow. A process that is defined as an entry process is displayed with a green flag symbol, as shown in the image below.

 

  1. While any process, other than an exit process, can be enabled as an entry process for a workflow, you should limit the steps that are enabled as entry processes for various reasons:
  2. Split Execution – A split execution process lets you start multiple threads in a workflow to perform parallel processing of the tasks in a workflow. This can speed up execution of a workflow for systems that can handle the parallel processing.
  3. Merge Execution – A merge execution process is created in the workflow
  4. Comment icon – comment is created in the workflow. Comments can be used to provide additional explanation to the design of a workflow
  5. Exit Workflow – An exit process allows you to end a workflow as well as explain how the workflow ended.
  6. Validate Workflow – If the workflow is listed as valid, click OK to close the dialog box. If the workflow is not valid, click Details to review the reasons why the workflow is not valid. Click OK and make any required changes to the workflow. Once all changes are made, validate the workflow again.
  7. Log – Log file can be generated for the work flow
  8. Properties and parameters – Storing user credentials within System Manager introduces a security risk. Configuration information is not known until or during the actual configuration.
  9. Parameters can be stored as a file and reuse it in any work flow

There are more features available in MicroStrategy System Manger, those can be find in MicroStrategy’s supporting PDF and help menu in System Manager.