If you are setting up one of the Business Objects products to use an OLAP data source for the first time sometimes it doesn’t ‘just work’. This article contains a quick list of items to check and tests to perform to get your first OLAP connection working.
Check 1: Support
The first check to make is to see if the version of the OLAP server is supported with the version of the Business Objects product you want to use. If your data source is unsupported then you may have connectivity set up correctly but the connection may be actively blocked by the Business Objects products.
A summary of which OLAP servers are supported in which products can be found here: Understand the Matrix (of OLAP support in Business Objects products). The final word on data source support are the platform availability reports. Information on where to find these can also be found at the above link.
Check 2: Client software
All the OLAP servers supported at the time of writing require some kind of client component from the OLAP server vendor to be installed on the machine where the Business Objects software is deployed. Descriptions for the major OLAP vendors are given below.
Microsoft Analysis Services
For Microsoft Analysis Services the client is available as a download via one of the feature packs for the relevant version.
For example if you are using Microsoft Analysis Services 2005 the client is called Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB Provider and is available from this link: http://www.microsoft.com/downloads/details.aspx?FamilyID=D09C1D60-A13C-4479-9B91-9E8B9D835CDC&displaylang=en
If you are using Microsoft Analysis Services 2008 the client is called Microsoft SQL Server 2008 Analysis Services 10.0 OLE DB Provider and is available from this link: http://www.microsoft.com/downloads/details.aspx?FamilyId=228DE03F-3B5A-428A-923F-58A033D316E1&displaylang=en
SAP BW/Netweaver BI
This required the file librfc32.dll or the UNIX equivalent to be available on the path. For windows an installation of the SAP GUI will ensure this happens.
The Essbase client will need to be installed. The version 9 of the client installation is available at the following link: http://www.oracle.com/technology/software/products/bi/performance-management/hyperion_essbase.html
Check 3: Has the client install worked?
If the OLAP server’s client software has been installed and the connection is still not showing up or working then there are quick trouble shooting methods to verify whether the install was successful.
A good check is if you have a non Business Objects piece of software on the Business Objects machine that also should be able to connect to the OLAP server then this should be tried to see if it also fails. For example, you should be able to connect to Microsoft Analysis services through Excel.
Check the listed ODBO providers
Another way to check that the Microsoft Analysis Services client or another ODBO client installed is by creating a new empty file with the extension ‘udl’ and double clicking on the file. For example, right click on the desktop and choose ‘New’ and then ‘Text Document’.
This should create a new file on the desktop.
Rename this file making sure it ends with the extension ‘udl’
Now double click on the file. When the Data Link Properties dialogue opens switch to the Provider tab.
In the above example the provider for Analysis Services 9.0 is shown as installed.
Check providers acknowledged by the OLAP Data Access component
A final check is to see which providers the Business Objects OLAP Data Access component acknowledges. To do this some logging needs to be turned on. Here is an example of the entries that need to be added to the registry for getting the information from an XI 3.1 installation of Voyager.
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesODBOSHAREDUTILITIES]
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0MDALogModulesUTILITIES]
For information on how to adapt these registry settings for other products and version see the article on logging located here: OLAP Data Access Logging: Part 1 – Introduction and basic settings
After the Voyager connection creation page has been brought up there will be information about which providers are available in the log files. For example, the following snippet from a log file describes which ODBO providers are available.
Thu Dec 10 13:50:40.565: ODBOSHAREDUTILITIES: ODBOPROVIDERENUMERATOR: Found Provider: MSOLAP – Microsoft OLE DB Provider for Analysis Services 10.0
Thu Dec 10 13:50:40.565: ODBOSHAREDUTILITIES: ODBOPROVIDERENUMERATOR: Found Provider: MSOLAP – Microsoft OLE DB Provider for Analysis Services 9.0
Thu Dec 10 13:50:40.566: ODBOSHAREDUTILITIES: ODBOPROVIDERENUMERATOR: Found Provider: MSOLAP – Microsoft OLE DB Provider for OLAP Services 8.0
Thu Dec 10 13:50:40.566: ODBOSHAREDUTILITIES: ODBOPROVIDERENUMERATOR: Found unsupported provider: MDrmSap
Thu Dec 10 13:50:40.566: ODBOSHAREDUTILITIES: ODBOPROVIDERENUMERATOR: Found Provider: MDrmSap – SAP BW OLE DB Provider
This describes that there are four ODBO providers installed on the system. Three versions of Microsoft Analysis Services and the SAP BW ODBO provider. As Voyager doesn’t use the ODBO interface (it uses the OLAP BAPI) this ODBO provider is indicated as unsupported and won’t be available on the connection creation page.
Other information that appears in the log file may look as follows.
Thu Dec 10 13:50:40.572: UTILITIES: ProviderBrowse: Discovered provider:
Description SAP Business Information Warehouse
URI identifier occa:sap://;PROVIDER=”sapbw_bapi”
Most recent true
This indicates that connectivity to SAP is available.
Check 4: Correct license
Most OLAP Data connectivity does not require a special licence key. However, connectivity to SAP BW/NetWeaver BI does. You will need to have installed the SAP Integration Kit with a Premium licence key. If there is no licence key or a lesser license key the SAP BW provider option will not appear and the entry in the log example shown above will indicate that the SAP BW provider is not licensed.