Beruflich Dokumente
Kultur Dokumente
You should be able to download the software either via SDN (Download area) or you might already have access to the software via service marketplace (Software Distribution Center > Installations and Upgrades > BusinessObjects packages and products). In this blog I will focus on the installation part of the software and in the next blog I will explain the configuration of the components. I will use a blank VMWare with Windows 2003 Server to create a system which will have the client components on the server components on a single VMWare. BusinessObjects Edge Series I start with the installation of BusinessObjects Edge. After calling the setup I am asked to select the language of the installation routine (not the language for the installed software).
...And will then provide the license key for the software.
In the next step I can now select the Language Packs for BusinessObjects Edge allowing me to deploy multiple languages of the software in a single step.
After selecting English as Language Pack, I can provide the folder for the software and I can select which database server I want to select to host the system database (a detailed list of supported databases is available in the platform matrix).
Then I can select the port for the Central Management Server and provide a password that will be set for the administrative account as part of the installation process.
... and I can then configure the port for the Server Intelligence Agent...
... and in the next step configure the password for - in my case - the MySQL database that will be deployed.
Now I select the Application Server and for my purposes I am selecting Tomcat as application Server (a list of supported Application Server can be found in the platform matrix).
After this the software will get installed as selected and depending on the hardware you will get the following screen after a couple of minutes.
I am restarting my system and continue the installation afterwards This is part 2 of the Installation and Configuration blog series for the integration of BusinessObjects with SAP. I will describe the following parts:
BusinessObjects Edge Series XI Release 3.0 (Part 1) Crystal Reports 2008 (Part 2)
Crystal Reports 2008 I start the installation of Crystal Reports 2008 and do select - identical to the previous installation - "English" as the language for the installation routine.
And similar to the installation of BusinessObjects Edge I can then select the Language Packs for Crystal Reports.
10
In the next screen I have the option to leverage the web update service or to disable it and...
Then in the last screen the actual installation based on the selections I did will start.
11
After the installation process is finished you will see this screen.
Xcelsius 2008 Now I will start the installation of Xcelsius 2008 and select English as setup language
12
13
Now I can select the Language Packs for Xcelsius 2008 and after clicking Next...
14
...and then the installation will start and after a few minutes you will see the following screen.
15
In Part 3 we will continue with Live Office and the SAP Frontend for the installation This is part 3 of the Installation and Configuration blog series for the integration of BusinessObjects with SAP. I will describe the following parts:
BusinessObjects Edge Series XI Release 3.0 (Part 1) Crystal Reports 2008 (Part 2) Xcelsius Enterprise 2008 (Part 2) Live Office XI Release 3.0 (Part 3) SAP GUI (Part 3) Integration Kit for SAP Solutions XI Release 3.0 (Part 4) SAP Transports (Part 4)
Live Office XI Release 3.0 Now I will start the installation of Live Office XI Release 3.0 and select English as setup language
16
17
Now I can select the Language Packs for Live Office XI Release 3.0 and after clicking Next...
18
and after a few minutes you will see the following screen.
19
SAP GUI
The SAP GUI is required for two areas. Crystal Reports is leveraging parts of the SAP GUI (like SAP Logon) to allow the user to open a BI Query or save a Crystal Report object to the BI System. BusinessObjects Edge requires the librfc to communicate with the SAP backend like Crystal Reports does as well. I start the installation of the SAP Frontend (7.1) and I select the SAP GUI Suite
20
.... The BW Add-On (for BW 3.5 Add-Ons) and the BI 7 Add On.
Right now Crystal Reports 2008 is using the dialogs from the BW 3.5 Add-On and therefore you have to deploy the BW 3.5 Add On components even when your backend is a BI 7 System. This is part 4 of the Installation and Configuration blog series for the integration of BusinessObjects with SAP. I will describe the following parts:
BusinessObjects Edge Series XI Release 3.0 (Part 1) Crystal Reports 2008 (Part 2) Xcelsius Enterprise 2008 (Part 2)
21
SAP Java Connector The SAP Java Connector is being leveraged from BusinessObjects Edge and the SAP Integration Kit as part of the SAP Authentication plug-in in the Central Management Console. 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) SAP Integration Kit Now we can start the installation process for the SAP Integration Kit. I select English as language and click OK to go to the next step.
22
23
In the next screen I select "Custom" to select all components from the SAP Integration Kit.
24
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.
25
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
Type a descriptive string to identify 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 Type the name of your BW server. If you
26
Host
have a BW cluster, enter the name of the central instance of BW. Gateway Type the port number that the Gateway Service Host is listening on. For example, type 33##, where ## represents the instance number of your SAP Gateway. Usually, the instance number is 00, and the value for this field is 3300.
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.
27
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.
28
Now we need to install the transports from the Integration Kit for SAP Solutions on the SAP server.
Open SQL connectivity. InfoSet connectivity. BW MDX Driver connectivity. BW ODS connectivity. SAP authentication. Content Administration Workbench. BW Query parameter personalization.
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.
29
SAP Connectivity
This component provides database drivers that are designed specifically for reporting off SAP data. The following drivers are included:
Open SQL. InfoSet. BW Query (BW Query only). BW MDX (BW cubes and queries). 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.
30
The SAP authentication allows the administrator to leverage the SAP users and roles and it allows the end user to leverage functionality like single-sign-on with BusinessObjects Enterprise. I am calling the Central Management Console
After Logon I am presented with the main screen of the Central Management Console
31
... and can now navigate to the item Authentication (right hand side).
I select the SAP Authentication from the list of available authentications and are now presented with the list of SAP Entitlement systems, which in our case is empty because so far we have not configured any systems.
32
I can now enter the System ID and Client number from my SAP system and can then enter either a combination of the Message Server and Logon Group or a Application Server and System number. The credentials used here is to read users and roles and to validate role membership during the authentication process. Please refer to the Installation Guide for the Integration Kit for SAP Solutions (Page 73) to see a detailed list of required authorizations for this user. I enter the details and then click Update to add the system to the list of available entitlement systems.
33
34
Here I can configure multiple items but for now I will only set the Default System to my newly created system and I will set the flag for the option "Automatically import user". By setting this option all users that are assigned to the roles that I will import in the next step will also become BusinessObjects Enterprise users. In case I would not set this option the users would get created based on the rolemembership as part of the initial authentication towards BusinessObjects Enterprise. Now I navigate to the tab "Role Import".
35
By importing SAP roles into BusinessObjects Enterprise, you allow role members to log onto BusinessObjects Enterprise with their usual SAP credentials. In addition, single-sign-on is enabled so that SAP users can be logged onto BusinessObjects Enterprise automatically when they access reports from within the SAP GUI or an SAP Enterprise Portal. For each role that is imported BusinessObjects Enterprise generates a user group. Each group is named with the following naming convention: [SAP system ID] ~ [SAP client number] @ [SAP role] For example: R37~800@BOBJ_TRAIN_ROLE_01
I now select the roles that I want to import and click "Add" and then "Update" to import those roles into my BusinessObjects Enterprise system.
36
Now I close the SAP Authentication screen and select the item "Users and Groups" to show the imported Groups and User.
37
Here you can see the imported roles and because I did set the option to "Automatically import users" the assigned users of those roles are imported as well.
38
To now validate this I call InfoView and select the SAP Authentication and logon to InfoView with my SAP credentials.
In case everything is configured correct you should be able to logon now with the SAP credentials and the SAP account is shown in the top right corner in InfoView
The user and roles that we imported into the BusinessObjects Enterprise system have no rights / authorizations in the BusinessObjects Enterprise system so far but you can use the standard mechanism to assign rights in the Central Management Console to those users and user groups. For the scenario where you want to use SSO based on tickets with the BusinessObjects Enterprise and the BI System (either from the SAP GUI or via the SAP Enterprise Portal) you need to configure profile parameters in the SAP BI System.
39
login/accept_sso2_ticket login/create_sso2_ticket
Profile parameter
Value
Comment Use the value 1 if the server possesses a public-key certificate signed by the SAP CA. Use the value 2 if the certificate is self-signed. If you are not sure, then use the value 2. Use the value 1 so that the system will also accept logon tickets.
login/create_sso2_ticket 1 or 2
login/accept_sso2_ticket 1
Please also check the SAP documentation for more details and keep in mind that those changes will require to restart the SAP system. I hope you are now at a point where you were able to install everything and you are now able to use your SAP Credentials to authenticate towards the BusinessObjects Enterprise system so far you should be in a situation where you have a running BusinessObjects Edge system with Crystal Reports, Xcelsius, Live Office and the SAP Integration Kit installed and you are able to logon to BusinessObjects Edge with your SAP credentials. In the next step we will configure the publishing of a Crystal Reports where we first will save the report into the BI repository and then push it from the BI environment to the BusinessObjects Edge server. In the last blog we did install all the required software so that we can no configure the BusinessObjects server to allow SAP accounts and SAP roles to leverage the software. This image outlines the publishing process:
40
Step #1 : When a user attempts to publish one or more Crystal reports, BW looks for a Remote Function Call (RFC) destination (of type TCP/IP) that is configured to connect to this BW Publisher. The TCP/IP destination provides SAP BW with the name and port number of the SAP Gateway that the BW Publisher is registered with.
Step #2: SAP BW then communicates over TCP/IP with the BW Publisher Service, and sends the following information across the network:
o o o
The appropriate Crystal report file(s), with any required translated report strings. A publishing command, if you are not using a local SAP Gateway. The name of the appropriate Central Management Server (CMS).
Step #3: The BW Publisher Service responds by executing the publishing command, thereby invoking the BW Publisher. The BW Publisher logs onto the specified CMS as the user, and checks to see if the user has the appropriate permissions in BusinessObjects Enterprise to publish reports. If the user's rights are sufficient, the CMS allows the reports to be added to the system.
When publishing a report from Crystal Reports the report is published with the language from the SAP Logon as "master-language". Master-language in this case means that the string values from this report are stored in SAP translation tables with the configured language set as source language for the translation process.
41
The configuration of the service is done via the registry. The path in the registry is: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service
Program ID
Type a descriptive string to identify 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 casesensitive. Type the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW.
Gateway Host
42
Gateway Service
Type the port number that the Gateway Host is listening on. For example, type 33##, where ## represents the instance number of your SAP Gateway. Usually, the instance number is 00, and the value for this field is 3300.
After you entered those items in the registry you should be able to start the Publishing service and the service should keep running. In my case I entered the following: Program ID : VMW010_PUBLISH Gateway Host : vanpgsap05.sap.crystald.net (which is my SAP BI Application Server) Gateway Service : 3300 In case you entered everything correct you should be able to start the BW Publishing Service and it should keep running. The publishing can also be configured using a SAP Gateway as an alternative for the Publishing Service.
43
... and provide a name for the RFC Destination. As Connection Type I select TCP/IP (T) and enter an description as well.
44
As Application Type I select "Registered Server Program" and enter the Program ID that I configured previously for my BW Publishing Service as the Program here. Important - this is case sensitive. I also enter the Gateway options: o Gateway host Type the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW. You must use the same BW server name here that you specified when you configured the BW Publisher service. o Gateway service Type the port number that the Gateway host is listening on. For example, type sapgw##, where ## represents the instance number of your SAP Gateway. Often, the instance number is 00, and the value for this field is sapgw00. In my case I configured the destination as follows: