business objects edge install linux en

8/6/2019 Business Objects Edge Install Linux En

1/170

BusinessObjects Edge SeriesIntegration for SAP Solutions

BusinessObjects Edge Series XI Release 2

Windows/Linux


2/170


3/170

ContentsIntroduction 9Chapter 1

About this guide.........................................................................................10

Who should read this guide..................................................................11

Installing BusinessObjects Edge Series Integration for SAP Solutions13

Chapter 2

Installation overview..................................................................................14

Installing on Windows................................................................................15

System requirements...........................................................................15

Installing BusinessObjects Edge Series Integration for SAP Solutions.18

Completing the installation...................................................................19

Deploying the web applications............................................................19

Installing on LINUX....................................................................................21

System requirements...........................................................................21

Installing the LINUX components.........................................................23Completing the installation...................................................................24

Deploying the web applications............................................................24

Configuring SAP authentication 27Chapter 3

Configuration overview..............................................................................28

Configuring transports...............................................................................28

Types of transports...............................................................................29

Selecting which transports to import....................................................31

Checking for conflicts...........................................................................32

Importing the transport files..................................................................32

Creating and applying authorizations........................................................33

BusinessObjects Edge Series Integration for SAP Solutions 3


4/170

Configuring SAP authentication for BusinessObjects Edge Series...........33

Creating a user account for BusinessObjects Edge Series.................34

Accessing the SAP authentication application in BusinessObjects EdgeSeries...................................................................................................35

To log on to the CMC............................................................................35

Connecting to SAP entitlement systems..............................................36

Setting SAP Authentication options .....................................................38

To change the Content folder root........................................................41

Importing SAP roles to BusinessObjects Edge Series..............................42

To import a role to BusinessObjects Edge Series................................43

To check that roles and users were imported correctly........................44

Integrating with Secure Network Communication......................................45

Configuring BusinessObjects Edge Series servers to run under an SNCaccount.................................................................................................45

Configuring the SAP system to trust the BusinessObjects Edge Seriessystem..................................................................................................47

Configuring the SNC settings in the Central Management Console ....48

Configuring Data Access 51Chapter 4

Processing scheduled reports in SAP's batch mode.................................52To process scheduled reports in SAP's batch mode............................52

Configuring SAP Logon for the Data Access Kit.......................................54

Reporting with BusinessObjects Edge Series Integration for SAPSolutions 55

Chapter 5

Reporting off BW queries, InfoSets, Operational Data Stores, and MDXcubes.........................................................................................................56

Authenticating SAP users..........................................................................57

Publishing from BW to BusinessObjects Edge Series...............................58Selecting your BW Publisher configuration..........................................58

Publishing Reports ..............................................................................59

4 BusinessObjects Edge Series Integration for SAP Solutions

Contents


5/170


6/170

Defining Security for the Open SQL driver 103Chapter 8

Security Definition Editor overview..........................................................104

Migrating your existing security model ...................................................105

Choosing your table-level security model ...............................................105

Customizing authorizations for specific tables ........................................108

Customizing authorizations for specific functions....................................113

Defining table authorizations by group....................................................113

Applying row-level security......................................................................114

Securing rows using authorization objects ........................................115

Securing rows using custom security exits .......................................117

Transport Files 121Chapter 9

Overview..................................................................................................122

Open SQL Connectivity transport......................................................122

InfoSet Connectivity transport............................................................124

Row-level Security Definition transport..............................................125

Cluster Definition transport.................................................................126

Authentication Helpers transport........................................................127Crystal Content Administration Workbench transport........................127

ODS connectivity transport.................................................................130

BW Query parameter personalization transport.................................130

BW MDX connectivity transport..........................................................131

Authorizations 135Chapter 10

Authorizations overview...........................................................................136

Actions in BW..........................................................................................136

From within Crystal Reports...............................................................136

From within the BusinessObjects Edge Series InfoView for SAP......146

Actions in R/3 and MySAP ERP..............................................................150


Contents


7/170

From within Crystal Reports using the Open SQL driver...................150

From within Crystal Reports using the InfoSet driver, reporting off

InfoSet................................................................................................152From within Crystal Reports using the InfoSet driver, reporting off anABAP query........................................................................................154

From within BusinessObjects Edge Series........................................156

Crystal entitlement system.......................................................................157

Troubleshooting 159Chapter 11

Troubleshooting overview........................................................................160

Locating and generating log files.............................................................160

Troubleshooting BusinessObjects Edge Series ......................................160

Troubleshooting your InfoSet driver installation.......................................161

Reports, tables, and functions............................................................161

Errors when connecting to SAP.........................................................161

Get More Help 163Appendix A

Index 167


Contents


8/170


Contents


9/170

Introduction

1


10/170

About this guide on page 10

About this guideBusinessObjects Edge Series Integration for SAP Solutions, provides theuser with the ability to extract the business intelligence contained within your SAP systems. By installing Desktop Intelligence InfoView for SAP allowsyou to share your reports over the Web, and SAP Authentication enablesSingle Sign On between your SAP system and BusinessObjects Edge Series.

BusinessObjects Edge Series Integration for SAP Solutions consists of several main components: Crystal Reports is the report-design tool thatallows you to report off your SAP data; BusinessObjects Edge Series providesthe framework for managing, scheduling, and distributing reports over theWeb; and report off the multidimensional data that is stored in the Info Cubesof your SAP Business Information Warehouse.

BusinessObjects Edge Series Integration for SAP Solutions provides thedatabase drivers and other features for reporting off SAP. This guidedocuments the SAP report-design features that are available once you installthe kit on top of Crystal Reports. It also shows how to publish and view these

reports in a BusinessObjects Edge Series environment.


Introduction1 About this guide


11/170

Who should read this guide

This help is intended for the system administrator or IT professional whoneeds to install BusinessObjects Edge Series Integration for SAP Solutions.Familiarity with your overall network environment, port usage, your databaseenvironment, and your web server software is especially beneficial. Familiaritywith your SAP system and BusinessObjects Edge Series is required to usethis guide.

For more information about the product, refer to Business Objects EdgeSeries Integration for SAP Solutions Getting Started guide located in thedocs directory of your product distribution.


1Introduction About this guide


12/170


Introduction1 About this guide


13/170

Installing BusinessObjectsEdge Series Integration for SAP Solutions

2


14/170

This section contains information about the system requirements and theprerequisites for the installation of BusinessObjects Edge Series Integrationfor SAP Solutions.

Installation overviewTo set up BusinessObjects Edge Series Integration for SAP Solutions, youmust complete the main installation and configuration stages in this order:

Check the system requirements and perform the installation proceduresthat correspond to your operating environment.

See Installing on LINUX on page 21.

See Installing on Windows on page 15. Complete the required base administrative tasks within SAP, necessary

to configure R/3, MySAP ERP, or BW systems to work withBusinessObjects Edge Series Integration for SAP Solutions. Requiredtasks include importing transport files and setting up authorizations inSAP, configuring SAP authentication in BusinessObjects Edge Series,and configuring Data Access for SAP.

If you have BW, complete the following additional configuration steps:

Setting up folders and security in BusinessObjects Edge Series onpage 64.

Configuring the BW Publisher on page 69.

Configuring publishing in the Content Administration Workbench onpage 79.

Configuring the SAP http request handler on page 95.

For complete information, see Configuring the BW Publisher on page 69.

A number of installation tasks require the skills and security privileges of anSAP BASIS administrator. Contact an SAP administrator for assistanceduring the installation.

Once you have completed the main installation and configuration stages,you may need to complete additional tasks, depending on the features thatyou want to enable. For details, consult the remaining sections of this help.

Note:


Installing BusinessObjects Edge Series Integration for SAP Solutions2 Installation overview


15/170

On Windows, businessobjects_root refers to

On LINUX, businessobjects_root refers to \bobje

Related Topics Configuring SAP authentication on page 27

Installing on WindowsThis section outlines how to install the core Business Objects products andthen how to install the BusinessObjects Edge Series Integration for SAPSolutions.

System requirements

All BusinessObjects Edge Series Integration for SAP Solutions componentsare supported for use with all editions of BusinessObjects Edge Series,Crystal Reports on Windows operating systems. For a stand-alone installation,ensure that all requirements are met on a single machine.

Note: For a detailed list of tested environments for BusinessObjects EdgeSeries Integration for SAP Solutions, consult the platforms_EN.txt fileincluded with your product distribution. This file includes specific version andService Pack requirements for application servers, operating systems, SAPcomponents, etc.

SAP Presentation CD requirements

BusinessObjects Edge Series Integration for SAP Solutions uses the SAPGUIfrom the SAP Presentation CD, and the SAP Gateway (if you choose toconfigure the BW Publisher using a stand-alone SAP Gateway). For version

requirements, see the platforms_EN.txt file on the installation CD.

Server requirements for BusinessObjects Edge Series

Download the RFC SDK for your platform from the SAP ServiceMarketplace.


2Installing BusinessObjects Edge Series Integration for SAP SolutionsInstalling on Windows


16/170

The file saplogon.ini needs to be installed on machines only with dataaccess components installed. Alternatively, you can add the full path tothe saplogon.ini file to the SAPLOGON_INI_FILE environment variable.

Supported web server software must be installed and configured correctlybefore you install BusinessObjects Edge Series. Consult the platforms_EN.txt file included with your BusinessObjects Edge Seriesproduct distribution for a complete list.

If you are using a load balanced logon, the following entry must appear in the Services file (found in %windir% \system32\drivers\etc\ ) on anyBusinessObjects Edge Series machines running a CMS, Page Server,and/or Report Job Server:

sapms SID portnumber /tcp

Replace SID with the system ID of your SAP system, and replaceportnumber with the port number of the message server thatBusinessObjects Edge Series will log on to (for example, sapmsQR63600/tcp). Ensure also that a blank line follows the entry. This standardsetting allows BusinessObjects Edge Series to log on to SAP with loadbalancing.

Client requirements for Crystal Reports

If you have a BW environment, install the SAPGUI along with the BW

AddOn option from the SAP Presentation CD before you install CrystalReports and the BusinessObjects Edge Series Integration for SAPSolutions.

For a detailed list of tested environments for Crystal Reports, consult theplatforms_EN.txt file included with your Crystal Reports productdistribution.

Sap Java Connector

To have the Java version of the BusinessObjects Edge Series InfoView for SAP install automatically, you must install and configure SAP Java Connector components.

To do this, copy librfc32.dlland sapjcorfc.dll to %windir%\system32and copy sapjco.jar to the application server's shared library folder. Consult


Installing BusinessObjects Edge Series Integration for SAP Solutions2 Installing on Windows


17/170

the documentation included with the SAP Java Connector for moreinformation.

To return to the installation procedure, go to Deploying the web applicationson page 19.

SAP requirements

Before you can enable ticket based Single Sign On between SAP andBusinessObjects Edge Series, you must set up your SAP system to acceptand create logon tickets. This involves setting two related profile parameterson your SAP server:

login/accept_sso2_ticket

login/create_sso2_ticket

The parameter values that you set depend upon whether or not the server'scertificate is self-signed or signed by the SAP Certification Authority (CA).For complete details on these profile parameters and configuring SAP toaccept and create logon tickets, see the SAP Library > Web ApplicationServer >SAP Web Application Server Security > SAP Web Application Server Security > User Authentication > Using Logon Tickets.

Note: You must re-start the SAP system to activate your changes.

Prerequisites for BusinessObjects Edge Series Integration for SAP Solutions Installation

This section mentions the prerequisites for BusinessObjects Edge SeriesIntegration for SAP Solutions Installation. The prerequisites are:

BusinessObjects Edge Series (Core product) should be at FP2.5 BI Server customers should be upgraded to FP2.5 Crystal Reports should be at FP2.5




18/170

Installing BusinessObjects Edge Series Integrationfor SAP Solutions

This section outlines the steps for installing BusinessObjects Edge SeriesIntegration for SAP Solutions.

1. Run the setup program from the installation disc on both the CrystalReports and the BusinessObjects Edge Server machine.

2. Proceed through the Setup program's dialog boxes and follow theinstructions displayed on your screen, until you reach the SelectInstallation Type dialog box.

3. Select the appropriate installation type, depending on the product(s) that

are already installed:a. If only BusinessObjects Edge Server is installed, select the Server

installation type.b. If only Crystal Reports is installed, select the Desktop installation

type.c. If you don't require the BW Report Publisher Service, select the

Custom installation type and ensure that the BW components aredeselected for installation.

4. If you select Desktop installation type, proceed through the Setupprogram's remaining dialog boxes and follow the instructions on your screen to complete the installation.

5. Click Next.6. If your installation includes the BW Publisher Service, you are prompted

for information about your BW system. Record the exact value you specifyhere for the Program ID. You will need this value when you configure theRFC destination on your BW system. Program ID

Type a descriptive string to identify the BW Publisher service. TheProgram ID value must not exceed 64 characters, and must not containblank spaces. The Program ID is case-sensitive.

Gateway Host

Type the name of your BW server. If you have a BW cluster, enter thename of the central instance of BW.

Gateway Service




