You are on page 1of 14

Business Objects XI

Integration Kit for SAP


Release Notes
Business Objects XI Integration Kit for SAP Release Notes
Installation

The notes contained in this document represent only some of the known
issues at the time of release. For the most up to date list of release notes, go
to http://support.businessobjects.com/library/docfiles/cps10/docs_en.asp.

Installation
• For a complete list of system requirements and supported platforms, see
the platforms.txt file included with your product distribution. For
complete installation instructions, see the installation guide
(install.pdf).
• Disable all antivirus software before installing BusinessObjects
Enterprise components. Enable your antivirus software after the
installation.
• The BusinessObjects XI SAP Integration Kit for SAP is not supported in
Simplified Chinese on any UNIX platform.

Uninstalling
• After uninstalling BusinessObjects XI Integration Kit for SAP on Windows,
you must restart the Central Management Server to completely remove
SAP authentication options from BusinessObjects Enterprise.

Upgrading and migrating


• When upgrading from Crystal Enterprise 10 to BusinessObjects
Enterprise XI, it is recommended that the BusinessObjects XI Integration
Kit for SAP is installed before BusinessObjects Enterprise XI. If
BusinessObjects Enterprise XI is installed first, an error may occur
indicating that the plug-in secSAPR3 could not be found on the server.
This occurs because the SAP security plug-in is disabled during the
upgrade.
To fix this error, run the following script:
http://<your_server_name>/businessobjects/enterprise11/WebTools/
websamples/changeAliasesPasswords/Jlogonform.aspx?framework=
This enables the user accounts that were disabled during the upgrade.

2 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
BW Report Publisher Service

BW Report Publisher Service


