grc intergation kit

BusinessObjects Integration Kit for SAP - Installation and Configuration

Applies to: BusinessObjects Enterprise XI Release 3.0, BusinessObjects Integration Kit for SAP Solutions

Summary This document outlines the required steps to install and configure BusinessObjects Enterprise in combination with SAP NetWeaver BI.

Author: Ingo Hilgefort

Company: Business Objects, an SAP company

Created on: 01 October 2008

Author Bio Ingo Hilgefort started in 1999 with Seagate Software / Crystal Decisions as a Trainer and Consultant.

He moved to Walldorf for Crystal Decisions by end of 2000 and worked with the SAP BI Development team on integrating Crystal Reports with SAP BW. He then relocated to Vancouver in the year 2004 and worked as Product Manager / Program Manager (Engineering) on the integration of Business Objects products with SAP products.

He is now focusing on the topic of Embedded Analytics for the SAP Solutions.

SAP DEVELOPER NETWORK | sdn.sap.com BUSINESS PROCESS EXPERT COMMUNITY | bpx.sap.com © 2008 SAP AG 1

BusinessObjects Integration Kit for SAP - Installation and ConfigurationSDN Community Day - BusinessObjects Enterprise with SAP

Table of Contents BusinessObjects Integration Kit for SAP – Components....................................................................................3

SAP Connectivity ............................................................................................................................................3 SAP Authentication .........................................................................................................................................3 BW Publisher ..................................................................................................................................................3 BW Content Administration Workbench..........................................................................................................3 SAP Enterprise Portal – Knowledge Management .........................................................................................3 SAP Enterprise Portal – iView Template & Sample iView ..............................................................................3

BusinessObjects Integration Kit for SAP – Technical Prerequisites ..................................................................4 SAP Frontend Installation ...............................................................................................................................4 SAP Java Connector.......................................................................................................................................5 SAP Transports...............................................................................................................................................6 SAP Single-Sign-On........................................................................................................................................6

Profile Parameters .......................................................................................................................................................6 BusinessObjects Enterprise Server Side requirements..................................................................................7

BusinessObjects Integration Kit for SAP - Installation........................................................................................8 Installation of the BusinessObjects Integration Kit for SAP ............................................................................8

Configuration of SAP Authentication ................................................................................................................16 Enable SAP authentication ...........................................................................................................................16 Configure Global Options for the SAP Authentication ..................................................................................18 Import SAP Users and Roles ........................................................................................................................20

Publishing integration for Crystal Reports ........................................................................................................25 Publishing Crystal Reports Objects with SAP BW........................................................................................25 Publishing Process........................................................................................................................................26 Configuring the BW Publish Service .............................................................................................................28 Creating an RFC Destination ........................................................................................................................31 Create a BusinessObjects Enterprise Server Definition ...............................................................................33 Configure the SAP Source Parameters ........................................................................................................38 Configuring the SAP HTTP Request Handler ...............................................................................................40 BusinessObjects Security Configuration for Publishing................................................................................43

Copyright...........................................................................................................................................................51



BusinessObjects Integration Kit for SAP – Components

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. • OLAP BAPI.

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.

BW Content Administration Workbench The Content Administration Workbench allows you to administer report publishing functionality from within SAP BW. You can identify roles from the SAP BW system with particular BusinessObjects Enterprise systems, publish reports, and synchronize reports between SAP BW and a BusinessObjects Enterprise system.

SAP Enterprise Portal – Knowledge Management

The repository manager interface allows integrating the BusinessObjects repository with SAP’s Knowledge Management capabilities like subscription, feedback, ranking and collaboration. BusinessObjects Enterprise uses the repository manager interface to create a virtual reference of the BusinessObjects Enterprise content inside the Knowledge Management system.

In addition to offering the Knowledge Management functionalities the repository manager also allows the user to create new content inside the portal – like a new Web Intelligence report.

SAP Enterprise Portal – iView Template & Sample iView

The BusinessObjects Integration Kit offers a specific iView template which allows quick creation of new content for the Enterprise portal and surface content from the BusinessObjects Enterprise system. The template offers BusinessObjects Enterprise specific functionalities like choosing a content viewer or choosing between a last instance and on-demand reporting.

