These steps assume that everything is on the one machine, but of course this is not necessary (and the joy of using IIS/xmla to connect from client to data source).
- Windows Server 2008R2 (the process is a little different in 2008, and quite different in 2003 and earlier).
- 'Web Server (IIS)' role enabled on the server.
- BI4.0, licenced for Advanced Analysis, Edition for Web Edition.
- Microsoft Analysis Services (2008 R2 used here).
Getting the Files
- First, create a folder for the files that you're about to copy. Go to C:\inetpub\wwwroot and create a new folder called 'olap'. If this path doesn't exist, then check that IIS is installed and configured correctly.
- On a vanilla install of SQL 2008R2 you will find the files you need in the folder C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\bin\isapi. In this directory, there will be a Resources folder, a msmdpump.dll and a msmdpump.ini file.
If you can't find the files, search for 'msmdpump' on your drive.
- Copy the contents of the isapi folder into the olap folder you created in step 1. You should now have a structure something like this:
Setting up IIS
- Open up the Internet Information Services (IIS) Manager.
- In the Connections pane, expand Sites > Default Web Site. If you see olap in the tree, then everything's going well.
- In the Connections pane, right click on Application Pools and select Add Application Pool…
- Configure the following settings:
- Now, in the list of application pools, select the olap pool and click Advanced Settings… over on the right. Ensure that Enable 32-Bit Applications is set to False. If this is true, the connection won't work.
- Convert your olap website to an application like so:
- In the window that appears, next to Application pool: click the Select… button.
- Change the application pool to olap.
- Click OK.
- Click OK again.
- With the olap site selected in the Connections pane, double-click Handler Mappings in the IIS category.
- With nothing in particular selected in the middle, click on Add Script Map… in the Actions pane on the right.
- Fill out the fields like this:
- Click OK.
- Click Yes to the message that appears.
We're half way through. Now to set up the authentication.
- Click again on the olap site in the Connections pane.
- Double click on Authentication in the IIS category.
- Right-click on the Windows Authentication entry and click Enable
SecurityFrom what I can see, there are two ways of allowing Business Objects to connect through IIS to your Analysis Services Cube. The first option is to simply enable Basic Authentication in the step above. If you're happy with the security implications of this, go for it, and skip ahead to Creating an OLAP Connection. Otherwise, follow these steps:
- Open SQL Server Management Studio, and log into your Analysis Services instance.
- Right-click on the instance node and select Properties…
- Go to the Security page and click Add… down in the bottom right.
- Type IUSR in the box and click the Check Names button. The text should become underlined like so:
- Click OK, then OK.
Disclaimer: I'm no security expert. Check with someone knowledgeable before putting this solution into a production environment.
Creating an OLAP Connection
- Open up the CMC and click on OLAP Connections in the Organize column of the home screen.
- Click the New Connection button.
- Give the connection a name.
- In the Provider box, select Microsoft Analysis Services 2008.
- In the Server box, type http://localhost/olap/msmdpump.dll (replacing localhost if applicable)
- If you allowed the ISUR account to access to your cube, here you can just type in the username and password required to access the cube.
If you instead have allowed Basic Authentication in your IIS site, you must enter the username in the format DOMAIN\User and a password.
- Click OK.
- Select a cube (or a perspective) and click Select.
- Enter the Authorization options to taste. Note that here you can just enter a user name (no domain prefix) regardless of the security path you chose.
- Click Save, and you're done!
Your cube will now be available to your Advanced Analysis Workspaces.