General Information
Installation Issues
Known Issues
Product Status
The installation of the WebIntelligence OLAP access is integrated with the installation of WebIntelligence. See the Installation and Update Guide for complete instructions on installing WebIntelligence.
The Installation and Update Guide includes information on installing both Business Objects Enterprise Server Products and Business Objects Desktop Products. WebIntelligence OLAP components are installed when Explorer and the appropriate OLAP Access Pack are installed on the server within the Business Objects Enterprise Server Products installation. The client requires only an Internet Explorer web browser. You do not need to install any additional Business Objects software on the client.
Documentation
Please see "WebIntelligence Guide for OLAP Data Sources" (WebIOLAPUser26en.pdf) and "WebIntelligence OLAP Administration and Universal Drill-through Services Guide " (DrillThroughAdmin26en.pdf) for additional information on this product.
This installation guide is specific to this version of the product and should not be used as a general guide for WebIntelligence installation. For additional installation guide, please see Chapter 5 "Information for Administrators" of the "OLAP Documents" in WebIntelligence help. A separate guide for OLAP data sources is also included in the product in the help section of the OLAP connectivity in WebIntelligence.
WebIntelligence OLAP is only tested to run on a cluster manager.
Configuration Support
For information on configurations currently supported in Business Objects 5.1.9 / WebIntelligence 2.7.5, refer to the Business Objects Product Availability Report Web Site (PAR).
The Product Availability Report (PAR) contains detailed up-to-date information on supported:
products and languages
operating systems
web and application servers
connectivities
browsers
printers
Middleware Installations
Important: Please make sure that Essbase middleware (Essbase 5.0.2 P14) is installed prior to running the WebIntelligence Setup Wizard. Follow the installation instructions from the database vendor.
UDS Designer Installation Issues
It is recommended that you do not install UDS Designer on the WebIntelligence server.
Windows 98 is not supported for UDS Designer installation.
If you are installing UDS Designer on Windows NT server 4.0 SP6, it may not function properly as it is not a supported platform for a
desktop products. If you have to install UDS Designer on this platform,
use the following workaround:
In the above scenario; after the installation is completed, launch UDS Designer and try connecting to your OLAP data. If you receive Run-Time Error 429, it means that you
must perform some manual registrations:
Find ATL.DLL in your system 32 folder and register the dll.
After ATL.DLL is properly registered, find DTSMAPDATA.dll in \Business Objects\BusinessObjects 5.0 folder and register the file.
How to register (or re-register) a DLL or OCX file
To manually register or re-register a DLL, use the program RegSvr32 in the system32 folder of WinNT with the following command:
RegSvr32.exe <path> filename of dll or ocx
Where <path> is the path to the folder containing the dll or ocx
Java.io.IOException Error in UDS
Case 1: If you run a web server on a port other than port 80 (in default
web site properties). When you try to get a dialog box you will get
the java.io.exception error.
Solution: Change the port to 80
Case 2:
Invalid map in Data folder. In some cases if the UDS is unable to translate
the map or the map is not correct, this error message is displayed
Solution:
Make sure that the map is valid
Essbase/DB2OLAP Servers
Note: If you have the ESSBASE.CFG, you may add the settings to the existing file. The above settings are case sensitive, please make sure that you have the following values set as shown (one setting on each line):
Setting Name | Recommended Value |
AGENTDELAY | 35 |
AGENTTHREADS | 55 |
SERVERTHREADS | 60 |
__SM__BUFFERED_IO | <space><tab>TRUE |
The above Settings were tested with the following Essbase server configuration:
Windows NT4.0 with Service Pack 6
800Mhz Processor
1GB Memory
Essbase API 6.0/P3
DB2 OLAP 7.1/P3
How to confirm the first three settings:
Launch Essbase/DB2 OLAP server application manager and log as an administrator.
Click on Server in the menu/information.
Click on Essbase Config tab and ensure Global ESSBASE.CFG settings are listing above specified values.
How to confirm __SM__BUFFERED_IO is set to TRUE:
Open the application's log file (for example, SAMPLE.LOG)
Search for "I/O"
For the default setting, it will say, "Using direct I/O..."
For the buffered setting (TRUE), it will say using "Using buffered I/O..."
SAP BW Connectivity
The SAP BW server name can be different than the actual machine's name. When creating a connection to a SAP BW server, make sure that the machine name is not entered as the Server name in "Create OLAP Data Source" page.
Please note that when creating a new connection for SAP BW in "Create OLAP Data Source" page, the SAP server name is case sensitive and connection may not succeed if they differ from the actual server name.
SAP- BW
Connectivity Middleware and MDAC
It is highly recommended that you install MDAC 2.6 RTM and SAP middleware for SAP connectivity. There have been compatibility issues in installing a combination of MDAC 2.7 and SAP middleware that results in WebIntelligence OLAP issues.
Security/Authentication Issues
Please read WebIntelligence documentation on install process and security issues.
When installing on Windows 2000,
make sure you edit the OLAP folder directory security to an anonymous user account with a valid Domain name\username and
password. User should have local administrator rights. It is recommended
that you use the same user name and password as the one used during the installation of
the product as BUSINESSOBJECTS Manager in step 9 of the setup.
User login fails if total number of Essbase ports exceeds your licensed copies.
Differences Between OLAP Servers
WebIntelligence for OLAP data sources attempts to provide a uniform interface across each of the OLAP servers to which you can connect. However, because of differences in the way that each of the vendors has implemented their servers, some differences in the interface remain.
For a detailed list of Essbase/DB2OLAP server limitations and restrictions, please see "WebIntelligence Guide for OLAP Data Sources" (WebIOLAPUser26en.pdf).
Modifying Drill Down Limit
You are able to limit the number of drill down operations in the reports to increase performance. This value is to be set by WebIntelligence administrator. It limits the number of drill down operations allowed in an Essbase / DB2OLAP reports. The number of drill down operations has direct impact on the performance of server and response time.
If you need to enable this feature, find the following file:
<Target Installation Folder>\Business Objects\Server\WebIntelligence 2.5\Config\Setup.txt
Add the following, case sensitive, text to the file and save:
drill_limit=12
Where 12 is the number of desired drill down for each report.
Optimizing Performance in Essbase or IBM DB2OLAP
Reports
When creating an Essbase or DB2OLAP report, to optimize the performance and prevent possible error message during analysis of the report, it is highly recommended that you modify a file after the installation of the Essbase and or DB2OLAP as an OLAP Access pack.
Make sure that installation is successful by creating a sample report connecting to an Essbase or DB2OLAP server.
Close WebIntelligence.
Find the following file: \Business Objects\Server\WebIntelligence
2.5\http-server\OLAP\global.asa.
Open the file with a text editor.
Copy and paste the following to the top of the script above "<SCRIPT LANGUAGE=VBScript RUNAT=Server>" section:
<OBJECT RUNAT=Server SCOPE=Application ID=reportInstance PROGID="O@WEss.ActiveX.1" >
</OBJECT>.
Locate the " Sub Application_OnStart()" section in the script.
Copy and paste the following to the end of the script right before "End Sub":
dim bOn
bOn = reportInstance.Connected()
Save and replace the file to the same location.
Stop and start the Default Web Site in IIS.
Please note that the above modification is only applicable if you have installed Essbase and or DB2OLAP as an access pack. If you decide to uninstall providers and select MDX Connect or SAP BW to replace them, you are required to undo the above changes, as the above changes requires Essbase and/or the DB2 OLAP access pack installed on the server.
Activating Universal Drill-through Services (UDS)
Important Note: If Universal Drill-through Services is not selected during the first round of WebIntelligence set up, installing it as a separate component does not prompt for a port number and therefore defaults to a NULL value. If you decide to install UDS as a separate install after WebIntelligence set-up is completed, please follow these steps to assign a port number:
Find and open the following file: <Install Path>Server\WebIntelligence 2.5\Config\setup.txt.
Add a five digit port number to replace NULL value in DTS_Port_ID=Null (i.e.
DTS_Port_ID=20060).
Please note that a valid port number may not exceed 65000.
Copy the five digit number into the following registry location:
HKEY_LOCALMACHINE\Software\Business Objects\DTS\1.0\Port
Universal Drill-through Services is set to manual start in NT services and you are required to start it prior to using it. To start UDS, open the Services console, right click "WebIntelligence DTS Manager" and select Start.
Universal Drill-through Services is a fully functional feature in this release version and requires some administration steps to activate. For additional information on this feature and to obtain a copy of all required samples, please contact your Business Objects representative. For additional information on Universal Drill-through Services and related administrative tasks, please see "Administration and Drill-Through Guide".
UDS Mapping Files
When you perform drill-through, if the UDS Server does not use the new translation maps in the "..\Business Objects\BusinessObjects 5.0\Data\" directory or does not use the updated version of a existing translation maps, follow one of the following workarounds:
Stop and restart the following Windows Service: "WebIntelligence DTS Manager"
If the previous solution doesn't work, you may have two (or more) translation maps in the ".\Business Objects\BusinessObjects 5.0\Data\" directory for the same combination of source data source and target data source. In this scenario the UDS Server will use the first one loaded to perform the translation. To fix this issue, keep only one translation map for the combination of source data source and target data source in the "..\Business Objects\BusinessObjects 5.0\Data\" directory. When done, you have to reload the translation maps.
Contact your Business Objects representative for additional help. A sample relational database and related universes along with sample target reports will be provided to activate the feature.
IIS Authentication in Windows 2000 Servers
To make sure that the "OLAP" folder in IIS has appropriate anonymous user:
In OLAP properties dialog, select Directory Security tab.
Click Edit button in Anonymous access and authentication control.
In Authentication Method dialog, check the anonymous access check box.
Click on Edit button for Account used for anonymous access.
In Anonymous User Account dialog, enter a valid Server administrator account .
Before selecting a username and password, ensure that the user has administrative rights on the server and is a member of the domain with access rights in MSOLAP server databases. This is usually the administrator of WebIntelligence server.
In this particular example the above user has been assigned as the anonymous user. This is the user that will be used for all resources that the Web
Application requires (for example, temp files, registry access, and in the case of MS Analysis Services - it is used to gain access to the OLAP Server).
"Update UDS" Feature in UDS Designer
There is an icon in the tool bar with the caption of "Update the UDS". When clicking on this icon, you are able to update the UDS services on any server.
You are required to input the WebIntelligence server name and the UDS port number in that server. Once all the server information is provided, upon clicking on the Update button, it reloads the Data folder that contains translation maps. This remote feature is to replace the required step to stop and start of the WebIntelligence DTS Manager after adding or modifying a map in the data folder. You may save the map directly onto the WebIntelligence server, data folder from a remote client where you have UDS Designer installed. Then update the server to activate the saved map. You are no longer required to stop and start the WebIntelligence DTS Manager in the NT services.
UDS Designer OLAP Data Sources and Middleware
In order to create translation maps in UDS Designer you will require a connection to an OLAP data source. Select the appropriate OLAP Access Pack during the setup (MDX Connect, Essbase, DB2 OLAP Server). Depending on your choice of OLAP provider, prior to installing the OLAP Access pack, you are required to install the appropriate and compatible middleware.
UDS Designer Installation Issues
It is recommended that you do not install UDS Designer on the WebIntelligence server.
Windows 98 is not supported for UDS Designer installation.
Registering (or Re-registering) a DLL or OCX File
To manually register or re-register a DLL use the program RegSvr32 in the system32 folder of WinNT with the following command:
RegSvr32.exe <path> filename of dll or ocx
Where <path> is the path to the folder containing the dll or ocx.Ensure that *.UDM files saved are not Read-only files, otherwise file access and modifications will cause errors.
Terminating the application by clicking on X button or shutting down the computer while UDS Designer is running may cause an error. Workaround is to save the map, close the application and then shut down the computer.
When logging to the universe for the first time in UDS Designer, a BusinessObjects application is launched in background. Simply close the background application and proceed with the UDS Designer.
Replacing a dimension, updating a hierarchy or a level is not supported in this version of UDS Designer.
Maps created or edited manually may cause an error when trying to open with UDS Designer for further modifications.
UDS Designer is not checking for validity of the Maps saved, if you select to save an incomplete map to use in with the drill-through feature, you may not succeed in activating the UDS server.
The optimized screen area size to display UDS Designer is 1024 by 768 pixels, reducing the size may cause some interface issues. UDS Designer dialog does not resize.
Opening the sample maps provided in sample CD might cause an error, as you may not have the identical server, database and cube to match the sources.
UDS Designer is currently listed as "MapDeveloper" in the BusinessObjects 5.1 folder and in the start menu.
When opening a saved map, if the target universe is missing or renamed, UDS Designer will not prompt for universe selection and it leaves the universe target section blank. You may select a universe after it is loaded and associate it with the map.
Connections to Microsoft OLAP servers require NT authentications; ensure to login to Windows using a valid domain username with rights to MS OLAP server.