The sample iViews offers some basic functions like a report listing as a sample application inside the SAP Enterprise Portal.



BusinessObjects Integration Kit for SAP – Technical Prerequisites

SAP Frontend Installation

The SAP GUI is required for using the Business Objects Integration Kit for SAP. The required version and the required patch level are listed in the list of supported platforms for the BusinessObjects Integration Kit for SAP.

When installing the SAP GUI you need to choose the components selected in the screenshot below.



SAP Java Connector

The SAP Java Connector is required for the SAP authentication and for the SAP specific features in InfoView. The SAP Java Connector can be downloaded for free from SAP’s service marketplace (http://service.sap.com).

The following files need to be copied to the BusinessObjects Enterprise server:

• sapjco.jar needs to be copied to the shared library path of the application server. In the case of a default Tomcat deployment the path would be C:\Program Files\Business Objects\Tomcat55\shared\lib.

• librfc32.dll and sapjcorfc.dll need to be copied to the Windows\system32 directory.

Note: In case the SAP GUI has been installed, the librfc32.dll doesn’t need to be copied.

Note: For UNIX environments copy the librfccm library and the libsapjcorfc library to

businessobjects_root/enterprise115/PLATFORM_PATH, where businessobjects_root is the full path to your BusinessObjects directory. For example, PLATFORM_PATH is solaris_sparc for an installation on Solaris.

Note: If you are planning to integrate with an SAP BI 7 system, your SAP Java Connector must be

version 2.1.6 at a minimum because SAP BI 7 allows passwords that are longer than 8 characters and this requires at a minimum the version 2.1.6 from the SAP JavaConnector.



SAP Transports

The BusinessObjects Integration Kit for SAP includes transports as part of the product. These transports include functionality especially designed for the integration with SAP. The following is a list of functionalities that require SAP transports:

• Open SQL connectivity. • InfoSet connectivity. • BW MDX Driver connectivity. • BW ODS connectivity. • Row-level Security Definition editor. • Cluster Definition editor. • SAP authentication. • Content Administration Workbench. • BW Query parameter personalization.

SAP Single-Sign-On

Profile Parameters

Before you can enable ticket based single-sign-on between SAP and BusinessObjects Enterprise, you must set up your SAP system to accept and create logon tickets. This involves setting two related profile parameters on your SAP server:

• login/accept_sso2_ticket • login/create_sso2_ticket

Profile parameter Value Comment

login/create_sso2_ticket 1 or 2 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.

login/accept_sso2_ticket 1 Use the value 1 so that the system will also accept logon tickets.

Note: These settings require a restart of the SAP system.



BusinessObjects Enterprise Server Side requirements

Before installing the Integration Kit for SAP, these are the prerequisites for the BusinessObjects Enterprise server:

• The file saplogon.ini needs to be installed on machines with data access components. You can add the full path to the saplogon.ini file to the SAPLOGON_INI_FILE environment variable.

Note: In case the SAP GUI has been installed the saplogon.ini file is installed on the client machine.

• In case load balanced logon will be part of the deployment, the following entry must appear in the services file (found in %windir%\system32\drivers\etc\) on any BusinessObjects Enterprise machines running a CMS or data processing server component (for example, Crystal Reports Job Server):

sapms [SAP System ID] [SAP tcp port number]/tcp



BusinessObjects Integration Kit for SAP - Installation

Installation of the BusinessObjects Integration Kit for SAP

To install the BusinessObjects Integration Kit for SAP

1. Double-click the setup.exe.

2. Select the language and click OK.

Note: The selected language is the language for the setup process – it is not the language for the product itself.

3. Click Next.



4. Select the option I accept the License Agreement.

5. Click Next.

6. Enter the Full Name and organization.

7. Enter the Product ID (license keycode).

8. Click Next.



9. Select the list of required languages for the BusinessObjects Integration Kit for SAP.

10. Click Next.

11. Select Custom.

12. Click Next.



Note: The above shows all components that are available for the installation.

13. Select the necessary components.

14. Click Next.

15. Enter the CMS Name (TECHED08) and make sure the port number is correct.



16. Enter the password for the Administrator account. Note: The reason for this CMS logon is that the SAP specific features for InfoView need to be

implemented in the system database.

17. Click Next.

18. Complete the following fields:

o 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.

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.

o 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.

19. Click Next.



20. Select the option Yes, automatically deploy the web application.

21. Click Next.



Note: After this step the installation routine will start. As a verification step after the installation

has finished you should see the SAP authentication as part of the available authentication options for InfoView.

22. Click Next.



After the installation is finished you should be able to open InfoView and see the SAP Authentication as an available option.



Configuration of SAP Authentication

Enable SAP authentication

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.

To enable the SAP authentication

1. Log onto the Central Management Console.

2. Navigate to Authentication.

3. Double-Click SAP.



4. Enter the system ID and client number from the SAP system into the fields System and Client.

5. Click Update. Note: The system ID and client number are combined and entered as an entry in the list of logical

systems.



Configure Global Options for the SAP Authentication

The SAP authentication includes a number of options that you can customize when integrating BusinessObjects Enterprise with your SAP systems. For instance, you can enable/disable SAP authentication and/or configure BusinessObjects Enterprise to temporarily disable SAP authentication for SAP systems when they become unavailable.

To configure the SAP authentication options



3. Double-click SAP.

4. Navigate to the Options tab.

• Enable SAP Authentication

Clear this check box if you want to disable SAP authentication completely. (To disable SAP authentication for specific SAP systems, select the system’s Disabled check box on the Entitlement Systems tab.)

• Max failed entitlement system accesses and Keep entitlement system disabled [seconds] Use these fields together to configure how BusinessObjects Enterprise handles SAP entitlement systems that are temporarily unavailable. BusinessObjects Enterprise uses these settings to determine when to stop communicating with an SAP system that is unavailable, and when it should resume communication with that system. In the “Max failed entitlement system accesses” field, type the number of times that BusinessObjects Enterprise should re-attempt contacting an SAP system to fulfill authentication requests. Setting the value to -1 allows BusinessObjects Enterprise to attempt to contact the entitlement system an unlimited number of times before ceasing. Setting the value to 0 limits BusinessObjects Enterprise to making one attempt to contact the entitlement system. In the “Keep entitlement system disabled [seconds]” field, type the number of seconds that BusinessObjects Enterprise should wait before resuming attempts to authenticate users against the SAP system.



For example, if you type 3 for “Max failed entitlement system accesses”, BusinessObjects Enterprise allows a maximum of 3 failed attempts to authenticate users against any particular SAP system; the fourth failed attempt results in BusinessObjects Enterprise ceasing its attempts to authenticate users against that system for the amount of time specified by “Keep entitlement system disabled [seconds].”

• Max concurrent connections per system Use this field to specify how many connections you want to keep open to your SAP system at the same time. For example, if you type 2 in this field, BusinessObjects Enterprise keeps 2 separate connections open to SAP.

• Number of uses per connection Use this field to specify how many logons you want to allow to the SAP system per connection. For example, if you specified 2 for “Max concurrent connections per system” and 3 for “Number of uses per connection”, once there has been 3 uses on one connection, BusinessObjects Enterprise will close that connection and restart it.

Note: Number of uses refers to actual transactions (or RFC calls) towards the SAP system.

• Content folder root Use this field to specify where you want BusinessObjects Enterprise to begin replicating the BW folder structure in the CMC and InfoView. To change this value, you must change it both in the CMC and the Content Administration Workbench. This value is relevant for the publishing integration with Crystal Reports.

• Automatically import users Select this check box if you want BusinessObjects Enterprise to create user accounts and user folders for all role members when you actually import the roles. Clear the check box to have BusinessObjects Enterprise create user accounts and user folders dynamically, when users log on for the first time with valid SAP credentials.

• Concurrent users / Named Users Use this option to specify if new user accounts are configured to use concurrent user licenses or named user licenses.

• Default system In this list, select the SAP entitlement system that BusinessObjects Enterprise uses as the default system (that is, the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system).

5. Select the CIM System as Default System

6. Set the option “Automatically import user” to true

7. Click Update.



Import SAP Users and Roles

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: CIM~003@BOBJ_TRAIN_ROLE_01 You can view the new groups in the groups management area of the CMC. You can also use these groups to define object security within BusinessObjects Enterprise.

To import SAP roles to BusinessObjects Enterprise



3. Double-click SAP.

4. Navigate to the Role Import tab.



5. Select the roles “BUSINESSOBJECTS_PM_TECHED08” from the list of available roles.

6. Click Add >.

7. Click Update.

Note: After the import of the SAP roles has been completed, users that are members of these SAP

roles are able to log on with their SAP account to BusinessObjects Enterprise.



For this session we will now add the imported SAP Role to the administrator role in the BusinessObjects Enterprise system.

To add the SAP roles to the administrator role in BusinessObjects Enterprise


2. Navigate to Users and Groups.

3. Right-click the imported role CIM~003/BUSINESSOBJECTS_PM_TECHED08



.

4. Select Join Group.

5. Select the Administrator Group and add it to the list on the right side.



6. Click OK.

The role should show up in the Group Hierarchy below the Administrators role.



Publishing integration for Crystal Reports

Publishing Crystal Reports Objects with SAP BW

The BW Publisher allows publishing Crystal reports (.rpt files) individually or in batches from SAP BW to BusinessObjects Enterprise. Reports are published from SAP BW to BusinessObjects Enterprise in several ways:

• Users who design Crystal reports can simultaneously save reports to their roles in SAP BW and publish them to BusinessObjects Enterprise, provided they have sufficient rights.

• Users with the appropriate rights within SAP BW and BusinessObjects Enterprise can also publish reports individually or in batches using the Content Administration Workbench.

You can configure the BW Publisher in one of two ways:

• Install the BW Publisher as a service on a BusinessObjects Enterprise machine. The BW Publisher service starts instances of the BW Publisher as required.

• Install a local SAP Gateway to create BW Publisher instances.



Publishing Process

Whether configuring the BW Publisher service with or without a local SAP Gateway, the same basic publishing process occurs.

• 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.

• SAP BW then communicates over TCP/IP with the BW Publisher, and sends the following information across the network:

o The appropriate Crystal Report file(s), with any required translated report strings. o A publishing command, if you are not using a local SAP Gateway. o The name of the appropriate Central Management Server (CMS).

• The SAP Gateway 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.

Note: Before beginning to publish, you must configure SAP authentication in BusinessObjects Enterprise, define a folder structure for your content, and import SAP roles.



The diagram below outlines the main steps involved in the publishing process.



Configuring the BW Publish Service

The publisher service uses the configured settings that are stored in the registry.

The path in the registry is:

HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service



To configure the BW Publisher service

1. Click Start.

2. Select Run.

3. Enter the command regedit.

4. Click OK.

5. Navigate to the area in the registry for the BW Publisher service: HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\SAP\BW Publisher Service

6. Configure the values for the BW Publisher service.

o 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.

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.

o 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.

7. Close the registry editor.



8. Start the Central Configuration Manager (Start > Programs > BusinessObjects XI Release 3 > BusinessObjects Enterprise > Central Configuration Manager).

9. Select the BW Publisher Service.

10. Click Start.



Creating an RFC Destination

To enable the BW Publisher, you must configure an RFC destination on your BW server to communicate with the BW Publisher service.

If you wish to publish to multiple BusinessObjects Enterprise systems from BW, create a separate RFC destination for the BW Publisher service configured for each BusinessObjects Enterprise system. You must use unique Program IDs for each destination, but the same Gateway Host and Gateway service.

To create a new RFC destination

1. Log onto the SAP server CIM.

2. Start transaction SM59 (RFC Destinations).

3. Click Create.

4. Enter a name for the RFC destination.

5. Select TCP/IP as connection type.

6. Enter a description for the RFC destination.



7. Click Save.

8. Select Registered Server Program as Application Type.

9. Enter the Program ID that was configured for the BW Publisher service as Program ID. Note: The Program ID name is case-sensitive.

10. 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.

o

11. Click Save.

12. Click Test Connection.



Create a BusinessObjects Enterprise Server Definition

You must create a system definition within the Content Administration Workbench for each BusinessObjects Enterprise system to which you want to publish reports to. The BusinessObjects Enterprise system definition combines the previous configuration steps with additional settings like user roles and languages.

To create a new BusinessObjects Enterprise server definition

1. Log onto the SAP server.

2. Start transaction /CRYSTAL/RPTADMIN (Content Administration Workbench).

3. Double-click Add new system.

4. Type a descriptive name in the Alias field.

Note: Avoid using spaces or special characters.



5. In the CMS name field, type the name of the machine that is running your BusinessObjects Enterprise Central Management Service. If you configured your CMS to listen on a port other than the default, type in the details in the following syntax: CMSNAME: PORT.

6. Select Default system if you want to publish reports to this system from any role that has not been explicitly assigned to a BusinessObjects Enterprise system. Only one BusinessObjects Enterprise system can be the default system per SAP System.

7. Navigate to the RFC Destinations tab.

8. Click Insert Row to add the RFC Destination for the BusinessObjects Enterprise system that was

created previously.

9. Select the RFC Destination created previously from the list of available RFC destinations.



10. Click Verify CE Definition.

Note: This test verifies that BW can communicate to the specified BW Publisher, and can log onto the BusinessObjects Enterprise system.

11. Navigate to the HTTP tab.

12. Provide the details for the BusinessObjects Enterprise system:

o Protocol Type http (unless the web server that is connected to BusinessObjects Enterprise is configured to use https).

o Web server host and port Type the fully qualified domain name or the IP address of the web server that hosts your BusinessObjects Enterprise InfoView or custom web application.

o Path This path is essentially the virtual path that your web server uses when referring to the SAP subfolder of your BusinessObjects Enterprise web content (or the path to any customer web application). Do not include a forward slash at the beginning or at the end of this entry.

o Viewer application Type the name of the viewer application.

13. Click the Languages tab.



14. Select the language that will be used to publish reports in multiple languages:

15. Click the Roles tab.

16. Select the roles that will be used for this BusinessObjects Enterprise system.

17. Click the Layout tab.



18. Define the default security settings and base folder for publishing.

Note: Publishing Crystal Report objects from SAP BW to BusinessObjects Enterprise results in a report object and in a folder structure replicating the SAP role structure on the BusinessObjects Enterprise system.

19. Click OK (F8).



Configure the SAP Source Parameters

Part of the publishing process is to set the correct data source settings for all the content being published from SAP BW to the BusinessObjects Enterprise system.

To set the SAP source parameters


2. Start transaction /CRYSTAL/RPTADMIN (Content Administration Workbench).

3. Navigate to the SAP System settings in the Publish reports area.

4. Open the folder of SAP System Settings.

5. Double-click the Set BW source parameter item.



6. Click New Entries.

7. Depending on the system landscape you either need to provide the values for:

• Application server and system number. • Application server and logon group.

8. Set the correct values for the SAP server.

9. Click Save.



Configuring the SAP HTTP Request Handler

To enable viewing of reports in BW via the role menu (for example, opening a Crystal Report from the SAP GUI), you must configure BW to use the HTTP request handler that is included as part of the Crystal Content Administration Workbench transport. Then, when a BW user opens a Crystal report from within the SAP GUI, BW is able to route the viewing request over the web appropriately to BusinessObjects Enterprise.

To configure the SAP HTTP request handler


2. Start transaction SICF (Maintain services).

3. Open the folder default_host.

4. Open the folder SAP.

5. Open the folder bw.



6. Double-click on the service ce_url.

7. Navigate to the Handler List tab.



8. Click Change.

9. Ensure the top entry is /CRYSTAL/CL_BW_HTTP_HANDLER.

10. In case the entry is not the top entry the Insert Row and Delete Row options can be used to add/remove items.

11. Click Save.

12. Close the window.

13. Log off from the SAP server.



BusinessObjects Security Configuration for Publishing

Based on the described details for the publishing process, consider three main categories of users when configuring BusinessObjects Enterprise for publishing, and when importing roles to BusinessObjects Enterprise:

• BusinessObjects Enterprise administrators Enterprise administrators configure the BusinessObjects Enterprise system for publishing content from SAP. They import the appropriate roles, create necessary folders, and assign rights to those roles and folders in BusinessObjects Enterprise.

• Content publishers Content publishers are those users who have rights to publish content into roles. The purpose of this category of user is to separate regular role members from those users with rights to publish reports.

• Role members

Role members are users who belong to “content bearing” roles. That is, these users belong to roles to which reports are published. They have rights to view and schedule content that has been published to the roles they are members of. However, regular role members cannot publish new content, nor can they publish updated versions of content.

Note: You must import all content publishing and all content bearing roles to BusinessObjects

Enterprise prior to publishing for the first time.

It is strongly recommended that you keep the activities of roles distinct. For example, while it is possible to publish from an administrator role, it is better practice to publish only from content publisher roles. Additionally, the function of content publishing roles is only to define which users can publish content. Thus, content publishing roles should not contain any content. Content publishers should publish to content bearing roles that are accessible to regular role members.



The following are recommendations for the previously described BusinessObjects user groups:

Role Members

BusinessObjects Enterprise imports a group for each role that is added to the entitlement system as defined in the CMC. To ensure that suitable default rights are granted to all members of a content bearing role, grant the following rights in the Content Administration Workbench for each entitlement system that is defined in BusinessObjects Enterprise:

• Default Security policy for reports = View • Default security policy for role folders = View on Demand

Content Publisher

Assign the following rights to a publisher role in the Central Management Console:

• Add objects to the folder. • View objects. • Edit objects. • Modify the rights users have to objects. • Delete objects. • Delete instances. • Copy objects to another folder.

Note: These rights should be assigned on a folder level or on an SAP system level and should only

be assigned to a role that focuses on publishing reports from SAP BW to BusinessObjects Enterprise.



In regards to the folder structure the following explains how SAP Roles and Crystal Report objects in the SAP Roles are being created in the BusinessObjects Edge server.

When publishing, the top-level folder “SAP” and the folder underneath “3.0” (naming depends on the configuration in the Content Administration Workbench and the SAP Authentication in the Central Management Console) are created automatically.

Underneath the folder structure is created based on the values retrieved from SAP BW during the publishing process:

• The Folder “SID” is replaced with the logical system name consisting of the SAP System ID and the SAP Client Number (for example, R37CLNT800).

• The role folder is created based on the technical name and description of the role that has been used to store the Crystal Report object on the SAP BW system.

• The report itself is saved to the actual role folder. • For each language the report is made available in, one report object is created.

For example, the following structure will appear on the BusinessObjects Enterprise system assuming the following values:

• SAP system ID : R37 • SAP client number : 800 • SAP BW role name : Business Objects Training Role • Used languages : English, German (DE), and simplified Chinese (ZH)



To configure the rights in the Content Administration Workbench

1. Start the SAP Logon.

2. Select the SAP server.

3. Click Log on.

4. Enter the User, Password, and Language.

5. Press Enter.

6. Enter the transaction code /CRYSTAL/RPTADMIN.

7. Press Enter.



8. Open the folder Enterprise system.

9. Open the folder Available systems.

10. Double-click the entry for the BusinessObjects Enterprise system.

11. Navigate to the Layout tab.

12. Configure the default security policy for reports and role folders.

13. Click OK.



To configure the rights in the Central Management Console


2. Navigate to the Folders.

3. Navigate to the SAP System ID folder.

4. Select the folder.

5. Select the menu Manage > Security > User Security.



6. Click Add Principals.

7. Click Groups.

8. Select the Content Publishing role from the SAP system.

9. Click the right arrow to move the role to the list of selected users/groups.

10. Click Add and Assign Security.



11. Navigate to the Advanced tab.

12. Click Add/Remove rights.

13. Ensure the needed rights are granted.

14. Click OK.

15. Click OK.

16. Click Close.




Copyright © 2008 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 in several other countries all over the world. 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.

These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials.

SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages.

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

grc intergation kit

Documents