19/170

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 valuefor this field is 3300. If you have defined a symbolic name for this port(such as sapgw## ), you may use this symbolic name instead.

Optional

If you plan to enforce Secure Network Communication (SNC) betweenSAP and BusinessObjects Edge, enter the appropriate switches here.For information on how to enable SNC for registered servers, consultthe RFC SDK documentation for API RfcAccept.

7. Proceed through the Setup program's remaining dialog boxes and followthe instructions on your screen to complete the installation.

Related Topics Integrating with Secure Network Communication on page 45

Completing the installation

The BusinessObjects Edge Series Integration for SAP Solutions installationis complete only after you complete the following steps.

1. Install Partners SP2.a. Run Setup.exe from the folder Partners SP2.

2. Install Partners FP2.5a. Run Setup.exe from the folder Partners FP2.5

After completing the installation deploy the web application.

Deploying the web applications

To deploy the Java version of the BusinessObjects Edge Series InfoViewfor SAP, you must create virtual path mappings on your Java web applicationserver.




20/170

To deploy the BusinessObjects InfoView for SAP on Tomcat

1. Ensure that you have deployed the SAP Java Connector as described inSap Java Connector on page 16.

2. Ensure that your CLASSPATH environment variable includes the sapjco.jar archive file. (See for details Sap Java Connector on page 16.)

3. Create a directory called META-INF in the SAP java applications folder in your BusinessObjects Edge Series installation directory.

4. Copy the authPluginExts. properties file to the META-INF folder.5. Add the path of the META-INF folder to the CLASSPATH environment

variable.

This properties file adds the SAP authentication option to the log on pageof the InfoView.

6. Confirm the location of the sap_desktop.war file. By default, it is locatedin c:\Program Files\Business Objects\BusinessObjects Enterprise11.5\java\applications\sap.

7. Open a text editor.8. Create a file called desktopwar.xml and add the following content:

Replace WARDIR with the with default location or the specific directorywhere you placed your files.

This desktopwar.xml file will be used as the context descriptor file for theSAP InfoView.

Note: If you install BusinessObjects Edge Series in a location other thanthe default installation directory of C:\Program Files\BusinessObjects\BusinessObjects Enterprise 11.5\, adjust the path description tomatch your actual install directory.

9. Save the desktopwar.xml file to TOMCATDIR\CONF\Catalina\localhost,where TOMCAT is replaced with the directory where Tomcat is installed.

10. Restart Tomcat. Open the Apache Tomcat Properties dialog. Go to theStart menu and select Tomcat >Configure Tomcat , and then, click Startto restart Tomcat.




21/170

Installing on LINUXLINUX versions of the following BusinessObjects Edge Series add-on

components are provided for environments where BusinessObjects EdgeSeries is running on LINUX: SAP Authentication

BW Publisher

Data Access

Web Content

System requirements

Before installing any of the BusinessObjects Edge Series Integration for SAPSolutions, ensure that your environment meets the following requirements.

BusinessObjects Edge Series must be installed and configured correctlyon Linux before you install the BusinessObjects Edge Series IntegrationSolution for SAP components. Complete this installation and configurationin accordance with the BusinessObjects Edge Series Installation Guide.

SAP Java Connector

BusinessObjects Edge Series Integration Solution for SAP web applications(including the InfoView for SAP), and the BusinessObjects Edge SeriesIntegration Solution for SAP Java SDK require the SAP Java Connector.The SAP Java Connector is available from http://service.sap.com/connectors

Please see the SAP MarketPlace for information on licensing SAP JavaConnector for use in your development environment. After you have installedBusinessObjects Edge Series, you must unpack the archive file containingthe SAP Java Connector.

To install BusinessObjects Edge Series Integration Solution for SAP:

Copy the librfccm library and the libsapjcorfc library tobusinessobjects_root /enterprise115/linux_x86

or


2Installing BusinessObjects Edge Series Integration for SAP SolutionsInstalling on LINUX
http://service.sap.com/connectorshttp://service.sap.com/connectors


22/170

Use symbolic links for the location of the .librfccm library and thelibsapjcorfc library

or

Add the location of the librfccm library and the libsapjcorfc library to thelibrary path

After you have installed BusinessObjects Edge Series, you must makesapjco.jar available to your Java application server as a shared resource(either by placing sapjco.jar in the application server's shared lib directory,or by adding sapjco.jar to the class. Consult your application server documentation for details.) Consult the documentation included with theSAP Java Connector for more information.

SAP requirements

Before you can enable ticket based Single Sign On between SAP andBusinessObjects Edge Series, you must set up SAP to accept and createlogon tickets. This involves setting two related profile parameters on your SAP server:

login/accept_sso2_ticket

login/create_sso2_ticket

The parameter values that you set depend upon whether or not the server'scertificate is self-signed or signed by the SAP CA. For complete details onthese profile parameters and configuring BW to accept and create logontickets, see the SAP Library > SAP Web Application Server > Security > SAPWeb Application Server Security > User Authentication > Using Logon Tickets.

Note: You must re-start the SAP system to activate your changes.

Prerequisites for BusinessObjects Edge Series Integration for SAP Solutions Installation

This section mentions the prerequisites for BusinessObjects Edge SeriesIntegration for SAP Solutions Installation. The prerequisites are:

BusinessObjects Edge Series (Core product) should be at FP2.5 BI Server customers should be upgraded to FP2.5 Crystal Reports should be at FP2.5


Installing BusinessObjects Edge Series Integration for SAP Solutions2 Installing on LINUX


23/170

Installing the LINUX components

Once you have set up BusinessObjects Edge Series on LINUX, and haveinstalled the SAP Java Connector, you can install the add-on components.Ensure that BusinessObjects Edge Series is running before you begin theinstallation. The installation script needs to log on to your CentralManagement Server.

To install SAP Add-Ons

1. Log on to your LINUX system under the BusinessObjectsuser accountyou created for businessobjects_root .

Note: You may also use another account that has permission to readand write files in businessobjects_root and its subdirectories.

2. Run the installer from the location that you mounted the CD using theinstallation script../install.sh

3. When prompted, press Enter to continue.

You are prompted to select a language.

4. Select the language that you want to install and press Enter.

The script displays the product license agreement. Press the spacebar to read through the information in its entirety.

5. Press Enter to accept the license agreement and to proceed with theinstallation.

6. The script prompts you for the absolute path of the BusinessObjects EdgeServer installation directory.

The script notifies you that it has collected all of the required information,and asks you if you are ready to have the installation begin.

7. Press Enter .

The installation script unpacks the archived installation file. This may takea few minutes.




24/170


25/170

5. Add the path of the META-INF folder to the CLASSPATH environmentvariable.

This properties file adds the SAP authentication option to the log on page

of the InfoView.6. Create a new and empty file: %CATALINA_HOME%\conf\Catalina\local

host\sap_desktopwar.xml

This file will be used as the context descriptor file for the SAP InfoView.

7. Add the line to sap_desktopwar.xml, in a text editor such as Notepad:

8. Save the sap_desktopwar.xml file.9. Restart Tomcat by typing %CATALINA_HOME%/bin/startup at the

command prompt.




26/170


Installing BusinessObjects Edge Series Integration for SAP Solutions2 Installing on LINUX


27/170

Configuring SAPauthentication

3


28/170


29/170

Checking for conflicts on page 32

Importing the transport files on page 32

The installation and configuration procedures required on the SAP systemmust be performed by a BASIS expert who is familiar with the Change andTransport system and who has administrative rights to the SAP system. Theexact procedure for importing transport files varies, depending upon theversion of BASIS that you are running. For specific procedural details, refer to your SAP documentation.

When you first deploy the Data Access Kit, all users can access all of your SAP tables by default. To secure the SAP data that users can access, usethe Security Definition Editor. For complete details, see Security DefinitionEditor overview on page 104.

After you have imported transports, you must configure the appropriate levelsof user access. Create the required authorizations and apply them throughprofiles or roles to SAP users who will be designing, running, or schedulingCrystal reports. For details, see Creating and applying authorizations onpage 33.

To return to the reporting overview, click Reporting off BW queries, InfoSets,Operational Data Stores, and MDX cubes on page 56.

Types of transportsBusinessObjects Edge Series Integration for SAP Solutions includes seventransports:

the Open SQL Connectivity transport, the InfoSet Connectivity transport, theRow-level Security Definition transport, the Cluster Definition transport, theAuthentication Helpers transport, the Crystal Content AdministrationWorkbench transport, and the BW Query parameter personalization transport.

A subset of these transports are available with BusinessObjects Edge Series

Integration for SAP Solutions.There are two different sets of the transports: Unicode compatible transportsand ANSI transports. If you are running a BASIS system of 6.20 or later, usethe Unicode compatible transports. If you are running a BASIS system earlier than 6.20, use the ANSI transports. The transports_EN.txt file located in


3Configuring SAP authenticationConfiguring transports


30/170

the transports directory on the installation cd lists the Unicode compatibleand ANSI transport files.

Each transport is described here. For details about the contents of each

transport file, see Transport Files on page 121. Open SQL Connectivity transport

The Open SQL Connectivity transport enables the Open SQL driver toconnect to and report off the SAP system. It is included only withBusinessObjects Edge Series Integration for SAP Solutions.

Row-level Security Definition transport

This transport provides the Security Definition Editor, which is a tool thatserves as a graphical interface to the /crystal/auth tables in the OpenSQL Connectivity transport. It is included only with BusinessObjects EdgeSeries Integration for SAP Solutions. For details on using the SecurityDefinition Editor, see Security Definition Editor overview on page 104.

Cluster Definition transport

This transport provides the Cluster Definition tool. This tool enables youto build up a metadata repository for ABAP data cluster definitions. Thesedefinitions provide the Open SQL driver with the information it requiresin order to report off these data clusters. It is included only withBusinessObjects Edge Series Integration for SAP Solutions. For detailson using the Cluster Definition Tool, see the "Reporting off clusters"

section of the BusinessObjects Edge Series Integration for SAP Solutions.

Note: ABAP data clusters are not the same as cluster tables. Cluster tables are already defined in the DDIC.

InfoSet Connectivity transport

The InfoSet Connectivity transport enables the InfoSet driver to accessInfoSets and SAP Queries.

Authentication Helpers transport

This transport provides the Single Sign On enhancement for the SAPauthentication plug-in. This enhancement frees users from having to enter their credentials more than once to access any of the BusinessObjectsEdge Series, R3, and BW systems.

Content Administration Workbench transport


Configuring SAP authentication3 Configuring transports


31/170


32/170

NotesTransportSAP System

Open SQL Connectivity Row-level Security

Definition

Cluster Definition

BW

InfoSet Connectivity

Required if you have in-stalled the SAP SolutionTools Plug-in (ST-PI).

Authentication Helpers

Required.Content AdministrationWorkbench

Required.BW Query parameter personalization

Checking for conflicts

The contents of the transport files are registered automatically under theBusiness Objects namespace when you import the files. The BusinessObjects namespace is reserved for this purpose within recent versions of R/3 and MYSAP ERP. Consequently, there is no need to check for conflictsprior to importing the transport files.

If the function group, any of the function modules, or any of the other objectsalready exists on the SAP system, then you must resolve the namespacebefore importing the BusinessObjects Edge Series Integration for SAPSolutions transport files. Refer to your SAP documentation for the proceduresappropriate to your version of SAP.

Importing the transport files

Read the transports_EN.txt file located in the transports directory onthe installation CD. This text file lists the exact names of the files that make


Configuring SAP authentication3 Configuring transports


33/170

up each transport. (The cofiles and data directories below the transportsdirectory correspond to the .../ trans/cofiles and .../ trans/data directorieson your SAP server.)

You must import the Open SQL Connectivity transport before importing theRow-level Security Definition or the Cluster Definition transports. You mayimport the other transports in any order.

Note:

After copying files from CD to server, ensure that all files are writablebefore you import the transports. Imports fail if the import files areread-only.

Because the transports are binary files, on LINUX installations you mustadd the files by FTP in Binary mode (to avoid file corruption). In addition,

you must have write permissions for the LINUX server.

Creating and applying authorizationsNext you must create and apply the authorizations needed by each user toaccess information using the Desktop Intelligence Integration Kit for SAP.The exact procedures for creating, configuring, and applying authorizationsdepend upon the version of SAP that you have installed.

Authorizations on page 135 provides a list of SAP authorizations that, in our

experience and in our test environment, are required when carrying outcommon tasks with BusinessObjects Edge Series Integration for SAPSolutions. Additional authorization objects or fields may be required,depending upon your individual implementation.

For information on the authorizations needed by content publishers,administrators of the content publishing tool, and users who view reportsfrom within BW, see Configuring publishing in the Content AdministrationWorkbench on page 79.

Configuring SAP authentication forBusinessObjects Edge Series

SAP authentication enables SAP users to log on to BusinessObjects EdgeSeries using their SAP user names and passwords, without storing thesepasswords in BusinessObjects Edge Series. SAP authentication also allows


3Configuring SAP authenticationCreating and applying authorizations


34/170

you to preserve information about user roles in SAP, and to use this roleinformation within BusinessObjects Edge Series to assign rights to performadministrative tasks, or access content.

To return to the information overview, see Authenticating SAP users onpage 57.

Creating a user account for BusinessObjects EdgeSeries

The BusinessObjects Edge Series system requires an SAP user accountthat is authorized to access SAP role membership lists, authenticate SAPusers, and so on. You will need this user name and its password when youconnect BusinessObjects Edge Series to your SAP system. For generalinstruction on creating SAP user accounts and assigning authorizationsthrough roles, see your SAP documentation.

Use transaction SU01 to create a new SAP user account named CRYSTAL.Use transaction PFCG to create a new role named CRYSTAL_ENTITLEMENT .(These names are recommended but not required.) Change the new role'sauthorization data by setting these values for the following authorizationobjects:

ValueField

Read, Write (33, 34)Activity (ACTVT)Authorization for file ac-cess (S_DATASET)

* (denotes All)Physical file name (FILE-NAME)

*ABAP program name(PROGRAM)

16Activity (ACTVT)Authorization Check for RFC Access (S_RFC)

BDCH, STPA, SUSO,SUUS,SU_USER, SYST,SUNI, PRGN_J2EE,/CRYSTAL/SECURITY

Name of RFC to be pro-tected (RFC_NAME)


Configuring SAP authentication3 Configuring SAP authentication for BusinessObjects Edge Series


35/170


36/170

Replace webserver with the name of your BusinessObjects Edge Seriesweb server. If you changed this default virtual directory on the web server,you will need to type your URL accordingly.

2. When the Log On page appears, select Enterprise in the AuthenticationType list.

Windows NT, Windows AD, LDAP, and SAP authentication may alsoappear in the list; however, you must map your third-party user accountsand groups to BusinessObjects Edge Series before you can use thesetypes of authentication.

3. Type your User Name and Password .

For this example, type Administrator as the User Name. This defaultEnterprise account does not have a password until you create one.

4. Click Log On .

The CMC Home page appears. For an introduction to the CMC, click Helpto open the BusinessObjects Enterprise Administrator's Guide; then seethe "Administering BusinessObjects Enterprise" section.

Connecting to SAP entitlement systems

Before you can import roles or publish BW content to BusinessObjects EdgeSeries, you must provide information about the SAP entitlement systemsthat you want to integrate with BusinessObjects Edge Series. BusinessObjectsEdge Series uses this information to connect to SAP when it determines rolememberships and authenticates SAP users.

To add an SAP entitlement system to BusinessObjects EdgeSeries

1. Go to the Authentication management area of the CMC.

2. Click the SAP tab.

The Entitlement systems tab appears.




37/170

Tip: If an entitlement system is already displayed in the Logical systemname list, click New.

3. In the System field, type the three-character System ID (SID) of your SAP system.

4. In the Client field, type the client number that BusinessObjects EdgeSeries must use when it logs on to your SAP system.

Tip: When you finish these steps, BusinessObjects Edge Series combinesyour System and Client information, and adds an entry to the "Logicalsystem name" list.

5. Ensure the Disabled check box is clear.

Note: The Disabled check box allows you, the administrator, to indicateto BusinessObjects Edge Series that a particular SAP system istemporarily unavailable.

6. If you have set up load balancing such that BusinessObjects Edge Seriesmust log on through a message server, complete the Message server and Logon group fields as appropriate.


3Configuring SAP authenticationConfiguring SAP authentication for BusinessObjects Edge Series


38/170

Note: You must make the appropriate entries in the Services file on your BusinessObjects Edge Series machine to enable load balancing.

7. Type the Username , Password , and Language for the SAP accountthat you want BusinessObjects Edge Series to use when it logs on toSAP.

Note: These credentials must correspond to the user account that youcreated for BusinessObjects Edge Series. For details, see Creating auser account for BusinessObjects Edge Series on page 34.

8. Click Update .9. On the Options tab, ensure that the Enable SAP Authentication check

box is selected.

Tip: If you add multiple entitlement systems, click the Options tab tospecify the system that BusinessObjects Edge Series uses as the default(that is, the system that is contacted to authenticate users who attemptto log on with SAP credentials but without specifying a particular SAPsystem).

To check that an entitlement system was added correctly

1. Click the Role Import tab.2. From the Logical system name list, select the name of the entitlement

system.

If the entitlement system was added correctly, the Available roles list willcontain a list of roles that you can choose to import.

If there are no roles visible in this list, scroll to the bottom of the page andlook for error messages. These may give you the information you needto correct the problem.

Setting SAP Authentication optionsSAP Authentication includes a number of options that you can customizewhen integrating BusinessObjects Edge Series with your SAP systems. For instance, you can enable/disable SAP Authentication and/or configure




39/170

BusinessObjects Edge Series to temporarily disable SAP Authentication for SAP systems when they become unavailable.

To set SAP Authentication options:

1. Go to the Authentication management area of the CMC.2. Click the SAP tab and then click the Options tab.

3. Review and modify settings as required: Enable SAP Authentication

Clear this check box if you want to disable SAP Authenticationcompletely. (To disable SAP Authentication for specific SAP Systems,select that system's Disabled check box on the Entitlement systemstab.)

Max failed entitlement system accesses and Keep entitlementsystem disabled [seconds]

Use these fields together to configure how BusinessObjects EdgeSeries handles SAP entitlement systems that are temporarilyunavailable. BusinessObjects Edge Series uses these settings to

determine when to stop communicating with an SAP system that isunavailable, and when it should resume communication with thatsystem.

In the "Max failed entitlement system accesses" field, type the number of times that BusinessObjects Edge Series should re-attemptcontacting an SAP system to fulfill authentication requests. Setting




40/170

the value to -1 allows BusinessObjects Edge Series to attempt tocontact the entitlement system an unlimited number of times beforeceasing. Setting the value to 0 limits BusinessObjects Edge Series tomaking one attempt to contact the entitlement system.

In the "Keep entitlement system disabled [seconds]" field, type thenumber of seconds that BusinessObjects Edge Series should waitbefore resuming attempts to authenticate users against the SAPsystem.

For example, if you type 3 for "Max failed entitlement systemaccesses", BusinessObjects Edge Series allows a maximum of 3 failedattempts to authenticate users against any particular SAP system; thefourth failed attempt results in BusinessObjects Edge Series ceasingits 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 connection you want to keep opento your SAP system at the same time. For example, if you type 2 inthis field, BusinessObjects Edge Series keeps two separateconnections 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 hasbeen 3 logons on one connection, BusinessObjects Edge Series willclose that connection and restart it.

Content folder root

Use this field to specify where you want BusinessObjects Edge Seriesto begin replicating the BW folder structure in the CMC and InfoView.The default is 2.0 but you can change it to a different folder if you want.

To change this value, you must change it both in the CMC and theContent Administration Workbench. For details, see To change theContent folder root on page 41.

Automatically import users




41/170

Select this check box if you want BusinessObjects Edge Series tocreate user accounts and user folders for all role members when youactually import the roles. Clear the check box to have BusinessObjectsEdge Series create user accounts and user folders dynamically, whenusers 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 useconcurrent user licenses or named user licenses.

Concurrent licenses specify the number of people who can connectto BusinessObjects Edge Series at the same time. This type of licensing is very flexible because a small number of concurrent licensescan support a large user base. For example, depending on how oftenand how long users access BusinessObjects Edge Series, a 100 user concurrent license could support 250, 500, or 700 users. Named user licenses are associated with specific users and allow people to accessthe system based on their user name and password. This providesnamed users with access to the system regardless of how many other people are connected.

Note that the option you select here does not change the number or type of user licenses that you have installed in BusinessObjects EdgeSeries. You must have the appropriate licenses available on your system.

Default systemIn this list, select the SAP entitlement system that BusinessObjectsEdge Series uses as the default (that is, the system that is contactedto authenticate users who attempt to log on with SAP credentials butwithout specifying a particular SAP system). If this list is empty, seeTo add an SAP entitlement system to BusinessObjects Edge Serieson page 36.

4. Click Update .

To change the Content folder root

1. Go to the Authentication management area of the CMC.2. Click the SAP tab.




42/170


43/170

Enterprise administrators configure the BusinessObjects Edge Seriessystem for publishing content from SAP. They import the appropriateroles, create necessary folders, and assign rights to those roles andfolders in BusinessObjects Edge Series.

Content publishers

Content publishers are those users who have rights to publish contentinto roles. The purpose of this category of user is to separate regular rolemembers 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 haveView, View on Demand, and Schedule rights for any reports published

to the roles they are members of. However, regular role members cannotpublish new content, nor can they publish updated versions of content.

You must import all content publishing and all content bearing roles toBusinessObjects Edge Series prior to publishing for the first time.

Note: 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 isbetter practice to publish only from content publisher roles. Additionally, thefunction of content publishing roles is only to define which users can publishcontent. Thus, content publishing roles should not contain any content;

content publishers should publish to content bearing roles that are accessibleto regular role members.

To import a role to BusinessObjects Edge Series

1. Go to the Authentication management area of the CMC.2. Click the SAP tab.3. On the Options tab, select or clear the Automatically import users

check box, depending on how you want BusinessObjects Edge Series tohandle user accounts when you import roles: Select the check box to have BusinessObjects Edge Series create a

user account and a user folder immediately for each member of therole(s) that you import

When you later add members to a role within SAP, BusinessObjectsEdge Series dynamically creates additional user accounts and user


3Configuring SAP authenticationImporting SAP roles to BusinessObjects Edge Series


44/170

folders when new role members first log on to BusinessObjects EdgeSeries with valid SAP credentials.

Clear the check box to have BusinessObjects Edge Series import

roles without immediately creating user accounts and user folders.BusinessObjects Edge Series dynamically creates new user accountsand user folders when role members first log on to BusinessObjectsEdge Series with valid SAP credentials.

Once user accounts and user folders are created, you can subsequentlyview them in the Users and Folders management areas of the CMC.

4. On the Options tab, select either Concurrent users or Named usersdepending on your licenses.

5. Note that the option you select here does not change the number or typeof user licenses that you have installed in BusinessObjects Edge Series.You must have the appropriate licenses available on your system.

6. Click Update .7. On the Role import tab, select the appropriate entitlement system from

the Logical system name list.

Note: If this list is empty, see Connecting to SAP entitlement systemson page 36.

8. In the Available roles area, select the role(s) that you want to import,

and then click Add .9. Click Update .

Related Topics Setting SAP Authentication options on page 38

To check that roles and users were imported correctly

1. Ensure that you know the user name and password of an SAP user who

belongs to one of the roles that you just mapped to BusinessObjects EdgeSeries.

2. Go to theBusinessObjects Edge Series InfoView:

http://webserver/businessobjects/enterprise115/sap/infoview

- OR -


Configuring SAP authentication3 Importing SAP roles to BusinessObjects Edge Series


45/170

http://webserver:port/businessobjects/enterprise115/sap/desktoplaunch

3. Click Log On .4. Type the user name and password of a mapped user.5. From the Authentication Type list, select SAP .6. Click Log On .

You should be logged on to the InfoView as the selected user.

Integrating with Secure NetworkCommunication

BusinessObjects Edge Series Integration for SAP Solutions supportsenvironments that implement Secure Network Communication (SNC) for authentication and/or for data encryption between SAP components. If youhave deployed the SAP Cryptographic Library (or another external securityproduct that uses the SNC interface) you must set some additional valuesto integrate BusinessObjects Edge Series effectively within your securedenvironment.

To configure BusinessObjects Edge Series to use your secure networkcommunication, you must complete the following tasks:

1. Configure BusinessObjects Edge Series servers to start and run under an appropriate user account.

2. Configure the SAP system to trust your BusinessObjects Edge Seriessystem.

3. Configure the SNC settings in the Central Management Console of BusinessObjects Edge Series.

4. Import SAP roles and users into BusinessObjects Edge Series.

Configuring BusinessObjects Edge Series servers torun under an SNC account

For SNC to work correctly, the BusinessObjects Edge Series servers mustbe running under the account that has been set up for SNC. The servers


3Configuring SAP authenticationIntegrating with Secure Network Communication


46/170

that need to run under this account depend on whether you are using Javaor .NET.

Java Central Management Server (CMS)

Crystal Reports Page Server

Crystal Reports Job Server

Web Application Server

.NET

Central Management Server (CMS)

Crystal Reports Page Server

Crystal Reports Job Server

.NET Servers

Deploying on either .NET or Java

1. Launch Central Configuration Manager.2. Right-click the Central Management Server and click Stop .

3. Right-click the Central Management Server again and click Properties .The Central Management Server Properties dialog box opens.

4. On the Properties tab, ensure that the User and Password provided under Log On As is the correct SNC account.

5. Repeat steps 1 through 4 for the Crystal Reports Page Server, Job Server,and Web Application Server in the case of a Java deployment.

Deploying on .NET

1. Go to Computer Management > System Tools > Local Users andGroups > IIS Worker Process Group .

2. Add the account credentials to this group.3. Go to Computer Management > Services and Applications > Internet

Information Services > > Application Pools .


Configuring SAP authentication3 Integrating with Secure Network Communication


47/170

4. Right-click DefaultAppPool and click Properties .5. On the Identity tab, click Configurable .6. Fill in the User name and Password fields with the correct account

credentials.7. Start the DCOM configuration utility by typing dcomcnfg.exe in the

command line.8. Expand Component Services until you see a folder called DCOM Config.9. Right-click RingleaderManager and then click Properties .

10. On the Security tab, click Edit and grant Launch and Access permissionsto the SNC account.

11. If BusinessObjects Edge Series is running on Windows 2003, repeatsteps 9 and 10 for the OlapSessions.

12. Restart the WWW service.

Deploying on Java

1. Stop your web application server.2. Configure the web application server to start under the correct account.

For specific instructions on performing this configuration, refer to your specificweb application server's documentation.

Configuring the SAP system to trust theBusinessObjects Edge Series system

Now that all the servers are configured to start and run under an accountthat has been set up for SNC, you must configure your SAP system to trustyour BusinessObjects Edge Series system.

To configure SAP to trust BusinessObjects Edge Series, you must add asystem ID to the SNC Access Control list in SAP BW and you must associatethe entitlement user to SNC.

To add a system ID to the SNC Access Control list

1. Log on to your SAP BW system and execute the transaction SNC0 .




48/170

The Change View "SNC: Access Control List (ACL) for Systems:Overview" screen opens.

2. Click the New Entries button on the toolbar.

The New Entries: Details of Added Entries screen opens.

3. Type the name of your BusinessObjects Edge Series machine in theSystem ID field.

4. Type p: in the SNC name field where SNC USERACCOUNTrepresents the account you used when configuring theBusinessObjects Edge Series servers.

Note: Use uppercase letters when indicating the SNC USER ACCOUNT.You must include the domain name when specifying the user account.For example: domain\username.

5. Select Entry for RFC activated and Entry for ext. ID activated .6. Clear all other options and click Save .

To associate the entitlement user to a SNC

1. Log on to your SAP BW system and execute the transaction SU01 .

The User Maintenance: Initial Screen opens.

2. In the User field, type the name of the SAP account designated as theentitlement user and then click the Change button on the toolbar.

The Maintain User screen opens.

3. Click the SNC tab.4. In the SNC name field, type the SNC USER ACCOUNTyou entered in step

4 above.5. Click the Save button.

Configuring the SNC settings in the CentralManagement Console

Now you must set up the SNC setting in BusinessObjects Edge Series.

To configure the SNC settings:




49/170

1. Add a new entitlement system as outlined in the section Connecting toSAP entitlement systems on page 36.

2. Click the SNC settings tab on the SAP Authentication page.

3. Select the Logical system name based on the entitlement system youadded in step 1.4. Select Enable Secure Network Communication (SNC) under Basic

Settings.5. Select Authentication under Quality of Protection.6. Enter the SNC name of the SAP system under Mutual authentication

settings.

The SNC name must be formatted asp:\ADM.

For example, if the sap server domain is sapdomain and the systemid isP33, the SNC name is p:sapdomain\P33ADM.

7. Leave the SNC name of Enterprise system field blank and click Update .8. Click the Entitlement systems tab.9. There is now another field under the Language field called SNC name .

10. In the SNC name field, type the SNC name that you configured on theSAP BW server. This is the name you configured in the section,Configuring the SAP system to trust the BusinessObjects Edge Seriessystem on page 47.




50/170




51/170

Configuring Data Access

4


52/170

This section guides you through the process of configuring data access.

Processing scheduled reports in SAP'sbatch modeYou can run scheduled reports in BusinessObjects Edge Series using SAP'sbatch mode. The InfoSet and Open SQL drivers can run reports using SAP'sbatch or background mode when specific environment variables are set to1. The relevant environment variables are:

CRYSTAL_INFOSET_FORCE_BATCH_MODE (for the InfoSet driver)

CRYSTAL_OPENSQL_FORCE_BATCH_MODE (for the Open SQL driver)

However, it is recommended that you use this feature only when you havea distributed installation of BusinessObjects Edge Series. When theseenvironment variables are set to 1, the drivers run reports using SAP's batchmode, regardless of the reporting component that is actually running thereport. Therefore, if you create these environment variables as systemenvironment variables on a machine that is running a combination of BusinessObjects Edge Series servers, the drivers run all reports in batchmode (including on-demand report requests from the Page Server and theReport Application Server).

To ensure that the drivers run only your scheduled reports in batch mode(i.e., reports run by the Report Job Server), avoid setting system environmentvariables on machines running combinations of BusinessObjects Edge Seriesservers. Instead, follow these steps to customize the environment variablesfor each Report Job Server.

Note: SAP users who schedule reports in BusinessObjects Edge Seriesmay require additional authorizations in SAP. For details, see Creating and applying authorizations on page 33 and Scheduling a report in batch mode(with an Open SQL query) on page 156.

To process scheduled reports in SAP's batch mode

1. Create a batch script (.bat file) in a text editor such as Notepad, with thefollowing contents:@echo offset CRYSTAL_INFOSET_FORCE_BATCH_MODE=1


Configuring Data Access4 Processing scheduled reports in SAP's batch mode


53/170

set CRYSTAL_OPENSQL_FORCE_BATCH_MODE=1%*

This script sets the environment variables to 1, and then executes anyparameters passed to the script from the command line.

2. Save the file as jobserver_batchmode.bat to a folder on each ReportJob Server machine.

3. Start the Central Configuration Manager (CCM).4. Right-click the Crystal Report Job Server and, on the shortcut menu,

click Stop .5. Right-click the Crystal Report Job Server and, on the shortcut menu,

click Properties .6. On the Properties tab, locate the Command field.

This is the startup command for the Report Job Server. For instance, thecommand might look like this (a single line):

"\\SERVER01\C$\Program Files\Business Objects\BusinessObjectsEnterprise 11\win32_x86\JobServer.exe" -service -name

SERVER01.report -ns SERVER01 -objectType BusinessObjectsEnterprise.Report -lib procReport -restart

7. Precede the default command with the full path to the jobserver_batchmode.bat file that you saved on the Report Job Server machine.

In this example, the batch file is saved on a machine named SERVER01

as:C:\Crystal Scripts\jobserver_batchmode.bat

Therefore, the new startup command for the Report Job Server is:

"\\SERVER01\C$\Crystal Scripts\jobserver_batchmode.bat""\\SERVER01\C$\Program Files\Business Objects\BusinessObjects

Enterprise 11\win32_x86\JobServer.exe" -service -nameSERVER01.report -ns SERVER01 -objectType BusinessObjectsEnterprise.Report -lib procReport -restart

This new startup command launches the batch file first. The batch file inturn sets the required environment variables before executing the original

startup command for the Report Job Server. This ensures that theenvironment variables available to the Report Job Server differ from theenvironment variables available to servers responsible for on-demandreporting (the Page Server and Report Application Server).

8. Once you have changed the Command field in the CCM, click OK .


4Configuring Data AccessProcessing scheduled reports in SAP's batch mode


54/170

9. Right-click the Crystal Report Job Server and, on the shortcut menu,click Start .

Note: If the Report Job Server fails to start, verify your new startup

command.10. On the CCM toolbar, click Enable/Disable Servers , log on with your

BusinessObjects Edge Series administrator credentials, and ensure thatthe Report Job Server is enabled.

Configuring SAP Logon for the DataAccess Kit

When users report off of data in SAP tables using Crystal Reports and theData Access Kit, they are first prompted to select their SAP system from the"Available SAP Systems" list. The Data Access Kit retrieves this list of available systems from the saplogon.ini file in the Windows directory onthat user's computer.

If users have the SAPGUI installed, adding a new SAP system to their SAPGUI logon adds information about this system to their saplogon.inifile. After the new SAP system is added, it becomes available via the DataAccess Kit (provided they are authorized to use the system). Alternately, youmay configure and distribute SAPlogon.ini using your standard procedures.

Consult your SAP documentation for details.


Configuring Data Access4 Configuring SAP Logon for the Data Access Kit


55/170

Reporting withBusinessObjects EdgeSeries Integration for SAPSolutions

5


56/170

This section describes the key features provided by BusinessObjects EdgeSeries Integration for SAP Solutions.

Reporting off BW queries, InfoSets,Operational Data Stores, and MDX cubes

BusinessObjects Edge Series Integration for SAP Solutions providesconnectivity to your SAP data through four database driversthe BW Querydriver, the InfoSet driver, the ODS driver, and the MDX driver:

The BW Query driver is integrated directly within the Crystal Reportsinterface. The "SAP Tools" toolbar works with the BW Query driver toallow you to report off your BW queries from within Crystal Reports. Thetoolbar also allows you to save reports to BW and publish them directlyto BusinessObjects Edge Series.

The InfoSet driver provides Crystal Reports with another means of accessing SAP data sources: this driver can access InfoSets (also knownas Functional Areas) and ABAP Queries. You access this driver throughthe Data Explorer in Crystal Reports.

The Operational Data Store (ODS) driver allows you to use existing ODSobjects from your BW Data Warehouse as a data source in CrystalReports. As with the BW Query driver, the ODS driver is integrated directly

into Crystal Reports through the SAP Tools toolbar. The SAP BW MDX Query driver introduces new flexibility when reporting

off BW cubes and queries. By writing reports with the MDX Query driver,you gain direct access to BW cubes.

One advantage of these drivers is that they allow business users to reportoff predefined views of your SAP data. Tables and fields are first logicallygrouped by an SAP content expert into queries, InfoSets, and so on. Youthen make these data sources accessible to users who are designing reportswith Crystal Reports.

These same four drivers are also included in the add-ons for BusinessObjectsEdge Series (the Data Access feature), so the BusinessObjects Edge Seriesprocessing servers can successfully run the reports you design against your SAP systems.


Reporting with BusinessObjects Edge Series Integration for SAP Solutions5 Reporting off BW queries, InfoSets, Operational Data Stores, and MDX cubes


57/170


58/170

Publishing from BW to BusinessObjectsEdge Series

The BW Publisher allows you to publish Crystal reports (.rpt files) individuallyor in batches from BW to BusinessObjects Edge Series.

Reports are published from BW to BusinessObjects Edge Series in severalways: users who design Crystal reports can simultaneously save reports totheir roles in BW and publish them to BusinessObjects Edge Series, providedthey have sufficient rights. Users with the appropriate rights within BW andBusinessObjects Edge Series can also publish reports individually or inbatches using the Content Administration Workbench. See Publishing reportsusing the Content Administration Workbench on page 86.

Details of the publishing process depend upon the publisher configurationthat you select.

Selecting your BW Publisher configuration

You can configure the BW Publisher in either ways:

Install the BW Publisher as a service on a BusinessObjects Edge Seriesmachine. The BW Publisher service will start instances of the BWPublisher as required.

Install a local SAP Gateway to create BW Publisher instances.

Select the configuration method based on the requirements of your site, after considering the advantages and disadvantages of each configuration.

BW Publisher service

Advantages

It is simpler to install than a local SAP Gateway

It is scalable because new publisher instances are created automaticallyin response to increased publishing load.

Disadvantages


Reporting with BusinessObjects Edge Series Integration for SAP Solutions5 Publishing from BW to BusinessObjects Edge Series


59/170

It is more difficult to administer than a local SAP Gateway becausechanges to the BW Publisher service require you to edit the registry.

It makes less efficient use of computing resources than a local SAP

Gateway because Publisher Instances are not stopped automaticallywhen they are no longer needed.

Local SAP Gateway

Advantages

It uses system resources more efficiently than a BW Publisher servicefor Windows installations of BusinessObjects Edge Series.

Disadvantages

It is more complex to install and configure than the BW Publisher service.

Note: For LINUX installations of BusinessObjects Edge Series, install BWPublisher as a service.

For LINUX installations of BusinessObjects Edge Series, follow theinstructions for installing the BW Publisher as a service. However, your system configuration will vary slightly as you must manually start the requirednumber of BW Publisher instances.

Publishing Reports

Whether you choose to configure the BW Publisher service with or withouta 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 configuredto connect to this BW Publisher. The TCP/IP destination provides BW withthe name and port number of the SAP Gateway that the BW Publisher isregistered with.

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

The appropriate Crystal report file(s), with any required translated reportstrings.


5Reporting with BusinessObjects Edge Series Integration for SAP SolutionsPublishing from BW to BusinessObjects Edge Series


60/170

Tip: For more on translated reports, see the BusinessObjects Edge SeriesIntegration for SAP Solutions. This series is included in the docs directoryon the installation CD and is also installed on the computer thatBusinessObjects Edge Series Integration for SAP Solutions is installedon. If you installed to the default path, the location is C:\ProgramFiles\Business Objects\Integration Kit for SAP 11.5\docs.

A publishing command, if you are not using a local SAP Gateway.

The name of the appropriate Central Management Server (CMS).

The SAP Gateway responds by executing the publishing command, therebyinvoking the BW Publisher. The BW Publisher logs on to the specified CMSas the user, and checks to see if the user has the appropriate permissionsin BusinessObjects Edge Series 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 authenticationin BusinessObjects Edge Series, define a folder structure for your content,and import SAP roles. See Configuring SAP authentication for BusinessObjects Edge Series on page 33 for complete instructions.

The main difference between the two configuration types is that if you do notinstall a local SAP Gateway, the BW Publisher service registers as a server program with the SAP Gateway running on your application host, using thename you specify as its Program ID string. This SAP Gateway may beinstalled on your single BW server, or on your central instance of BW if youhave a BW cluster. Also, in this case, BW sends a publishing command tothe BW Publisher which does not occur if a local SAP Gateway is installed.

Distributing information over the WebThe Web Content feature includes the BusinessObjects Edge Series InfoViewfor SAP, which is a customized edition of the standard BusinessObjects EdgeSeries InfoView (InfoView). These new features are designed especially for

SAP users: Users whose roles you import can log on to the BusinessObjects Edge

Series InfoView for SAP with their usual SAP credentials.

Users can browse a hierarchy of "My Groups" folders that correspond tothe structure of the imported roles whose content you publish from BW


Reporting with BusinessObjects Edge Series Integration for SAP Solutions5 Distributing information over the Web


61/170

to BusinessObjects Edge Series. In these folders, users can locate, view,and refresh Crystal reports that have been saved in their BW roles.

Users can schedule translated reports in specific languages and viewreport titles and on-demand reports in their usual logon language.

Tip: These features require that you translate the reports within BW,before you publish the reports to BusinessObjects Edge Series. For moreinformation, see the BusinessObjects Edge Series Integration for SAPSolutions. This series is included in the docs directory on the installationCD and is also installed on the computer that BusinessObjects EdgeSeries Integration for SAP Solutions is installed on. If you installed to thedefault path, the location is C:\Program Files\Business Objects\IntegrationKit for SAP 11.5\docs.

Administrators can divide report processing by language across server groups. This ensures that reports created or translated in a specificlanguage are always processed by servers that can handle data in thatlanguage.

After installing the Web Content, see Setting up the sample reports onpage 99.

With BusinessObjects Edge Series Integration for SAP Solutions you receiveall of the functionality provided with it. (See Reporting with BusinessObjectsEdge Series Integration for SAP Solutions on page 55 for details.) In addition,you are able to report off of a variety of other SAP data sources from withinCrystal Reports, and BusinessObjects Edge Series.

Reporting off other SAP data sourcesIn addition to the components provided with your product distribution, youcan download the Open SQL driver which allows you to report off additionalSAP data sources from within Crystal Reports and BusinessObjects EdgeSeries.

Reporting off tables, views, clusters, and functions

The Open SQL driver is the most powerful of the drivers due to the flexibilityit provides for accessing data in SAP. This flexibility, however, results in ahigher level of complexity than with the InfoSet driver.


5Reporting with BusinessObjects Edge Series Integration for SAP SolutionsReporting off other SAP data sources


62/170


63/170

Integrating BusinessObjectsEdge Series and BW

6


64/170

This section shows how to configure BW to enable and administer reportpublishing from BW to BusinessObjects Edge Series. It also includesinstructions for configuring the http request handler in SAP.

Click the appropriate link to jump to that section:

Configuration overview on page 64

Setting up folders and security in BusinessObjects Edge Series onpage 64

Configuring the BW Publisher on page 69

Configuring publishing in the Content Administration Workbench onpage 79

Configuring the SAP http request handler on page 95

Configuration overviewThis section outlines the configuration steps needed to integrate BW andBusinessObjects Edge Series:

Setting up folders and security in BusinessObjects Edge Series onpage 64

Configuring the BW Publisher on page 69

Configuring the BW Publisher as a service on page 70 Configuring the BW Publisher with a local SAP Gateway on page 76

Configuring publishing in the Content Administration Workbench onpage 79

Configuring the SAP http request handler on page 95

Before beginning this section, complete the configuration steps outlined inConfiguring SAP authentication on page 27.

Setting up folders and security inBusinessObjects Edge Series

When you define an entitlement system in BusinessObjects Edge Series,BusinessObjects Edge Series creates a logical folder structure to match your


Integrating BusinessObjects Edge Series and BW6 Configuration overview


65/170

SAP system. When you import roles and publish content to BusinessObjectsEdge Series, corresponding folders are created. You, as administrator, donot have to create these folders. They are created as a result of you definingan entitlement system in BusinessObjects Edge Series, importing roles intothe CMC, and publishing content to BusinessObjects Edge Series.

The diagram below displays the basic folder structure that is created.

Note that you, the administrator, are responsible for assigning the correctrights to these folders.

SAP top-level folder

Assign the principal Everyone to No Access for the SAP top-level folder.

System folders

Assign the principal Publisher Advanced rights in the CMC. Assign thefollowing advanced rights.

Add objects to folder

View objects

Edit objects

Modify the rights users have to objects

Delete objects

Delete instances Copy objects to another folder


6Integrating BusinessObjects Edge Series and BWSetting up folders and security in BusinessObjects Edge Series


66/170

To assign publishing rights to a system folder

1. In the system folder you created, click the Rights tab.2. Click Add/Remove .

The Add/Remove page appears.

3. In the Select Operation list, select Add/Remove Groups .4. In the Available groups list, select the group(s) that corresponds to the

imported content publishing role(s) whose rights you want to specify.5. Click the > arrow to grant the group access to this folder; then click OK .

You are returned to the Rights tab.

6. Click the group's Access Level list and select Advanced .

The Advanced Rights page appears.

7. In the Explicitly Granted column, select the following rights: Add objects to the folder

View objects

Edit objects


Delete objects (optional)

8. Click OK .

To assign publishing rights to the group

1. From the home page of the Central Management Console, click Groups .2. Click the Rights button on the top right side of the screen.3. Click the Add/Remove... button.

The Add/Remove page appears.

4. In the Select Operation list, select Add/Remove Groups .5. In the Available groups list, select the group(s) that corresponds to the

imported content publishing role(s) whose rights you want to specify.6. Click the > arrow to grant the group access to this folder; then click OK .


Integrating BusinessObjects Edge Series and BW6 Setting up folders and security in BusinessObjects Edge Series


67/170

You are returned to the Rights tab.

7. Click the group's Access Level list and select Advanced .

The Advanced Rights page appears.

8. In the Explicitly Granted column, select the following rights: Add objects to the folder

View objects

Edit objects


Delete objects (optional)

9. Click OK .Members of this imported role now have permission to publish contentfrom BW to BusinessObjects Edge Series. For complete details on thepredefined access levels and advanced rights, click Help to see theBusinessObjects Enterprise Administrator's Guide.

Note: After you have set up folders and security in BusinessObjects EdgeSeries, complete the tasks in Configuring the BW Publisher on page 69, andConfiguring publishing in the Content Administration Workbench on page 79.Once you have completed those tasks, you can publish content toBusinessObjects Edge Series from BW.

Continue to the next section, Understanding the default folder security patterns on page 67 for an overview of the folder structure thatBusinessObjects Edge Series creates when you publish content from BWto BusinessObjects Edge Series.

Understanding the default folder security patterns

When you publish content to BusinessObjects Edge Series from SAP,BusinessObjects Edge Series automatically creates the remaining hierarchyof roles, folders, and reports. That is, BusinessObjects Edge Series organizesyour Crystal reports in folders that are named according to the System ID,the Client number, and the name of the role.

The diagram that follows shows how BusinessObjects Edge Series organizescontent when you publish two roles from one BW system:


6Integrating BusinessObjects Edge Series and BWSetting up folders and security in BusinessObjects Edge Series


68/170

BusinessObjects Edge Series creates the top-level folders - that is, theSAP, 2.0, and system ( ) folders - when you define an entitlementsystem.

BusinessObjects Edge Series creates Role folders (imported as groupsinto BusinessObjects Edge Series) as necessary, when a role is publishedfrom BW.

BusinessObjects Edge Series creates a Content folder for each role thatcontent is published to.

Security is set on each report object, so users can view only the reportsthat belong to their roles.

The diagram below displays the basic folder structure that is created.

The administrator is responsible for assigning rights to members of differentroles. To do this, the following rights should be assigned in the ContentAdministration Workbench.


Integrating BusinessObjects Edge Series and BW6 Setting up folders and security in BusinessObjects Edge Series


69/170

Con

business objects edge install linux en

Documents