Page tree
Skip to end of metadata
Go to start of metadata

This BOpedia page is provided by the RIG team. Don't hesitate to put comments.
Contributor : Gregory Botticchio, RIG specialist,

Product versions:
MSAS 2005 and 2008
Microsoft Windows Server 2003 and 2008



This article is for those of you who want to create an HTTP access to a Microsoft Analysis Services OLAP cube, for SAP BusinessObjects InformationDesignTool (IDT) 4.0 or SAP BusinessObjects Analysis edition for OLAP.

Microsoft SQL Server 2008 Analysis Services uses the same architecture for providing HTTP access as did SQL Server 2005 and 2000 Analysis Services.
The pump component is loaded into IIS (Internet Information Services) and serves as an ISAPI extension, pumping data from the client to an Analysis Services server and back.

(source: Microsoft)

NOTE: This article walks you through the process of setting up HTTP access to SQL Server Analysis Services 2008 on MS Windows Server 2008.
It is based on the following Microsoft white paper (here), related to the same topic, but for SQL Server Analysis Services 2005 on MS Windows Server 2003.

Check IIS and ISAPI installation.

  1. Verify it is up and running by accessing the following URL:
  2. You should get the following:
  3. Otherwise, execute the "Computer Management" tool
    1. To do so, do a "Right Click >> Manage" on the "My Computer" icon;
    2. Then, select the "Features" tab;
    3. Click on "Add Features";
    4. Add the following features:
      1. ".NET Framework 3.0 Features";
      2. "Web Server (IIS) Tools" in "Remote Server Administration >> Role Administration Tools";
      3. "Windows PowerShell";
      4. "Windows Process Activation Service";
    5. Click on "Next" then "Install";

Getting binaries.

  1. Copy the contents of the "%Installation folder%\OLAP\bin\isapi" directory into the folder you would like to become the base for the virtual directory in IIS.
  2. In this example, copy all the files from the "C:\Program Files\Microsoft SQLServer\MSAS10.MSSQLSERVER\OLAP\bin\isapi" folder into the "C:\inetpub\wwwroot\olap" folder.

NOTE: Make sure that the folder becoming the base for the virtual directory is located on the drive formatted for the NTFS file system. Due to IIS limitations, the path to your directory should not contain spaces.

Creating an application pool.

  1. Open the "Computer Management console": right-click the "My Computer" icon and select "Manage" on the shortcut menu;
  2. In the Computer Management console, expand the "Roles" node and then the "Web Server (IIS) and Internet Information Services" node;
  3. Right-click the "Application Pools" to open the shortcut menu and select "Add Application Pool...";
  4. Name the application pool "olap";
  5. See Figure 2:

Settings up an application.

  1. Do a "Right-click" on the OLAP directory in your Web site to open the shortcut menu and select "Convert to Application";
  2. In the "Application pool" field, choose the one previously created. See Figure 3:

Setting up directory properties.

  1. Click the "olap" virtual directory node and select "Handler Mappings" from the menu. See Figure 4:
  2. Click on the "Edit Feature Permissions..." in the top right corner of the "Handler Mappings";
  3. Make sure that the directory has "Read and Script" permissions. See Figure 5:
  4. Click OK to close this dialog box;
  5. Click the option " Add Script Map..." in the top right corner of the "Handler Mappings" screen;
    1. Enter ".dll" in the "Request path" text field;
    2. In the "Executable" option, enter the full path name to "msmdpump.dll". In our example, it would be: "C:\inetpub\wwwroot\olap\msmdpump.dll";
    3. Name the Script Map. In our example, we call it "olap";
    4. See Figure 6:
  6. Click on the "OK" button to accept the settings;
  7. When you hit "OK" to add the script mapping you will be prompted if you want to enable the ISAPI extension. (See Figure 7.). Click "YES" to accept the settings;
  8. The configuration of this decision can be found under "ISAPI and CGI Restrictions" of the server IIS. See Figure 8:
    1. Click on the "ISAPI and CGI Restrictions" icon;
    2. Verify that the "olap" extension is well present into the list;
    3. Otherwise, click on "Add..." from the top right corner of the "ISAPI and CGI Restrictions" to add it like in the Figure9:

Selecting security settings.

  1. Click your virtual directory node and select "Autentication" from the menu. See Figure 10:
  2. You are presented with three options. Choose & enabled one of them.
  3. See Figure 11:

Selecting the target Analysis Services server.

  1. As you can see in the architectural diagram in Figure 1, every pump component uses its own
    configuration file;
  2. Open the "msmdpump.ini" file located in your folder and take a look at the contents of this file. It should look like the following:
  3. The only setting you are interested in at this point is <ServerName>.
    If the Analysis Services instance that you need to provide access to is located on the local machine and installed as a default instance, there is no reason to change this setting. Otherwise, you need to specify the machine name and instance name ( mymachine\inst1).

Getting it all together.

At this point you should have configured your HTTP pump and should be ready to connect from your application.
If your application provides you with a way to specify the server name, all you need to do is to substitute your server name with the path to your virtual directory concatenated with
As in SQL Server Analysis Services, the MSOLAP OLEDB provider will understand that the server name includes an URL path and will automatically start using HTTP protocol.
In our example, to connect to "MyMachine" from the MDX sample application, you should be able to connect to the Analysis Services server using "http://MyMachine/olap/msmdpump.dll" as a server name.