• If you try to restart the BW Publisher Service using the Windows Central
Configuration Manager (CCM), the message "An instance of the service
is already running" appears and the BW Publisher Service stops. To
restart the BW Publisher Service, do not use the restart option. Instead,
first select the BW Publisher Service in the CCM and click Stop. Then
select Start.
If you install the BW Report Publisher Service on Windows, you must
enter the following information in the installation program:
Program ID
Gateway Host
Gateway Service
Extra (optional)
To change these values after installation is complete, you must edit the
following registry entries:
--HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite
11.0\SAP\BW Publisher Service\
• Program ID
String Value "ProgId".
The default value is "" (Blank).
Set ProgID to match the Program Id that you defined for the
RFC destination for the BW Publisher Service. The Program ID
can take any value, but must be 64 characters or fewer, and may
not contain spaces. The Program ID is case-sensitive.
• Gateway Host
String Value "GwHost".
The default value is ""(Blank).
Set GwHost to the name of your BW server. If you have a BW
cluster, enter the name of the central instance of BW.
• Gateway Service
String Value "GwServ".
The default value is ""(Blank).
Set GwServ to the port number that the Gateway Host is
listening on. For example, type 33##, where ## represents the
instance number of your SAP Gateway. Typically, the instance
number is 00, and the value for this field is 3300. If you have
defined a symbolic name for this port (such as sapgw##), you
may use this symbolic name instead.

BusinessObjects XI Integration Kit for SAP Release Notes 3


Business Objects XI Integration Kit for SAP Release Notes
BusinessObjects Enterprise

• Extra
String Value "Extra".
The default value is ""(Blank).
If you plan to enforce Secure Network Communication (SNC)
between SAP and BusinessObjects Enterprise, enter the
appropriate switches as the value for Extra. For information on
how to enable SNC for registered servers, consult the RFC SDK
documentation for API RfcAccept.

BusinessObjects Enterprise
• After migrating reports published in an earlier edition of BusinessObjects
XI Integration Kit for SAP to BusinessObjects XI Integration Kit for SAP,
users may no longer be able to view these reports on demand. User's
rights on these objects have not changed; however, to enable viewing on
demand you must manually indicate for each report that users be
prompted for their database logon information.
To change this setting, go to the Objects management area of the Central
Management Console and find the report. From the Process tab, click
Database. At the bottom of this screen, select "Prompt the user for
database logon" and then click Update.
• To significantly improve performance while importing or removing SAP
roles from BusinessObjects Enterprise, ensure that "Automatically import
users" is selected on the Authentication > SAP > Options tab in the
Central Management Console.
• If SAP authentication is not listed as an authentication type on the logon
page of the Central Management Console, and BusinessObjects
Enterprise is installed on UNIX (or on Windows when using a Java web
application server), check the authPluginExts.properties file. It must be
copied to the $CATALINA_HOME/shared/classes/META-INF directory
(for Tomcat) or copied to the META-INF directory you created when
deploying other Java web application servers. Consult the Business
Objects XI Integration Kit for SAP Installation Guide and the
Documentation section of these release notes for details.
• If you cannot access the SAP authentication tab in the Central
Management Console, check that the SAP Java Connector Library is
installed correctly. Consult the Business Objects XI Integration Kit for
SAP Installation Guide for details.

4 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
Data Access Kit

• The BusinessObjects Enterprise InfoView for SAP and the


BusinessObjects XI Integration Kit for SAP SDKs do not support the use
of the exclude option, the wildcard operator (*), or the NOT operator (<>)
in personalized or default parameter values. If you select a parameter
value (created in the SAP Business Explorer) that contains one of these
features, the value will not load.
• To view thumbnails in BusinessObjects EnterpriseXI, a user must be
granted the "Download files associated with the report" right. To grant this
right, in the Central Management Console, click Rights and then click
Advanced. Open the Reports panel, and grant the right called "Download
files associated with the report". If you do this at the folder level, the
reports will inherit this right.

Data Access Kit


• In version 8.5 of Crystal Enterprise SAP Edition, empty string fields within
the Infoset and BW query drivers returned NULL values. This behavior
has been modified; in version 9 and 10 and XI of the product, string fields
with empty values return empty strings.

SAP Enterprise Portal


• Use Internet Explorer 6.0 to view the three sample iViews included with
BusinessObjects XI Integration Kit for SAP. The use of Netscape 6.x and
7.x is not supported for these iViews.

Enterprise Reporting
• When loading a Crystal report that contains a single parameter, the
parameter prompt appears twice. This only occurs if the Crystal report
was originally created using Crystal Reports 8.5. To resolve this second
prompt, verify the database on the report.

BusinessObjects XI Integration Kit for SAP Release Notes 5


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

OLAP Reporting (BW OLAP Kit)


Known Issues
Server Variables
• Variables flagged in BW as Changeable with Query Navigation are not
supported because these variables are not available within the OLAP
BAPI at this time. Business Objects is working with SAP to rectify this for
the future.
• Text variables created with Processing Type "User Input" are not
supported by OLAP Intelligence. The user will not be prompted to enter
the values of any "text variables" if they are defined as such in the SAP
query. Text variables created with Processing Type "Replacement Path"
are supported.
• Structures and restricted key figures that use characteristic variables
derived from dimensions not referenced directly in the BW query have
the following limitations:
• If the variable has a mandatory entry type and represents multiple single
values, a range, or selection, the OLAP Intelligence report will fail to
open.
• If the variable has an optional entry type and represents multiple single
values, a range, or selection, it will be ignored and does not appear in the
parameter/refresh dialog.
• If the variable has a mandatory or optional entry type and represents a
single value, the end user will be prompted to enter or select a value for
the variable using a combo box.
To work around this issue, in the SAP/BW Query Designer, move the
reference dimension for the characteristic variable to the free
characteristics area. Doing this will expose the variable in OLAP
Intelligence.
• Values for range variables (or ranges within complex variables) must be
entered in the correct logical 'from:to' sequence. By default, the members
for the range variable will be sorted and displayed in the correct
sequence in the member selector. The order of the members is
determined by the dimension schema. If the end value entered for the
range variable is located before the start value, then the resolved query
will not return any data. OLAP Intelligence does not have the ability to
automatically detect the correct order and swap the values automatically.

6 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

• Queries containing multiple key date variables are not supported. Where
multiple key date variables exist, the input value for the first key date
variable returned by the server will be applied to the query.
• Hierarchy node variables defined on a time dependent hierarchy do not
get filtered by the key date of the query. The hierarchy node variable
displays all values in the default hierarchy. This occurs whether the key
date is set by a variable at runtime or fixed in the query at design time.
• Creating a new application from a SAP BW query with the menu option
"Choose Cube" does not prompt for SAP variable values. To set values
for the variables, click on the Refresh Server Parameters button on the
toolbar.
• Default values for hierarchy variables are not displayed in the Set
Parameters dialog. As a result, if the hierarchy variable has a dependent
hierarchy node variable, the default value for the hierarchy node variable
also does not get displayed in the Set Parameters dialog. This is not a
Business Objects issue. The default values for the hierarchy variables
that are returned to the OLAP BAPI component by SAP BW are not
correct. This issue has been logged with SAP.
• When refreshing hierarchy node variables, the member selector does not
display the previously selected values in an expanded tree view.

Multiple Structures
• Queries defined in SAP BW without a key figure structure in the row or
column axis will not return data in CA.

DHTML Viewer
• The Change Caption command triggers an error message the first time it
is invoked. This only happens in the OLAP Intelligence DHTML viewer if
the SAP Infoview application runs on a SAP Netweaver application
server. The Change Caption command works correctly when it is invoked
a second time.
• An error message appears when you click on the Cancel button in the
Set Parameters dialog box. This happens if the SAP query contains any
required variables for which default values have not been specified.
• For a query that contains a complex variable, the remove button in the
Set Parameter Elements dialog only allows you to remove the last
parameter element that you specified. Click on the OK or Cancel button
to start over.

BusinessObjects XI Integration Kit for SAP Release Notes 7


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

Passing Logon Credentials to the SAP BW Server from the SAP Infoview
Application
• When you publish a new report from the OLAP Intelligence Desktop
Designer to the Enterprise system, the default logon type is set to single
sign on. This means that when you request to view the published report
in the SAP Infoview application, the Enterprise system will attempt to log
you on to the SAP BW server with your Enterprise session account. If this
fails, the system displays a secondary logon dialog that prompts you to
enter your SAP username and password manually. To override this
behavior, you must view go into the Central Management Console and
modify the Data Source properties for the OLAP Intelligence report.
The following three options are available on the Data Source Logon tab
for the OLAP Intelligence report:
• Logon using Web Component Adapter credentials
• Secondary Logon for each OLAP Intelligence report
• Logon using specific credentials
• When an OLAP Intelligence report is first published to the Enterprise
system and its properties are viewed from the Central Management
Console, the default option displayed on the Data Source Logon tab is
“Logon using specific credentials”. This is not correct. The specific
credentials shown will not be used if a user makes a request to view the
report in the SAP Infoview application. The system will default to the
single sign on workflow. If the single sign on mechanism fails, the system
prompts the user to enter his SAP username and password in a
secondary dialog.
If you want to set the logon credentials for the OLAP Intelligence report to
a specific SAP username and password, you must perform the following
steps.
1. Publish the new OLAP Intelligence report to the Enterprise system.
2. Open the Central Management Console by clicking on the link in the
BusinessObjects Enterprise Administration Launchpad page.
3. Click on the Objects link.
4. Find the name of the newly published OLAP Intelligence report and
click on it to bring up its property pages.
5. Click on the Data Source Logon Tab.
6. Select either “Logon using Web Component Adapter credentials” or
“Secondary Logon for each OLAP Intelligence report” and then click
the Update button.

8 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

7. Select the “Logon using specific credentials” option and enter the
credentials that you want to apply to the report in the text boxes
below.
8. Click on the Update button.
After performing these steps, any user who makes a request to view this
report will be logged on to the SAP BW server with the credentials that
were specified on the Data Source Logon tab. You must perform step 6
before you perform step 7. Otherwise, the report does not get updated to
use the option “Logon using specific credentials”.
If you want to change the logon type for this report so that users are
always prompted to enter their username and password manually, select
the option “Secondary Logon for each OLAP Intelligence report”.
If you want to change the logon type back to the default behavior of using
single sign on, you must perform the following steps:
1. Open the published report in the OLAP Intelligence Desktop
Designer.
2. You will be presented with a dialog that states the cube no longer
exists and prompts you to select a new cube. Select the correct
query cube that the report was created with.
3. Save the report back to Enterprise.

Web Authoring
• An OLAP Intelligence report that is created directly from the Infoview
application is by default set to use the logon option “Secondary Logon for
each OLAP Intelligence report”. This means that any user who tries to
view the report will be prompted for a username and password. To
change the logon type for the web-authored report, go to the Data Source
Logon tab for the report in the Central Management Console. See the
previous section “Passing Logon Credentials to the SAP BW Server from
the SAP Infoview Application” for more details on how to set the correct
logon option.
• You may receive a script timeout error when you create a new OLAP
Intelligence report from the SAP Infoview application and select a SAP
BW server that contains a large number of queries or cubes. To resolve
this error, you can increase the script timeout value in the follow registry
path:
HKEY_LOCAL_MACHINE\Software\Business Objects\Suite 11.0\Web
Component Adapter\csp

BusinessObjects XI Integration Kit for SAP Release Notes 9


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

Central Management Console


• You cannot use the single sign on option to preview an OLAP Intelligence
report from the Central Management Console. You will always be
prompted for secondary logon or authenticated with specific credentials.

Installing the OLAPI BAPI components for the OLAP Intelligence ActiveX
Viewer
• The OLAP Intelligence ActiveX Viewer is a thick client that connects
directly to the SAP data source. To enable users to view OLAP
Intelligence reports against SAP in the Active X viewer, you must update
the Active X Viewer package on the web server and ensure that the SAP
client library librfc32.dll has been installed to the C:\winnt\system32 folder
on each client machine.
Here are detailed instructions.
1. Ensure that the SAP client library librfc32.dll is installed in the
C:\WNNT\system32 directory on the client machines where you want
to install the ActiveX viewer
2. Install the SAP BW OLAP components onto the client machines by
inserting the CD for the BusinessObjects 11 Integration Kit for SAP,
choosing custom install and selecting the following option: Desktop
>SAP BW >Data Access > OLAP BAPI. This installs only the OLAP
BAPI components.
To install the ActiveX Viewer on each client:
1. Log on to the BusinessObjects Infoview for SAP on the client
machine.
2. Navigate to the Preferences tab and change the OLAP Intelligence
viewer to ActiveX.
3. From the client machine, make a request to view a OLAP Intelligence
report from the Web desktop. The request will automatically
download the ActiveX Viewer installer package (.exe) to the client
machine and execute it.
Once the package installs the ActiveX Viewer components to the client
machine, the OLAP Intelligence report appears in the browser.

10 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
OLAP Reporting (BW OLAP Kit)

Silent Install Option for ActiveX Viewer Client Machines


• Administrators can use the following command to perform a silent install
of the SAP OLAP BAPI connectivity components on a client machine:
<path to the cd>\cd\setup.exe /qn PIDKEY=<product activation
keycode> ADDLOCAL=AlwaysInstall,DBW_DataAccess_OLAP
CLIENTLANGUAGE=”<language>”

/qn Performs the install silently


without prompting the user.
/qn+ Performs the install silently,
prompting the user when the
install is complete
PIDKEY=00000-00000000- Specifies your product
0000000-0000 activation keycode.
ADDLOCAL= Specifies an install of the SAP
ADDLOCAL=AlwaysInst OLAP connectivity components
on the local machine
all,DBW_DataAccess_OL
AP
CLIENTLANGUAGE Specifies the language to install
EN English
FR French
DE German
IT Italian
ES Spanish
JP Japanese
CHS Simplified Chinese
NL Dutch

Using the Sample OLAP Intelligence Applications with the SAP Enterprise
Portal
• Sample applications have been included that allow you to invoke OLAP
Intelligence reports directly from a SAP Web Portal application without
having to manually log on to BusinessObjects Enterprise. For these
sample applications to work, single sign must be configured correctly on
the BusinessObjects Enterprise and SAP servers.

BusinessObjects XI Integration Kit for SAP Release Notes 11


Business Objects XI Integration Kit for SAP Release Notes
Documentation

To view a OLAP Intelligence report with the sample CSP application, use
the following URL syntax:
http://<serverName>/styles/csp/
analysisviewer_sap.csp?id=<id>&sap_client=<client>&sap_sysid=<
system ID>&prompt-<parameterName>=<parameterValue>
To view a OLAP Intelligence report with the sample JSP application, use
the following URL syntax:
http://<serverName>:<port>/businessobjects/enterprise11/sap/
desktoplaunch/InfoView/plugin/crystalenterprise/analysis/
analysisviewer_sap.jsp?id=<id>&cms=<cms>&sap_client=<client>&
sap_sysid=<system ID>&prompt-
<parameterName>=<parameterValue>

<id> Enter the ID of the OLAP


Intelligence report that you
want to view. This is the unique
identifier for the object in the
Central Management Server
<client> Enter the client number for your
SAP BW server
<system id> Enter the 3 character system
ID of your SAP BW system.
<parameterName> Enter the unique name of any
server variable that you want to
pass to the query. Consult the
appropriate SAP BW tool to get
the unique name of a server
variable
<parameter value> Enter the input value for the
corresponding server variable

Documentation
• In the Installing BusinessObjects XI Integration Kit for SAP chapter, in the
Deploying the web applications section, step 3 for WebLogic and
WebSphere incorrectly states that you must add the
authPluginExts.properties file to the CLASSPATH environment variable.

12 BusinessObjects XI Integration Kit for SAP Release Notes


Business Objects XI Integration Kit for SAP Release Notes
Documentation

Instead of doing this, you should create a directory called META-INF in


the SAP java applications folder within your BusinessObjects Enterprise
installation directory and copy the authPluginExts.properties file to the
META-INF folder. Then add the parent path of the META-INF folder to the
CLASSPATH environment variable.
• In the Installing BusinessObjects XI Integration Kit for SAP chapter, in the
Deploying the web applications section, the instructions for deploying the
SAP Infoview on Tomcat are incorrect.
1. Shut down Tomcat if it is running. Type
%CATALINA_HOME%\bin\shutdown in a Command Prompt window.
Note: %CATALINA_HOME% represents the root directory of the
Tomcat installation.
2. Create a new and empty file:
3. %CATALINA_HOME%\conf\Catalina\localhost\sap_desktopwar.
xml
This file will be used as the context descriptor file for the SAP
InfoView.
4. Add the following line to sap_desktopwar.xml, in a text editor such
as Notepad:
<Context path="/businessobjects/enterprise11/sap/desktoplaunch”
docBase="war file path\sap_desktop.war" debug="0"
reloadable="true" crossContext="true" />
5. Save the sap_desktopwar.xml file.
6. Restart Tomcat by typing %CATALINA_HOME%\bin\startup at the
command prompt.
Note: You may need to restart your computer for these changes to
take effect.
• In the Installing BusinessObjects XI Integration Kit for SAP chapter, in the
Installing the UNIX components section, step 11 incorrectly states to
restart the Central Management Console (CMC). It should state to start
the Central Management Server (CMS)
• In the Installing BusinessObjects XI Integration Kit for SAP chapter, in the
Installing the UNIX components section, steps 9 and 10 do not occur.
After the installation script unpacks the installation file, no more user input
is required.

BusinessObjects XI Integration Kit for SAP Release Notes 13


Business Objects XI Integration Kit for SAP Release Notes
Documentation

• On page 135, the BusinessObjects XI Integration Kit for SAP User’s


Guide states that the OpenDocument format should be used as the new
standard for URL reporting. This is not the case for the Integration Kit for
SAP when used with OLAP Intelligence. Continue using the legacy
syntax that is documented on pages 135 to 138 of the User’s Guide.
• In the BusinessObjects XI Integration Kit for SAP Installation Guide, in
the “Defining a BusinessObjects Enterprise system“ secion the path
setting is are. The setting should be:
For .NET:
• Path: businessobjects/enterprise11/sap/infoview
For Java:
• Path: businessobjects/enterprise11/sap/desktoplaunch/
apps

14 BusinessObjects XI Integration Kit for SAP Release Notes

You might also like