Professional Documents
Culture Documents
windows
Copyright © 2010 SAP AG. All rights reserved.SAP, R/3, SAP NetWeaver, Duet, PartnerEdge,
ByDesign, SAP Business ByDesign, and other SAP products and services
mentioned herein as well as their respective logos are trademarks or registered
trademarks of SAP AG in Germany and other countries. Business Objects and the
Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web
Intelligence, Xcelsius, and other Business Objects products and services mentioned
herein as well as their respective logos are trademarks or registered trademarks
of Business Objects S.A. in the United States and in other countries. Business
Objects is an SAP company.All other product and service names mentioned are
the trademarks of their respective companies. Data contained in this document
serves informational purposes only. National product specifications may vary.These
materials are subject to change without notice. These materials are provided by
SAP AG and its affiliated companies ("SAP Group") for informational purposes
only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for
SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
2010-05-24
Contents
Chapter 1 Welcome to the BusinessObjects Enterprise XI Portal Integration
Kit 5
About this guide...........................................................................................6
Who should read this guide....................................................................6
List integration......................................................................................18
Viewer web part.........................................................................................19
Viewer integration.................................................................................20
Chapter 4 Troubleshooting 23
Trace Exceptions.......................................................................................24
Index 29
1
1 Welcome to the BusinessObjects Enterprise XI Portal Integration Kit
About this guide
2
2 Configuring Your Deployment
Overview
Overview
There are many possible configurations for your SharePoint deployment.
This chapter provides detailed information about configuring BusinessObjects
Enterprise and on scheduling and setting report properties to maximize their
effectiveness for Information Consumers. This chapter requires that you
have experience in using and administering BusinessObjects Enterprise.
For more information on BusinessObjects Enterprise, refer to the SAP
BusinessObjects Enterprise Administrator's Guide, which is found in your
BusinessObjects Enterprise product distribution.
Note:
After you install the BusinessObjects Enterprise XI 3.1 Portal Integration Kit,
no icons or shortcuts are added to your Start menu.
Note:
If you are using Enterprise or LDAP authentication to sign on automatically,
the BusinessObjects Enterprise XI Portal Integration Kit will attempt to log
on with the portal user's name and a blank password. Please ensure that
your CMC authentication is setup to handle this situation.
For more information, see the “BusinessObjects Enterprise Security Concepts”
section in the SAP BusinessObjects Enterprise Administrator's Guide.
If users do not have View On Demand rights to reports that do not have
instances in the BusinessObjects Enterprise system, they will see an
“Unavailable” status (and no hyperlinks) in the Availability column of the
listing web part.
Users need View rights to see reports in the list; they need View On Demand
rights to access reports in real-time (versus reports that have been scheduled
and run beforehand).
To ensure that all users have View rights, in the BusinessObjects Enterprise
Central Management Console, add your users to the Everyone group and
then give this group View rights to specific folders that contain reports that
are accessed by SharePoint. For more information about setting user rights,
see the “Controlling User Access” section in the SAP BusinessObjects
Enterprise Administrator's Guide.
If you want to configure the system to use the RAS to process reports, create
a new Server Group for your RAS in BusinessObjects Enterprise. Then,
specify this server group in all of the reports. (Alternatively, you can stop the
Page Server.)
For more information about server groups, see “Managing Server Groups”
in the SAP BusinessObjects Enterprise Administrator's Guide.
BusinessObjects Enterprise will use the server that has the most
resources free at the time of viewing.
• Give preference to servers belonging to the selected group
This option will attempt to process the object from the servers that are
found within the server group that you select from the list. If the
specified servers are not available, then the object will be processed
on the next available server.
• Only use servers belonging to the selected group
This option ensures that BusinessObjects Enterprise will use only the
specified servers that are found within the server group that you select.
If all of the servers in the server group are unavailable, then the object
will not be processed.
4. Click Update.
Using parameters
Tip:
• If your report contains parameters, users who view the report require
View On Demand (or greater) rights.
• To allow Information Consumers to modify parameter values, the reports
that they view must be real-time reports. However, real-time reports can
be resource-intensive; therefore, to reduce the processing load on your
BusinessObjects Enterprise services, you should use scheduled reports
whenever possible.
• If you have one report that has two uses (for example, real-time filtering
and general viewing by date), separate the usage by having two copies
of the report. For real-time filtering, allow users to view the report on
demand (which is resource intensive); for general viewing by date,
schedule the report to run as often as required. By separating the usage,
this method results in less impact on your system resources, because
only the real-time filtering report needs to be viewed on demand.
Tip:
• When you have reports that need to be updated regularly, schedule
reports to run as required if the users are going to access the same set
of data.
• When you need to view a report, schedule and run the report instead of
viewing it on demand. Scheduled reports are less resource-intensive.
• When assigning View On Demand rights, note that every time a user
(with the proper rights) refreshes a report, the report accesses the data
source. In addition, the Page Server or the Report Application Server
processes the request.
• When designing your portal, be wary of mixing web parts that contain
real-time views from the BusinessObjects Enterprise XI 3.0 Portal
Integration Kit along with other parts from different vendors that are page
refresh intensive. Whenever a page refresh occurs, everything that is
contained in the web page is refreshed. Thus, if the web page contains
a stock ticker that refreshes every ten seconds, any reports contained in
the same web page also refreshes.
Exporting reports
For performance reasons, set export options (Microsoft Excel, Adobe Acrobat,
and so on) at schedule time when possible. When users export a report
dynamically by selecting the alternative format viewing options on the toolbar,
this request is more process and resource intensive.
Set your database logon information for your reports through the CMC;
otherwise, users will need to log on to the database every time they refresh
or view a report.
Availability column
In your portal, note that the Availability column in a web part is not driven by
the status of a scheduled instance (for example, a recurring instance). The
Availability information comes from the default value that is specified in the
CMC for the report object.
Report rights
If your report contains parameters, users who view the report require View
On Demand (or greater) rights.
If you are using the Page Server to view the summaries of different reports,
you need to grant your users Edit rights.
Your Web Site Creators may want to access a location or report directly
through the location or report's unique identifier, or CUID. For example, when
a Web Site Creator wants to guarantee that he or she is accessing a specific
location or report, the CUID provides the necessary information.
4. Click Submit.
Performance Improvement
For detailed information about creating Crystal reports, refer to the Crystal
Reports User's Guide, which is included in your Crystal Reports product
distribution.
3
3 Building Customized Web Parts
Communication interfaces
Communication interfaces
This chapter provides information on communication interfaces for web part
developers. Using this chapter as a reference guide, you can create web
parts that communicate with web parts from the BusinessObjects Enterprise
XI Portal Integration Kit.
Note:
A CUID is the unique cluster ID for an InfoObject within BusinessObjects
Enterprise. For more information about CUIDs and objects, see the SAP
BusinessObjects Enterprise .NET SDK Guide or the SAP BusinessObjects
Enterprise Java SDK Guide, at https://boc.sdn.sap.com/developer/library/
List integration
Web part integration for developers occurs through the use of the Microsoft
defined communication interfaces.
The Document List web part makes use of the ICellProvider, ICellConsumer,
IRowProvider, and IRowConsumer interfaces.
The interfaces expect the following structured information for the Document
List web part:
The Crystal Report View web part can receive the report that it needs to
make active via the web part communication interface or the portal page
URL query string. The Crystal Report View web part can send active reports
to another web part through the communication interface. The Crystal Report
View web part is also able to send and receive prompts.
The Document View web part can receive an object type that it needs to
make active via the web part communication interface or the portal page
URL query string.
Viewer integration
Interface Description
4
4 Troubleshooting
Trace Exceptions
Trace Exceptions
In some instances, where you need to provide detailed information on an
issue (for example, when consulting with Business Objects technical support
staff), you can enable tracing. To enable tracing, you need to modify the
web.config file manually and change the BusinessObjects Enterprise
Trace Enabled key to True:
<appSettings>
Tracing provides you with stack trace information and web page configuration
options that can help you to understand any issues in greater detail. For
example, if you see an unexpected error message, and tracing is enabled,
the tracing information is listed at the bottom of the same web page where
the error occurred. Scroll down to see the tracing information provided by
SharePoint for the web part.
Note:
Tracing is a resource-intensive option and should only be enabled when
necessary.
A
A More Information
https://boc.sdn.sap.com/
Developer resources
https://www.sdn.sap.com/irj/sdn/businessobjects-sdklibrary
https://service.sap.com/notes
Notes These notes were formerly known as Knowledge Base ar-
ticles.
http://www.sap.com/services/education
http://service.sap.com/bosap-support
http://www.sap.com/services/bysubject/businessobjectscon
sulting
D
T
determining specific IDs 14
trace exceptions 24
troubleshooting 24
G
group rights 9 U
user rights 9
L
List web part 18 V
Viewer web part 19
P
parameters 11