Boxi Sap Installguide En

BusinessObjects XI Integration Kit for SAP Installation GuideBusinessObjects XI Integration Kit for SAP Patents Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352. Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners. Copyright © 2004 Business Objects. All rights reserved. Trademarks Copyright Contents Chapter 1 Introduction 11 About this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Who should read this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Business Objects information resources . . . . . . . . . . . . . . . . . . . . . . . 12 Chapter 2 What’s New in the BusinessObjects XI Integration Kit for SAP 13 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Improved hierarchy reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Wildcard capabilities in the Security Definition Editor . . . . . . . . . . . . . . . . 15 Enhanced Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Certifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Chapter 3 Components and Features 17 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Crystal Reports Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 BusinessObjects Enterprise Professional . . . . . . . . . . . . . . . . . . . . . . 18 OLAP Intelligence Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Add-Ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Integrated architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Reporting with BusinessObjects XI Integration Kit for SAP . . . . . . . . . . . . 22 Reporting off BW queries and InfoSets . . . . . . . . . . . . . . . . . . . . . . . . 22 Authenticating SAP users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Publishing from BW to BusinessObjects Enterprise . . . . . . . . . . . . . . 23 Selecting your BW Publisher configuration . . . . . . . . . . . . . . . . . . 24 Publishing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 Distributing information over the Web . . . . . . . . . . . . . . . . . . . . . . . . . 26 Reporting off other SAP data sources . . . . . . . . . . . . . . . . . . . . . . . . . 27 Reporting off tables, views, clusters, and functions . . . . . . . . . . . 27 Reporting off multidimensional data in BW . . . . . . . . . . . . . . . . . . 27 BusinessObjects XI Integration Kit for SAP Installation Guide 3 . . . . . . . . . . . 33 Requirements for using the BusinessObjects XI Integration Kit for SAP Java SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 SAP Java Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Server requirements for BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . 51 Importing the transport files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 Distributing the BW Publisher installation . . . 45 BW Publisher Service . 33 SAP requirements . . . . . . . . . . . . . . . . . . . . . . . 46 Adding servers to BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Checking for conflicts . . . . . . . . . . . . . . . . . . . . 44 Separating BusinessObjects Enterprise from your web server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Installing the UNIX components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Deploying the web applications . 46 Chapter 5 Performing the initial configuration 47 Configuration overview . . 36 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Selecting which transports to import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Configuring transports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Client requirements for Crystal Reports . . . . . . . . . . . . . 52 4 BusinessObjects XI Integration Kit for SAP Installation Guide . . . . . . . . . . . . . . . . . 51 Creating and applying authorizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Distributed installation . . . . . . 33 Recommended initial installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 SAP requirements . . . . . . . . . . . 34 Installing on UNIX . . . . . . . . . . . . . . . . . . . . . . . 31 Installing on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Installing components on BusinessObjects Enterprise machines . . . 32 SAP Presentation CD requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Chapter 4 Installing BusinessObjects XI Integration Kit for SAP 29 Installation overview . 45 BW Publisher on a stand-alone SAP Gateway . . . . . . 48 Types of transports . . . . . . . . . . . . . . . . . . . . . 88 Publishing roles or reports . . . . . . . . 55 Setting SAP Authentication options . . . . . 81 Users who can access the Content Administration Workbench . . . . . . . . . . . 57 Importing SAP roles to BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . 60 Integrating with Secure Network Communication . . . . . . . . . . . . . . 88 Scheduling background publishing . . . . . . . 85 Publishing reports using the Content Administration Workbench . . . . . . 77 Configuring the BW Publisher with a local SAP Gateway . . . . . . . . . . . . . 75 Configuring a destination for the BW Publisher service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 BusinessObjects XI Integration Kit for SAP Installation Guide 5 . . . . . . . . . . . . . 65 Processing scheduled reports in SAP’s batch mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Maintaining reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Updating system information for published reports . . . . . . . . . .Contents Configuring SAP authentication for BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Connecting to SAP entitlement systems . . . . . 70 Setting up folders and security in BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . 67 Chapter 6 Integrating BusinessObjects Enterprise and BW 69 Configuration overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Configuring SAP Logon for the Data Access Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Creating a user account for BusinessObjects Enterprise . . . . . . . . . . . . . . . . . 75 Starting the BW Publisher . . . . . . . . . . . . . . . . . 82 Configuring access to the Content Administration Workbench . . . . . . . . . . . . . . . . . . . . . . . . 82 Creating roles in BW for designated content publishers . . . . . . . . . . . . 74 Configuring the BW Publisher as a service . 70 Understanding the default folder security patterns . . . . . . 53 Accessing the SAP authentication application in BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Installing a local SAP Gateway . . 80 Configuring publishing in the Content Administration Workbench . . . . . . . . . . . . . 63 Configuring Data Access . . . 79 Configuring a destination for the BW Publisher . . 83 Defining a BusinessObjects Enterprise system . . . . . . . . . . . 73 Configuring the BW Publisher . . . . . . . . . . . . . . . . . . . . .Contents Updating the status of reports . . . . . . . . . . 105 Customizing authorizations for specific tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Chapter 9 Troubleshooting 119 Troubleshooting overview . . . . . . 98 Verifying configuration options in Crystal Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Configuring the SAP http request handler . . . 121 Chapter 10 Transport Files 123 Overview . . . . . . . . . 107 Customizing authorizations for specific functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111 Defining table authorizations by group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Setting up the sample reports . . . . . . . 121 Errors when connecting to SAP . . . . . . . . . . . . . . 120 Troubleshooting BusinessObjects Enterprise . . . . 113 Securing rows using custom security exits . . . . . . . . . tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Open SQL Connectivity transport . . . . . . . . . . . . . . . . . . . . 93 Deleting reports . . 105 Choosing your table-level security model . . . . . . . . . . . . . . . . . . . . . . . . 95 Chapter 7 Working with Web Content and Sample Reports 97 BusinessObjects Enterprise InfoView . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Reports. 126 6 BusinessObjects XI Integration Kit for SAP Installation Guide . . . . . . . . . . . . . . . . . . . . . . 120 Troubleshooting your InfoSet driver installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Completing a report migration . . . . 112 Securing rows using authorization objects . . . . . . . . . . . . and functions . . . . 104 Migrating your existing security model . . . . . . . . . . . . . . . . . 120 Locating and generating log files . . . . . . . . . . . . . . . . 124 InfoSet Connectivity transport . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Applying row-level security . . . . . . . . . . 100 Chapter 8 Defining Security for the Open SQL driver 103 Security Definition Editor overview . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Logging on to an SAP server . . . . . . . . . . . . . . . 137 Exporting a report as a . . . . . . . . . . . . . . .Contents Row-level Security Definition transport . . . . . . . . . . . . . . . . . . . . . . . 126 Cluster Definition transport . . . . . . . . . . . . . . . 138 From within the BusinessObjects Enterprise InfoView for SAP . . . . . . . . . . . . . . . . . . .ivu file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 BusinessObjects XI Integration Kit for SAP Installation Guide 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Starting the Business Explorer Query Designer . . . . . . . 132 Logging on to an SAP server . 127 Crystal Content Administration Workbench transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Appendix A Authorizations 131 Authorizations overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Actions in BW . . . . . . . . . . . . . . . . . . . . . . . . . 135 Setting the location of the data source . . . . . . . . . . . . 139 Logging on to BusinessObjects Enterprise with SAP credentials 139 Viewing an SAP BW report on demand . . . . . . . . 134 Verifying the database (refreshing table definitions in a report) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Creating a new report from a query in a BW role . . . . . . . . . . . . 142 Creating a new report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140 Scheduling a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 BW Query parameter personalization transport . . . . 136 Saving a report and simultaneously publishing it to BusinessObjects Enterprise . 140 Reading dynamic picklists in report parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 From within Crystal Reports using the Open SQL driver . . . . . . . . . . . . . . . . . . . . . . . 141 Actions in R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Previewing or refreshing a report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Saving a report as an iView . . . . . . . . . . . . . . . . . . . . . 132 From within Crystal Reports . . . . . . 136 Preparing a report for translation while saving to BW . . . . . . . . . . . . . . . . . 139 Refreshing a report from the viewer . . . . . . . . . . . . . . 136 Saving a report to a BW role . . . . . . . . . . . . . . . . . . 127 Authentication Helpers transport . . . . . . . . . . . . . . . . 133 Opening an existing report from a BW role . . . . . . . . . . 142 Verifying the database (refreshing table definitions in a report) . . . 144 From within Crystal Reports using the InfoSet driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Where is the documentation? . . . . . . . . . . . . . . . . 149 Online Customer Support . . . . . . . . . . . . . . . . . . . . 146 Appendix B Business Objects Information Resources 147 Documentation and information services . . . . . . . . . 143 Verifying the database (refreshing table definitions in a report) . . . . . . . . . . . . . . 148 What’s in the documentation set? . . 145 Scheduling a report in dialog mode (with an Open SQL query) . . . . . . . . . . . . . . . . . 149 How can we support you? . . . . . . . . . . . . . 148 Documentation from the products . . . . . . . . . . . . 148 Documentation on the product CD . . . .Contents Opening or previewing an existing report . . . . . . . . . . . . . . . . . . 144 Creating a new report from an ABAP query on R/3 . . . . . . . . reporting off InfoSet 143 Logging on to an SAP server . . . . . . . . . . . . . . 144 Logging on to an SAP server . . . . . . . . . . . . . . . . 145 Scheduling a report in batch mode (with an Open SQL query) . . . . . . . . . . . . . . . . . . . . . . . . . . 143 From within Crystal Reports using the InfoSet driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Setting the location of the data source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Crystal entitlement system . . 150 8 BusinessObjects XI Integration Kit for SAP Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Documentation on the web . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Setting the location of the data source . . . . . . . . . . . . . . . . . . . . . . 144 Verifying the database (refreshing table definitions in a report) . 143 Creating a new report from an InfoSet on R/3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . consulting and training . . . . . . . . . . . . . . . . . . . . . . . . . reporting off an ABAP query . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Send us your feedback . . . . . . . . . 142 Setting the location of the data source . . . . 148 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 145 From within BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 149 Customer support. 149 Looking for the best deployment solution for your company? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Looking for training options? . . . . . . . . . . . . . . . 150 Index 153 BusinessObjects XI Integration Kit for SAP Installation Guide 9 . . . 150 Useful addresses at a glance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents 10 BusinessObjects XI Integration Kit for SAP Installation Guide . BusinessObjects XI Integration Kit for SAP User’s Guide Introduction chapter . with links to online resources. ABAP queries.pdf). For details on installing the BusinessObjects XI Integration Kit for SAP. located in the docs directory of the BusinessObjects XI Integration Kit for SAP CD. It also shows how to publish and view these reports in a BusinessObjects Enterprise environment. you can organize. scheduling. The Integration Kit provides the database drivers and other features for reporting off SAP. with the Business Explorer (BEx) Query Designer. Who should read this guide This guide is intended for SAP users who want to use the power of Crystal Reports and OLAP Intelligence to design professional reports based on their SAP data. 12 BusinessObjects XI Integration Kit for SAP User’s Guide . see Appendix B: Business Objects Information Resources. and share your SAP data. The BusinessObjects XI Integration Kit for SAP consists of several main components: Crystal Reports is the report-design tool that allows you to report off your SAP data. and SAP Authentication enables Single Sign On between your SAP system and BusinessObjects Enterprise. with the ability to extract the business intelligence contained within your SAP systems. but not required. and distributing reports over the Web. format. see the BusinessObjects XI Integration Kit for SAP Installation Guide (installguide.1 Introduction About this guide About this guide The BusinessObjects XI Integration Kit for SAP provides you. Business Objects information resources For more information and assistance. By generating Crystal and OLAP reports from SAP BW queries. training. Familiarity with your InfoProviders (BW queries. and InfoSets. and with your standard translation workflow is beneficial. and consulting services. and OLAP Intelligence allows you to analyze and report off the multidimensional data that is stored in the Info Cubes of your SAP Business Information Warehouse. BusinessObjects Enterprise provides the framework for managing. the SAP user. InfoSets. This guide documents the SAP report-design features that are available once you install the kit on top of Crystal Reports or OLAP Intelligence. This appendix describes the Business Objects documentation. customer support. BusinessObjects InfoView for SAP allows you to share your reports over the Web. and so on). What’s New in the BusinessObjects XI Integration Kit for SAP chapter . 2 What’s New in the BusinessObjects XI Integration Kit for SAP Introduction Introduction BusinessObjects XI Integration Kit for SAP extends the robust information infrastructure provided by Crystal Enterprise 10 SAP Edition. BusinessObjects XI Integration Kit for SAP provides support for specific BusinessObjects products and delivers improvements in the areas of usability, implementation, and administration. This chapter’s focus is to provide a high level overview of the key new features and enhancements that are specific to BusinessObjects XI Integration Kit for SAP. For more information on what’s new in Crystal Reports XI, see the “What’s New in Crystal Reports XI” chapter of the Crystal Reports User’s Guide. For more information on what’s new in BusinessObjects Enterprise XI, see the “What’s New in BusinessObjects Enterprise” chapter of the BusinessObjects Enterprise Administrator’s Guide. Note: This feature list provides a general overview of key new features in BusinessObjects XI Integration Kit for SAP. It is not intended to provide an exhaustive list of all of the new features found within BusinessObjects XI Integration Kit for SAP. Improved hierarchy reporting Hierarchy reporting has been improved with Crystal Reports XI enhanced hierarchical grouping capabilities. Crystal Reports is now able to determine each group’s parent and children, and at the same time update hierarchical summaries. You also have increased layout control because groups are now nested in a hierarchy, and you have more fine-grained control over hierarchy indenting. You can indent specific objects in a section according to their hierarchy level, instead of automatically indenting all objects in the hierarchy. There is no need for extra formulas. Crystal Reports is able to import and understand your BW hierarchy. 14 BusinessObjects XI Integration Kit for SAP User’s Guide What’s New in the BusinessObjects XI Integration Kit for SAP Wildcard capabilities in the Security Definition Editor 2 Wildcard capabilities in the Security Definition Editor When setting record level security in the Security Definition Editor, you can now apply an authorization object to multiple tables simultaneously. By using wildcards when specifying the table name, you can apply the same authorization object to many tables if they have similar names. Previously, authorization objects had to be applied to one table at a time because wildcards could not be used. This feature allows for more efficiency when setting record level security. Enhanced Platform Support The BusinessObjects XI Integration Kit for SAP supports SAP Netweaver 04 which consists of the following: • • • BW 3.5 WAS 640 J2EE engine for the Java Application Server SAP Enterprise Portal 6 For a complete listing of supported platforms, refer to the platforms.txt file included with your product CD. Certifications BusinessObjects is the most highly certified partner of SAP. The BusinessObjects XI Integration Kit for SAP holds the following certifications: • • • SAP Enterprise Portals Certification OLAP BAPI Certification J2EE Certification For more information about BusinessObjects certifications, refer to the SAP web site at http://www11.sap.com/partners/. Search under Global & Local Partner Directories -- Software Partner and Product Directory. BusinessObjects XI Integration Kit for SAP User’s Guide 15 2 What’s New in the BusinessObjects XI Integration Kit for SAP Certifications 16 BusinessObjects XI Integration Kit for SAP User’s Guide Components and Features chapter . OLAP Intelligence is the report-design tool that allows you to create reports off multidimensional data and save those report directly to BusinessObjects Enterprise. BusinessObjects Enterprise Professional Your BusinessObjects Enterprise product distribution contains the setup program and core product documentation for BusinessObjects Enterprise Professional.3 Components and Features Overview Overview BusinessObjects XI Integration Kit for SAP provides you with powerful reportdesign tools and a framework for managing. scheduling. and renders Crystal reports for viewing over the Web. Crystal Reports is the report-design tool that allows you to create reports off virtually any data source and save those reports directly to BusinessObjects Enterprise. BusinessObjects Enterprise is the server-based system that manages. As such. it enables you to extract value from your SAP Business Information Warehouse (BW) and R/3 data and share it with users across the enterprise. schedules. OLAP Intelligence Professional Your OLAP Intelligence Professional product distribution contains the setup program and core product documentation for OLAP Intelligence Professional. 18 BusinessObjects XI Integration Kit for SAP Installation Guide . Crystal Reports Professional Your Crystal Reports product distribution contains the setup program and core product documentation for Crystal Reports Professional. BusinessObjects XI Integration Kit for SAP includes two major products— BusinessObjects Enterprise Professional and Crystal Reports Professional— along with add-on components that integrate the Crystal reporting technologies with your existing SAP systems. and distributing your Crystal reports over the Web. and the BW OLAP Kit. which serves to complement the core product documentation included with OLAP Intelligence. It allows you to log on to BW and work with its data sources. the Open SQL Driver. see the BusinessObjects XI Integration Kit for SAP User’s Guide. Crystal Reports and BusinessObjects Enterprise. and must therefore be installed atop Crystal Reports or OLAP Intelligence and BusinessObjects Enterprise. thereby providing Single Sign On to your SAP users. It also enables BusinessObjects Enterprise to authenticate users against the SAP system. see “Reporting off BW queries and InfoSets” on page 22 and “Reporting off other SAP data sources” on page 27. once SAP users are logged on to the SAP system. The database drivers and kits are used by the report engine. For details. The setup program determines which Business Objects products are already installed. • SAP Authentication This component allows you to map your existing SAP roles and users to BusinessObjects Enterprise.Components and Features Overview 3 Add-Ons The Add-Ons distribution contains the setup program and additional documentation for the components that integrate Crystal Reports. The BW Query driver. the InfoSet driver. and BusinessObjects Enterprise with your SAP system. • Documentation The setup program installs all BusinessObjects XI Integration Kit for SAP documentation. OLAP Intelligence. see “Authenticating SAP users” on page 23. the “SAP Tools” toolbar facilitates tasks associated with reporting off BW queries. The add-on components are: • Data Access This component provides database drivers that are designed specifically for reporting off SAP data. save reports to BW. For details. For details on using the toolbar. and then installs the add-on components as required. they are recognized by BusinessObjects Enterprise as authenticated users. • Crystal Reports SAP Toolbar Integrated within Crystal Reports. and publish reports immediately to BusinessObjects Enterprise. As a result. BusinessObjects XI Integration Kit for SAP Installation Guide 19 . • BW Content Administration Workbench The Content Administration Workbench allows you to administer report publishing functionality from within BW. • Transport files The transport files are included in the transports directory of the installation CD. see “Publishing from BW to BusinessObjects Enterprise” on page 23. and thumbnail views inside SAP Enterprise Portal. see “Configuring transports” on page 48. For details. These iViews demonstrate sample functionality for alerts. see “Distributing information over the Web” on page 26. see the “Managing the SAP Enterprise Portal” section of the BusinessObjects XI Integration Kit for SAP User's Guide. For details. 20 BusinessObjects XI Integration Kit for SAP Installation Guide . Sample iViews Sample iViews illustrate how BusinessObjects Enterprise SAP Edition can be implemented with SAP Enterprise Portal version 6. For details. You must import these transports and configure a number of authorization objects in order for users to connect to SAP through Crystal Reports and BusinessObjects Enterprise. This InfoView allows users to organize and view their Crystal reports in multiple languages over the Web. • • Sample Reports The sample reports demonstrate a variety of ways in which you can extract value from SAP data using different database drivers. • Web Content This optional component includes the BusinessObjects Enterprise InfoView for SAP. You can identify roles in your BW system with particular BusinessObjects Enterprise systems. For details. publish reports. report folders. and synchronize reports between BW and a BusinessObjects Enterprise system.3 Components and Features Overview • BW Publisher This component allows you to publish reports individually or in batches from BW to BusinessObjects Enterprise. BusinessObjects XI Integration Kit for SAP Installation Guide 21 .Components and Features Overview 3 Integrated architecture The following diagram illustrates how each of the BusinessObjects XI Integration Kit for SAP components expands upon the multi-tier framework of BusinessObjects Enterprise. and the general tasks that each component performs. This guide is included in the docs directory on the installation CD and is also 22 BusinessObjects XI Integration Kit for SAP Installation Guide . These same two drivers are also included in the add-ons for BusinessObjects Enterprise (the Data Access feature). The toolbar also allows you to save reports to BW and publish them directly to BusinessObjects Enterprise. The InfoSet driver provides Crystal Reports with another means of accessing SAP data sources: this driver can access InfoSets (also known as Functional Areas) and ABAP Queries. One advantage of these drivers is that they allow business users to report off predefined views of your SAP data. you must install the InfoSet Connectivity transport file on the SAP system. You then make these data sources accessible to users who are designing reports with Crystal Reports. Reporting with BusinessObjects XI Integration Kit for SAP This section describes the key features provided by BusinessObjects XI Integration Kit for SAP. You access this driver through the Data Explorer in Crystal Reports. so the BusinessObjects Enterprise processing servers can successfully run the reports you design against your SAP systems. The “SAP Tools” toolbar works with the BW Query driver to allow you to report off your BW queries from within Crystal Reports. For instruction on creating Crystal reports with these drivers. its components.3 Components and Features Reporting with BusinessObjects XI Integration Kit for SAP If you are new to BusinessObjects Enterprise. see its documentation for a more detailed explanation of the framework. consult the BusinessObjects XI Integration Kit for SAP User’s Guide (userguide. and so on. Tables and fields are first logically grouped by an SAP content expert into queries. Reporting off BW queries and InfoSets BusinessObjects XI Integration Kit for SAP provides connectivity to your SAP data through two database drivers—the BW Query driver and the InfoSet driver: • • The BW Query driver is integrated directly within the Crystal Reports interface. For more information. see “Configuring transports” on page 48.pdf). Note: Before you can design or process reports with the InfoSet driver. InfoSets. you need not update or refresh the listing in BusinessObjects Enterprise. Publishing from BW to BusinessObjects Enterprise The BW Publisher allows you to publish Crystal reports (. once you map an SAP role to BusinessObjects Enterprise. Users with the appropriate rights within BW and BusinessObjects XI Integration Kit for SAP Installation Guide 23 . the location is C:\Program Files\Business Objects\Integration Kit for SAP 11\docs. all users who belong to that role can log on to BusinessObjects Enterprise.rpt files) individually or in batches from BW to BusinessObjects Enterprise. they can choose SAP Authentication and provide their usual SAP user name and password. If you installed to the default path. and it facilitates account management by allowing you to assign rights to users and groups in a consistent manner within BusinessObjects Enterprise. It facilitates account creation by allowing you to map roles from SAP to BusinessObjects Enterprise. The SAP Authentication feature includes an SAP security plug-in (secSAPR3. After installing the SAP Authentication component.Components and Features Reporting with BusinessObjects XI Integration Kit for SAP 3 installed on the computer that BusinessObjects XI Integration Kit for SAP is installed on. The SAP Authentication component includes a web application for configuring the plug-in. provided they have sufficient rights. see “Configuring SAP authentication for BusinessObjects Enterprise” on page 52. When users log on to BusinessObjects Enterprise directly.dll) for the Central Management Server (CMS) component of BusinessObjects Enterprise. Authenticating SAP users Security plug-ins expand and customize the ways in which BusinessObjects Enterprise authenticates users. So. Reports are published from BW to BusinessObjects Enterprise in several ways: users who design Crystal reports can simultaneously save reports to their roles in BW and publish them to BusinessObjects Enterprise. When you make subsequent changes to the SAP role membership. This SAP security plug-in offers several key benefits: • • • It acts as an authentication provider that verifies user credentials against your SAP system on behalf of the CMS. This application is displayed as an additional tab within the Central Management Console (CMC). BusinessObjects Enterprise can also be configured to automatically and seamlessly recognize SAP users who have already been authenticated by your SAP system. It dynamically maintains SAP role listings. Install a local SAP Gateway to create BW Publisher instances. On UNIX.3 Components and Features Reporting with BusinessObjects XI Integration Kit for SAP BusinessObjects Enterprise can also publish reports individually or in batches using the Content Administration Workbench. The BW Publisher service will start instances of the BW Publisher as required. after considering the advantages and disadvantages of each configuration. Disadvantages Local SAP Gateway Advantages • • It uses system resources more efficiently than a BW Publisher service for Windows installations of BusinessObjects Enterprise. See “Publishing reports using the Content Administration Workbench” on page 88. Disadvantages 24 BusinessObjects XI Integration Kit for SAP Installation Guide . Selecting your BW Publisher configuration On Windows. Details of the publishing process depend upon the publisher configuration that you select. Select the configuration method based on the requirements of your site. you can configure the BW Publisher in one of two ways: • • Install the BW Publisher as a service on a BusinessObjects Enterprise machine. It is more difficult to administer than a local SAP Gateway because changes to the BW Publisher service require you to edit the registry. BW Publisher service Advantages • • • • It is simpler to install than a local SAP Gateway It is scalable because new publisher instances are created automatically in response to increased publishing load. It is more complex to install and configure than the BW Publisher service. it is recommended that you only use the local Gateway to create BW Publisher instances. It makes less efficient use of computing resources than a local SAP Gateway because Publisher Instances are not stopped automatically when they are no longer needed. follow the instructions for installing the BW Publisher as a service. Tip: For more on translated reports. if you are not using a local SAP Gateway. using a local SAP Gateway imposes a performance penalty and is not recommended. Note: Before beginning to publish. the same basic publishing process occurs.pdf). When a user attempts to publish one or more Crystal reports. • • A publishing command. with any required translated report strings. the CMS allows the reports to be added to the system. define a folder structure for your content. The main difference between the two configuration types is that if you do not install a local SAP Gateway. This guide is included in the docs directory on the installation CD and is also installed on the computer that BusinessObjects XI Integration Kit for SAP is installed on. and sends the following information across the network: • The appropriate Crystal report file(s). BW looks for a Remote Function Call (RFC) destination (of type TCP/IP) that is configured to connect to this BW Publisher. However. The BW Publisher logs on to the specified CMS as the user. The SAP Gateway responds by executing the publishing command. If the user’s rights are sufficient. Publishing Reports Whether you choose to configure the BW Publisher service with or without a local SAP Gateway. your system configuration will vary slightly as you must manually start the required number of BW Publisher instances. and import SAP roles. thereby invoking the BW Publisher.Components and Features Reporting with BusinessObjects XI Integration Kit for SAP 3 Note: For UNIX installations of BusinessObjects Enterprise. The TCP/IP destination provides BW with the name and port number of the SAP Gateway that the BW Publisher is registered with. BW then communicates over TCP/IP with the BW Publisher. the location is C:\Program Files\Business Objects\Integration Kit for SAP 11\docs. For UNIX installations of BusinessObjects Enterprise. If you installed to the default path. the BW Publisher service registers as a server program with the SAP Gateway running on your application host. see the BusinessObjects XI Integration Kit for SAP User’s Guide (userguide. you must configure SAP authentication in BusinessObjects Enterprise. and checks to see if the user has the appropriate permissions in BusinessObjects Enterprise to publish reports. The name of the appropriate Central Management Server (CMS). using the BusinessObjects XI Integration Kit for SAP Installation Guide 25 . See “Configuring SAP authentication for BusinessObjects Enterprise” on page 52 for complete instructions. users can locate. or on your central instance of BW if you have a BW cluster. the location is C:\Program Files\Business Objects\Integration Kit for SAP 11\docs. Users can schedule translated reports in specific languages and view report titles and on-demand reports in their usual logon language. These new features are designed especially for SAP users: • • • Users whose roles you import can log on to the BusinessObjects Enterprise InfoView for SAP with their usual SAP credentials. and refresh Crystal reports that have been saved in their BW roles. This SAP Gateway may be installed on your single BW server. • Administrators can divide report processing by language across server groups. view.3 Components and Features Reporting with BusinessObjects XI Integration Kit for SAP name you specify as its Program ID string. in this case. BW sends a publishing command to the BW Publisher which does not occur if a local SAP Gateway is installed. Users can browse a hierarchy of “My Groups” folders that correspond to the structure of the imported roles whose content you publish from BW to BusinessObjects Enterprise. (See “Reporting with BusinessObjects XI Integration Kit for SAP” on page 22 for 26 BusinessObjects XI Integration Kit for SAP Installation Guide . In these folders. Tip: These features require that you translate the reports within BW. Also.pdf). Distributing information over the Web The Web Content feature includes the BusinessObjects Enterprise InfoView for SAP. This guide is included in the docs directory on the installation CD and is also installed on the computer that BusinessObjects XI Integration Kit for SAP is installed on. If you installed to the default path. After installing the Web Content. For more information. see “Setting up the sample reports” on page 98. see the BusinessObjects XI Integration Kit for SAP User’s Guide (userguide. With BusinessObjects XI Integration Kit for SAP you receive all of the functionality provided with BusinessObjects XI Integration Kit for SAP. before you publish the reports to BusinessObjects Enterprise. which is a customized edition of the standard BusinessObjects Enterprise InfoView (InfoView). This ensures that reports created or translated in a specific language are always processed by servers that can handle data in that language. you are able to report off of a variety of other SAP data sources from within Crystal Reports. BusinessObjects XI Integration Kit for SAP Installation Guide 27 .) In addition. pool tables. Reporting off multidimensional data in BW The BW OLAP Kit has been specially designed to integrate the Online Analytical Processing (OLAP) viewing capabilities of OLAP Intelligence and Crystal Reports with your SAP Business Information Warehouse (BW) system. and BusinessObjects Enterprise. Users who are currently involved with the production of ABAP reports will find it easy to build reports quickly with this driver. views. clusters. For additional information on OLAP analysis and reporting. which allow you to report off additional SAP data sources from within Crystal Reports. BusinessObjects Enterprise. however. Reporting off other SAP data sources In addition to the components provided with your product distribution. This flexibility. When you create reports that use the Open SQL driver. Advanced functionality in the driver also allows reporting against ABAP functions and ABAP data clusters. OLAP Intelligence. and views. Users can connect to multidimensional BW Info Cubes and generate reports that incorporate complex data analysis. results in a higher level of complexity than with the InfoSet driver. ABAP developers can use these features to perform advanced tasks such as reporting against data clusters in HR. you can download the Open SQL driver and the BW OLAP Kit. refer to your OLAP Intelligence and/or Crystal Reports documentation. cluster tables. Reporting off tables. Developers can also utilize ABAP to augment report processing. you gain easy access to SAP’s transparent tables. and OLAP Intelligence. and functions The Open SQL driver is the most powerful of the drivers due to the flexibility it provides for accessing data in SAP.Components and Features Reporting with BusinessObjects XI Integration Kit for SAP 3 details. 3 Components and Features Reporting with BusinessObjects XI Integration Kit for SAP 28 BusinessObjects XI Integration Kit for SAP Installation Guide . Installing BusinessObjects XI Integration Kit for SAP chapter . 30 BusinessObjects XI Integration Kit for SAP Installation Guide .4 Installing BusinessObjects XI Integration Kit for SAP This chapter shows how to install BusinessObjects XI Integration Kit for SAP. System requirements are provided. as well as procedures covering various installation and configuration tasks. Once you have completed the main installation and configuration stages. and configuring Data Access for SAP.Installing BusinessObjects XI Integration Kit for SAP Installation overview 4 Installation overview To set up BusinessObjects XI Integration Kit for SAP. see “Performing the initial configuration” on page 47. Then install the BusinessObjects XI Integration Kit for SAP. depending on the features that you want to enable. • If you have BW. For complete details. See “Installing on Windows” on page 31. Required tasks include importing transport files and setting up authorizations in SAP. complete the following additional configuration steps: • • • • Setting up folders and security in BusinessObjects Enterprise Configuring the BW Publisher Configuring publishing in the Content Administration Workbench. BusinessObjects XI Integration Kit for SAP Installation Guide 31 . you must complete the main installation and configuration stages in this order: • Check the system requirements and perform the installation procedures that correspond to your operating environment. Crystal Reports. you may need to complete additional tasks. you will need to contact one for assistance during the installation. A number of installation tasks require the skills and security privileges of an SAP BASIS administrator. see “” on page 69. Configuring the SAP http request handler For complete information. and OLAP Intelligence if you purchased it. consult the remaining chapters of this guide. see “Recommended initial installation” on page 34. consider the following: • Install BusinessObjects Enterprise. • Complete the required base administrative tasks within SAP necessary to configure R/3 or BW systems to work with BusinessObjects XI Integration Kit for SAP. If you are not an SAP administrator. For details. or “Installing on UNIX” on page 36. configuring SAP authentication in BusinessObjects Enterprise. Installing on Windows Before installing BusinessObjects XI Integration Kit for SAP on Windows. For details. ensure that each machine meets the requirements that correspond to the components you are installing.ini file to the SAPLOGON_INI_FILE environment variable. see “Distributed installation” on page 44. You can expand your deployment by distributing the BusinessObjects Enterprise servers across multiple machines. and the SAP Gateway (if you choose to configure the BW Publisher using a stand-alone SAP Gateway). SAP Presentation CD requirements BusinessObjects XI Integration Kit for SAP uses the SAPGUI from the SAP Presentation CD. OLAP Intelligence. Crystal Reports. Note: For a detailed list of tested environments for BusinessObjects XI Integration Kit for SAP. For details. The file saplogon. Use the Windows file paths provided in notes to that procedure. and the BusinessObjects XI Integration Kit for SAP on a single Windows machine. If you choose to install the Java version of the BusinessObjects XI Integration Kit for SAP web applications. operating systems. and OLAP Intelligence on the same machine. However it is not necessary to install BusinessObjects Enterprise. deploy the BusinessObjects Enterprise InfoView for SAP as described in “Deploying the web applications” on page 39. SAP components. For a standalone installation. consult the platforms_EN. Crystal Reports. and OLAP Intelligence on Windows operating systems.4 Installing BusinessObjects XI Integration Kit for SAP Installing on Windows • • • You can install BusinessObjects Enterprise. System requirements All BusinessObjects XI Integration Kit for SAP components are supported for use with the version XI releases of BusinessObjects Enterprise. ensure that all requirements are met on a single machine. This file includes specific version and Service Pack requirements for application servers. etc.txt file on the installation CD. you can add the full path to the saplogon. Alternatively. see the platforms_EN. Crystal Reports.ini only needs to be installed on machines with data access components installed. For version requirements. 32 BusinessObjects XI Integration Kit for SAP Installation Guide . Server requirements for BusinessObjects Enterprise • • Download the RFC SDK for your platform from the SAP Service Marketplace. For a distributed installation.txt file included with your product distribution. For a detailed list of tested environments for Crystal Reports. This standard setting allows BusinessObjects Enterprise to log on to SAP with load balancing. Consult the platforms_EN. sapmsQR6 3600/ tcp). Ensure also that a blank line follows the entry. you must install and configure SAP Java Connector components. Client requirements for Crystal Reports • • If you have a BW environment. Consult the documentation included with the SAP Java Connector for more information.dlland sapjcorfc. you must set up your SAP system to accept and create logon tickets. and replace portnumber with the port number of the message server that BusinessObjects Enterprise will log on to (for example.dll to %windir%\system32 and copy sapjco. Page Server. and/ or Report Job Server: sapmsSID portnumber/tcp Replace SID with the system ID of your SAP system.txt file included with your BusinessObjects Enterprise product distribution for a complete list. copy librfc32. consult the platforms_EN. To do this. Requirements for using the BusinessObjects XI Integration Kit for SAP Java SDK To have the Java version of the BusinessObjects Enterprise InfoView for SAP install automatically. SAP requirements Before you can enable ticket based Single Sign On between SAP and BusinessObjects Enterprise. If you are using a load balanced logon. This involves setting two related profile parameters on your SAP server: • • login/accept_sso2_ticket login/create_sso2_ticket BusinessObjects XI Integration Kit for SAP Installation Guide 33 .txt file included with your Crystal Reports product distribution.Installing BusinessObjects XI Integration Kit for SAP Installing on Windows 4 • • Supported web server software must be installed and configured correctly before you install BusinessObjects Enterprise. the following entry must appear in the Services file (found in %windir%\system32\drivers\etc\) on any BusinessObjects Enterprise machines running a CMS.jar to the application server’s shared library folder. install the SAPGUI along with the BW AddOn option from the SAP Presentation CD before you install Crystal Reports and the BusinessObjects XI Integration Kit for SAP. Ensure that you have selected a Program ID for the BW Publisher component. Follow the procedures in this section in order: • • Install the core Business Objects products first (BusinessObjects Enterprise. and select the BW Publisher Service component. If you choose to install the BW Publisher Service. See “Publishing Reports” on page 25 for details. Install Crystal Reports XI. Note: You must re-start the SAP system to activate your changes. and that you know the Gateway Host and Gateway Service that you will use for publishing.pdf) included on your Crystal Reports product distribution. 2. Crystal Reports. Recommended initial installation Before beginning this installation. Before running the installer. read “Publishing from BW to BusinessObjects Enterprise” on page 23 and select your publisher configuration. For details. Next. see the SAP Library > Web Application Server >SAP Web Application Server Security > SAP Web Application Server Security > User Authentication > Using Logon Tickets. For details. install or upgrade to OLAP Intelligence. During the installation. see the BusinessObjects Enterprise Installation Guide (install. See “System requirements” on page 32. install the BusinessObjects XI Integration Kit for SAP.pdf) included on your BusinessObjects Enterprise product distribution. if purchased it). and OLAP Intelligence. see Installing Crystal Reports (install. it is recommended that you install Crystal Reports first. For complete details on these profile parameters and configuring SAP to accept and create logon tickets. Log on as an Administrator of the local machine to install any components. select a custom installation. 34 BusinessObjects XI Integration Kit for SAP Installation Guide . If you are planning to use OLAP Intelligence with BusinessObjects XI Integration Kit for SAP. 3.4 Installing BusinessObjects XI Integration Kit for SAP Installing on Windows The parameter values that you set depend upon whether or not the server’s certificate is self-signed or signed by the SAP Certification Authority (CA). you will be prompted for information about your BW system. To install the core Business Objects products Note: If you are installing BusinessObjects Enterprise and Crystal Reports on the same machine. ensure that each machine meets the minimum requirements. Deploy BusinessObjects Enterprise XI or upgrade all existing BusinessObjects Enterprise machines to BusinessObjects Enterprise XI. 1. depending on the product(s) that are already installed: 3. Click Next. select the Custom installation type and click Next. If only Crystal Reports is installed. run the setup program from the installation Disc. Proceed through the Setup program’s dialog boxes and follow the instructions displayed on your screen until you reach the Select Installation Type dialog box. and click Next. but must be 64 characters or fewer. 1. see the OLAP Intelligence Installation Guide (Install. the setup program detects which BusinessObjects Enterprise components are present and installs the appropriate features of BusinessObjects XI Integration Kit for SAP. If your installation includes the BW Publisher Service.exe on the CD. Note: If you are performing a distributed installation of BusinessObjects Enterprise. If both BusinessObjects Enterprise and a desktop client are installed. choose the features that you need.Installing BusinessObjects XI Integration Kit for SAP Installing on Windows 4 For details. or if you want to select which components will be installed. 2.pdf) included on your OLAP Intelligence product distribution. Record the exact value you specify here for the Program ID. next you are prompted for information about your BW system. select the Desktop installation type. 6. and may not contain spaces. See “Configuring a destination for the BW Publisher service” on page 77. 4. select the Server installation type. • Program ID Type a descriptive string to identify the BW Publisher service. If you selected a Desktop installation type. Tip: If Autoplay is disabled on your system. double-click Setup. To install BusinessObjects XI Integration Kit for SAP On each Crystal Reports and BusinessObjects Enterprise machine. • • • If only BusinessObjects Enterprise is installed. 5. You will need this value when you configure the RFC destination on your BW system. proceed through the Setup program’s remaining dialog boxes and follow the instructions on your screen to complete the installation. The Program ID is case-sensitive. The Program ID can take any value. In the Select Features dialog box. Select the appropriate installation type. BusinessObjects XI Integration Kit for SAP Installation Guide 35 . 4 Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX • • Gateway Host Type the name of your BW server. Usually. you may use this symbolic name instead. For details. and the value for this field is 3300. For details. enter the name of the central instance of BW. 36 BusinessObjects XI Integration Kit for SAP Installation Guide .sh script. type 33##. see “Installing the UNIX components” on page 38. You can expand your deployment by distributing the BusinessObjects Enterprise servers across multiple machines. consult the RFC SDK documentation for API RfcAccept. See “Integrating with Secure Network Communication” on page 63 for more information. the instance number is 00. For information on how to enable SNC for registered servers. Proceed through the Setup program’s remaining dialog boxes and follow the instructions on your screen to complete the installation. • Extra (optional) If you plan to enforce Secure Network Communication (SNC) between SAP and BusinessObjects Enterprise. 7. If you have a BW cluster. see “Distributed installation” on page 44. If you have defined a symbolic name for this port (such as sapgw##). Installing on UNIX UNIX versions of the following BusinessObjects Enterprise add-on components are provided for environments where BusinessObjects Enterprise is running on UNIX: • • • • • • SAP Authentication BW Publisher Data Access Web Content When installing BusinessObjects XI Integration Kit for SAP on UNIX. For example. enter the appropriate switches here. Gateway Service Type the port number that the Gateway Host is listening on. consider the following: You install the BusinessObjects Enterprise add-on components by running the winstall. where ## represents the instance number of your SAP Gateway. SAP Java Connector BusinessObjects XI Integration Kit for SAP web applications (including the InfoView for SAP). you must unpack the archive file containing the SAP Java Connector. The SAP Java Connector is available from http://service.Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 4 System requirements Before installing any of the BusinessObjects XI Integration Kit for SAP components. For example. and replace port with the port number of the message server that BusinessObjects Enterprise will log onto (for example. or Use symbolic links for the location of the . Complete this installation and configuration in accordance with the BusinessObjects Enterprise Installation Guide. and the BusinessObjects XI Integration Kit for SAP Java SDK require the SAP Java Connector. PLATFORM_PATH is solaris_sparc for an installation on Solaris. or Add the location of the librfccm library and the libsapjcorfc library to the library path.sap. Then you must do one of the following things: • Copy the librfccm library and the libsapjcorfc library to crystal_root/enterprise/PLATFORM_PATH. Please see the SAP MarketPlace for information on licensing SAP Java Connector for use in your development environment. where crystal_root is the full path to your businessobjects directory.com/connectors. • • BusinessObjects XI Integration Kit for SAP Installation Guide 37 . After you have installed BusinessObjects Enterprise. This standard setting allows BusinessObjects Enterprise to log on to SAP with load balancing. • • BusinessObjects Enterprise must be installed and configured correctly on UNIX before you install the BusinessObjects XI Integration Kit for SAP components.librfccm library and the libsapjcorfc library. sapmsQR6 3600/tcp). ensure that your environment meets the following requirements. The following entry must appear in the Services file on the BusinessObjects Enterprise machine (found in /etc) sapms<SID> tcp/port Replace SID with the system ID of your SAP system. The installation script needs to log on to your Central Management Server. you must set up SAP to accept and create logon tickets.jar to the CLASSPATH environment variable. Note: You must re-start the SAP system to activate your changes. 1.jar in the application server's shared lib directory.) Consult the documentation included with the SAP Java Connector for more information. and have installed the SAP Java Connector. see the SAP Library > SAP Web Application Server > Security > SAP Web Application Server Security > User Authentication > Using Logon Tickets. Note: You may also use another account that has permission to read and write files in the businessobjects directory and its subdirectories. Installing the UNIX components Once you have set up BusinessObjects Enterprise on UNIX. To install SAP Add-Ons Log on to your UNIX system under the BusinessObjects user account you created for your BusinessObjects Enterprise installation. 3. See “Deploying the web applications” on page 39 or consult your application server documentation for details. or by adding sapjco. 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’s certificate is self-signed or signed by the SAP CA. SAP requirements Before you can enable ticket based Single Sign On between SAP and BusinessObjects Enterprise. you must make sapjco.4 Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX After you have installed BusinessObjects Enterprise. 2. Ensure that you are working in your businessobjects directory: 38 BusinessObjects XI Integration Kit for SAP Installation Guide .jar available to your Java application server as a shared resource (either by placing sapjco. Ensure that BusinessObjects Enterprise is running before you begin the installation. Run the installer from the location that you mounted the SIK CD and in the installer provide the path to your BusinessObjects Enterprise install. you can install the add-on components. For complete details on these profile parameters and configuring BW to accept and create logon tickets. The script displays the product license agreement. Press Enter. The script prompts you for the absolute path of the installation directory. 11. Type begin and press Enter.sh script. 10. the script completes the final installation steps and finishes. you must create virtual path mappings on your Java web application server. the default value of 6400 is used. After you make your selection. Deploying the web applications To deploy the Java version of the BusinessObjects Enterprise InfoView for SAP.sh When prompted. 5. and asks you if you are ready to have the installation begin. Restart your Java application server and your Central Management Console (CMC) to make the SAP authentication application available in the CMC. 7. the script asks you if you want to restart the CMS. and then type yes and press Enter to accept the license agreement and to proceed with the installation. BusinessObjects XI Integration Kit for SAP Installation Guide 39 . Press Enter to accept the default.war files) that implement the InfoView. Note: Before performing this procedure. ensure that you have deployed the SAP Java Connector as described in “SAP Java Connector” on page 37. which is your current directory The script notifies you that it has collected all of the required information. 9. Use the format cmsname:portnum. They map specific URLs to the web application archives (. Note: If you do not specify a port number. Consult the BusinessObjects Enterprise Administrator’s Guide for details. The installation script unpacks the archived installation file. you can restart it later using the ccm. Press the spacebar to read through the information in its entirety. This may take a few minutes. If you choose not to restart the CMS now.Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 4 cd $HOME/businessobjects 4. 8. Run the installation script: . press Enter to continue. Next. 6. enter the name and port number of your Central Management Server./winstall. When prompted. Restart Tomcat by typing sh $CATALINA_HOME/bin/startup. 9.xml. substitute that port number for 8080. To deploy the BusinessObjects Enterprise InfoView for SAP on Tomcat Shut down Tomcat if it is running.sh To test the BusinessObjects Enterprise InfoView for SAP. If you did not install on the default Tomcat port.war file found at C:\Program Files\BusinessObjects\Enterprise 11\java\applications\SAP\sap_desktop.4 Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 1.sh Ensure that the sapjco. 5. substitute the name of the machine where you installed Tomcat. 6.war" debug="0" reloadable="false"/> Substitute your BusinessObjects Enterprise install directory for crystal_root Note: If you are deploying the Java version of the InfoView on Windows. 40 BusinessObjects XI Integration Kit for SAP Installation Guide . Save the file. Check to see if the following file exists: $CATALINA_HOME/shared/classes/META-INF/ authPluginExts. Type sh $CATALINA_HOME/bin/ shutdown. For servername.jar Java archive file is in $CATALINA_HOME/ shared/lib (see “SAP Java Connector” on page 37 for details).Tomcat Examples Context -->: <Context path="/businessobjects/enterprise11/sap/ desktoplaunch" docBase="crystal_root/enterprise/java/ applications/sap/sap_desktop. use the . If it does not. Open the file $CATALINA_HOME/conf/server. in a text editor such as vi.properties to this location: $CATALINA_HOME/shared/classes/META-INF/ This properties file adds the SAP authentication option to the log on page of the InfoView. copy the following file: crystal_root/enterprise/java/applications/sap/ authPluginExts. Add the following lines directly above the line <!-. open a web browser and type http://servername:8080/businessobjects/ enterprise11/SAP/desktoplaunch/infoview in its address bar. 2. Substitute the root directory of your BusinessObjects Enterprise installation for crystal_root 3. 8.war. 4.properties 7. Make sure that your BEA WebLogic server is not running. substitute that port number in the URL. Open a web browser. For servername. Note: By default. and type http://servername:7001/console in its address bar to open the BEA WebLogic Administrative Console. Ensure that your CLASSPATH environment variable includes the sapjco.properties 3. open a web browser and type http://servername:8080/businessobjects/ enterprise11/admin in its address bar to launch the Central Management Console (CMC). BusinessObjects XI Integration Kit for SAP Installation Guide 41 . Log on to the CM C using your Administrator account and password. If it does not. 10. To test that the SAP authentication module is now available. The SAP authentication tab (as shown in “Connecting to SAP entitlement systems” on page 55) should appear. To deploy the BusinessObjects Enterprise InfoView for SAP on BEA WebLogic 1. (See “SAP Java Connector” on page 37 for details. and restart your Java application server. This properties file adds the SAP authentication option to the log on page of the InfoView. 4. Click Authentication. ensure that the librfccm library is in your crystal_root/enterprise/PLATFORM directory. Start your BEA WebLogic server. and restart your Java application server. 5. substitute that port number for 8080.jar archive file. If you configured your application server to use a different port number. Note: For a Windows installation of BusinessObjects Enterprise that uses the Java version of the InfoView. BEA WebLogic uses port 7001. and then SAP. (By default the password is blank when you first install BusinessObjects Enterprise. substitute the name of the machine where you installed Tomcat.Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 4 The BusinessObjects Enterprise InfoView for SAP should start. 11. If you did not install on the default Tomcat port. Substitute the name of the machine where you installed BEA WebLogic for servername. 2. ensure that librfc32.) 12.) Add the following file to your CLASSPATH environment variable: crystal_root/enterprise/java/applications/sap/ authPluginExts.dll is in your C:\WNNT\system32 directory. open a web browser and type http://servername:7001/businessobjects/ enterprise11/admin in its address bar to launch the Central Management Console (CMC).war file found at crystal_root/enterprise/java/ applications/sap/sap_desktop. If you are deploying the Java version of the InfoView on Windows. Log on to the CMC using your Administrator account and password. To test that the SAP authentication module is now available. 2.war.jar archive file.dll is in your C:\WNNT\system32 directory. and restart your Java application server. 9. use the .war.) 42 BusinessObjects XI Integration Kit for SAP Installation Guide . and set the context root to / businessobjects/enterprise11/sap/desktoplaunch Note: • • To set the context root for the web application. To test that the BusinessObjects Enterprise User Launchpad deploys correctly. and then SAP. Use the . Note: For a Windows installation of BusinessObjects Enterprise that uses the Java version of the InfoView. 8.) The SAP authentication tab (as shown in “Connecting to SAP entitlement systems” on page 55) should appear. (See “SAP Java Connector” on page 37 for details. 1. Click WebApp Ext in the left-hand tree menu. Ensure that your CLASSPATH environment variable includes the sapjco. Click Authentication. ensure that librfc32. 7.4 Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 6. edit the Web Application Deployment Descriptor. type http://servername:7001/businessobjects/ enterprise11/sap/desktoplaunch in the address bar of a web browser. then make your changes to the Context Root field. Click Apply]. and restart your Java application server. To deploy the BusinessObjects Enterprise InfoView on IBM WebSphere Make sure that your IBM WebSphere server is not running. Deploy the BusinessObjects Enterprise InfoView for SAP as a new web application. (By default the password is blank when you first install BusinessObjects Enterprise.war file found at C:\Program Files\BusinessObjects\Enterprise 11\java\applications\SAP\sap_desktop. 10. [Click Edit Web Application Deployment Descriptors. ensure that the librfccm library is in your crystal_root/enterprise/PLATFORM directory. If it does not. Log on to the CMC using your Administrator account and password. type http://servername:9080/businessobjects/ enterprise11/sap/desktoplaunch/ in the address bar of a web browser. 9. and set the context root to / businessobjects/enterprise11/sap/desktoplaunch 5. To test that the SAP authentication module is now available. Add the following file to your CLASSPATH environment variable: crystal_root/enterprise/java/applications/sap/ authPluginExts. Install the BusinessObjects Enterprise InfoView as a new application. Start your IBM WebSphere Server. use the .war. 7. If you chose to use a port number other than the default value for the administrative console. substitute that value for 9090.war.) The SAP authentication tab (as shown in “Connecting to SAP entitlement systems” on page 55) should appear. and restart your Java application server. Use the .properties This properties file adds the SAP authentication option to the log on page of the InfoView.Installing BusinessObjects XI Integration Kit for SAP Installing on UNIX 4 3. 6. Note: If you are deploying the Java version of the InfoView on Windows. Click Authentication. To test that the BusinessObjects Enterprise User Launchpad deploys correctly. If it does not. (By default the password is blank when you first install BusinessObjects Enterprise. Note: For a Windows installation of BusinessObjects Enterprise that uses the Java version of the InfoView. 10. BusinessObjects XI Integration Kit for SAP Installation Guide 43 . 4. and launch the Administrative Console (at http://servername:9090/admin/). For servername. ensure that the librfccm library is in your _root/enterprise/PLATFORM directory. and restart your Java application server. substitute the name of the machine where you installed IBM WebSphere. and then SAP.war file found at crystal_root/enterprise/java/ applications/sap/sap_desktop.war file found at C:\Program Files\BusinessObjects\Enterprise 11\java\applications\SAP\sap_desktop. 8. ensure that librfc32. Start the new application.dll is in your C:\WNNT\system32 directory. open a web browser and type http://servername:9080/businessobjects/ enterprise11/admin in its address bar to launch the Central Management Console (CMC). single-machine environments. to large-scale deployments supporting global organizations. For general information about distributing the BusinessObjects Enterprise components. If you select a default server installation of BusinessObjects XI Integration Kit for SAP. ranging from stand-alone. see the “Scaling Your System” section of the BusinessObjects Enterprise Administrator’s Guide (admin.4 Installing BusinessObjects XI Integration Kit for SAP Distributed installation Distributed installation The BusinessObjects Enterprise architecture is scalable in that it allows for a multitude of server configurations. Note: This section provides details that are specific to BusinessObjects XI Integration Kit for SAP. The flexibility offered by the product’s architecture allows you to set up a system that suits your current reporting requirements. install the listed BusinessObjects XI Integration Kit for SAP components on the appropriate machines. Components Data Access BusinessObjects Enterprise machines • • • • • • • Page Server Report Job Server Report Application Server (RAS) Page Server Report Job Server RAS BusinessObjects Enterprise SDK BW Publisher (installed as a service on one or more of these machines) 44 BusinessObjects XI Integration Kit for SAP Installation Guide .pdf in the doc directory of your BusinessObjects Enterprise product distribution). without limiting the possibilities for future growth and expansion. and installs the appropriate BusinessObjects XI Integration Kit for SAP components. the setup program detects which elements of BusinessObjects Enterprise are present. Installing components on BusinessObjects Enterprise machines If you have a distributed installation of BusinessObjects Enterprise. When you install the BW Publisher on the BusinessObjects Enterprise machines. BusinessObjects Enterprise Java SDK Security Web Content Separating BusinessObjects Enterprise from your web server The BusinessObjects Enterprise Installation Guide (install. BW load-balances publishing between the BusinessObjects XI Integration Kit for SAP Installation Guide 45 . Distributing the BW Publisher installation BW Publisher Service You can load-balance publishing from BW by installing BW Publisher services on two separate machines in the same BusinessObjects Enterprise system. If you set up your system in this manner. configure each one to use the same Program ID and SAP Gateway Host and Gateway Service.pdf) included with your BusinessObjects Enterprise product distribution explains how to connect BusinessObjects Enterprise to a web server or Java application server that is running on a different machine.Installing BusinessObjects XI Integration Kit for SAP Distributed installation 4 Components BW Publisher (installed with a local SAP Gateway) BusinessObjects Enterprise machines • • • • • • • Page Server Report Job Server RAS BusinessObjects Enterprise SDK Central Management Server All machines that have the BusinessObjects Enterprise SDK installed. After you create an RFC destination that uses this Program ID. This feature includes the files that make up the BusinessObjects XI Integration Kit for SAP web application. you will need to install the Web Content feature from the BusinessObjects XI Integration Kit for SAP installation disc onto the server that is connected to BusinessObjects Enterprise. Configure each BW Publisher service to use the Gateway Host and Gateway service of a separate BW application server (using the instructions from “Recommended initial installation” on page 34 or “To start the BW Publisher on UNIX” on page 76).) In this case you must install a local SAP Gateway on the same machine as the BW Publisher. if you install the BW Publisher and the local SAP Gateway on a dedicated machine. Moreover. Adding servers to BusinessObjects Enterprise If you expand your BusinessObjects Enterprise system after installing BusinessObjects XI Integration Kit for SAP. Thus. install a separate BW Publisher service on a BusinessObjects Enterprise machine. you must also install the Page Server. For each one. In this configuration. publishing from BW can continue if either a BW Publisher or an application server fails. Configure each BW application server to run an SAP Gateway. as described in “Installing components on BusinessObjects Enterprise machines” on page 44. the BW Publisher requires access to the BusinessObjects Enterprise Software Development Kit (SDK) and the Crystal Reports Print Engine. (See “Selecting your BW Publisher configuration” on page 24 for details of this configuration. you must install components from the installation Disc. 46 BusinessObjects XI Integration Kit for SAP Installation Guide . In addition. it is not recommended that you use a BW Publisher on a standalone SAP Gateway. please read “Publishing from BW to BusinessObjects Enterprise” on page 23 On UNIX. You can add an additional level of system redundancy to any configuration that includes multiple BW application servers. publishing from BW falls over to the remaining BW Publisher. if one BW Publisher becomes unavailable. BW Publisher on a stand-alone SAP Gateway If you want to separate the BW Publisher from other BusinessObjects Enterprise components. install the BW using a stand-alone SAP Gateway. or Report Application Server. Crystal Reports Job Server.4 Installing BusinessObjects XI Integration Kit for SAP Distributed installation BusinessObjects Enterprise machines. Tip: • • Before selecting your BW Publisher configuration. Performing the initial configuration chapter 5 Performing the initial configuration Configuration overview Configuration overview Once you have updated BusinessObjects Enterprise and with BusinessObjects XI Integration Kit for SAP, you must configure your SAP system and BusinessObjects Enterprise. These steps must be performed for both BW and R/ 3 systems: • • • Configuring transports Configuring SAP authentication for BusinessObjects Enterprise Configuring Data Access After you have completed these steps on an R/3 system, configuration is complete. You can begin using BusinessObjects XI Integration Kit for SAP. For BW systems, additional configuration is required to enable report viewing and report publishing. After completing these steps, go on to “” on page 69. Configuring transports To set up the Data Access Kit or BW Publisher component of BusinessObjects XI Integration Kit for SAP, you must import the appropriate transports from the installation disc to your SAP system. The Data Access Kit and the BW Publisher use the contents of these transport files when communicating with the SAP system. The transports provided with BusinessObjects XI Integration Kit for SAP are located in the transports directory on the installation cd. These sections provide you with details on setting up the appropriate transports: • • • • “Types of transports” on page 49 “Selecting which transports to import” on page 50 “Checking for conflicts” on page 51 “Importing the transport files” on page 51 The installation and configuration procedures required on the SAP system must be performed by a BASIS expert who is familiar with the Change and Transport system and who has administrative rights to the SAP system. The exact procedure for importing transport files varies, depending upon the version 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, use the Security Definition Editor. For complete details, see Chapter 8: Security Definition Editor overview. 48 BusinessObjects XI Integration Kit for SAP Installation Guide Performing the initial configuration Configuring transports 5 After you have imported transports, you must configure the appropriate levels of user access. Create the required authorizations and apply them through profiles or roles to SAP users who will be designing, running, or scheduling Crystal reports. For details, see “Creating and applying authorizations” on page 52. Types of transports BusinessObjects XI Integration Kit for SAP includes seven transports: the Open SQL Connectivity transport, the InfoSet Connectivity transport, the Row-level Security Definition transport, the Cluster Definition transport, the Authentication Helpers transport, the Crystal Content Administration Workbench transport, and the BW Query parameter personalization transport. A subset of these transports are available with BusinessObjects XI Integration Kit for SAP. There are two different sets of the transports: Unicode compatible transports and ANSI transports. If you are running a BASIS system of 6.20 or later, use the 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 the transports directory on the installation cd lists the Unicode compatible and ANSI transport files. Each transport is described here. For details about the contents of each transport file, see Appendix : . • Open SQL Connectivity transport The Open SQL Connectivity transport enables the Open SQL driver to connect to and report off the SAP system. It is included only with BusinessObjects XI Integration Kit for SAP. • Row-level Security Definition transport This transport provides the Security Definition Editor, which is a tool that serves as a graphical interface to the /crystal/auth tables in the Open SQL Connectivity transport. It is included only with BusinessObjects XI Integration Kit for SAP. For details on using the Security Definition Editor, see “Security Definition Editor overview” on page 104. • Cluster Definition transport This transport provides the Cluster Definition tool. This tool enables you to build up a metadata repository for ABAP data cluster definitions. These definitions provide the Open SQL driver with the information it requires in order to report off these data clusters. It is included only with BusinessObjects XI Integration Kit for SAP. For details on using the Cluster Definition Tool, see the “Reporting off clusters” section of the BusinessObjects XI Integration Kit for SAP User’s Guide. Note: ABAP data clusters are not the same as cluster tables. Cluster tables are already defined in the DDIC. BusinessObjects XI Integration Kit for SAP Installation Guide 49 5 Performing the initial configuration Configuring transports • • InfoSet Connectivity transport The InfoSet Connectivity transport enables the InfoSet driver to access InfoSets and SAP Queries. Authentication Helpers transport This transport provides the Single Sign On enhancement for the SAP authentication plug-in. This enhancement frees users from having to enter their credentials more than once to access any of the BusinessObjects Enterprise, R3, and BW systems. • • Content Administration Workbench transport This transport provides content administration functionality for BW systems. It is available only as a UNICODE compatible transport. BW Query parameter personalization transport This transport provides support for personalized and default parameter values in reports based on BW queries. Note: Read the transports_EN.txt file located in the transports directory on the installation CD. This text file lists the names of the files that make up each transport. Selecting which transports to import Import the transports that are required for your R/3 or BW system. Select the Data Access Kit components that you want, and import the required transports. SAP System R/3 Transport Open SQL Connectivity Row-level Security Definition Cluster Definition Recommended. Required if you have installed the SAP Solution Tools Plug-in (ST-PI). Notes • • InfoSet Connectivity Authentication Helpers 50 BusinessObjects XI Integration Kit for SAP Installation Guide (The cofiles and data directories below the transports directory correspond to the ../trans/cofiles and . Importing the transport files Read the transports_EN. Refer to your SAP documentation for the procedures appropriate to your version of SAP. Required. there is no need to check for conflicts prior to importing the transport files. or any of the other objects already exists on the SAP system..txt file located in the transports directory on the installation CD. The Business Objects namespace is reserved for this purpose within recent versions of R/3. BusinessObjects XI Integration Kit for SAP Installation Guide 51 . If the function group.) You must import the Open SQL Connectivity transport before importing the Rowlevel Security Definition or the Cluster Definition transports.Performing the initial configuration Configuring transports 5 SAP System BW Transport Open SQL Connectivity Row-level Security Definition Cluster Definition Notes • • InfoSet Connectivity Authentication Helpers Recommended.. Required. You may import the other transports in any order. Content Administration Workbench BW Query parameter personalization Checking for conflicts The contents of the transport files are registered automatically under the Business Objects namespace when you import the files. Consequently. then you must resolve the namespace before importing the BusinessObjects XI Integration Kit for SAP transport files.. any of the function modules./trans/data directories on your SAP server. This text file lists the exact names of the files that make up each transport. Required if you have installed the SAP Solution Tools Plug-in (STPI). 52 BusinessObjects XI Integration Kit for SAP Installation Guide . and applying authorizations depend upon the version of SAP that you have installed. Imports fail if the import files are read-only. if your SAP server is installed on a UNIX machine. you must have write permissions for the UNIX server. For information on the authorizations needed by content publishers. depending upon your individual implementation. in our experience and in our test environment. Creating and applying authorizations Next you must create and apply the authorizations needed by each user to access information using the BusinessObjects Integration Kit for SAP. The exact procedures for creating. you must add the files by FTP in Binary mode (to avoid file corruption). Configuring SAP authentication for BusinessObjects Enterprise SAP authentication enables SAP users to log on to BusinessObjects Enterprise using their SAP user names and passwords.5 Performing the initial configuration Creating and applying authorizations Note: • • After copying files from CD to server. or access content. In addition. see “Configuring publishing in the Content Administration Workbench” on page 81. configuring. without storing these passwords in BusinessObjects Enterprise. administrators of the content publishing tool. The transports are binary files. So. Additional authorization objects or fields may be required. ensure that all files are writable before you import the transports. are required when carrying out common tasks with BusinessObjects XI Integration Kit for SAP. Appendix : Authorizations provides a list of SAP authorizations that. SAP authentication also allows you to preserve information about user roles in SAP. and users who view reports from within BW. and to use this role information within BusinessObjects Enterprise to assign rights to perform administrative tasks. add the CRYSTAL user to the CRYSTAL_ENTITLEMENT role. Finally. /CRYSTAL/ SECURITY Function group (FUGR) Change. BusinessObjects XI Integration Kit for SAP Installation Guide 53 . Display (02. Use transaction PFCG to create a new role named CRYSTAL_ENTITLEMENT. SUNI. and so on. SUSO. STPA. 03) Authorization for file access Activity (ACTVT) (S_DATASET) Physical file name (FILENAME) ABAP program name (PROGRAM) Authorization Check for RFC Access (S_RFC) Activity (ACTVT) Name of RFC to be protected (RFC_NAME) Type of RFC object to be protected (RFC_TYPE) User Master Maintenance: User Groups (S_USER_GRP) Activity (ACTVT) User group in user master * maintenance (CLASS) Note: For greater security. SUUS. 34) * (denotes All) * 16 BDCH. You will need this user name and its password when you connect BusinessObjects Enterprise to your SAP system. authenticate SAP users. see your SAP documentation.) Change the new role’s authorization data by setting these values for the following authorization objects: Authorization object Field Value Read. you may prefer to explicitly list the user groups whose members require access to BusinessObjects Enterprise. SU_USER. SYST. For general instruction on creating SAP user accounts and assigning authorizations through roles.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 Creating a user account for BusinessObjects Enterprise The BusinessObjects Enterprise system requires an SAP user account that is authorized to access SAP role membership lists. Use transaction SU01 to create a new SAP user account named CRYSTAL. Write (33. (These names are recommended but not required. PRGN_J2EE. click Help to open the BusinessObjects Enterprise Administrator’s Guide.5 Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise Tip: If your system policies require users to change their passwords when they first log on to the system. Accessing the SAP authentication application in BusinessObjects Enterprise After installing SAP Authentication. you must map your third-party user accounts and groups to BusinessObjects Enterprise before you can use these types of authentication. 1. select Authentication. Click Log On. log on now with the CRYSTAL user account and reset its password. the Central Management Console (CMC). When the Log On page appears. Type your User Name and Password. LDAP. then see the “Administering BusinessObjects Enterprise” section. If you changed this default virtual directory on the web server. 3. This web application is accessible through the main BusinessObjects Enterprise administration tool. The CMC Home page appears. 54 BusinessObjects XI Integration Kit for SAP Installation Guide . For this example. select Enterprise in the Authentication Type list. 4. type Administrator as the User Name. To access it from the home page of the CMC. you will need to type your URL accordingly. Windows AD. 2. To log on to the CMC Go to the following page: http://webserver/businessobjects/enterprise11/admin/ Replace webserver with the name of your BusinessObjects Enterprise web server. For an introduction to the CMC. This default Enterprise account does not have a password until you create one. however. and SAP authentication may also appear in the list. BusinessObjects XI Integration Kit for SAP installs a web application to assist you. you must provide BusinessObjects Enterprise with information about your SAP system. Windows NT. 3. Tip: When you finish these steps. 2. BusinessObjects XI Integration Kit for SAP Installation Guide 55 . type the three-character System ID (SID) of your SAP system. To add an SAP entitlement system to BusinessObjects Enterprise Go to the Authentication management area of the CMC. Ensure the Disabled check box is clear.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 Connecting to SAP entitlement systems Before you can import roles or publish BW content to BusinessObjects Enterprise. BusinessObjects Enterprise combines your System and Client information. type the client number that BusinessObjects Enterprise must use when it logs on to your SAP system. In the Client field. 1. 4. In the System field. and adds an entry to the “Logical system name” list. Tip: If an entitlement system is already displayed in the Logical system name list. click New. Click the SAP tab. BusinessObjects Enterprise uses this information to connect to SAP when it determines role memberships and authenticates SAP users. 5. you must provide information about the SAP entitlement systems that you want to integrate with BusinessObjects Enterprise. The Entitlement systems tab appears. 7. complete the Application server and System number fields as appropriate. and Language for the SAP account that you want BusinessObjects Enterprise to use when it logs on to SAP. If the entitlement system was added correctly. Click Update. select the name of the entitlement system. 1. For details. 56 BusinessObjects XI Integration Kit for SAP Installation Guide . Password. To check that an entitlement system was added correctly Click the Role Import tab. These may give you the information you need to correct the problem. the Available roles list will contain a list of roles that you can choose to import. 2.5 Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise Note: The Disabled check box allows you. ensure that the Enable SAP Authentication check box is selected. If there are no roles visible in this list. see “Server requirements for BusinessObjects Enterprise” on page 32. scroll to the bottom of the page and look for error messages. If you have not set up load balancing (or if you prefer to have BusinessObjects Enterprise log on directly to the SAP system). If you have set up load balancing such that BusinessObjects Enterprise must log on through a message server. the administrator. 8. Note: You must make the appropriate entries in the Services file on your BusinessObjects Enterprise machine to enable load balancing. 9. On the Options tab. to indicate to BusinessObjects Enterprise that a particular SAP system is temporarily unavailable. 6. complete the Message server and Logon group fields as appropriate. click the Options tab to specify the system that BusinessObjects Enterprise uses as the default (that is. For details. the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system). Note: These credentials must correspond to the user account that you created for BusinessObjects Enterprise. see “Creating a user account for BusinessObjects Enterprise” on page 53. From the Logical system name list. 10. Type the Username. Tip: If you add multiple entitlement systems. 1.) BusinessObjects XI Integration Kit for SAP Installation Guide 57 . Click the SAP tab and then click the Options tab. (To disable SAP Authentication for specific SAP Systems. 3. select that system’s Disabled check box on the Entitlement systems tab. you can enable/disable SAP Authentication and/or configure BusinessObjects Enterprise to temporarily disable SAP Authentication for SAP systems when they become unavailable. To set SAP Authentication options Go to the Authentication management area of the CMC. 2.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 Setting SAP Authentication options SAP Authentication includes a number of options that you can customize when integrating BusinessObjects Enterprise with your SAP systems. Review and modify settings as required: • Enable SAP Authentication Clear this check box if you want to disable SAP Authentication completely. For instance. BusinessObjects Enterprise keeps two separate connections open to SAP. Setting the value to -1 allows BusinessObjects Enterprise to attempt to contact the entitlement system an unlimited number of times before ceasing. 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]. if you type 2 in this field. once there has been 3 logons on one connection. For example.5 Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise • 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. For example. BusinessObjects Enterprise uses these settings to determine when to stop communicating with an SAP system that is unavailable. Setting the value to 0 limits BusinessObjects Enterprise to making one attempt to contact the entitlement system. BusinessObjects Enterprise allows a maximum of 3 failed attempts to authenticate users against any particular SAP system. For example. In the “Max failed entitlement system accesses” field. BusinessObjects Enterprise will close that connection and restart it. type the number of seconds that BusinessObjects Enterprise should wait before resuming attempts to authenticate users against the SAP system. 58 BusinessObjects XI Integration Kit for SAP Installation Guide . In the “Keep entitlement system disabled [seconds]” field. and when it should resume communication with that system. if you specified 2 for “Max concurrent connections per system” and 3 for “Number of uses per connection”. if you type 3 for “Max failed entitlement system accesses”. type the number of times that BusinessObjects Enterprise should re-attempt contacting an SAP system to fulfill authentication requests. • Number of uses per connection Use this field to specify how many logons you want to allow to the SAP system per connection.” • Max concurrent connections per system Use this field to specify how many connection you want to keep open to your SAP system at the same time. Click Update. • Concurrent users / Named Users Use this option to specify if new user accounts are configured to use concurrent user licenses or named user licenses. This provides named users with access to the system regardless of how many other people are connected. see“To change the Content folder root” on page 60.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 • 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. 500.0 but you can change it to a different folder if you want. For details. see “To import a role to BusinessObjects Enterprise” on page 61. • 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. the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system). 4. you must change it both in the CMC and the Content Administration Workbench. see “To add an SAP entitlement system to BusinessObjects Enterprise” on page 55. If this list is empty. The default is 2. select the SAP entitlement system that BusinessObjects Enterprise uses as the default (that is. You must have the appropriate licenses available on your system. For details. when users log on for the first time with valid SAP credentials. a 100 user concurrent license could support 250. • Default system In this list. This type of licensing is very flexible because a small number of concurrent licenses can support a large user base. Concurrent licenses specify the number of people who can connect to BusinessObjects Enterprise at the same time. To change this value. Note that the option you select here does not change the number or type of user licenses that you have installed in BusinessObjects Enterprise. Clear the check box to have BusinessObjects Enterprise create user accounts and user folders dynamically. BusinessObjects XI Integration Kit for SAP Installation Guide 59 . For example. or 700 users. depending on how often and how long users access BusinessObjects Enterprise. Named user licenses are associated with specific users and allow people to access the system based on their user name and password. you allow role members to log on to BusinessObjects Enterprise with their usual SAP credentials. 2. 60 BusinessObjects XI Integration Kit for SAP Installation Guide . Click the SAP tab. 6. refer to the appropriate security documents in SAP and BusinessObjects Enterprise. For more information about configuring your system for SSO. Importing SAP roles to BusinessObjects Enterprise By importing SAP roles into BusinessObjects Enterprise. BusinessObjects Enterprise generates a group. expand Enterprise system. Note: There are often many requirements for enabling SSO. see “Setting up folders and security in BusinessObjects Enterprise” on page 70. For each role that you import. 7. Expand Available systems and double-click the system that you BusinessObjects Enterprise is connecting to. 3. For example. type the folder that you want to use as the root SAP folder in BusinessObjects Enterprise.0 4. Each group is named with the following convention: [email protected] Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 1. Some of these might include using a driver and application that are SSO-capable. Click the Layout tab and in the Content base folder. You can view the new groups in the Groups management area of the CMC. The folder name that you type here is the folder that you want BusinessObjects Enterprise to begin replicating the BW folder structure from. For details. You can also use these groups to define object security within BusinessObjects Enterprise. In the BW Content Administration Workbench. and ensuring your server and web server are in the same domain. Click the Options tab and type the name of the folder in Content folder root field. Click Update. In addition. /SAP/2. 5. To change the Content folder root Go to the Authentication management area of the CMC. Single Sign On is enabled so that SAP users can be logged on to BusinessObjects Enterprise automatically when they access reports from within the SAPGUI or an SAP Enterprise Portal. For example. They have View.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 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. • Role members Role members are users who belong to “content bearing” roles. 1. On the Options tab. Additionally. View on Demand. That is. However. create necessary folders. these users belong to roles to which reports are published. To import a role to BusinessObjects Enterprise Go to the Authentication management area of the CMC. while it is possible to publish from an administrator role. regular role members cannot publish new content. The purpose of this category of user is to separate regular role members from those users with rights to publish reports. 2. select or clear the Automatically import users check box. You must import all content publishing and all content bearing roles to BusinessObjects Enterprise prior to publishing for the first time. the function of content publishing roles is only to define which users can publish content. and assign rights to those roles and folders in BusinessObjects Enterprise. it is better practice to publish only from content publisher roles. content publishing roles should not contain any content. and Schedule rights for any reports published to the roles they are members of. 3. nor can they publish updated versions of content. • Content publishers Content publishers are those users who have rights to publish content into roles. Click the SAP tab. depending on how you want BusinessObjects Enterprise to handle user accounts when you import roles: BusinessObjects XI Integration Kit for SAP Installation Guide 61 . Thus. They import the appropriate roles. Note: It is strongly recommended that you keep the activities of roles distinct. content publishers should publish to content bearing roles that are accessible to regular role members. you can subsequently view them in the Users and Folders management areas of the CMC. 2. Click Update. 6. see “Connecting to SAP entitlement systems” on page 55. Note: If this list is empty. 8. BusinessObjects Enterprise dynamically creates additional user accounts and user folders when new role members first log on to BusinessObjects Enterprise with valid SAP credentials. 1. 62 BusinessObjects XI Integration Kit for SAP Installation Guide . To check that roles and users were imported correctly 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 Enterprise. 7. On the Role import tab. For details about these options. and then click Add. You must have the appropriate licenses available on your system. Once user accounts and user folders are created. BusinessObjects Enterprise dynamically creates new user accounts and user folders when role members first log on to BusinessObjects Enterprise with valid SAP credentials. In the Available roles area. Click Update. On the Options tab. 9. see “Concurrent users / Named Users” on page 59 Note that the option you select here does not change the number or type of user licenses that you have installed in BusinessObjects Enterprise. select the role(s) that you want to import.5 Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise • Select the check box to have BusinessObjects Enterprise create a user account and a user folder immediately for each member of the role(s) that you import When you later add members to a role within SAP. Go to theBusinessObjects Enterprise InfoView: http://webserver/businessobjects/enterprise11/sap/ infoview (on Windows) http://webserver:port/businessobjects/enterprise11/sap/ desktoplaunch (on UNIX) 5. • Clear the check box to have BusinessObjects Enterprise import roles without immediately creating user accounts and user folders. select the appropriate entitlement system from the Logical system name list. select either Concurrent users or Named users depending on your licenses. 4. On Windows. You should be logged on to the InfoView as the selected user. Note: • • • • If you have configured the BW Publisher to use a local SAP Gateway. which is available through SAPNet. Click Log On. You will need this SNC name when configuring BusinessObjects Enterprise. If you have deployed the SAP Cryptographic Library (or another external security product that uses the SNC interface) you must set some additional values to integrate BusinessObjects Enterprise effectively within your secured environment. you must enable SNC for registered servers. see the SAP Library > Basis Services/Communication Interfaces > SAP Communication: Configuration > SAP Gateway.” If you have configured the BW Publisher to use the BW Publisher Service. Relevant headings include “The SAP Gateway and the SNC Interface” and “Parameterization of the SAP Gateway. the additional switches must be entered in the “Extra” field when you are prompted for more information about your BW system during installation. See “To install SAP Add-Ons” on page 38. select SAP. it must be started with the system profile parameter snc/enable). Type the user name and password of a mapped user. Click Log On. To enable SNC support within BusinessObjects Enterprise Go to the Authentication management area of the CMC.Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 5 3. 4. see the SNC User’s Guide. 5. For details. For information on how to enable SNC for registered servers. consult the RFC SDK documentation for API RfcAccept. For complete details on using SNC. Use your external SNC security product to create an external name for BusinessObjects Enterprise. BusinessObjects XI Integration Kit for SAP Installation Guide 63 . 2. 6. 1. From the Authentication Type list. Click the SAP tab. you must also configure the local SAP Gateway for SNC (for instance. then create the corresponding SNC name. Integrating with Secure Network Communication BusinessObjects XI Integration Kit for SAP supports environments that implement Secure Network Communication (SNC) for authentication and/or for data encryption between SAP components. 5 Performing the initial configuration Configuring SAP authentication for BusinessObjects Enterprise 3. the gssapi library. Tip: If you clear this check box to disable SNC at a later time. This value depends on the SNC product that you have installed. you must provide your SNC information in the definition of the RFC (Remote Function Call) destination. you must enable SNC for the registered server if you use the BW Publisher service. Consequently. The “Max.dll). Note: If this list is empty. On the SNC settings tab. This library may be referred to elsewhere as the external library. Quality of Protection 64 BusinessObjects XI Integration Kit for SAP Installation Guide . Execute transaction SM59 and set your SNC options on the Logon/Security tab. this option requires you to enable SNC in the SAP Gateway. depending on the capabilities of your SNC product. 7. available” option adjusts the quality of protection. 4. For details. select the appropriate entitlement system from the Logical system name list. Click Update. 6. see the SAP Library. Specify the level of security that BusinessObjects Enterprise should apply when it communicates with your SAP system. Value Type the absolute path to the library that contains the functions provided by your external security product. 5. In addition. Select Enable Secure Network Communication [SNC]. This option enforces the use of SNC and ensures that the BW Publisher uses SNC when users publish reports. see “Connecting to SAP entitlement systems” on page 55. the CMC retains the rest of your SNC settings. or SNC_LIB (for example. Alternatively. Field SNC library path Use the remaining fields to provide the information that corresponds to your SNC implementation. C:\WINNT\system32\gssapi32. Select Disallow insecure incoming RFC connections if you want BusinessObjects Enterprise to refuse requests that do not use SNC. Tip: The Encryption option corresponds to the level referred to as “Privacy” in some SNC products. reports run by the Report Job Server). If BW is configured to trust incoming connections from this SNC identity.e. the drivers run reports using SAP’s batch mode. then SAP users logged on to BusinessObjects Enterprise need not provide their credentials again. Instead. see “Creating and applying authorizations” on page 52 and “Scheduling a report in batch mode (with an Open SQL query)” on page 146. it is recommended that you use this feature only when you have a distributed installation of BusinessObjects Enterprise. This optional field is reserved for future use. if you create these environment variables as system environment variables on a machine that is running a combination of BusinessObjects Enterprise servers. This feature is not currently supported by BW 3. follow these steps to customize the environment variables for each Report Job Server. To ensure that the drivers run only your scheduled reports in batch mode (i. regardless of the reporting component that is actually running the report.Performing the initial configuration Configuring Data Access 5 Field SNC name of SAP system SNC name of BusinessObjects Enterprise system Value Type the SNC identity of your SAP system.0B integration. Note: SAP users who schedule reports in BusinessObjects Enterprise may require additional authorizations in SAP.. Therefore. 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. The InfoSet and Open SQL drivers can run reports using SAP’s batch or background mode when specific environment variables are set to 1. BusinessObjects XI Integration Kit for SAP Installation Guide 65 . the drivers run all reports in batch mode (including on-demand report requests from the Page Server and the Report Application Server). When these environment variables are set to 1. It allows you to specify the SNC identity that you have created for BusinessObjects Enterprise. avoid setting system environment variables on machines running combinations of BusinessObjects Enterprise servers. For details. Configuring Data Access Processing scheduled reports in SAP’s batch mode You can run scheduled reports in BusinessObjects Enterprise using SAP’s batch mode. bat Therefore. the batch file is saved on a machine named SERVER01 as: C:\Crystal Scripts\jobserver_batchmode. This is the startup command for the Report Job Server. 3. on the shortcut menu.exe" -service -name SERVER01. 4. and then executes any parameters passed to the script from the command line. Precede the default command with the full path to the jobserver_batchmode. on the shortcut menu. the command might look like this (a single line): "\\SERVER01\C$\Program Files\Business Objects\BusinessObjects Enterprise 11\win32_x86\JobServer. click Properties. Start the Central Configuration Manager (CCM) from the BusinessObjects Enterprise program group.bat" "\\SERVER01\C$\Program Files\Business Objects\BusinessObjects Enterprise 11\win32_x86\JobServer. with the following contents: @echo off set CRYSTAL_INFOSET_FORCE_BATCH_MODE=1 set CRYSTAL_OPENSQL_FORCE_BATCH_MODE=1 %* This script sets the environment variables to 1. For instance. Right-click the Crystal Report Job Server and. Right-click the Crystal Report Job Server and. locate the Command field. Save the file as jobserver_batchmode.bat to a folder on each Report Job Server machine.exe" -service -name SERVER01. 2. 6. click Stop.5 Performing the initial configuration Configuring Data Access 1.report -ns SERVER01 -objectType BusinessObjects Enterprise. On the Properties tab. To process scheduled reports in SAP’s batch mode Create a batch script (. the new startup command for the Report Job Server is: "\\SERVER01\C$\Crystal Scripts\jobserver_batchmode.bat file) in a text editor such as Notepad.Report -lib procReport restart - 7. In this example. 5.report -ns SERVER01 -objectType BusinessObjects Enterprise.Report -lib procReport restart 66 BusinessObjects XI Integration Kit for SAP Installation Guide .bat file that you saved on the Report Job Server machine. Performing the initial configuration Configuring Data Access 5 This new startup command launches the batch file first. The batch file in turn sets the required environment variables before executing the original startup command for the Report Job Server. This ensures that the environment variables available to the Report Job Server differ from the environment variables available to servers responsible for on-demand reporting (the Page Server and Report Application Server). 8. 9. Once you have changed the Command field in the CCM, click OK. 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 Enterprise administrator credentials, and ensure that the Report Job Server is enabled. Configuring SAP Logon for the Data Access Kit When users report off of data in SAP tables using Crystal Reports and the Data 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 on that 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.ini file. After the new SAP system is added, it becomes available via the Data Access Kit (provided they are authorized to use the system). Alternately, you may configure and distribute SAPlogon.ini using your standard procedures. Consult your SAP documentation for details. BusinessObjects XI Integration Kit for SAP Installation Guide 67 5 Performing the initial configuration Configuring Data Access 68 BusinessObjects XI Integration Kit for SAP Installation Guide Integrating BusinessObjects Enterprise and BW chapter When you import roles and publish content to BusinessObjects Enterprise. They are created as a result of you defining an entitlement system in BusinessObjects Enterprise. corresponding folders are created. 70 BusinessObjects XI Integration Kit for SAP Installation Guide . as administrator. Note that you. the administrator. The diagram below displays the basic folder structure that is created.You. are responsible for assigning the correct rights to these folders.6 Integrating BusinessObjects Enterprise and BW Configuration overview Configuration overview This chapter outlines the configuration steps needed to integrate BW and BusinessObjects Enterprise: • • Setting up folders and security in BusinessObjects Enterprise Configuring the BW Publisher • • • • Configuring the BW Publisher as a service Configuring the BW Publisher with a local SAP Gateway Configuring publishing in the Content Administration Workbench Configuring the SAP http request handler Before beginning this chapter. BusinessObjects Enterprise creates a logical folder structure to match your SAP system. and publishing content to BusinessObjects Enterprise. • SAP top-level folder Assign the principal Everyone to No Access for the SAP top-level folder. complete the configuration steps outlined in Chapter 5: Performing the initial configuration. Setting up folders and security in BusinessObjects Enterprise When you define an entitlement system in BusinessObjects Enterprise. do not have to create these folders. importing roles into the CMC. Click the > arrow to grant the group access to this folder. 2. The Add/Remove page appears. The Add/Remove page appears. button. BusinessObjects XI Integration Kit for SAP Installation Guide 71 . To assign publishing rights to the group From the home page of the Central Management Console. You are returned to the Rights tab. then click OK. Click Add/Remove. 2. 3. 4.. select the following rights: • • • • • 8. 3. Add objects to folder View objects Edit objects Modify the rights users have to objects Delete objects Delete instances Copy objects to another folder To assign publishing rights to a system folder In the system folder you created. Click the Add/Remove. In the Available groups list. Assign the following advanced rights. Click the group’s Access Level list and select Advanced. 6. The Advanced Rights page appears. Add objects to the folder View objects Edit objects Modify the rights users have to objects Delete objects (optional) Click OK. click Groups. Click the Rights button on the top right side of the screen. select Add/Remove Groups. click the Rights tab. select the group(s) that corresponds to the imported content publishing role(s) whose rights you want to specify. In the Select Operation list. 7.. In the Explicitly Granted column. • • • • • • • 1. 5. 1.Integrating BusinessObjects Enterprise and BW Setting up folders and security in BusinessObjects Enterprise 6 • System folders Assign the principal Publisher Advanced rights in the CMC. Click the group’s Access Level list and select Advanced. select the group(s) that corresponds to the imported content publishing role(s) whose rights you want to specify. In the Explicitly Granted column. you can publish content to BusinessObjects Enterprise from BW. In the Select Operation list. Members of this imported role now have permission to publish content from BW to BusinessObjects Enterprise. select the following rights: • • • • • 9. You are returned to the Rights tab. 72 BusinessObjects XI Integration Kit for SAP Installation Guide . “Understanding the default folder security patterns” on page 73 for an overview of the folder structure that BusinessObjects Enterprise creates when you publish content from BW to BusinessObjects Enterprise. Note: After you have set up folders and security in BusinessObjects Enterprise. 7. Continue to the next section. The Advanced Rights page appears. Add objects to the folder View objects Edit objects Modify the rights users have to objects Delete objects (optional) Click OK.6 Integrating BusinessObjects Enterprise and BW Setting up folders and security in BusinessObjects Enterprise 4. In the Available groups list. 6. 8. then click OK. Once you have completed those tasks. and “Configuring publishing in the Content Administration Workbench” on page 81. For complete details on the predefined access levels and advanced rights. click Help to see the BusinessObjects Enterprise Administrator’s Guide. select Add/Remove Groups. 5. Click the > arrow to grant the group access to this folder. complete the tasks in “Configuring the BW Publisher” on page 74. 2.that is. The administrator is responsible for assigning rights to members of different roles.0. so users can view only the reports that belong to their roles. BusinessObjects XI Integration Kit for SAP Installation Guide 73 . That is. the Client number. Security is set on each report object.To do this. the following rights should be assigned in the Content Administration Workbench. the SAP. BusinessObjects Enterprise creates a Content folder for each role that content is published to. BusinessObjects Enterprise creates Role folders (imported as groups into BusinessObjects Enterprise) as necessary.Integrating BusinessObjects Enterprise and BW Setting up folders and security in BusinessObjects Enterprise 6 Understanding the default folder security patterns When you publish content to BusinessObjects Enterprise from SAP. and system (<SID>) folders . BusinessObjects Enterprise automatically creates the remaining hierarchy of roles. when a role is published from BW. and the name of the role. and reports. folders. The diagram that follows shows how BusinessObjects Enterprise organizes content when you publish two roles from one BW system: • • • • BusinessObjects Enterprise creates the top-level folders . BusinessObjects Enterprise organizes your Crystal reports in folders that are named according to the System ID.when you define an entitlement system. The diagram below displays the basic folder structure that is created. Note: It is strongly recommended that you keep the activities of roles distinct. publishing roles should not contain any content. it is better practice to publish only from publisher roles. while it is possible to publish from an administrator role. the function of publishing roles is only to define which users can publish content. 74 BusinessObjects XI Integration Kit for SAP Installation Guide . Click OK. The BW Publisher service will start instances of the BW Publisher as required. Members of these roles will now be able to view scheduled instances of reports published to other roles and will be able to refresh reports published to roles that they are a member of. 3. In the Content Administration Workbench. Click the Layout tab. Set Default security policy for role folders to View On Demand. you can configure the BW Publisher in one of two ways: • • Start the BW Publisher using a service on a BusinessObjects Enterprise machine. Set Default security policy for reports to View. 5.6 Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher Content folders BusinessObjects Enterprise imports a group for each role that is added to the entitlement system as defined in the CMC. Thus. Start the BW Publisher using a local SAP Gateway to create BW Publisher instances. On Windows. Additionally. To ensure that suitable default rights are granted to all members of a contentbearing role. 4. These settings are reflected in BusinessObjects Enterprise for all content roles. publishers should publish to content bearing roles that are accessible to regular role members. For example.rpt files) individually or in batches from BW to BusinessObjects Enterprise. 1. expand Enterprise system and then expand Available systems. 6. Double-click the system you want. That is. roles that have content published to them. grant the following rights in the Content Administration Workbench for each entitlement system that is defined in BusinessObjects Enterprise. 2. Configuring the BW Publisher The BW Publisher allows you to publish Crystal reports (. perform the following procedures: • • “Starting the BW Publisher” on page 75 “Configuring a destination for the BW Publisher service” on page 77. using the BW Publisher as a service. For UNIX installations of BusinessObjects Enterprise. it establishes a connection with the SAP Gateway Service that you specified when you ran the BusinessObjects XI Integration Kit for SAP setup program. However. Starting the BW Publisher On Windows. On UNIX. See “Configuring publishing in the Content Administration Workbench” on page 81 for details.Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher 6 You must select the configuration method based on the requirements of your site. the BW Publisher automatically spawns additional publishers to meet the demand. your system configuration will vary slightly as you must manually start the required number of BW Publisher instances. For details. see “Distributing the BW Publisher installation” on page 45. run the BW Publisher script to create a publisher instance or instances to handle publishing requests. For more information on the CCM. (See “Recommended initial installation” on page 34 for details. Once the BW Publisher service or script starts. When you start the BW Publisher service it creates a publisher instance to service publishing requests from your BW system.) BusinessObjects XI Integration Kit for SAP Installation Guide 75 . If the volume of publishing requests increases. It is recommended that you start one publisher instance. see “Selecting your BW Publisher configuration” on page 24. However. you must configure publishing in the Content Administration Workbench. follow the instructions for installing the BW Publisher as a service. use the Central Configuration Manager (CCM) to start the BW Publisher service. in most cases it is recommended that you start the BW Publisher using an SAP Gateway. after considering the advantages and disadvantages of each configuration. Once you have configured the BW Publisher in BusinessObjects Enterprise. For information on adding system redundancy using multiple BW Publishers. Configuring the BW Publisher as a service To enable publishing of reports from BW to BusinessObjects Enterprise. consult the BusinessObjects Enterprise Administrator’s Guide. Right-click the Crystal BW Publisher Service and. and the value for this field is 3300. To check that the BW Publisher has started on Windows Open the Windows Task Manager dialog box. portnum is the port number of the Gateway Service. 2. the instance number is 00. 2. (Simultaneously press the Ctrl +Alt-Del keys. To start the BW Publisher on UNIX Log on to your UNIX system under the crystal user account you created for your BusinessObjects Enterprise installation.exe and bcepub.exe processes are running. 3. select Run. 4. and has opened a TCP/IP connection with the BW Gateway Service. 2. click Start. Run the following script to start a publisher instance: crystal_root/bwcepub num -aPROGID -gGWHOST -xGWSERVICE where: 76 BusinessObjects XI Integration Kit for SAP Installation Guide . (Under the Windows Start menu. This command establishes if the BW Publisher has started correctly.6 Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher 1. To start the BW Publisher service on Windows Start the Central Configuration Manager (CCM) from the BusinessObjects Enterprise program group. BWPub_portnum is the port number of the BW Publishing service. 5. For example.) Type the following command. IP_Gateway is the IP address of the machine hosting the BW Gateway Host. where ## represents the instance number of your SAP Gateway. Open a command window. and then click Task Manager. substituting the port number of the SAP Gateway Service for portnum. type 33## for portnum. The result of this command should be: TCP IP_BW_Publisher:BWPub_portnum IP_Gateway:portnum where: • • • • 1. Type cmd in the run dialog box. 6. Ensure that the bwcepubsvc. Typically. IP_BW_Publisher is the IP address of the machine hosting the BW Publishing service. Include the quotation marks: netstat -an | find "portnum" 1. on the shortcut menu.) Click the Processes tab. click Test connection. The connection test attempts to contact your BW Publisher service. BusinessObjects XI Integration Kit for SAP Installation Guide 77 . 1. Tip: You cannot view all of these fields until you provide the Connection type. See “Configuring a destination for the BW Publisher service” on page 77. If the RFC destination cannot contact your BW Publisher service. You will need this value when you configure the RFC destination on your BW system. GWSERVICE Configuring a destination for the BW Publisher service To enable the BW Publisher. and may not contain spaces. The Program ID can take any value. 2. • • GWHOST is the name of your Gateway Host. the result is a list showing how long it took to contact the service on each of four attempts. After saving your settings. using the central instance of BW as your Gateway Host in every case. Click Create and provide the values described in the following table. but must be 64 characters or fewer. the result is a connection error. If you wish to publish to multiple BusinessObjects Enterprise systems from BW. but the same Gateway host and Gateway service. is the port number of the Gateway Service. 3.Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher 6 • • • crystal_root is the root crystal directory where you installed BusinessObjects Enterprise and BusinessObjects XI Integration Kit for SAP. If the RFC destination is properly configured and can communicate with your BW Publisher service. If you have a BW cluster. Record the exact value you specify here for the Program ID. PROGID is the Program ID of the RFC Destination for the BW Publisher. num is the number of publisher instances to start. Note: Use this procedure if your BW publisher is running on UNIX. configure the RFC destination on each server. To create the required RFC destination (TCP/IP connection) Execute transaction SM59. The Program ID is case-sensitive. You must use unique Program IDs for each destination. you must configure an RFC destination on your BW server to communicate with the BW Publisher service. which allows you to display and maintain RFC destinations. create a separate RFC destination for the BW Publisher service in each BusinessObjects Enterprise system. Select “Registered Server Program. 78 BusinessObjects XI Integration Kit for SAP Installation Guide . Description Activation Type Program ID Type a short description of the destination. See “To start the BW Publisher on UNIX” on page 76. For details about SNC. see “Integrating with Secure Network Communication” on page 63. • On UNIX. RFC destination Use a descriptive name. You must use the same Program ID that you specified: • On Windows. when you installed BusinessObjects XI Integration Kit for SAP on your BusinessObjects Enterprise machines. Field Value Note: Do not use the name CRYSTAL_PUBLISHER unless you do not have the Content Administration Workbench. Program ID should not contain any spaces. Tip: • • Program ID is case-sensitive.” Type the descriptive string used to identify the process associated with this destination. See “Configuring publishing in the Content Administration Workbench” on page 81 for details. you must provide your SNC options on the Logon/Security tab for the CRYSTAL_PUBLISHER destination. If you plan to enforce Secure Network Communication (SNC) between SAP and BusinessObjects Enterprise. when you started the BW Publisher. For more information on RFC destinations and TCP/IP connection types. See “Recommended initial installation” on page 34.6 Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher Note: • • The publishing process will not work until the destination is working successfully. consult your SAP documentation. Connection type Type T (for TCP/IP connection) and press Enter. You must use the same BW server name here that you specified when you installed BusinessObjects XI Integration Kit for SAP on your BusinessObjects Enterprise machines. you may use this symbolic name instead. the instance number is 00. For details. If you have defined a symbolic name for this port (such as sapgw##). (See “Recommended initial installation” on page 34. • “Distributing information over the Web” on page 26 Configuring the BW Publisher with a local SAP Gateway To enable publishing of reports from BW to BusinessObjects Enterprise. Often. see the SAP installation instructions included on your SAP Presentation CD. Note: It is not recommended that you use this configuration if BusinessObjects Enterprise is installed on UNIX. using a local SAP Gateway. “Configuring a destination for the BW Publisher” on page 80. Installing a local SAP Gateway A local SAP Gateway must be installed on the machine where you installed the BW Publisher. see: • “Recommended initial installation” on page 34. You must use the same port number or symbolic name here that you specified when you installed BusinessObjects XI Integration Kit for SAP on your BusinessObjects Enterprise machines. perform the following procedures: • • “Installing a local SAP Gateway” on page 79. BusinessObjects XI Integration Kit for SAP Installation Guide 79 .) It is recommended that an SAP BASIS administrator perform the installation of one of these SAP Gateways. For example. type sapgw##. For up-to-date instructions on installing a local SAP Gateway.Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher 6 Field Gateway host Value Type the name of your BW server. Gateway service Type the port number that the Gateway host is listening on. For details. enter the name of the central instance of BW. where ## represents the instance number of your SAP Gateway. and the value for this field is sapgw00. • “Publishing Reports” on page 25. see: • “Recommended initial installation” on page 34. Using this method on UNIX could result in unpredictable system behavior. If you have a BW cluster. 2. which must be a valid absolute directory path. use regedit to verify the TMP and TEMP registry entries under the HKEY_CURRENT_USER\Environment subkey. This file includes specific version and Service Pack requirements for application servers. consult the platforms_EN. SAP components. the result is a list showing how long it took to contact the Gateway on each of four attempts. both registry entries are set to C:\WINNT\TEMP Configuring a destination for the BW Publisher To enable the BW Publisher. 1. see “Integrating with Secure Network Communication” on page 63. 80 BusinessObjects XI Integration Kit for SAP Installation Guide . If the RFC destination is properly configured and can communicate with your BW Publisher. etc. Both registry entries should hold the same string value. operating systems. To create the required RFC destination (TCP/IP connection) Execute transaction SM59. Tip: You cannot view all of these fields until you provide the Connection type. After have installed the SAP Gateway. you must provide your SNC options on the Logon/Security tab for the CRYSTAL_PUBLISHER destination. If the RFC destination cannot contact your BW Publisher. Note: • • The publishing process will not work until the destination is working successfully. After saving your settings. Here you will create a TCP/IP connection. Click Create and provide the values described in the following table. consult your SAP documentation. Typically. you must configure an RFC destination to provide BW with the location of the machine where you have installed the local SAP Gateway and the BW Publisher. 3.txt file included with your product distribution. The connection test attempts to contact your BW Publisher on the local SAP Gateway. If you plan to enforce Secure Network Communication (SNC) between SAP and BusinessObjects Enterprise. For more information on RFC destinations and TCP/IP connection types.6 Integrating BusinessObjects Enterprise and BW Configuring the BW Publisher For a detailed list of tested environments for BusinessObjects XI Integration Kit for SAP. For details about SNC. click Test connection. replace it with an absolute directory path. which allows you to display and maintain RFC destinations. the result is a connection error. If either entry’s value contains the %USERPROFILE% variable. Publish content from BW to BusinessObjects Enterprise. Define which roles can publish to each BusinessObjects Enterprise system. Type a short description of the destination. Select “Start on Explicit Host. Connection type Description Activation Type Program Type T (for TCP/IP connection) and press Enter. and have configured the BW Publisher.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 Field RFC destination Value Use a descriptive name.” For example: boserver01 Gateway service Type sapgw##. and the value for this field is sapgw00 Configuring publishing in the Content Administration Workbench Once you have set up SAP authentication.exe Tip: Use the MS-DOS short path name. Target host Type the fully qualified domain name or IP address of the machine where you installed the BW Publisher. BusinessObjects XI Integration Kit for SAP Installation Guide 81 .0\bin\bwcepub.privatedomain.com Gateway host Type the name of the machine where you installed the SAP Gateway. This should be the same machine as the “Target host. Note: Do not use the name CRYSTAL_PUBLISHER unless you do not have the Content Administration Workbench. the instance number is 00. as shown here. the value is: C:\Progra~1\Common~1\Busine~1\3.” Type the absolute path to the BW Publisher program (bwcepub.exe). Set up connections to the BusinessObjects Enterprise systems where content is published. where ## represents the instance number of your SAP Gateway. perform the functions outlined in this section to enable publishing. These instructions will allow you to: • • • • Set appropriate authorizations for different users of the Content Administration Workbench. If you installed it in the default directory on Windows. For example: ceserver01. See “Configuring publishing in the Content Administration Workbench” on page 81 for details. Typically. and performing report maintenance. who can view. Examples of descriptive role names would include BOE_CONTENT_PUBLISHERS and BOE_SYSTEM_ADMINISTRATORS. 82 BusinessObjects XI Integration Kit for SAP Installation Guide . consult “Controlling Administrative Access” in the BusinessObjects Enterprise Administrator’s Guide. Tip: In BusinessObjects Enterprise XI you can assign an administrative user either full system administration rights or a subset of those rights. publishing reports. Creating roles in BW for designated content publishers When you are configuring BW for integration with BusinessObjects Enterprise. you must first set up SAP Authentication and import the roles. modify. These tasks include defining BusinessObjects Enterprise systems. For more information. who belong to content-bearing roles and who can view reports. BusinessObjects Enterprise content publishers. and (optionally) delete reports from BW. To modify the rights that these new roles (or any of your existing roles) are granted in BusinessObjects Enterprise. BusinessObjects Enterprise administrators. who are able to perform all tasks within Content Administration Workbench.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench Users who can access the Content Administration Workbench There are three types of users who may access the Content Administration Workbench: • • • Content consumers. You can then modify the rights of each imported role through the Central Management Console in BusinessObjects Enterprise. It is suggested that you label any new roles you create in a descriptive manner. publish. assess whether or not your current role structure allows you to quickly designate particular BW users as BusinessObjects Enterprise content publishers or system administrators. They do not have authorization to do anything other than view reports. Activate. RSCR_MAINT_PUBLISH X Change.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 For details on creating roles. RELE ’’ Execute (16) Create new. Configuring access to the Content Administration Workbench For each type of user that can access the Content Administration Workbench. see your SAP documentation. Display (02. 03) &NC& DELE. Delete. you must apply the appropriate set of authorizations within BW. see the following sections: • • • “Importing SAP roles to BusinessObjects Enterprise” on page 60. 03. Change. 06) Create new. 06. Delete (01. For more information on the use of roles in administering content. 23. Authorizations for administrative users Authorization object Field S_RFC RFC_TYPE RFC_NAME ACTVT S_TCODE S_TABU_CLI S_TABU_DIS S_BTCH_JOB S_RS_ADMWB ZCNTADMCES ZCNTADMJOB ZCNTADMRPT TCD CLIIDMAINT ACTVT DICBERCLS JOBACTION JOBGROUP ACTVT ACTVT ACTVT ACTVT Values FUGR /CRYSTAL/CE_SYNCH. 39) RSADMWBOBJ WORKBENCH BusinessObjects XI Integration Kit for SAP Installation Guide 83 . SUNI Execute (16) /CRYSTAL/RPTADMIN. Delete (01. 02. The authorizations are listed in the following tables. “Setting up folders and security in BusinessObjects Enterprise” on page 70. “Understanding the default folder security patterns” on page 73. 07. Display. Maintain. SH3A. Check (03. 06) Display. SH3A. be aware that deleting a report in BW also deletes the report in BusinessObjects Enterprise. Maintain. Delete) 01.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench Authorizations for content publishers Authorization object Field S_RFC RFC_TYPE RFC_NAME ACTVT S_TCODE S_BTCH_JOB S_RS_ADMWB ZCNTADMCES ZCNTADMJOB ZCNTADMRPT TCD JOBACTION JOBGROUP ACTVT ACTVT ACTVT ACTVT Values FUGR /CRYSTAL/CE_SYNCH. RELE ’’ Execute (16) Display (03) (New. Activate. See “Setting up folders and security in BusinessObjects Enterprise” on page 70 for information on granting rights in BusinessObjects Enterprise. 06 Display. However. Check (03. 23. Authorizations for content consumers Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT S_TCODE S_RS_ADMWB ZCNTADMRPT TCD ACTVT RSADMWBOBJ ACTVT Values FUGR SH3A. 07. SUNI Execute (16) /CRYSTAL/RPTADMIN DELE. If publishers do not have sufficient rights to delete reports in BusinessObjects Enterprise. an error results. SUNI Execute (16) /CRYSTAL/RPTADMIN Execute (16) WORKBENCH Display (03) 84 BusinessObjects XI Integration Kit for SAP Installation Guide . 39) Delete (optional) (06) Edit (optional) (02) RSADMWBOBJ WORKBENCH Granting content publishers the right to delete reports in the BW Content Administration Workbench is optional. 5. On the System tab. On the RFC Destinations tab. click the Insert Row button. 3. Type the name of the machine that is running your BusinessObjects Enterprise CMS. Only one BusinessObjects Enterprise system can be the default. 2. the default system is indicated with a green checkmark. In the list that appears. doubleclick the name of the RFC destination. To add a destination. 4. Next. Click Verify CE definition. type CMSNAME:PORT 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. select Enterprise System. and can log on to this BusinessObjects Enterprise system using the Crystal entitlement user account. 6.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 Defining a BusinessObjects Enterprise system You must create a system definition within the Content Administration Workbench for each BusinessObjects Enterprise system to which you want to publish reports. 1. add each RFC destination that is associated with this BusinessObjects Enterprise system. This test verifies that BW can contact the specified BW Publisher. 8. To add a BusinessObjects Enterprise system Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. Click Save. enter the following values: • • • Type a descriptive name in the Alias field. BusinessObjects XI Integration Kit for SAP Installation Guide 85 . Select the destination you just added by clicking the gray box to the left of its name. test the destination. See “Distributing the BW Publisher installation” on page 45 for more information. From the Operations pane. Avoid using spaces or special characters. If you configured your CMS to listen on a port other than the default. Double-click Add new system. 7. Note: A BusinessObjects Enterprise system may have multiple destinations to add system redundancy. as these characters need special treatment when the alias name is used while configuring Enterprise Portals. In the list of all available systems. ) Or type the name of your own custom viewer application. select the languages of reports that will be published to this BusinessObjects Enterprise system.businessobjects. On the Languages tab. 10.NET. Type viewreport.com:8080 • Path If you followed a default installation of BusinessObjects Enterprise for .do to use the default viewer for BusinessObjects Enterprise installations that use the Java version of the InfoView.NET configuration. Provide an alternate value only if you have customized your web environment and the location of the BusinessObjects Enterprise web content files. type: businessobjects/enterprise11/sap/desktoplaunch/apps This path is essentially the virtual path that your web server uses when referring to the sap subfolder of your BusinessObjects Enterprise web content. 86 BusinessObjects XI Integration Kit for SAP Installation Guide . For a installation that uses a Java application server. enter the following values: • • Protocol Type http (unless the web server that is connected to BusinessObjects Enterprise is configured to use https). Web server host and port Type the fully qualified domain name or IP address of the web server that hosts your BusinessObjects Enterprise InfoView. • Viewer application Type the name of your viewer application. On the HTTP tab. Do not include a forward slash at the beginning or at the end of this entry. For example: boserver01. (All UNIX installations of BusinessObjects Enterprise use the Java InfoView.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 9. type report/report_view.aspx to use the default viewer. If BusinessObjects Enterprise was installed on Windows using the default ASP. include the port number. type: businessobjects/enterprise11/sap/infoview If you followed a default installation of BusinessObjects Enterprise for Java. (This will not delete the actual reports. You are now able to publish reports to BusinessObjects Enterprise from BW. and click the Ok button. and republish the roles and reports. 15. Click the Ok button at the bottom to save your settings and create the BusinessObjects Enterprise system in the Content Administration Workbench. 12. Use the Roles tab to add the content-bearing roles that you want to associate with this BusinessObjects Enterprise system. Then click Reassign Roles. 14. Once you have configured a BusinessObjects Enterprise system. See “Importing SAP roles to BusinessObjects Enterprise” on page 60 for more information. To change the default security levels for all roles and content published to this BusinessObjects Enterprise. BusinessObjects XI Integration Kit for SAP Installation Guide 87 . Note: Each role can publish to only one BusinessObjects Enterprise system. delete the roles folders and shortcuts in BusinessObjects Enterprise. Select the roles that you want to publish to this BusinessObjects Enterprise system. This folder contains shortcuts to the reports published under that role. set the default security settings for content published to this BusinessObjects Enterprise system. A list of roles available to add to this BusinessObjects Enterprise system is displayed. Note: • • A folder is created automatically in BusinessObjects Enterprise for each role published to that system.) Then change the security settings here. Click the Insert Row button. Consult your BusinessObjects Enterprise Administrator’s Guide for more information about these security settings. Next. click Cancel to return to the Roles tab. If the roles that you want to add to this BusinessObjects Enterprise are not displayed in the list.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 11. changing the default security levels here will not affect the security levels of published role folders or reports. Click the Layout tab. and select the security settings that are used by default for reports and roles folders. 13. select Publish reports. double-click Select reports and roles to publish. To find content saved to your BW system. Publishing roles or reports 1. 2. Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. You can use the Content Administration Workbench to publish individual reports. A dialog box designed to help you filter the available roles and reports appears. Note: The BusinessObjects Enterprise System list contains all available systems defined on this BW system. 88 BusinessObjects XI Integration Kit for SAP Installation Guide . 3. From the Operations pane. Only a user who has the authorizations granted to a Crystal content publisher (see “Creating and applying authorizations” on page 52) can use the Content Administration Workbench to publish and maintain reports. 4. or you can publish all reports saved to a particular role. you can publish it using the Content Administration Workbench. select the BusinessObjects Enterprise system or systems containing content that you want to display. From the BusinessObjects Enterprise System list.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench Publishing reports using the Content Administration Workbench After a report has been saved to BW. For example. only the roles that match what you type here are displayed.) • Role filter If you type text in this box. (The remaining options are SAP reserved terms. type *revenue*. executable” to display only reports that have been published. Click Ok. For example.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 5. Next. Selecting the blank option displays all reports. Leave the field blank to display all reports. Use * as a wildcard character to match any number of characters. 6.) • Object status Select “ACT Active. BusinessObjects XI Integration Kit for SAP Installation Guide 89 . not executable” to display only reports which have not been published. filter your results to limit the number of reports and roles that will be displayed. (The remaining options are SAP reserved terms. type “d*”. to display all reports whose description contains the word revenue. • Report description If you type text in this box. Use * as a wildcard character. Use these options: • Object version Selecting “A: active” displays all reports that can be published. only the reports whose descriptions match what you type here are displayed. Use + as a wildcard to match 0 or 1 characters. Select “INA Inactive. to display all roles beginning with the letter d. Content is not available for publishing until it has been activated using the BW Administration Workbench. If the item is a report. then the role shows as yellow (active). Yellow: The item is active. Each item in the hierarchy is labeled with a red. Red: The item is SAP content. 90 BusinessObjects XI Integration Kit for SAP Installation Guide . yellow. the item is available for publishing. but all of the rest are green (published). If the item is a role or a BusinessObjects Enterprise system. If the item is a BusinessObjects Enterprise system or a role. or green dot. but not published. all reports in that item are published. then all content is active and at least one item that the role or system contains has not been published. and is not available for publishing using the Content Administration Workbench. For example.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench The list of reports that meet your criteria appears in the right-hand panel. • • • Green: The item is fully published. Items higher in the hierarchy reflect the status of the items that they contain. with the least favorable condition percolated to the top of the hierarchy. The reports are arranged in a hierarchy: BusinessObjects Enterprise system > Roles on that system > Reports saved to the role. if one report in a role is yellow (active). It is recommended that you publish reports in the background to improve system responsiveness. BusinessObjects XI Integration Kit for SAP Installation Guide 91 . It is recommended that you schedule all reports (or roles containing these reports). 1. Note: Only active (green or yellow) reports or roles are available to be published. Click Publish. Click Refresh to update the display of the status of BusinessObjects Enterprise systems. Publishing reports periodically. roles.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 7. clear the role (or system) checkbox. select the system. as described in “Publishing roles or reports” on page 88. To publish all o f the reports in a role. Tip: To view a report. See “Scheduling background publishing” on page 91 for details. all reports contained in that role (or system) are selected. To clear this selection. To see which queries are used by the report. See “Updating the status of reports” on page 93 for details. select the roles or reports to publish. To use this option. To publish a report immediately Use the Content Administration Workbench to find the reports or roles that you want to publish. 2. 3. 8. right-click the report and select Used Queries. synchronizes the report information between BW and your BusinessObjects Enterprise system. and then click Refresh. In the Content panel. and reports in the Content Administration Workbench. click “In background” instead of Publish. Click In background to publish the selected items as a background process. either immediately or as a scheduled job. Scheduling background publishing Publishing reports in the background. Note: When you select a role (or a system). 9. You can also manually synchronize roles and reports using the Update status option of the Report Maintenance operation. The “Define Background Job” transaction appears. To publish all roles on a BusinessObjects Enterprise system. Note: Reports published in the background are processed as system resources become available. select the role. Select the reports that you want to publish. as scheduled jobs. right-click the report and select View. conserves system resources. 2. 1. 92 BusinessObjects XI Integration Kit for SAP Installation Guide . Click Save to save the period values. click Start Condition. To publish the item at a scheduled time. Use the Period Values dialog to specify how often the job should run. Updating system information for published reports The BW Publisher uses the SAP system information entered here to update the data source of published reports. To publish the item immediately. 3. 4. 3. To update system information Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. Click In background to publish the selected items as a background process. The job appears under Scheduled jobs in the Operations tree. 4. and then Period values. 2. Click Date/Time and specify when the job should start. double-click Set BW source parameters.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 4. A user with administrative privileges may need to release this job (using transaction SM37) before it is published. Under SAP system settings. click Display ->Change. and then update the information about the listed system. The “Define Background Job” transaction appears. select the roles or reports to publish. 5. as described in “Publishing roles or reports” on page 88. and then click Save again to save the job. The job appears under Scheduled jobs in the Operations tree. From the Operations pane. or the central BW instance if you prefer a load balancing configuration. and then click Immediate and save the job. 7. Note: Only active (yellow) reports or roles are available to be published. select Publish reports. Click Periodic job. In the Content panel. click Start Condition. To change an existing BW system. You can choose to use the local BW application server. 6. 1. To publish a report as a scheduled job Use the Content Administration Workbench to find the reports or roles that you want to publish. A user with administrative privileges may need to release this job (using transaction SM37) before it is published. To select all reports and roles on a BusinessObjects Enterprise system. and add information about the new system. 5. Click Save. select the system. 2. You must correct the problem before you can update the status of reports on that system in BW. 4. 3. Use the dialog that appears to filter the list of displayed BusinessObjects Enterprise systems. 1. Maintaining reports Report maintenance tasks include synchronizing information about reports between BusinessObjects Enterprise and BW (Update status). BusinessObjects XI Integration Kit for SAP Installation Guide 93 . Select the reports you want to update from the displayed list. double-click Update Status. and click Delete. to synchronize information. If BW cannot contact a BusinessObjects Enterprise system. BW connects to the BusinessObjects Enterprise systems containing the reports you have indicated. first select any existing entries. deleting unwanted reports (Delete reports). it returns an error message. roles. as described in “Publishing roles or reports” on page 88. Updating the status of reports If you make a change to a published report on a BusinessObjects Enterprise system (such as changing which role a report is published to). To update reports Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. or you can manually update the status of the report using the Report Maintenance tool. Click Version Check. and updating reports migrated from previous versions of BusinessObjects Enterprise (Post-migration). 6. Under Report Maintenance. To add a new BW system (or a load-balanced system). and reports. Then click New Entries. You can schedule a publishing job to periodically synchronize BusinessObjects Enterprise and BW (see “Scheduling background publishing” on page 91). the change is not reflected in BW until you synchronize BusinessObjects Enterprise and BW.Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench 6 5. you may encounter an error. it returns an error message. and reports. To migrate reports Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. Select the systems you want to migrate. you must update all of your published reports. 2. Under Report Maintenance. to delete the reports. 4. These reports are SAP content. Note: You cannot delete reports using the Content Administration Workbench if their status dot is red. Select the reports you want to delete from the displayed list. 94 BusinessObjects XI Integration Kit for SAP Installation Guide . double-click Post-migration All BusinessObjects Enterprise systems containing reports that need to be migrated are displayed. 1. BW connects to the BusinessObjects Enterprise systems containing the reports you have indicated. 1. and then click Execute post migration. Use the dialog that appears to filter the list of displayed BusinessObjects Enterprise systems. select the system. 2. Completing a report migration After you migrate from Crystal Enterprise 10 to BusinessObjects Enterprise XI. 3. 3. roles. To delete reports Execute the transaction /crystal/rptadmin to access the Content Administration Workbench. double-click Delete reports. Click Delete reports. You must correct the problem before you can delete these reports. Under Report Maintenance. 5. To select all reports and roles on a BusinessObjects Enterprise system. Only users who have been granted the authorizations necessary to delete reports on both BW and the BusinessObjects Enterprise system can remove reports. as described in “Publishing roles or reports” on page 88. but not on the BusinessObjects Enterprise system where that report is published.6 Integrating BusinessObjects Enterprise and BW Configuring publishing in the Content Administration Workbench Deleting reports Deleting a published report from BW using the Content Administration Workbench also deletes the report from BusinessObjects Enterprise. If BW cannot contact a BusinessObjects Enterprise system. Note: If a user has rights to delete a report on BW. Integrating BusinessObjects Enterprise and BW Configuring the SAP http request handler 6 You must update all reports and roles on a system. You may have to manually activate this service after creating it. If BW cannot contact a BusinessObjects Enterprise system. BW is able to route the viewing request over the Web appropriately. Configuring the SAP http request handler To enable viewing of reports in BW or using a Crystal iView. Then. You must correct the problem before you can update these reports and complete the system migration to version XI. Note: You must have rights to copy source content if you are migrating reports. BW connects to the BusinessObjects Enterprise systems containing the reports you have indicated. when a BW user opens a Crystal report from within the SAPGUI or an SAP Enterprise Portal. it returns an error message. you must configure BW to use the http request handler that is included as part of the Crystal Content Administration Workbench transport. Use the transaction SICF to access the list of virtual hosts and services active on your BW system. Create a new node named ce_url under BW in the default_host hierarchy and add /CRYSTAL/CL_BW_HTTP_HANDLER to the handler list. to update the reports. BusinessObjects XI Integration Kit for SAP Installation Guide 95 . 6 Integrating BusinessObjects Enterprise and BW Configuring the SAP http request handler 96 BusinessObjects XI Integration Kit for SAP Installation Guide . Working with Web Content and Sample Reports chapter . The InfoView helps organize your reports into logical groups—using folders—and allows you to search for and view reports. you can choose the BusinessObjects Enterprise InfoView or a web desktop designed by someone in your company. on the File menu. Once you have found the reports you want to look at. you can access all the Crystal reports that have been saved in your SAP roles or included with BW’s predefined Business Content. By analyzing or modifying these samples. When you use BusinessObjects XI Integration Kit for SAP. To analyze the sample reports Start Crystal Reports and. 2. For more information about the InfoView.7 Working with Web Content and Sample Reports BusinessObjects Enterprise InfoView BusinessObjects Enterprise InfoView The BusinessObjects Enterprise InfoView serves as a window to Crystal Reports on your company’s existing intranet or Internet site. click Open. the InfoView offers report viewers with printing and exporting capabilities. click Help to see the BusinessObjects Enterprise InfoView for SAP User’s Guide. and Open SQL Reports. you can create reports that display your SAP data in ways that offer the greatest value to your SAP users. Through theBusinessObjects Enterprise InfoView for SAP. 1. InfoSet Reports. Setting up the sample reports The Data Access Kit includes sample reports that have been saved with SAP data in order to demonstrate some of the ways in which you can use Crystal reports to extract and format your SAP data. 98 BusinessObjects XI Integration Kit for SAP Installation Guide . To access the BusinessObjects Enterprise InfoView for SAP Go to the main page of the InfoView for SAP: http://webserver/businessobjects/enterprise11/sap/infoview (on Windows) http://webserver:port/businessobjects/enterprise11/sap/ desktoplaunch (on UNIX) Replace webserver with the name of the web server that is set up for BusinessObjects Enterprise. Locate the sample reports folder (usually C:\Program Files\Business Objects\Integration Kit for SAP 11\Sample Reports). You can configure your own personal desktop settings and save your favorite reports. you will see up to three subfolders—BW Query Reports. Depending on which database drivers you installed. Each subfolder corresponds to a specific Data Access Kit driver. on the File menu. click Open. Locate the sample reports folder (usually C:\Program Files\Business Objects\Integration Kit for SAP 11\Sample Reports\). Browse the subfolders’ contents. and then click Open. Click Finish. select your SAP system. select “Use current parameter values” and click OK.Working with Web Content and Sample Reports Setting up the sample reports 7 3. and the Record Selection Formula Editor—to see how the SAP data has been incorporated and utilized in the report. The SAP System Logon dialog box appears. Browse the subfolders’ contents. Password. the Refresh Report Data dialog box prompts you to “Use current parameter values” or “Prompt for new parameter values. 4. To refresh the sample reports against your SAP system Note: Depending on your current SAP configuration. 2. click Refresh Report Data. type the number appropriate to your SAP system.” If you are unfamiliar with report parameters. Use the other tools in Crystal Reports—such as the Field Explorer. 8. you may or may not retrieve data when you refresh the sample reports against your SAP system. the Formula Workshop. The SAP System Logon dialog box prompts you for User Data. If you want the SAP Communication Library to create trace files for all client/server communication (for troubleshooting purposes). your SAP system will not appear in the Available SAP systems list. 9. Note: If the report contains parameters. 5. then click Next. The report appears in the Preview tab of Crystal Reports. Type your usual logon information in the User Name. The report appears in the Preview tab of Crystal Reports. Then. select the Generate RFC trace files check box. 5. 7. Click the Design tab see how the sections and groups have been used to create the report’s layout. 6. On the Report menu. select the report that you want to see. 4. BusinessObjects XI Integration Kit for SAP Installation Guide 99 . In the Available SAP systems list. select the report that you want to see. and Language fields. Note: If your SAP administrator has not configured SAP Logon. Start Crystal Reports and. In the Client field. and then click Open. 1. click Next. 3. 7 Working with Web Content and Sample Reports Verifying configuration options in Crystal Reports The report should now be refreshed with data from your SAP system. To locate the record selection formula. These global changes affect your default reporting options. To view configuration options On the Crystal Reports File menu. see “To view configuration options” on page 100. click Report > Selection Formulas > Record. To locate these configuration options in the Report Designer. therefore. Your SAP system may contain thousands of tables. However. then it is likely that the report is using tables and fields that are empty in your SAP system. These configuration changes generally improve the experience of reporting off SAP data. if no data appears in the report. Click the Database tab. you may notice slightly altered behaviors when you report off data sources other than SAP. By editing the report’s record selection formula. you may be able to alter the report so that it coincides with your SAP data. 2. each with a predefined. Verifying configuration options in Crystal Reports The setup program changes some configuration options of your Report Designer so that it can take advantage of the drivers’ advanced features. The driver installation configures the Report Designer to list tables and fields by both name and description. The configuration changes ensure that you can select specific tables for a report without having to search through an immense list. non-descriptive name. and you receive no database error messages. The Database tab shows your current configuration 100 BusinessObjects XI Integration Kit for SAP Installation Guide . 1. click Options. use an underscore (_) to denote a single character. Add wildcards to select multiple queries or InfoSets: use a percentage sign (%) to denote any number of characters. To see both names and descriptions of tables and fields. Note: InfoSets and ABAP queries are treated as Stored Procedures. so verify that this check box is selected. • 5. Separate distinct names with commas. In the Data Explorer area. If the number of queries or InfoSets in SAP exceeds this limit (which is by default 8000). select the check boxes for the types of data that you want to make available to the report. Use the following techniques when filtering: • • • Type full or partial names of tables. that there is a limit to the number of objects that can be displayed in the Data Explorer.Working with Web Content and Sample Reports Verifying configuration options in Crystal Reports 7 3. Use the Table name LIKE and/or the Owner LIKE fields to select only a subset of the available data types. Note. select Both. 4.) Clear the field and click OK to proceed without filtering. (The % and _ wildcards correspond respectively to the * and ? wildcards used within Windows. in the Tables and Fields area. however. BusinessObjects XI Integration Kit for SAP Installation Guide 101 . you may receive an Out of Memory error or a blank Data Explorer. 6. Click OK. 7 Working with Web Content and Sample Reports Verifying configuration options in Crystal Reports 102 BusinessObjects XI Integration Kit for SAP Installation Guide . Defining Security for the Open SQL driver chapter . In previous versions of BusinessObjects XI Integration Kit for SAP. the restrictions you apply affect all users who access SAP using the same client used to define the restrictions. refresh. in order to design. whether to design. easily reverse this default behavior with the Security Definition Editor’s Global Lock feature. By default. which initially restricts users from accessing all SAP tables. the Open SQL driver provides an open reporting environment where there are no data access restrictions. Data access restrictions that you define using the Security Definition Editor are applied on a per-client basis. refresh. and tables containing data clusters (for instance. or schedule a Crystal report against R/3 or BW. see “Configuring transports” on page 48. (You can. The restrictions that you specify are enforced whenever a user attempts to connect to SAP with the Open SQL driver. For details. which you import into your SAP system when you set up the Data Access Kit. PCL2).) If you need to deploy a security model that regulates users’ access to SAP data.8 Defining Security for the Open SQL driver Security Definition Editor overview Security Definition Editor overview When you deploy the Data Access Kit component and distribute the database drivers. or schedule a Crystal report. use the Security Definition Editor (transaction /CRYSTAL/RLS) to restrict data access at the table level and at the row level. follow the instructions in “Migrating your existing security model” on page 105 before continuing. This chapter includes the following sections: • • • • • “Migrating your existing security model” on page 105 “Choosing your table-level security model” on page 105 “Customizing authorizations for specific tables” on page 107 “Defining table authorizations by group” on page 112 “Applying row-level security” on page 112 Note: The Security Definition Editor is provided by the Security Definition Editor transport. data access restrictions were client-independent. users require access to all of the tables referred to by the report. Thus. see “Choosing your table-level security model” on page 105. For details. To preserve restrictions that you defined using earlier versions of this tool. cluster tables. 104 BusinessObjects XI Integration Kit for SAP Installation Guide . That is. The Security Definition Editor defines security for transparent tables. you allow SAP users to access the data stored within your SAP R/3 and BW systems. however. pool tables. you can authorize users to access particular tables on a table-by-table basis. the Global Lock is disabled by default. To migrate data access restrictions Enter the transaction /CRYSTAL/RLS in your SAP system. BusinessObjects XI Integration Kit for SAP Installation Guide 105 . 3. A dialog appears. select Import Global Data. Import these data restrictions before using / CRYSTAL/RLS to create or modify additional restrictions. • Global Lock enabled This closed security model initially denies all users access to all tables. 1.Defining Security for the Open SQL driver Migrating your existing security model 8 Migrating your existing security model To continue to use the data access restrictions that you defined using a previous version of BusinessObjects XI Integration Kit for SAP (using the ZRLS transaction). Additionally. Your global. 2. To customize the model to match your current SAP security conventions. you must import these restrictions into client-dependent form using /CRYSTAL/RLS. you can specify a list of custom functions that users can still report off when the Global Lock is enabled. To customize the model to match your current SAP security configuration. Click Yes. import these restrictions once for each client. Any changes you made using /CRYSTAL/RLS will be overwritten when you import the global restrictions. warning you that importing these restrictions will overwrite any restrictions you have defined using /CRYSTAL/RLS. you can prevent users from accessing particular tables on a table-by-table basis. Choosing your table-level security model For enhanced flexibility. For details. client-independent data access restrictions are imported. To apply your global data access restrictions to additional clients. Under the Extras menu. the Security Definition Editor provides a Global Lock feature. see “Customizing authorizations for specific functions” on page 111 for details. When you first deploy the Data Access Kit. which allows you to define the basis of your data access security model in one of two ways: • Global Lock disabled This open security model initially provides all users with access to all tables. thereby allowing or disallowing data access in order to match your SAP security conventions. execute transaction /CRYSTAL/RLS.8 Defining Security for the Open SQL driver Choosing your table-level security model Once you have enabled or disabled the Global Lock. To enable/disable the Global Lock From the SAPGUI. select the “Allow access only to the tables specified above” option. see “Customizing authorizations for specific tables” on page 107. 1. You now have two options: • • If you want to enable the Global Lock. ensure that the “Allow access only to the tables specified above” option is not selected. Now that you’ve chosen an open or closed basis for your security model. If you want to disable the Global Lock. The Security Definition Editor appears. 2. 106 BusinessObjects XI Integration Kit for SAP Installation Guide . you can refine the security model by customizing data access authorizations for particular tables. you can customize authorizations for particular users and tables. For details. The ZTABCHK authorization is being used to secure the VBAK table from all but a particular subset of users. In other words. if the Global Lock is disabled. or reuse an existing one. that table is withheld from all users—regardless of your Global Lock settings. you will need to allow all or some users to access particular tables. In either case. you may need to customize the data access authorizations for one or more SAP tables. you incorporate the new authorization object into your current configuration of user profiles or roles. 1. whether you want to secure a table or to permit access to a table. The Security Definition Editor screen appears BusinessObjects XI Integration Kit for SAP Installation Guide 107 . or see the SAPGUI Help for more information on creating authorization objects. create an authorization object called ZTABCHK that consists of one authorization field called TABLE. users will be unable to design or refresh reports against the SAP system. by associating an authorization object with an SAP table.) Alternatively. You must then use the authorization object according to your usual SAP security conventions in order to provide particular users with access to the SAP table. From the SAPGUI.) Then. Finally. execute transaction /CRYSTAL/RLS. 2. To customize authorizations for a specific table Create a new authorization object. using the Security Definition Editor. For this example. Note: Use transaction SU21 to create the authorization object. you may need to prevent all or some users from accessing tables that contain sensitive data. Essentially.Defining Security for the Open SQL driver Customizing authorizations for specific tables 8 Customizing authorizations for specific tables Whether you have enabled or disabled the Global Lock feature. (You can customize a new authorization object. If the Global Lock is enabled. you associate the authorization object with the table in question. you define that table as an exception to the Global Lock settings that you have made within the Security Definition Editor. you must use an authorization object for that purpose. (Otherwise. once you’ve associated an authorization object with a table. 3. Click Create.8 Defining Security for the Open SQL driver Customizing authorizations for specific tables You will now associate your new authorization object with an SAP table. For this example. type VBAK. In the Table name field. type the name of the table whose security definition you will customize. The “Authorization entries” screen appears 108 BusinessObjects XI Integration Kit for SAP Installation Guide . Defining Security for the Open SQL driver Customizing authorizations for specific tables 8 4. Click OK. 6. 5. Click Create. For details on the second option—Reference to an already defined table or group—see “Defining table authorizations by group” on page 112. Click Reference to an authorization object. The “Authorization Object entry” dialog box appears. BusinessObjects XI Integration Kit for SAP Installation Guide 109 . The “Authorization field values” screen appears. Click Create. For this example. type ZTABCHK. type the name of the authorization object that you created in step 1.8 Defining Security for the Open SQL driver Customizing authorizations for specific tables The “Authorization Object entry” screen appears. In the Authorization object name field. 110 BusinessObjects XI Integration Kit for SAP Installation Guide . 8. 7. Click Save. you can specify a list of functions that users are able to call. 12. and the SAP authorization model that you have already deployed. BusinessObjects XI Integration Kit for SAP Installation Guide 111 . Customizing authorizations for specific functions When the Global Lock feature is disabled. For instance. the VBAK table must be specified. Following your usual procedure. you can specify a list of functions that are exceptions to the Global Lock. ensure that your new authorization holds the name of the correct database table in its TABLE field value. following this example.Defining Security for the Open SQL driver Customizing authorizations for specific functions 8 9. report designers essentially have the freedom to call any function on the SAP system. The end result is that the authorization is added to the master user data. enable the Global Lock. That is. For this example. This restricts users from calling any functions on the SAP system. Note: Regardless of the method you use. you can accomplish this in various ways: • • Attach the new authorization object to a new role that you in turn add to each user’s security profile. incorporate the new authorization object into your configuration of user profiles or roles. Attach the new authorization object to a new profile that you in turn add to each user’s security profile. Depending on the version of R/3 that you are using. type the name of the table whose security definition you want to customize. you would apply the ZTABCHK authorization object to the subset of users who need to access the VBAK table. To restrict the functions available to report off. 11. In the Field value list. In the /CRYSTAL/AUTHFCN table. type VBAK. Exit the Security Definition Editor. In this example. Use the /CRYSTAL/ RLSFCN transaction you created in “Customizing authorizations for specific tables” on page 107 to access the /CRYSTAL/AUTHFCN table. 10. You have now associated your customized authorization object with a specific SAP table. so the database drivers can adhere to your customized data access restrictions. • You can reference multiple tables to a group table that acts as a security template. execute transaction /CRYSTAL/RLS and specify a nonexistent table name in the Editor. To enable this type of restriction. you specify the Customer values for those customers whose Sales records the user is permitted to view. use the Security Definition Editor to define an additional level of security for the individual rows of data. you create an authorization object and use the Security Definition Editor to associate the object with the Customer field in the Sales table. When the user designs or refreshes reports against the Sales table. while at the same time limiting a subset of those users to a certain portion of the table’s data. 112 BusinessObjects XI Integration Kit for SAP Installation Guide . row-level security is based on a particular field within a table. Then. To create a group table. when you apply the new authorization object to each user’s profile or role. You can now share security levels by referencing existing tables to this security template. To accomplish this.8 Defining Security for the Open SQL driver Defining table authorizations by group Defining table authorizations by group The Security Definition Editor provides two ways for you to quickly define table authorizations for tables that require similar levels of security: • You can reference a table to any other table whose data access authorizations you have already defined. Applying row-level security Sometimes table-level security does not allow you to secure data in a way that corresponds with the security privileges of your SAP users: you may need to grant all users access to a particular table. In general. The “Reference to an already defined table or group” option is provided in the “Select authorization entry type” screen. the Editor assumes instead that you are creating a group or template. data is returned only for those customers that you have specified. you might need to prevent users from seeing data for all customers within a Sales table.) The main screen listing all the definitions will show the table type as group. (When the specified table does not exist. For instance. which appears in the Security Definition Editor when you create an authorization entry for a table. Note: The “Reference to an already defined table or group” option is not supported in SAP BW at this time. Defining Security for the Open SQL driver Applying row-level security 8 Essentially. 1. In the Table name field. For this example. 4. type the name of the table that contains the rows you want to secure. This is an efficient way to apply an authorization to multiple tables with similar names simultaneously. You then apply the new authorization object to the roles or profiles of SAP users who need to access any of the table’s data. Use * to specify zero or more characters and + to specify one character. For this example. This authorization is being used to secure the GLT0 table based on the values in the BUKRS (Company Codes) field. by associating an authorization object with a field within an SAP table. In the “Authorization entries” screen. You can use authorization objects or custom functions. Note: You can now use wildcards to specify the table name. 3. you define that table as an exception to the Global Lock settings that you have made within the Security Definition Editor. you can create an authorization object and use the Security Definition Editor to associate the object with one of the table’s fields. you specify the rows of data that each user is permitted to access. BusinessObjects XI Integration Kit for SAP Installation Guide 113 . When you apply the authorization object. You must then use the authorization object according to your usual SAP security conventions in order to provide particular users with access to rows of data within the SAP table. Securing rows using authorization objects In order to define row-level security for tables. Note: Use transaction SU21 to create the authorization object. or see the SAPGUI Help for more information on creating authorization objects. click Create. There are two ways to secure rows within a table. type GLT0. To define row-level security using an authorization object Create a new authorization object. create an authorization object called Z_BUKRS that consists of one authorization field called BUKRS. once you’ve associated an authorization object with a field. In other words. Click Create. 5. the parent table is secured from all users—regardless of your Global Lock settings. Execute transaction /CRYSTAL/RLS to access the Security Definition Editor. 2. you would type Z_BUKRS. For instance. on the shortcut menu. Click OK to access the “Authorization Object entry” screen. 7. Click Save. The “Authorization field values” screen appears. Exit the Security Definition Editor. For this example. In the Field value list. following this example. click Possible entries. In the “Select authorization entry type” screen. BUKRS) to insert it along with the required equals sign (=). 9. For this example. you enter 114 BusinessObjects XI Integration Kit for SAP Installation Guide . right-click the Field value list and. you would type =BUKRS. 10.8 Defining Security for the Open SQL driver Applying row-level security 6. 11. type the equals sign (=) and the name of the field that you want to secure. 12. In the Authorization object name field. you would apply the Z_BUKRS authorization object to each user who needs to access rows of data within the GLT0 table. Click Create. Double-click the desired field (in this case. Tip: To view a list of available fields. 13. Following your usual procedure. click Reference to an authorization object. 8. apply the new authorization object to the profiles or roles of the appropriate users. When you apply the authorization object. type the name of the authorization that you created in step 1. This is an efficient way to apply an authorization to multiple tables with similar names simultaneously. or instead of using authorization-based restrictions for tables. Use * to specify zero or more characters and + to specify one character. type PA0000 to secure the rows in that table. BusinessObjects XI Integration Kit for SAP Installation Guide 115 . Attach the new authorization to a new profile that you in turn add to each user’s security profile. 1. Mapping incompatible types results in a failure at runtime. Depending on the version of R/3 that you are using. For this example. For example. you can secure rows using custom security exits. so the database drivers can adhere to your customized data access restrictions. and the SAP authorization model that you have already deployed. type the name of the data table whose rows you want to secure. The following example shows how to map table fields to function parameters in a custom security exit. That is. you can map table fields to function parameters so that you can define the call to one function to handle the post filtering for any table. do not link a function parameter for a date to a number field.Defining Security for the Open SQL driver Applying row-level security 8 the appropriate Company Code values into the BUKRS authorization field. Make mappings between compatible types. 3. Note: • • You must give a value (either constant or field-mapped) for all nonoptional parameters. you can accomplish this in various ways: • • Attach the new authorization to a new role that you in turn add to each user’s security profile. Click Create. In the Table name field. The end result is that the authorization is added to the master user data. To define row-level security using a custom security exit Execute transaction /CRYSTAL/RLS. Note: You can now use wildcards to specify the table name. Securing rows using custom security exits In addition to. 2. thereby specifying the Company Codes that the specified user is authorized to access. 116 BusinessObjects XI Integration Kit for SAP Installation Guide . 4. type the name of the function that you want to use to secure the table. For this example. Click Custom exit. type HR_CHECK_AUTHORITY_INFTY. In the Function name field. The “Edit custom function security exit mappings” window appears.8 Defining Security for the Open SQL driver Applying row-level security The “Authorization entries” screen appears. This screen lists the authorization entries (if any) that are currently applied to the table. 5. and then click Transfer. Field name ‘0000’ =PERNR =SUBTY You are returned to the “Authorization entries” screen. the driver checks the appropriate field(s) in the table. The field values you mapped are passed as parameters to the function you selected. which now indicates that there is an active custom security exit for this table. Click Save. In this example make the entries listed in the table below: Imported parameter name INFTY PERNR SUBTY 7.Defining Security for the Open SQL driver Applying row-level security 8 6. specify a value or field to map to that parameter. For each necessary parameter. in this example HR_CHECK_AUTHORITY_INFTY. When a user attempts to access a table secured by a custom security exit. BusinessObjects XI Integration Kit for SAP Installation Guide 117 . 8 Defining Security for the Open SQL driver Applying row-level security 118 BusinessObjects XI Integration Kit for SAP Installation Guide . Troubleshooting chapter . you can temporarily disable a connection between BusinessObjects Enterprise and an SAP entitlement system. user forums. see the BusinessObjects Enterprise Administrator’s Guide (admin.businessobjects.com/search/ Locating and generating log files You can create and view several log files to help determine the cause of errors. and Knowledge Base articles: http://support. 120 BusinessObjects XI Integration Kit for SAP Installation Guide . and so on. For details about these system log files. Note: See the BusinessObjects Enterprise Administrator’s Guide (admin. go to the Authorization management area. To temporarily disable a connection to an SAP entitlement system In the CMC. In particular. or Crystal Reports. Formatted Reporting. Troubleshooting BusinessObjects Enterprise In the CMC. path mapping. and check notes 509786 and 510045. BusinessObjects Enterprise. search the online SAP Notes for items related to BW. The core BusinessObjects Enterprise server components log information by default to the logging directory of your BusinessObjects Enterprise installation. This may be useful to maintain the responsiveness of BusinessObjects Enterprise in cases such as the scheduled down time of an SAP entitlement system.9 Troubleshooting Troubleshooting overview Troubleshooting overview For the latest troubleshooting information from SAP. 2. 4. Select the Disabled check box. Click Update. 3. select the system you want to disable.pdf in the doc directory of your BusinessObjects Enterprise product distribution) for a number of sections devoted to general system troubleshooting. You can also check out the Business Objects Customer Support technical support web site for white papers. In the Logical system name list. 1. such as web server configuration.pdf in the doc directory of your BusinessObjects Enterprise product distribution). Click the SAP tab. report processing. 5. files and updates. search for notes in the BW-BEXET-FR or XX-PART-CRR application areas. there may be a problem with the driver installation. The InfoSet driver is supported only for versions 4. you may be trying to use the InfoSet driver to access a system that is older than R/3 4. or required files may have been deleted since installation.6c. Run the Crystal Reports–SAP Edition installation again. Reports.6c and later of SAP R/3.Troubleshooting Troubleshooting your InfoSet driver installation 9 Troubleshooting your InfoSet driver installation This section describes some common installation and configuration issues in order to assist you in troubleshooting an installation of the InfoSet driver. tables. and functions If the SAP data source does not appear when you create a new report. Errors when connecting to SAP If an error message indicates that the RSAQ_REMOTE_FUNCAREA_CATALOG function module was not found. BusinessObjects XI Integration Kit for SAP Installation Guide 121 . 9 Troubleshooting Troubleshooting your InfoSet driver installation 122 BusinessObjects XI Integration Kit for SAP Installation Guide . Transport Files chapter . the InfoSet Connectivity transport. A subset of these transports are available with BusinessObjects XI Integration Kit for SAP. Object /CRYSTAL/BC /CRYSTAL/OPENSQL /CRYSTAL/OSQL_EXECUTE /CRYSTAL/ OSQL_TYPEPOOLPROG /CRYSTAL/OSQL_TYPEPOOLS /CRYSTAL/OSQL_UTILS ZSSI ZSEGREPORT Type Package Function group Program Program Program Program Authorization object class Authorization object Description Development class Open SQL functions Helper program Helper program Helper program Helper program Helper program Reporting authorization objects Reporting authorization object /CRYSTAL/OSQL_AUTH_FORMS Program 124 BusinessObjects XI Integration Kit for SAP Installation Guide . the Cluster Definition transport. To determine which transports you need to import. Note: When checking for possible installation conflicts. the Crystal Content Administration Workbench transport. use the ANSI transports. the Authentication Helpers transport. The transports_EN. There are two different sets of the transports: Unicode compatible transports and ANSI transports. If you are running a BASIS system of 6. see “Configuring transports” on page 48. use the Unicode compatible transports. the Row-level Security Definition transport.10 Transport Files Overview Overview BusinessObjects XI Integration Kit for SAP includes seven transports: the Open SQL Connectivity transport. and the BW Query parameter personalization transport. Open SQL Connectivity transport The Open SQL Connectivity transport enables the drivers to connect to and report off the SAP system.20.20 or later. The contents of each transport are listed here.txt file located in the transports directory on the installation CD lists the Unicode compatible and ANSI transport files. If you are running a BASIS system earlier than 6. ensure that none of the object names already exists in your SAP system. Transport Files Overview 10 Object /CRYSTAL/ OSQL_CLU_ACTKEY_ENTRY /CRYSTAL/OSQL_FCN_PARAM /CRYSTAL/ OSQL_FCN_PARAM_FIELD /CRYSTAL/ OSQL_OBJECT_ENTRY /CRYSTAL/ OSQL_RLS_CHK_ENTRY /CRYSTAL/ OSQL_RLS_FCN_ENTRY /CRYSTAL/ OSQL_RLS_VAL_ENTRY ZCLUSTDATA ZCLUSTID ZCLUSTKEY ZCLUSTKEY2 /CRYSTAL/AUTHCHK /CRYSTAL/AUTHFCN /CRYSTAL/AUTHKEY /CRYSTAL/AUTHOBJ /CRYSTAL/AUTHREF ZSSAUTHCHK ZSSAUTHOBJ ZSSAUTHKEY ZSSAUTHREF ZSSAUTH FCN Type Table Table Table Description Cluster meta data Function meta data Function meta data Table meta data Table meta data RLS meta data RLS meta data RLS meta data Cluster meta data Cluster meta data Cluster meta data Cluster meta data RLS meta data RLS meta data RLS meta data RLS meta data RLS meta data Old RLS meta data Old RLS meta data Old RLS meta data Old RLS meta data Old RLS meta data /CRYSTAL/OSQL_FIELD_ENTRY Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table BusinessObjects XI Integration Kit for SAP Installation Guide 125 . 6c and later. Object /CRYSTAL/BC /CRYSTAL/FLAT /CRYSTAL/QUERY_BATCH /CRYSTAL/ QUERY_BATCH_STREAM Type Package Function group Program Program Description Development class InfoSet wrapper functions Batch mode execution Streaming batch mode execution. Do not import this transport if you are running R/3 4. which is a tool that serves as a graphical interface to the /CRYSTAL/AUTH tables in the Open SQL Connectivity transport.10 Transport Files Overview InfoSet Connectivity transport The InfoSet Connectivity transport enables the InfoSet driver to access InfoSets. Row-level Security Definition transport This transport provides the Security Definition Editor. This transport is compatible with R/3 4.6a or earlier. Object /CRYSTAL/BC /CRYSTAL/TABMNT Type Package Function group Description Development class Function group for table maintenance view for function restrictions Main program Include program containing the module definitions Include program containing the subroutine definitions Table maintenance definition Table maintenance definition /CRYSTAL/RLSDEF /CRYSTAL/ RLS_INCLUDE1 /CRYSTAL/ RLS_INCLUDE2 TDDAT [/CRYSTAL/ AUTHFCN] TVDIR [/CRYSTAL/ AUTHFCN] Program Program Program Table contents Table contents 126 BusinessObjects XI Integration Kit for SAP Installation Guide . see “Security Definition Editor overview” on page 104. For details on using the Security Definition Editor. and BW systems. R3. For details on using the Cluster Definition Tool. Cluster Definition transport This transport provides the Cluster Definition tool. Object ZCIMPRBG ZCRBGTOP ZCDD Type Program Program Transaction Description Main program Include program Main program transaction Authentication Helpers transport This transport provides the Single Sign On enhancement for the InfoSet driver. see the “Reporting off clusters” section of the BusinessObjects XI Integration Kit for SAP User’s Guide. Object /CRYSTAL/BC /CRYSTAL/SECURITY Type Package Function group Description Development class Security helper functions BusinessObjects XI Integration Kit for SAP Installation Guide 127 . This enhancement frees users from having to enter their credentials more than once to access any of the BusinessObjects Enterprise. Cluster tables are already defined in the DDIC.Transport Files Overview 10 Object /CRYSTAL/AUTHFCNS Type Definition of transport and maintenance object Transaction Transaction Description Table maintenance definition /CRYSTAL/RLS /CRYSTAL/RLSFCN Main program transaction Helper transaction called internally by main program. Note: ABAP data clusters are not the same as cluster tables. This tool enables you to build up a metadata repository for ABAP data cluster definitions. These definitions provide the Open SQL driver with the information it requires in order to report off these data clusters. 10 Transport Files Overview Crystal Content Administration Workbench transport This transport provides content administration functionality for BW systems. Object /CRYSTAL/BC /CRYSTAL/ CL_BW_HTTP_HANDLER /CRYSTAL/ OBJECT_STATUS_DOM /CRYSTAL/OBJ_POLICY_DOM /CRYSTAL/OBJECT_STATUS /CRYSTAL/OBJ_POLICY /CRYSTAL/CE_SYNCH /CRYSTAL/CA_MSG /CRYSTAL/CE_SYNCH_FORMS /CRYSTAL/CONTENT_ADMIN /CRYSTAL/ CONTENT_ADMIN_CLASS_D /CRYSTAL/ CONTENT_ADMIN_CLASS_I /CRYSTAL/ CONTENT_ADMIN_CTREE /CRYSTAL/ CONTENT_ADMIN_FORMS /CRYSTAL/ CONTENT_ADMIN_MODULES /CRYSTAL/ CONTENT_ADMIN_PAIS /CRYSTAL/ CONTENT_ADMIN_PBOS /CRYSTAL/ CONTENT_ADMIN_TAB_FRM /CRYSTAL/ CONTENT_ADMIN_TOP Type Package Class Domain Domain Data element Data element Function group Program Program Program Program Program Program Program Program Program Program Program Description Development class Multi CE-aware HTTP request handler Report activity CE object security Report activity CE object security Publisher stubs Message class Status messages Program component Program component Program component Program component Program component Program component Program component Program component Program component Program component Program component 128 BusinessObjects XI Integration Kit for SAP Installation Guide . It is available only as a Unicode compatible transport. Transport Files Overview 10 Object /CRYSTAL/PUBLISH_WORKER /CRYSTAL/ PUBLISH_WORKER_DISP /CRYSTAL/ PUBLISH_WORKER_DISP_I /CRYSTAL/ PUBLISH_WORKER_FORMS /CRYSTAL/ PUBLISH_WORKER_PROC /CRYSTAL/ PUBLISH_WORKER_PROC_I /CRYSTAL/ PUBLISH_WORKER_SCREEN /CRYSTAL/CA_DEST /CRYSTAL/CA_JOB /CRYSTAL/CA_JOB2 /CRYSTAL/CA_LANG /CRYSTAL/CA_PARM /CRYSTAL/CA_ROLE /CRYSTAL/CA_SYST /CRYSTAL/MENU_TREE_ITEMS /CRYSTAL/REPORT_ID /CRYSTAL/RPTADMIN /CRYSTAL/EDIT_REPORT /CRYSTAL/EDIT_REPORT ZSSI ZCNTADMCES ZCNTADMRPT ZCNTADMJOB Type Program Program Program Program Program Program Program Table Table Table Table Table Table Table Structure Table Transaction Program Description Program component Program component Program component Program component Program component Program component Program component Application state Application state Application state Application state Application state Application state Application state Application state Application state Main program transaction Wrapper for report edit Function Group Functions for report edit Authorization Crystal Authorizations object class Authorization object Authorization object Authorization object CE operations Report operations Background job operations BusinessObjects XI Integration Kit for SAP Installation Guide 129 . 10 Transport Files Overview BW Query parameter personalization transport This transport provides support for personalized and default parameter values in reports based on BW queries. Object /CRYSTAL/BC /CRYSTAL/PERS_VAR /CRYSTAL/PERS_VALUE /CRYSTAL/PERS Type Package Structure Structure Description Development class Variable definition Value definition Function Group Personalization functions 130 BusinessObjects XI Integration Kit for SAP Installation Guide . Authorizations appendix . 02. From each authorization object. depending upon your individual implementation. you must create an authorization and define the appropriate field values. RFC1. For procedural details that are specific to your version of SAP. 06 * USER_ROLE denotes the name of any role that the user belongs to. You can enter multiple values in this field 132 BusinessObjects XI Integration Kit for SAP Installation Guide . Additional authorization objects or fields may be required. SUNI. The following sections describe the required authorizations and provide you with the necessary field values. RSCR. Note: • • The information in this appendix is provided as a guideline only.A Authorizations overview Authorizations overview This appendix provides a list of SAP authorizations that. You then apply the appropriate authorizations to the profiles (or roles) of your SAP users. are required when carrying out common tasks with BusinessObjects XI Integration Kit for SAP. refer to your SAP documentation. in our experience and in our test environment. The ZSEGREPORT authorization object belongs to the ZSSI object class. which is installed when you import the BusinessObjects XI Integration Kit for SAP transport files needed to support Open SQL queries. RZX2 16 USER_ROLE* 01. RZX0. Actions in BW From within Crystal Reports Logging on to an SAP server Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT S_USER_AGR ACT_GROUP ACTVT Values FUGR SUSO. SH3A. You can enter multiple values in this field * QUERY_OWNER denotes the name of the owner of the query. If you specify a specific value. ** For INFO_AREA.Actions in BW A Creating a new report from a query in a BW role Authorization object S_USER_AGR S_RFC Field ACT_GROUP ACTVT RFC_TYPE RFC_NAME ACTVT S_CTS_ADMI S_RS_COMP CTS_ADMFCT RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT Values USER_ROLE* 01. Enter * to report off of queries with any owner. or COMP_ID enter * to denote any value. 02. INFO_CUBE. you can only report off of queries that contain these info areas. If you specify a name. BusinessObjects XI Integration Kit for SAP Installation Guide 133 . 06 FUGR RS_PERS_BOD 16 TABL INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 * USER_ROLE denotes the name of any role that the user belongs to. cubes. you can report off only those queries with that owner. and component IDs. A Actions in BW Opening an existing report from a BW role Authorization object S_RFC Field RFC_TYPE RFC_NAME Values FUGR SUSO. RSOB 16 INFO_AREA** INFO_CUBE** ACTVT S_RS_COMP RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT * QUERY_OWNER REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 denotes the name of the owner of the query from which you are creating the report. you can only report off of queries that contain these info areas. and component IDs. cubes. SUNI. INFO_CUBE. you can only report off of queries with this owner. If you enter the name of the query owner. RZX0. SH3A. or COMP_ID enter * to denote any value. RZX2. RSCR. ** For INFO_AREA. If you specify a specific value. RS_PERS_BOD. RFC1. Enter * to denote any query owner. Previewing or refreshing a report Authorization object S_RS_COMP Field RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT Values INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 134 BusinessObjects XI Integration Kit for SAP Installation Guide . / CRYSTAL/PERS. Actions in BW A * QUERY_OWNER denotes the name of the owner of the query from which you are creating the report. ** For INFO_AREA. or COMP_ID enter * to denote any value. If you enter the name of the query owner. INFO_CUBE. and component IDs. ** For INFO_AREA. If you specify a specific value. INFO_CUBE. BusinessObjects XI Integration Kit for SAP Installation Guide 135 . If you specify a specific value. you can only report off of queries with this owner. If you enter the name of the query owner. cubes. and component IDs. or COMP_ID enter * to denote any value. you can only report off of queries that contain these info areas. Enter * to denote any query owner. you can only report off of queries that contain these info areas. Verifying the database (refreshing table definitions in a report) Authorization object S_RS_COMP Field RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT * QUERY_OWNER Values INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 denotes the name of the owner of the query from which you are creating the report. you can only report off of queries with this owner. Enter * to denote any query owner. cubes. you can only report off of queries that contain these info areas. or COMP_ID enter * to denote any value. INFO_CUBE. If you enter the name of the query owner. you can only report off of queries with this owner. ** For INFO_AREA. 02. cubes. If you specify a specific value.A Actions in BW Setting the location of the data source Authorization object S_RS_COMP Field RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT * QUERY_OWNER Values INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 denotes the name of the owner of the query from which you are creating the report. Enter * to denote any query owner. and component IDs. 06 TABL Preparing a report for translation while saving to BW Authorization object S_USER_AGR S_CTS_ADMI Field ACT_GROUP ACTVT CTS_ADMFCT Values USER_ROLE* 01 TABL 136 BusinessObjects XI Integration Kit for SAP Installation Guide . Saving a report to a BW role Authorization object S_USER_AGR S_CTS_ADMI Field ACT_GROUP ACTVT CTS_ADMFCT Values USER_ROLE* 01. Actions in BW A Saving a report and simultaneously publishing it to BusinessObjects Enterprise Authorization object S_USER_AGR S_CTS_ADMI S_RS_COMP Field ACT_GROUP ACTVT CTS_ADMFCT RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT * QUERY_OWNER Values USER_ROLE* 01 TABL INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 denotes the name of the owner of the query from which you are creating the report. ** For INFO_AREA. If you specify a specific value. 06 TABL BusinessObjects XI Integration Kit for SAP Installation Guide 137 . or COMP_ID enter * to denote any value. Enter * to denote any query owner. INFO_CUBE. you can only report off of queries that contain these info areas. you can only report off of queries with this owner. If you enter the name of the query owner. cubes. Saving a report as an iView Authorization object S_USER_AGR S_CTS_ADMI Field ACT_GROUP ACTVT CTS_ADMFCT Values USER_ROLE* 01. and component IDs. 02. 138 BusinessObjects XI Integration Kit for SAP Installation Guide .A Actions in BW Exporting a report as a . cubes. If you enter the name of the query owner.ivu file Authorization object S_USER_AGR S_CTS_ADMI S_GUI Field ACT_GROUP ACTVT CTS_ADMFCT ACTVT Values USER_ROLE* 01 TABL 61 Starting the Business Explorer Query Designer Authorization object S_RS_COMP Field RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT S_CTS_ADMI CST_ADMFCT * QUERY_OWNER Values INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 TABL denotes the name of the owner of the query from which you are creating the report. If you specify a specific value. Enter * to denote any query owner. ** For INFO_AREA. or COMP_ID enter * to denote any value. INFO_CUBE. you can only report off of queries that contain these info areas. and component IDs. you can only report off of queries with this owner. ** For INFO_AREA. you can only report off of queries with this owner. cubes. SUNI 16 INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 INFO_AREA** 0CRM_OLVM DATA 03 denotes the name of the owner of the query from which you are creating the report. STOM Viewing an SAP BW report on demand Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT S_RS_COMP RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT S_RS_ODSO RSINFOAREA RSODSOBJ RSODSPART ACTVT * QUERY_OWNER Values FUGR SYST. and component IDs. If you specify a specific value. If you enter the name of the query owner. you can only report off of queries that contain these info areas.Actions in BW A From within the BusinessObjects Enterprise InfoView for SAP Logging on to BusinessObjects Enterprise with SAP credentials Authorization object S_ADMI_FCD Field S_ADMI_FCD Values STOR. Enter * to denote any query owner. INFO_CUBE. BusinessObjects XI Integration Kit for SAP Installation Guide 139 . RSOB. or COMP_ID enter * to denote any value. If you enter the name of the query owner. ** For INFO_AREA. INFO_CUBE. Scheduling a report Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT S_RS_COMP RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID Values FUGR SYST. cubes. or COMP_ID enter * to denote any value. and component IDs. Enter * to denote any query owner. you can only report off of queries that contain these info areas.A Actions in BW Refreshing a report from the viewer Authorization object S_RS_COMP Field RSINFOAREA RSINFOCUBE RSZCOMPTP RSZCOMPID S_RS_COMP1 RSZCOMPID RSZCOMPTP RSZOWNER ACTVT S_RS_ODSO RSINFOAREA RSODSOBJ RSODSPART ACTVT * QUERY_OWNER Values INFO_AREA** INFO_CUBE** REP COMP_ID** COMP_ID** REP QUERY_OWNER* 16 INFO_AREA** 0CRM_OLVM DATA 03 denotes the name of the owner of the query from which you are creating the report. SUNI 16 INFO_AREA** INFO_CUBE** REP COMP_ID** 140 BusinessObjects XI Integration Kit for SAP Installation Guide . If you specify a specific value. you can only report off of queries with this owner. RSOB. ** For INFO_AREA. If you specify a specific value. or COMP_ID enter * to denote any value. you can only report off of queries with this owner.Actions in BW A Authorization object S_RS_COMP1 Field RSZCOMPID RSZCOMPTP RSZOWNER ACTVT Values COMP_ID** REP QUERY_OWNER* 16 INFO_AREA** S_RS_ODSO RSINFOAREA RSODSOBJ RSODSPART ACTVT * QUERY_OWNER 0CRM_OLVM DATA 03 denotes the name of the owner of the query from which you are creating the report. Enter * to denote any query owner. Reading dynamic picklists in report parameters Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT Values FUGR SYST. If you enter the name of the query owner. cubes. and component IDs. you can only report off of queries that contain these info areas. INFO_CUBE. RSOB 16 BusinessObjects XI Integration Kit for SAP Installation Guide 141 . STOM 02 142 BusinessObjects XI Integration Kit for SAP Installation Guide .A Actions in R/3 Actions in R/3 From within Crystal Reports using the Open SQL driver Logging on to an SAP server Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT Values FUGR SYST. /CRYSTAL/OPENSQL 16 Creating a new report Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT ZSEGREPORT ACTVT Values FUGR SYST. /CRYSTAL/OPENSQL 16 01 Opening or previewing an existing report Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT ZSEGREPORT ACTVT Values FUGR SYST. /CRYSTAL/OPENSQL 16 02 Verifying the database (refreshing table definitions in a report) Authorization object S_ADMI_FCD ZSEGREPORT Field S_ADMI_FCD ACTVT Values STOR. BusinessObjects XI Integration Kit for SAP Installation Guide 143 . P_ORIG or P_APAP (see “Setting the location of the data source” on page 144). For example.Actions in R/3 A Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT Values FUGR /CRYSTAL/OPENSQL 16 Setting the location of the data source Authorization object ZSEGREPORT S_RFC Field ACTVT RFC_TYPE RFC_NAME ACTVT Values 02 FUGR /CRYSTAL/OPENSQL 16 From within Crystal Reports using the InfoSet driver. AQRC 16 TABL Note: Also add enough authorizations to view data rows. SKBW. reporting off InfoSet Logging on to an SAP server Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT Values FUGR SYST 16 Creating a new report from an InfoSet on R/3 Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT S_CTS_ADMI CTS_ADMFCT Values FUGR /CRYSTAL/FLAT. STOM 03 Name of table group 144 BusinessObjects XI Integration Kit for SAP Installation Guide .A Actions in R/3 Verifying the database (refreshing table definitions in a report) Authorization object S_ADMI_FCD Field S_ADMI_FCD Values STOR. reporting off an ABAP query Logging on to an SAP server Authorization object S_RFC Field RFC_TYPE RFC_NAME ACTVT Values FUGR SYST 16 Creating a new report from an ABAP query on R/3 Authorization object P_ABAP S_ADMI_FCD S_TABU_DIS Field REPID COARS S_ADMI_FCD ACTVT GROUP Values AQTG02==========P6. STOM Setting the location of the data source Authorization object P_ABAP Field REPID COARS Values AQTGSYSTGENERATESY. SAPDBPNP 2 From within Crystal Reports using the InfoSet driver. SAPDBPNP 2 STOR. SAPDBPNP 2 STOR. RFC1. SAPDBPNP 2 From within BusinessObjects Enterprise Scheduling a report in dialog mode (with an Open SQL query) Authorization object S_USER_GRP S_RFC Field CLASS ACTVT RFC_TYPE RFC_NAME ACTVT ZSEGREPORT ACTVT Note: The value for CLASS is BLANK. STOM FUGR SKBW 16 Setting the location of the data source Authorization object P_ABAP S_ADMI_FCD S_RFC Field REPID COARS S_ADMI_FCD RFC_TYPE RFC_NAME ACTVT S_TABU_DIS P_ABAP ACTVT GROUP REPID COARS Values AQTG02==========P6. /CRYSTAL/OPENSQL 16 02 Values BusinessObjects XI Integration Kit for SAP Installation Guide 145 . STOM FUGR SKBW 16 03 Name of table group AQTG02==========P6. 03. 05 FUGR SYST.Actions in R/3 A Verifying the database (refreshing table definitions in a report) Authorization object S_ADMI_FCD S_RFC Field S_ADMI_FCD RFC_TYPE RFC_NAME ACTVT Values STOR. /CRYSTAL/ OPENSQL. RFC1.A Crystal entitlement system Scheduling a report in batch mode (with an Open SQL query) Authorization object S_USER_GRP S_RFC Field CLASS ACTVT RFC_TYPE RFC_NAME ACTVT S_BTCH_JOB ZSEGREPORT S_BTCH_ADM JOBGROUP JOBACTION ACTVT BTCADMIN Note: The value for CLASS is BLANK. 03. 146 BusinessObjects XI Integration Kit for SAP Installation Guide . SH3A 16 '' RELE 02 Y Values Crystal entitlement system See “Creating a user account for BusinessObjects Enterprise” on page 53 for a complete listing. 05 FUGR SYST. Business Objects Information Resources appendix . Additional support and services are also available to help maximize the return on your business intelligence investment. Documentation You can find answers to your questions on how to install. and use Business Objects products from the documentation. from where. Where only online help is provided. What’s in the documentation set? View or download the Business Objects Documentation Roadmap. Where is the documentation? You can access electronic documentation at any time from the product interface. Documentation on the web The full electronic documentation set is available to customers on the web from support web site at: http://www. the web.com/support/. Documentation from the products Online help and guides in Adobe PDF format are available from the product Help menus.businessobjects. The Documentation Roadmap references all Business Objects guides and lets you see at a glance what information is available. Documentation on the product CD Look in the docs directory of your product CD for versions of guides in Adobe PDF format. and in what format. deploy.B Documentation and information services Documentation and information services Business Objects offers a full documentation set covering its products and their deployment.com/support/. and consulting. the online help file contains the entire contents of the PDF version of the guide. The following sections detail where to get Business Objects documentation and how to use the resources at Business Objects to meet your needs for technical support.businessobjects. education. available with the product documentation at http://www. 148BusinessObjects XI Integration Kit for SAP User’s Guide . configure. or from your product CD. It also has links to a wide range of technical information including knowledgebase articles. Note: If your issue concerns a Business Objects product and not the documentation. How can we support you? Business Objects offers customer support plans to best suit the size and requirements of your deployment. downloads.com/support/ BusinessObjects XI Integration Kit for SAP User’s Guide 149 . We operate customer support centers in the following countries: • • • • • USA Australia Canada United Kingdom Japan Online Customer Support The Business Objects Customer Support web site contains information about Customer Support programs and services. and we will do our best to ensure that your suggestion is included in the next release of our documentation: documentation@businessobjects. education.businessobjects. please contact our Customer Support experts. and consulting to ensure maximum business intelligence benefit to your business. consulting and training B Send us your feedback Do you have a suggestion on how we can improve our documentation? Is there something you particularly like or have found useful? Drop us a line.businessobjects. Customer support.com/ support/. http://www.Customer support. and support forums. For information about Customer Support visit: http://www.com. consulting and training A global network of Business Objects technology experts provides customer support. we can offer a training package to suit your learning needs and preferred learning style.businessobjects. customized embedding technology.com/services/training Useful addresses at a glance Address Business Objects product information http://www. and online forums. Find more information on the Business Objects Education web site: http://www. For more information.com/services/consulting/ Looking for training options? From traditional classroom learning to targeted e-learning seminars.com Online Customer Support http://www.com Product documentation http://www.businessobjects.com/ support Business Objects Documentation mailbox documentation@businessobjects. or contact us at: http://www. and more. Send us feedback or questions about documentation. downloads.com/ support/ Content Information about the full range of Business Objects products. Expertise is available in relational and multidimensional databases. Information on Customer Support programs.businessobjects. Business Objects product documentation.B Useful addresses at a glance Looking for the best deployment solution for your company? Business Objects consultants can accompany you from the initial analysis stage to the delivery of your deployment project.businessobjects. 150BusinessObjects XI Integration Kit for SAP User’s Guide . as well as links to technical articles. in connectivities. database design tools. contact your local sales office. including the Business Objects Documentation Roadmap.businessobjects. com/ services/training Content Information on how Business Objects can help maximize your business intelligence investment.businessobjects. BusinessObjects XI Integration Kit for SAP User’s Guide 151 . Information on Business Objects training options and modules.Useful addresses at a glance B Address Business Objects Consulting Services http://www.businessobjects.com/ services/consulting/ Business Objects Education Services http://www. B Useful addresses at a glance 152BusinessObjects XI Integration Kit for SAP User’s Guide . Business Objects 150 Content Administration Workbench adding BusinessObjects Enterprise systems 85 applying authorizations for 83 defining user access levels 83 deleting reports 94 migrating reports from earlier versions 94 overview of report publishing 81 publishing reports in background 91 publishing reports using 88 synchronizing report information 91. reporting off 22 C client requirements 33 Cluster Definition tool 49. 127 communication. 33 configuration options 100 requirements 33 customer support 149 customizing sample reports 98 security definitions 104 B Business Information Warehouse. 151 support services 149 training services 150. 38 BW Publisher 18.Index A ABAP queries. 127 Cluster Definition transport 49. 151 BusinessObjects Enterprise 18 adding servers 46 configuring for SNC 63 creating account for 53 distributing components 44 UNIX requirements 37 Windows requirements 32 BW 18 configuring 48 integrating with BusinessObjects Enterprise 70 requirements 33. reporting off 22 applying authorizations 52 architecture 18 diagram 21 authorizations applying for Data Access Kit users 52 for BusinessObjects Enterprise 53 rights in BusinessObjects Enterprise 70 Automatically import users check box 57 BW queries. over TCP/IP 23 components Cluster Definition tool 49. 127 of the product 18 Security Definition Editor 104 configuration options. 93 updating data source of reports 92 creating authorizations 52 Crystal Decisions namespace 51 Crystal Management Server (CMS) 23 Crystal Reports 18. See BW 18 Business Objects consulting services 150. 23 configuring as a service 75 configuring on UNIX 75 distributing components 45 selecting a configuration 24 BW Publisher service configuring 75 creating RFC destination 77 starting 75 BusinessObjects XI Integration Kit for SAP Installation Guide 153 . 151. Report Designer 100 conflicts. resolving 51 consultants. Index D Data Access 18 Data Access Kit contents of the transports 123 installation overview 48 required authorizations 52 sample reports 98 data access restrictions 104 data sources 22 updating for reports 92 default security patterns 73 defining security 104 description. 31 default security levels 73 distributed 44 recommended 34 troubleshooting 119 installation types 31 installing 31 on UNIX 36 on Windows 31 SAP Gateway on Windows 79 server components on UNIX 38 integrating with SNC 63 J Job Server 46 E education. of the product 18 feedback. for default system 85 groups 60 GWSETUP 79 I importing roles to BusinessObjects Enterprise 60 N namespace.5 or 9 94 minimum requirements UNIX 37 Windows 32 G global lock feature 105 green checkmark. resolving Crystal Decisions 51 154 BusinessObjects XI Integration Kit for SAP Installation Guide . on documentation 149 folder security 70 function groups included in transports 124 M mapping roles 60 Max failed entitlement system accesses field 57 migrating reports from BusinessObjects Enterprise 8. of product 18 disabling SAP authentication 57 distributing components 44 reports over the Web 26 documentation feedback on 149 on product CD 148 on the web 148 roadmap 148 information resources 148 InfoSet Connectivity transport 50 InfoSet driver sample reports 98 troubleshooting installation 121 InfoSets. BusinessObjects Enterprise SAP Edition 98 installation 12. See training Enable SAP Authentication check box 57 entitlement systems 55 K Keep entitlement system disabled field 57 L locking down tables 105 logon tickets 33 F features. reporting off 22 InfoView. See training education. configuration options 100 report maintenance 93 reporting configuration options 100 off SAP data 22 reports creating 22 deleting 94 migrating from version 8. See BW 18 SAP Gateway and SNC 63 distributing components 45 installing 79 publishing using a local 79 SAP Presentation CD. in BW 82 in the background 91 multiple reports using roles 88 reports in batch mode 65 scheduling in background 91 setting up 81 to multiple BusinessObjects Enterprise systems 85 processing on server groups 98 publishing 88 in batch mode 65 overview 23 samples 98 viewing 98 requirements for installing UNIX 37 Windows 32 resources 148 restrictions data access 104 row-level 112 table-level 105 RFC destination for BW Publisher service 77 for local SAP Gateway 80 roles creating for administration 82 importing 60 row-level security authorization objects. 63 programs included in transports 124 publishing 23 all reports in a role or system 88 defining roles for. 23 distributing components 46 enabling/disabling 57 options 57 SAP BW. Report Designer configuration 100 P Page Server 46 prerequisites to installing UNIX 37 Windows 32 product overview 18 profile parameters 33. requirements 32 SAP Tools toolbar 22 SAPGUI requirements 33 scaling your installation 44 R R/3 48 recommended installation 34 report designer 18 Report Designer.5 or 9 94 BusinessObjects XI Integration Kit for SAP Installation Guide 155 . using 113 custom security exits.Index O object rights 70 objects included in transports 124 Online Customer Support 149 Open SQL Connectivity transport 49 Open SQL driver default security model 104 defining security 104 sample reports 98 Options tab 57 options. using 115 overview 112 S sample reports analyzing 98 refreshing against SAP 99 setting up 98 SAP Authentication 18. contents of 123 services files UNIX 37 Windows 33 Single Sign On 23 importing roles 60 support customer 149 locations 149 technical 149 web site 149 synchronizing report information 91. 98 distributing components 46 web server. integrating with 63 security default patterns 73 defining 104 global lock feature 105 in BusinessObjects Enterprise 70 migrating from client-independent model 105 preserving existing restrictions 105 row-level restrictions 112 table-level restrictions 105 Security Definition Editor transport 49.Index Secure Network Communication (SNC). on Business Objects products 150 transports authentication helper 127 156 BusinessObjects XI Integration Kit for SAP Installation Guide . distributing 45 web sites support 149 training 150 Windows installing 31 requirements 32 T table-level security 105 tables customizing authorizations 107 defining security by group 112 included in transports 124 locking down 105 TCP/IP communication 23 technical support 149 toolbar. described 104 security plug-ins 23 server installation 38. 46 server transports. 93 system account 53 system requirements UNIX 37 Windows 32 checking for conflicts 51. 26. creating for BusinessObjects Enterprise 53 V viewing configuration options 100 enabling in BW or IViews 95 reports 98 W web customer support 149 getting documentation via 148 useful addresses 150 Web Content 18. 130 Row-level security definition 126 U UNIX installing 36 requirements 37 user account. 126 Security Definition Editor. SAP Tools 22 training. 51 cluster definition 127 Content Administration Workbench 128 contents 123 importing 51 InfoSet connectivity 126 Open SQL Connectivity 124 parameter personalization 50.