Recently, while working on one of my project assignments I got to work on the integration of SharePoint 2010 with MicroStrategy 9. The requirement was to pull the report from the MicroStrategy and show that in a web part. We had the MicroStrategy environment set up and also I had my SharePoint development environment set up.Here, I will show you how you can configure the SharePoint environment to pull reports from the MicroStrategy. When you contact MicroStrategy for their portlets, which can be plugged with SharePoint, you will get a .CAB file. This CAB file has two web parts in it 1) ‘MicroStrategy Master Web Part’ 2) ‘MicroStrategy Web Part’. This also has MSTRWebParts.dll which, you can use to create a custom web part to display data from MicroStrategy(I will talk about this in other post), and a few .js files. You might be thinking “Enough of talking, Take me to the procedures of configuration”. So here you go:

Step 1: Install the CAB file: Log in to the server machine as an Administrator. To install the CAB file you can use following commands:stsadm.exe -o addwppack -filename “$your_location_of_cab_file$\MSTRWebParts.CAB”. 

Step 2: Configuring security for the MicroStrategy Web Part:
To configure the security either you can elevate the permission level to ‘Full Trust’ in the web.config file, which is neither a good practice nor secure, or you can use Trust level as WSS_minimal” and modify the appropriate policy configuration file which is located at “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Config\wss_minimaltrust.config” and make an entry for MSTRWebParts.dll in the <CodeGroup> section. You can read more about it over the net. There are many good articles explaining “Custom CAS policy for SharePoint”. You can also follow this Microsoft documentation.

Step 3: Enabling HTTP Session State in SharePoint

The MicroStrategy Web Part for the SharePoint Portal requires the HTTP Session State to be enabled. However, by default, HTTP Session State is disabled by the SharePoint Portal Server. To enable the HTTP Session State in SharePoint Portal 2010, you must modify the web.config file for SharePoint (located by default under C:\Inetpub\wwwroot\wss\VirtualDirectories\ and SharePoint Admin (located by default under C:\Inetpub\wwwroot\wss\VirtualDirectories\.

Note: It is a good practice to make a backup of important configuration files, such as the web.config file, before making changes.

To enable HTTP Session State, use any text editor to make the following changes to the web.config files in the locations described above:

1. Enable the SessionStateModule:

Add the node shown in bold below as a child node for the node:Before:<httpModules/>

After:

<httpModules>

<add name=”Session” />

</httpModules>

1. 1. Enable the SessionState:

Find the node beneath . Set the enableSessionState attribute to “true”.

1. Add the session state module to the IIS (Internet Information Services) 7 managed pipeline for MicroStrategy Web.
   1. Open IIS 7 Manager and find SharePoint.
   2. Double-click Modules in the IIS section.
   3. Click Add Managed Module … in the right-hand pane.
   4. On the Add Managed Module dialog, enter a name such as “SessionState” and choose System.Web.SessionState.SessionStateModule from the dropdown.
2. Restart IIS for the changes to take effect.

Step 4: Creating User Profiles for MicroStrategy Credentials and Locals:

To set user credentials and locales for a MicroStrategy Web Part, you must add the necessary user profile properties on the SharePoint Portal Server. To set these properties, do the following:

1. Open SharePoint Central Administration, click Manage Service Applications under Applications and then click on User Profile Service Application. On the page that opens, click on Manage User Properties under People and then click on New Property
2. In the Property Settings textboxes, add the properties listed below, using the values provided or indicated. If you want to give users the ability to change credentials or set locales, choose “Allow users to edit values for this property” in the Edit Settings options.
   

   Property	Settings	Name	DataLocale	DisplayLocale	MSTR-UID	MSTR-PWD	MetadataLocale
   	Display name	Data Locale	Display Locale	MicroStrategy User	MicroStrategy	Password	Metadata Locale
   	Type	integer	integer	string	string	string	integer
   Sub-type of Profile	Make sure that the checkbox for “Default User Profile Sub-type” is checked
   Policy Settings	Select “Optional”, rather than “Required” (which is the default selection)
   Edit Settings	Select “Allow users to edit values for this property”

   When you make these property settings, you must use the exact property names and types shown in the table above, but you can use different display names if you want.

   You can choose whether or not to let user see or edit these settings. To give users the ability to change credentials or set locales in a MicroStrategy Web Part, you must add the necessary user profile properties on the SharePoint Portal Server.

   If you don’t want Web Part users to be able to change the data locale or display locale, the DisplayLocale and DataLocale profile properties are optional. In this case, the SharePoint Portal user’s language setting will be used for these two locales. If you use only Windows Authentication or Guest Authentication, the MSTR-UID and MSTR-PWD profile properties are also optional.

   If you don’t want to allow Web Part users to change the values for any of their user profile properties (DataLocale, DisplayLocale, MSTR-UID, or MSTR-PWD) on the edit pane, you should not change Edit Settings to “Allow Users to edit values for this property”. When this setting is not made, only portal server administrators can assign and change the values for these profile properties in the Shared Services Administration page.

That’s it. You are good to go now. Go to the page>Edit Page and add “MicroStrategy Web Part” to it and configure all its values. If you have proper permissions to your MicroStrategy environment then you should be able to see the report that you have configured in the web part settings.

 

[This blog may not be relevant]