Beruflich Dokumente
Kultur Dokumente
Part 4
This is part 4 of the Installation and Configuration blog series for the integration of BusinessObjects
with SAP. I will describe the following parts:
You can download the SAP Java Connector from the service marketplace
(http://service.sap.com/connectors).
I am downloading the version 2.1.8
After unzipping the Java Connector download, I copy the file sapjco.jar to the shared library folder of
the application server (in my example : \Program Files\Business Objects\Tomcat55\shared\lib) and
the file sapjcorfc.dll to %windir%\system32.
(see page 51 in the installation guide for the Integration Kit for SAP Solutions for details)
In the next screen I select Custom to select all components from the SAP Integration Kit.
In the next screen I can select the components and the screen below shows the complete list of all
available elements (details see further down in the blog).
In the next screen I need to authenticate to the BusinessObjects Edge system so that the necessary
changes can be applied to the system database.
I authenticate towards the system and move on to the next step.
In the next step I need to enter the details for the publishing service that is being used to publish the
Crystal Report objects from the BI System to the BusinessObjects Edge server.
Program ID is case-sensitive
Gateway Type the name of your BW server. If you have a BW cluster,
The details for the Publishing Service and those settings will be explained in the next part where we
will configure the publishing for Crystal Reports.
In the next screen I can select to deploy the web applications (customizations to InfoView, SAP
Authentication plug-in) automatically.
In the next step the installation routine is asking if the SAP Java Connector has been deployed. the
installation can continue without the files but then the files need to be deployed afterwards.
After this the installation starts and the final screen you will see looks like this.
As soon as the installation is finished and when you call the Central Management Console from the
BusinessObjects Edge server you should be able to select SAP as authentication method and your
screen should look similar to this.
Now we need to install the transports from the Integration Kit for SAP Solutions on the SAP server.
InfoSet connectivity.
BW ODS connectivity.
SAP authentication.
The transports are available as part of the SAP Integration Kit in a separate folder \transports with
a detailed documentation about the import and the objects that will be created in the appendix of the
Installation Guide for the SAP Integration Kit.
SAP Connectivity
This component provides database drivers that are designed specifically for reporting off SAP data.
The following drivers are included:
Open SQL.
InfoSet.
ODS / DSO
OLAP BAPI.
Except the OLAP BAPI connectivity the drivers are only available for Crystal Reports.
SAP Authentication
This component allows you to map your existing SAP roles and users to BusinessObjects Enterprise
users and user groups. It also enables BusinessObjects Enterprise to authenticate users against the
SAP system, thereby providing Single-Sign-On to your SAP system.
BW Publisher
This component allows you to publish reports individually or in batches from SAP BW to
BusinessObjects Enterprise.
Web Content
This component includes the SAP specific customizations to BusinessObjects Enterprise InfoView.
These customizations include functionalities like multilingual scheduling for Crystal Reports and the
ability to retrieve personalization values for SAP Variable from SAP BW queries.
In the next parts of this blog series we will continue to configure topics like SSO and publishing for
the Integration between BusinessObjects and SAP.