Crystal Enterprise 10

Crystal Enterprise™ 10 SAP® Edition Installation Guide

Copyright © 2004 Business Objects SA. All rights reserved.

Issue 1.

No part of this documentation may be stored in a retrieval system, transmitted or reproduced in any way, except in accordance with the terms of the applicable software license agreement. This documentation contains proprietary information of Business Objects SA., and/or its suppliers.

Trademark AcknowledgementsThe Business Objects logo, Business Objects, WebIntelligence, Crystal Analysis, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA in the United States and/or other countries. All other trademarks or registered trademarks referenced are the property of their respective owners.

Contents

Chapter 1: Welcome to Crystal Enterprise SAP Edition version 10What is Crystal Enterprise SAP Edition? ............................................ 2

What is Crystal Enterprise Enhanced SAP Edition? ............................ 2

Who should use this guide? ............................................................... 2

About this guide ................................................................................ 2Chapter contents ................................................................................................... 3

Product registration .......................................................................... 4

Customer Handbook ......................................................................... 4

Business Objects Technical Support .................................................. 5

Business Objects Training ................................................................. 5

Business Objects Consulting ............................................................. 5

Document conventions ..................................................................... 5

Chapter 2: What’s New in Crystal Enterprise SAP EditionIntroduction ...................................................................................... 8

Personalized and default SAP BW query variable values .................. 8Personalized values ............................................................................................... 8Default values ....................................................................................................... 8

SDK for Java, COM, and .NET ........................................................... 8

Java applications ............................................................................... 9

Improved SAP Enterprise Portal Support ........................................... 9Sample iViews ...................................................................................................... 9Master iView for Crystal Reports ............................................................................ 9

Publisher Service ............................................................................... 9

Crystal Enterprise SAP Edition Installation Guide iii

Content Administration Workbench ................................................. 9Content synchronization and administration ......................................................... 9

Improved hierarchy reporting ......................................................... 10

Client-specific security definition ................................................... 10

Chapter 3: Components and FeaturesOverview ........................................................................................ 12Crystal Reports Professional ................................................................................. 12Crystal Enterprise Professional ............................................................................. 12Add-Ons Disc 1 .................................................................................................. 12Add-Ons Disc 2 for Crystal Enterprise Enhanced SAP Edition .............................. 14Integrated architecture ......................................................................................... 14

Reporting with Crystal Enterprise SAP Edition ................................ 15Reporting off BW queries and InfoSets ................................................................. 15Authenticating SAP users ..................................................................................... 15Publishing from BW to Crystal Enterprise ............................................................ 16Distributing information over the Web ................................................................ 18

Crystal Enterprise Enhanced SAP Edition overview ......................... 19Reporting off other SAP data sources ................................................................... 19

Chapter 4: Installing Crystal Enterprise SAP EditionInstallation overview ....................................................................... 22

Installing on Windows .................................................................... 22System requirements ........................................................................................... 23Recommended initial installation ........................................................................ 24

Installing on UNIX .......................................................................... 27System requirements ........................................................................................... 27Installing the UNIX components .......................................................................... 28Deploying the web applications .......................................................................... 30

iv Crystal Enterprise SAP Edition Installation Guide

Distributed installation ................................................................... 34Installing components on Crystal Enterprise machines ......................................... 34Separating Crystal Enterprise from your web server ............................................. 35Distributing the BW Publisher installation ........................................................... 35Adding servers to Crystal Enterprise ..................................................................... 36

Chapter 5: Performing the initial configurationConfiguration overview .................................................................. 38

Configuring transports .................................................................... 38

Creating and applying authorizations ............................................. 41

Configuring SAP authentication for Crystal Enterprise .................... 41Creating a user account for Crystal Enterprise ...................................................... 41Accessing the SAP authentication application in Crystal Enterprise ...................... 42Connecting to SAP entitlement systems ............................................................... 43Setting SAP Authentication options ..................................................................... 45Importing SAP roles to Crystal Enterprise ............................................................. 47Integrating with Secure Network Communication ............................................... 49

Configuring Data Access ................................................................. 51Processing scheduled reports in SAP’s batch mode .............................................. 51Configuring SAP Logon for the Data Access Kit ................................................... 53

Chapter 6: Integrating Crystal Enterprise and BWConfiguration overview .................................................................. 56

Setting up folders and security in Crystal Enterprise ....................... 56Understanding the default folder security patterns ............................................... 57

Configuring the BW Publisher ......................................................... 59Configuring the BW Publisher as a service .......................................................... 59Configuring the BW Publisher with a local SAP Gateway .................................... 63

Crystal Enterprise SAP Edition Installation Guide v

Configuring publishing in the Content Administration Workbench 65Creating roles in BW for designated content publishers and administrators ......... 66Configuring access to the Content Administration Workbench ............................ 66Defining a Crystal Enterprise system .................................................................... 68Publishing reports using the Content Administration Workbench ........................ 70Maintaining reports ............................................................................................. 74

Configuring the SAP http request handler ....................................... 76

Chapter 7: Working with Web Content and Sample ReportsCrystal Enterprise SAP Edition web desktop .................................... 78

Setting up the sample reports .......................................................... 78

Verifying configuration options in Crystal Reports ......................... 80

Chapter 8: Defining Security for the Open SQL driverSecurity Definition Editor overview ................................................ 84

Migrating your existing security model ........................................... 85

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

Customizing authorizations for specific tables ................................ 87

Customizing authorizations for specific functions .......................... 91

Defining table authorizations by group ........................................... 91

Applying row-level security ............................................................ 92Securing rows using authorization objects ........................................................... 92Securing rows using custom security exits ........................................................... 94

Appendix A: TroubleshootingTroubleshooting overview ............................................................... 98

Locating and generating log files ..................................................... 98

vi Crystal Enterprise SAP Edition Installation Guide

Troubleshooting Crystal Enterprise ................................................. 98

Troubleshooting your InfoSet driver installation ............................. 99Reports, tables, and functions .............................................................................. 99Errors when importing transport files ................................................................... 99Errors when connecting to SAP ............................................................................ 99

Obtaining Add-Ons Disc 2 .............................................................. 99

Appendix B: Transport FilesOverview ...................................................................................... 102Open SQL Connectivity transport ...................................................................... 102InfoSet Connectivity transport ........................................................................... 103Row-level Security Definition transport ............................................................. 104Cluster Definition transport ............................................................................... 104Authentication Helpers transport ....................................................................... 105Crystal Content Administration Workbench transport ........................................ 105BW Query parameter personalization transport ................................................. 107

Appendix C: AuthorizationsAuthorizations overview ............................................................... 110

Actions in BW ............................................................................... 110From within Crystal Reports .............................................................................. 110From within the Crystal Enterprise SAP Edition web desktop ............................. 115

Actions in R/3 ............................................................................... 118From within Crystal Reports using the Open SQL driver .................................... 118From within Crystal Reports using the InfoSet driver, reporting off InfoSet ......... 119From within Crystal Reports using the InfoSet driver, reporting off an ABAP query ...................................................................................................... 120From within Crystal Enterprise ........................................................................... 121

Crystal entitlement system ............................................................ 122

Crystal Enterprise SAP Edition Installation Guide vii

Appendix D: Using ABAP to configure publishingConfiguring publishing without the Content Administration Workbench ................................................................................... 124

Setting the installation parameters ................................................ 124

viii Crystal Enterprise SAP Edition Installation Guide

Welcome to Crystal Enterprise SAP Edition version 10 1

This chapter briefly describes Crystal Enterprise SAPEdition and outlines the contents and the intendedaudience of this guide.

Crystal Enterprise SAP Edition Installation Guide 1

What is Crystal Enterprise SAP Edition?

What is Crystal Enterprise SAP Edition?Crystal Enterprise SAP Edition is bundled with SAP BW and provides you, the SAP user, with the ability to extract the business intelligence contained within your SAP systems. By generating Crystal reports from SAP BW queries, ABAP queries, and InfoSets, you can organize, format, and share your SAP data. The Crystal Enterprise SAP Edition web desktop allows you to share your reports over the Web, and SAP Authentication enables Single Sign On between your SAP system and Crystal Enterprise. Certain limitations may apply. For more details, contact SAP.

What is Crystal Enterprise Enhanced SAP Edition?Crystal Enterprise Enhanced SAP Edition includes all of the features of Crystal Enterprise SAP Edition, and adds the ability to report off of Open SQL queries, BW OLAP data sources, and a multitude of non-SAP data sources from within Crystal Reports, Crystal Enterprise, and Crystal Analysis Professional.

Add-Ons Disc 2 contains the setup program for the Open SQL driver and the BW OLAP Kit. If you did not receive the Add-Ons Disc 2 with your product distribution, you can request it at:http://www.businessobjects.com/CEESEV10/Disc2

Who should use this guide?This guide leads administrators and users through the planning and installation stages of a Crystal Enterprise SAP Edition implementation or a Crystal Enterprise Enhanced SAP Edition implementation. Familiarity with your operating system and your network environment is certainly beneficial, as is a general understanding of web server management.

A number of installation tasks require the skills and security privileges of an SAP BASIS administrator. If you are not an SAP administrator, you will need to contact one for assistance during the installation.

For more information about using the product, consult the Crystal Enterprise SAP Edition User’s Guide (userguide.pdf), included in the docs directory on both Add-Ons CDs.

About this guideThis guide provides you with information and procedures for installing and configuring the components included in Crystal Enterprise SAP Edition and Crystal Enterprise Enhanced SAP Edition.

For brevity, this guide refers to Crystal Enterprise SAP Edition when discussing features or procedures that apply to both editions. This guide only refers to Crystal

2 Crystal Enterprise SAP Edition Installation Guide

1 Welcome to Crystal Enterprise SAP Edition version 10

Enterprise Enhanced SAP Edition when discussing features or procedures that apply exclusively to that edition.

Chapter contentsThe following is a short description of each of the remaining chapters in this guide.

Chapter 2: What’s New in Crystal Enterprise SAP Edition

This chapter provides a high level overview of the key new features and enhancements that are specific to Crystal Enterprise SAP Edition.

Chapter 3: Components and Features

This chapter introduces the various reporting components that make up Crystal Enterprise SAP Edition and Crystal Enterprise Enhanced SAP Edition. The chapter then provides information on the overall product architecture and describes features provided by various components.

Chapter 4: Installing Crystal Enterprise SAP Edition

This chapter shows how to install Crystal Enterprise SAP Edition. System requirements are provided, as well as procedures covering various installation and configuration tasks.

Chapter 5: Performing the initial configuration

This chapter explains how to configure Crystal Enterprise and your R/3 or BW system so Crystal Enterprise SAP Edition can process reports and logon requests effectively.

Chapter 6: Integrating Crystal Enterprise and BW

This chapter shows how to configure BW to enable and administer report publishing from BW to Crystal Enterprise. It also includes instructions for configuring the http request handler in SAP.

Chapter 7: Working with Web Content and Sample Reports

This chapter briefly describes the Crystal Enterprise SAP Edition web desktop, which is included with the Web Content feature of Crystal Enterprise SAP Edition.

Chapter 8: Defining Security for the Open SQL driver

This chapter shows how to use the Security Definition Editor to define table-level and row-level security for specific SAP tables when you access them using the Open SQL driver. The Security Definition Editor enables you to maintain your current SAP security levels when you deploy the Open SQL driver.

Appendix A: Troubleshooting

This appendix describes some common installation and configuration issues in order to assist you in troubleshooting your Crystal Enterprise SAP Edition implementation.


Product registration

Appendix B: Transport Files

This appendix lists the names and contents of the transports that are included on both Add-Ons CDs. Also read the transports_EN.txt file located in the transports directory on both Add-Ons CDs. This text file lists the names of the files that make up each transport.

Appendix C: Authorizations

This appendix provides a list of SAP authorizations that, in our experience, are required when carrying out common tasks with Crystal Enterprise Enhanced SAP Edition.

Appendix D: Using ABAP to configure publishing

This appendix describes how to configure the BW Publisher using an ABAP program. Use this procedure if you do not have the Content Administration Workbench.

Product registrationIf you have purchased Crystal Enterprise Enhanced SAP Edition from Business Objects, you are required to register the product components in the following way:

Note: This does not apply if you have Crystal Enterprise SAP Edition or if you have purchased Crystal Enterprise Enhanced SAP Edition from SAP.

To register your product, fill out the Product Registration form at:http://www.businessobjects.com/register/

Registration of your products is required to access online or technical support. In addition, registering the product ensures that you are kept up-to-date with product advancements.

Customer HandbookFor the latest details about product registration, maintenance, support, and services, visit our web site and download the Customer Handbook that corresponds to your region:• North America:

http://www.businessobjects.com/customers/handbook.asp (English)• Europe:

http://www.businessobjects.com/customers/handbook.asp (English)http://www.businessobjects.com/customers/handbook_de.asp (German)http://www.businessobjects.com/customers/handbook_fr.asp (French)

If a Customer Handbook is not available for your region, please refer to the rest of this Welcome chapter, or contact your sales or support representative for complete details.


1 Welcome to Crystal Enterprise SAP Edition version 10

Business Objects Technical SupportYour standard SAP service agreement may include technical support. If you require assistance when integrating Crystal Enterprise Enhanced SAP Edition with your SAP system, it is recommended that you first check your SAP service agreement and follow your usual SAP support procedures.

To find out about the Business Objects technical support programs that are available:• Go to our support web site at:

http://www.businessobjects.com/services/support/support_programs.asp

• Contact your regional office. For details, go to:http://www.businessobjects.com/company/locations/

Business Objects TrainingWhether you’re a developer, information technology professional, or business user, we offer a wide range of training courses designed to build or enhance your existing skills. Courses are available online, at certified training centers, or at your own site:• For a complete list of training courses and special offers, visit:

http://www.businessobjects.com/training/

• Or contact your regional office. For details, go to:http://www.businessobjects.com/company/locations/

Business Objects ConsultingOur global team of certified consultants and consulting partners can guide you through a corporate-wide solution—including strategy, design, integration and deployment—for the fastest results, maximum performance, and increased productivity.• To learn more, visit:

http://www.businessobjects.com/services/consulting

• Or contact your regional office. For details, go to:http://www.businessobjects.com/company/locations/

Document conventionsThis guide uses the following conventions:• Commands and buttons

For easy recognition within procedures, User Interface (UI) features appear in bold type. For example: On the File menu, click New.


Document conventions

• Keyboard shortcutsDelete means the Delete key, or the Del key on your numeric keypad. Enter means the Enter, Return, or CR key, depending on which of these keys appears on your keyboard.

• Key combinationsCTRL+KEY, SHIFT+KEY, and ALT+KEY are examples of key combinations. Hold down the first key in the combination and, at the same time, press the second key in the combination (designated above as KEY). For example: CTRL+C means hold the Control key down and press the letter C on your keyboard (CTRL+C is the Windows Copy command).

• Key terms are italicized when first defined.• Monospaced font indicates data that you enter using your keyboard. For

example: In the Formula Editor, type If Sales > 1000 Then crRed• Monospaced, italicized font indicates variable data that you must replace with

data appropriate to your current settings, environment, or task. For example, in the following URL, you would replace webserver:

http://webserver/crystal/enterprise10/


What’s New in Crystal Enterprise SAP Edition 2

This chapter provides a high level overview of the key newfeatures and enhancements that are specific to CrystalEnterprise SAP Edition.

Crystal Enterprise SAP Edition User Guide 7

Introduction

IntroductionCrystal Enterprise SAP Edition version 10 extends the robust information infrastructure provided by the previous version of Crystal Enterprise SAP Edition. Crystal Enterprise SAP Edition version 10 provides support for version 10 of the Crystal family of products and delivers improvements in the areas of usability, ease of implementation and administration, and report dissemination.

While a number of enhancements and feature additions have been made to core products that Crystal Enterprise SAP Edition integrates with, this chapter’s focus is to provide a high level overview of the key new features and enhancements that are specific to Crystal Enterprise SAP Edition. For more information on what’s new in Crystal Reports 10, see the “What’s New in Crystal Reports 10” chapter of the Crystal Reports User’s Guide. For more information on what’s new in Crystal Enterprise 10, see the “What’s New in Crystal Enterprise” chapter of the Crystal Enterprise Administrator’s Guide.

Note: This feature list provides a general overview of key new features in Crystal Enterprise SAP Edition version 10. It is not intended to provide an exhaustive list of all of the new features found within Crystal Enterprise SAP Edition.

Personalized and default SAP BW query variable values

Personalized valuesThe Crystal Enterprise SAP Edition web desktop retrieves values dynamically from SAP and can now pre-populate SAP BW variables with user-selected parameters. This enables each user to set personalized values for variables and save time whenever they run reports.

Default valuesDefault values are similar to personalized values except that they have a global instead of user-based scope. When designing a BW query, users can set a default value for a variable; when a report is run without a personalized value, the default value is retrieved.

SDK for Java, COM, and .NETCrystal Enterprise SAP Edition ships with Java, COM, and .NET SDKs. These SDKs are documented and provide helper classes to enable developers to integrate Crystal Enterprise SAP Edition functionality (for example, Single Sign On, report-to-report interface, and so on) in custom applications.

8 Crystal Enterprise SAP Edition User Guide

2 What’s New in Crystal Enterprise SAP Edition

Java applicationsCrystal Enterprise SAP Edition web desktop is now delivered in Java and includes virtually all of the features available in the new Java SDK. The functionality available in this version of the web desktop is equivalent to the functionality that was available in the previous (CSP) version of the Crystal Enterprise SAP Edition web desktop.

Improved SAP Enterprise Portal Support

Sample iViewsSample iViews are a way of illustrating how Crystal Enterprise SAP Edition can be implemented together with SAP Enterprise Portal version 5 or version 6. These samples help customers get started quickly by demonstrating sample functionality for alerts, report folders, and thumbnail iViews inside SAP Enterprise Portal.

Master iView for Crystal ReportsThere are improvements in SAP Enterprise Portal version 6 that make it possible to create Crystal Enterprise iViews more efficiently by reducing the dependency on SAP BW for processing of these iViews.

In addition, improvements have been made to SAP Enterprise Portal version 6 (starting with SP03) that make it easier to integrate Crystal Enterprise SAP Edition into the portal landscape. These enhancements include changes to the Master iView for Crystal report-based iViews as well as new Crystal Enterprise server maintenance functionality in the system landscape administration.

Publisher ServicePublisher Service eliminates the dependency on the SAP Gateway and is an alternative to using a standalone SAP Gateway for publishing Crystal content. This new feature makes the administration and maintenance of Crystal Enterprise SAP Edition simpler. Users have the option of leveraging either Publishing Service or SAP Gateway to publish their Crystal content.

Content Administration Workbench

Content synchronization and administrationThe purpose of this tool is to provide a central point of access for managing Crystal content within SAP BW. Operations such as publishing reports in both background and dialogue mode and maintaining reports (updates, post-migration, deletion) can be accomplished using the content synchronization and administration tool.

Crystal Enterprise SAP Edition User Guide 9

Improved hierarchy reporting

This tool supports the notion of multiple Crystal Enterprise systems connected to one SAP BW system.

Improved hierarchy reportingHierarchy reporting has been improved for SAP BW through the following enhancements:• Formulas enable users to create parent-child relationships in Crystal Reports

and to use standard hierarchy reporting from Crystal Reports.• Dependency between hierarchy and hierarchy node variables reduce the load

on the server and the size of hierarchy node picklists by filtering them by the relevant hierarchy.

Client-specific security definitionThe row-level security definition tool is now client-specific and security can be defined for each SAP client. Previously, only one security definition was available per implementation and the settings had global effects. Now the same user can have different security settings when using different SAP clients. For example, client 100 and client 800 can now have different security settings.

10 Crystal Enterprise SAP Edition User Guide

Components and Features 3

This chapter introduces the various reporting componentsthat make up Crystal Enterprise SAP Edition and CrystalEnterprise Enhanced SAP Edition. The chapter thenprovides information on the overall product architectureand describes features provided by various components.


Overview

OverviewCrystal Enterprise SAP Edition provides you with powerful report-design tools and a framework for managing, scheduling, and distributing your Crystal reports over the Web. 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.

Crystal Enterprise SAP Edition includes two major products—Crystal Enterprise Professional and Crystal Reports Professional—along with add-on components that integrate the Crystal reporting technologies with your existing SAP systems.

Crystal Reports ProfessionalYour Crystal Reports product distribution contains the setup program and core product documentation for Crystal Reports Professional. Crystal Reports is the report-design tool that allows you to create reports off virtually any data source and save those reports directly to Crystal Enterprise.

Crystal Enterprise ProfessionalYour Crystal Enterprise product distribution contains the setup program and core product documentation for Crystal Enterprise Professional. Crystal Enterprise is the server-based system that manages, schedules, and renders Crystal reports for viewing over the Web.

Add-Ons Disc 1The Add-Ons Disc 1 distribution contains the setup program and additional documentation for the components that integrate Crystal Reports and Crystal Enterprise with your SAP system. The setup program determines which Crystal products are already installed, and then installs the add-on components as required.

The add-on components are:• Data Access

This component provides two database drivers that are designed specifically for reporting off SAP data—the BW Query driver and the InfoSet driver. The database drivers are used by the report engine, and must therefore be installed atop Crystal Reports and Crystal Enterprise.For details, see “Reporting off BW queries and InfoSets” on page 15.

• Crystal Reports SAP ToolbarIntegrated within Crystal Reports, the “SAP Tools” toolbar facilitates tasks associated with reporting off BW queries. It allows you to log on to BW and work with its data sources, save reports to BW, and publish reports immediately to Crystal Enterprise.For details on using the toolbar, see the Crystal Enterprise SAP Edition User’s Guide.


3 Components and Features

• DocumentationThe setup program installs all Crystal Enterprise SAP Edition documentation, which serves to complement the core product documentation included with Crystal Reports and Crystal Enterprise.

• SAP AuthenticationThis component allows you to map your existing SAP roles and users to Crystal Enterprise. It also enables Crystal Enterprise to authenticate users against the SAP system, thereby providing Single Sign On to your SAP users. As a result, once SAP users are logged on to the SAP system, they are recognized by Crystal Enterprise as authenticated users.For details, see “Authenticating SAP users” on page 15.

• BW PublisherThis component allows you to publish reports individually or in batches from BW to Crystal Enterprise.For details, see “Publishing from BW to Crystal Enterprise” on page 16.

• Web ContentThis optional component includes the Crystal Enterprise SAP Edition web desktop. This web desktop allows users to organize and view your Crystal reports in multiple languages over the Web.For details, see “Distributing information over the Web” on page 18.

• Transport filesThe transport files are included in the transports directory of both Add-Ons CDs. You must import these transports and configure a number of authorization objects in order for users to connect to SAP through Crystal Reports and Crystal Enterprise.For details, see “Configuring transports” on page 38.

• BW Content Administration WorkbenchThe Content Administration Workbench allows you to administer report publishing functionality from within BW. You can identify roles in your BW system with particular Crystal Enterprise systems, publish reports, and synchronize reports between BW and a Crystal Enterprise system.

• Sample ReportsThe sample reports demonstrate a variety of ways in which you can extract value from SAP data using different database drivers.

• Sample iViewsSample iViews illustrate how Crystal Enterprise SAP Edition can be implemented with SAP Enterprise Portal version 5 or version 6. These iViews demonstrate sample functionality for alerts, report folders, and thumbnail views inside SAP Enterprise Portal.For details, see the “Managing the SAP Enterprise Portal” section of the Crystal Enterprise SAP Edition User's Guide.


Overview

Add-Ons Disc 2 for Crystal Enterprise Enhanced SAP EditionThe Add-Ons Disc 2 distribution of Crystal Enterprise Enhanced SAP Edition contains the setup program for the Open SQL driver and the BW OLAP Kit. These components allow you to report off additional SAP data sources from within Crystal Reports, Crystal Enterprise, and Crystal Analysis Professional. If you did not receive the Add-Ons Disc 2 with your product distribution, you can request it at:http://www.businessobjects.com/CEESEV10/Disc2

Integrated architectureThe following diagram illustrates how each of the Crystal Enterprise SAP Edition components expands upon the multi-tier framework of Crystal Enterprise.

If you are new to Crystal Enterprise, see its documentation for a more detailed explanation of the framework, its components, and the general tasks that each component performs.



Reporting with Crystal Enterprise SAP EditionThis section describes the key features provided by Crystal Enterprise SAP Edition.

Reporting off BW queries and InfoSetsCrystal Enterprise SAP Edition 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.

The “SAP Tools” toolbar works with the BW Query driver to allow you to report off your BW queries from within Crystal Reports. The toolbar also allows you to save reports to BW and publish them directly to Crystal 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. You access this driver through the Data Explorer in Crystal Reports.

One advantage of these drivers is that they allow business users to report off predefined views of your SAP data. Tables and fields are first logically grouped by an SAP content expert into queries, InfoSets, and so on. You then make these data sources accessible to users who are designing reports with Crystal Reports.

These same two drivers are also included in the add-ons for Crystal Enterprise (the Data Access feature), so the Crystal Enterprise processing servers can successfully run the reports you design against your SAP systems.

Note: Before you can design or process reports with the InfoSet driver, you must install the InfoSet Connectivity transport file on the SAP system. For more information, see “Configuring transports” on page 38.

For instruction on creating Crystal reports with these drivers, consult the Crystal Enterprise SAP Edition User’s Guide (userguide.pdf), included in the docs directory on both Add-Ons CDs.

Authenticating SAP usersSecurity plug-ins expand and customize the ways in which Crystal Enterprise authenticates users. The SAP Authentication feature includes an SAP security plug-in (secSAPR3.dll) for the Crystal Management Server (CMS) component of Crystal Enterprise. 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. When users log on to Crystal Enterprise directly, they can choose SAP Authentication and provide their usual SAP user name and password. Crystal Enterprise can also be configured to automatically and seamlessly recognize SAP users who have already been authenticated by your SAP system.


Reporting with Crystal Enterprise SAP Edition

• It facilitates account creation by allowing you to map roles from SAP to Crystal Enterprise, and it facilitates account management by allowing you to assign rights to users and groups in a consistent manner within Crystal Enterprise.

• It dynamically maintains SAP role listings. So, once you map an SAP role to Crystal Enterprise, all users who belong to that role can log on to Crystal Enterprise. When you make subsequent changes to the SAP role membership, you need not update or refresh the listing in Crystal Enterprise.

The SAP Authentication component includes a web application for configuring the plug-in. This application is displayed as an additional tab within the Crystal Management Console (CMC). After installing the SAP Authentication component, see “Configuring SAP authentication for Crystal Enterprise” on page 41.

Publishing from BW to Crystal EnterpriseThe BW Publisher allows you to publish Crystal reports (.rpt files) individually or in batches from BW to Crystal Enterprise.

Reports are published from BW to Crystal Enterprise in several ways: users who design Crystal reports can simultaneously save reports to their roles in BW and publish them to Crystal Enterprise, provided they have sufficient rights. Users with the appropriate rights within BW and Crystal Enterprise can also publish reports individually or in batches using the Crystal Content Administration Workbench. See “Publishing reports using the Content Administration Workbench” on page 70.

Details of the publishing process depend upon the publisher configuration that you select.

Selecting your BW Publisher configurationOn Windows, you can configure the BW Publisher in one of two ways: • Install the BW Publisher as a service on a Crystal Enterprise machine. The BW

Publisher service will start instances of the BW Publisher as required.• Install a local SAP Gateway to create BW Publisher instances.

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

When you create a BW Publisher service, the overall installation process is significantly simpler. This configuration is also very scalable as new Publisher instances are created automatically in response to increased publishing load. However, when you use a BW Publisher service your publishing system is somewhat more difficult to administer. Changes to the BW Publisher service require you to edit the registry. The BW Publisher service also makes less efficient use of computing resources, as publisher instances are not stopped automatically when they are no longer needed.



Using a local SAP Gateway also has its advantages and disadvantages. In our experience, installing and configuring a stand-alone SAP Gateway can be considerably complex. This configuration does use system resources more efficiently for Windows installations of Crystal Enterprise. However for UNIX installations of Crystal Enterprise, using a local SAP Gateway imposes a performance penalty and is not recommended.

In most cases it is recommended that you install the BW Publisher as a service.

For UNIX installations of Crystal Enterprise, follow the instructions for installing the BW Publisher as a service. However, your system configuration will vary slightly as you must manually start the required number of BW Publisher instances.

Publishing using the BW Publisher serviceWhen you install the BW Publisher service, it registers as a server program with the SAP Gateway running on your application host, using the name you specify as its Program ID string. This SAP Gateway may be installed on your single BW server, or on your central instance of BW if you have a BW cluster.

When a user attempts to publish one or more Crystal reports, BW looks for a Remote Function Call (RFC) destination (of type TCP/IP) that is configured to connect to this BW Publisher. The TCP/IP destination provides 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, and sends the following information across the network:• The appropriate Crystal report file(s), with any required translated report strings.

Tip: For more on translated reports, see the Crystal Enterprise SAP Edition User’s Guide (userguide.pdf), included in the docs directory on both Add-Ons CDs.

• A publishing command.• The name of the appropriate Crystal Management Server (CMS).

The SAP Gateway responds by executing the publishing command, thereby invoking the BW Publisher. The BW Publisher logs on to the specified CMS as the user, and checks to see if the user has the appropriate permissions in Crystal Enterprise to publish reports. If the user’s rights are sufficient, the CMS allows the reports to be added to the system.

Note: Before beginning to publish, you must configure SAP authentication in Crystal Enterprise, define a folder structure for your content, and import SAP roles. See “Configuring SAP authentication for Crystal Enterprise” on page 41 for complete instructions.

Publishing using a local SAP GatewayWhen you select this configuration, you install a local SAP Gateway along with Crystal Enterprise SAP Edition on a Crystal Enterprise machine.


Reporting with Crystal Enterprise SAP Edition

When a user attempts to publish one or more Crystal reports, BW looks for a Remote Function Call (RFC) destination (of type TCP/IP) that is defined on the system. This TCP/IP destination provides BW with the location of the machine where you have installed the local SAP Gateway and the BW Publisher.

BW then communicates over TCP/IP with the specified SAP Gateway service, and sends the following information across the network:• The appropriate Crystal report file(s), with any required translated report strings.

Tip: For more on translated reports, see the Crystal Enterprise SAP Edition User’s Guide (userguide.pdf), included in the docs directory on both Add-Ons CDs

• A publishing command.• The name of the appropriate Crystal Enterprise Crystal Management Server

(CMS).

The SAP Gateway responds by executing the publishing command, thereby invoking the BW Publisher. The BW Publisher logs on to the specified CMS as the user, and checks to see if the user has the appropriate permissions in Crystal Enterprise to publish reports. If the user’s rights are sufficient, the CMS allows the reports to be added to the system.

Note: Before beginning to publish, you must configure SAP authentication in Crystal Enterprise, define a folder structure for your content, and import SAP roles. See “Configuring SAP authentication for Crystal Enterprise” on page 41 for complete instructions.

Distributing information over the WebThe Web Content feature includes the Crystal Enterprise SAP Edition web desktop, which is a customized edition of the standard Crystal Enterprise web desktop. These new features are designed especially for SAP users:• Users whose roles you import can log on to the Crystal Enterprise SAP Edition

web desktop with their usual SAP credentials.• Users can browse a hierarchy of “My Roles” folders that correspond to the

structure of the imported roles whose content you publish from BW to Crystal Enterprise. In these folders, users can locate, view, and refresh Crystal reports that have been saved in their BW roles.

• Users can schedule translated reports in specific languages and view report titles and on-demand reports in their usual logon language.Note: These features require that you translate the reports within BW, before you publish the reports to Crystal Enterprise. For more information, see the Crystal Enterprise SAP Edition User’s Guide (userguide.pdf), included in the docs directory on both Add-Ons CDs.

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

After installing the Web Content, see “Working with Web Content and Sample Reports” on page 77.



Crystal Enterprise Enhanced SAP Edition overviewWith Crystal Enterprise Enhanced SAP Edition you receive all of the functionality provided with Crystal Enterprise SAP Edition. (See “Overview” on page 12, and “Reporting with Crystal Enterprise SAP Edition” on page 15 for details.) In addition, you are able to report off of a variety of other SAP data sources from within Crystal Reports, Crystal Analysis Professional, and Crystal Enterprise.

Reporting off other SAP data sourcesIn addition to the components provided with your product distribution, you can download the Open SQL driver and the BW OLAP Kit, which allow you to report off additional SAP data sources from within Crystal Reports, Crystal Enterprise, and Crystal Analysis Professional. If you did not receive the Add-Ons Disc 2 with your product distribution, you can request it at:

http://www.businessobjects.com/CEESEV10/Disc2/

Reporting off tables, views, clusters, and functionsThe Open SQL driver is the most powerful of the drivers due to the flexibility it provides for accessing data in SAP. This flexibility, however, results in a higher level of complexity than with the InfoSet driver.

When you create reports that use the Open SQL driver, you gain easy access to SAP’s transparent tables, pool tables, cluster tables, and views. Users who are currently involved with the production of ABAP reports will find it easy to build reports quickly with this driver.

Advanced functionality in the driver also allows reporting against ABAP functions and ABAP data clusters. ABAP developers can use these features to perform advanced tasks such as reporting against data clusters in HR. Developers can also utilize ABAP to augment report processing.

Reporting off multidimensional data in BWThe BW OLAP Kit has been specially designed to integrate the Online Analytical Processing (OLAP) viewing capabilities of Crystal Analysis Professional and Crystal Reports with your SAP Business Information Warehouse (BW) system. Users can connect to multidimensional BW Info Cubes and generate reports that incorporate complex data analysis.

For additional information on OLAP analysis and reporting, refer to your Crystal Analysis Professional and/or Crystal Reports documentation.


Crystal Enterprise Enhanced SAP Edition overview


Installing Crystal Enterprise SAP Edition 4

This chapter shows how to install Crystal Enterprise SAPEdition. System requirements are provided, as well asprocedures covering various installation and configurationtasks.


Installation overview

Installation overviewTo set up Crystal Enterprise SAP Edition, 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.See “Installing on Windows” on page 22, or “Installing on UNIX” on page 27.

• Complete the required base administrative tasks within SAP necessary to configure R/3 or BW systems to work with Crystal Enterprise SAP Edition. Required tasks include importing transport files and setting up authorizations in SAP, configuring SAP authentication in Crystal Enterprise, and configuring Data Access for SAP.For complete details, see “Performing the initial configuration” on page 37.

• If you have BW, complete the following additional configuration steps: • Setting up folders and security in Crystal Enterprise• Configuring the BW Publisher• Configuring publishing in the Content Administration Workbench.• Configuring the SAP http request handlerFor complete information, see “Integrating Crystal Enterprise and BW” on page 55.

A number of installation tasks require the skills and security privileges of an SAP BASIS administrator. If you are not an SAP administrator, you will need to contact one for assistance during the installation.

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

Installing on WindowsBefore installing Crystal Enterprise SAP Edition on Windows, consider the following:• Install Crystal Enterprise and Crystal Reports (and Crystal Analysis Professional if

you purchased it) first. Then install the Crystal Enterprise SAP Edition Add-Ons. For details, see “Recommended initial installation” on page 24.

• You can install Crystal Enterprise, Crystal Reports, Crystal Analysis Professional, and the Crystal Enterprise SAP Edition Add-Ons on a single Windows machine.

• You can expand your deployment by distributing the Crystal Enterprise servers across multiple machines. For details, see “Distributed installation” on page 34.

• If you choose to install the Java version of the Crystal Enterprise SAP Edition web applications, deploy the Crystal Enterprise SAP Edition web desktop as described in “Deploying the web applications” on page 30. Use the Windows file paths provided in notes to that procedure.


4 Installing Crystal Enterprise SAP Edition

System requirementsAll Crystal Enterprise SAP Edition components are supported for use with the version 10 releases of Crystal Enterprise, Crystal Reports, and Crystal Analysis Professional on Windows operating systems. For a stand-alone installation, ensure that all requirements are met on a single machine. For a distributed installation, ensure that each machine meets the requirements that correspond to the components you are installing.

Note: For a detailed list of tested environments for Crystal Enterprise SAP Edition, consult the platforms_EN.txt file included with your product distribution. This file includes specific version and Service Pack requirements for application servers, operating systems, SAP components, etc.

SAP Presentation CD requirementsCrystal Enterprise SAP Edition uses the SAPGUI from the SAP Presentation CD, and the SAP Gateway (if you choose to configure the BW Publisher using a stand-alone SAP Gateway). For version requirements, see the platforms_EN.txt file on both Add-Ons CDs.

Server requirements for Crystal Enterprise• Install the SAPGUI along with the BW AddOn option from the SAP

Presentation CD before you install the Crystal Enterprise SAP Edition Add-Ons atop Crystal Enterprise. Installing the SAPGUI ensures that the SAP library librfc32 SAP library is installed. Alternatively, download librfc32 for your platform from the SAP Service Marketplace.

• Supported web server software must be installed and configured correctly before you install Crystal Enterprise. Consult the platforms_EN.txt file included with your Crystal Enterprise product distribution for a complete list.

• The following entry must appear in the Services file (found in %windir%\system32\drivers\etc\) on any Crystal Enterprise machines running a WCS, CMS, Page Server, and/or Job Server:

sapmsSID portnumber/tcp

Replace SID with the system ID of your SAP system, and replace portnumber with the port number of the message server that Crystal Enterprise will log on to (for example, sapmsQR6 3600/tcp). Ensure also that a blank line follows the entry. This standard setting allows Crystal Enterprise to log on to SAP with load balancing.

• For a detailed list of tested environments for Crystal Enterprise, consult the platforms_EN.txt file included with your Crystal Enterprise product distribution. This file includes specific version and Service Pack requirements for web servers, web browsers, databases, and operating systems.


Installing on Windows

Client requirements for Crystal Reports• Install the SAPGUI along with the BW AddOn option from the SAP

Presentation CD before you install Crystal Reports and the Crystal Enterprise SAP Edition Add-Ons.

• For a detailed list of tested environments for Crystal Reports, consult the platforms_EN.txt file included with your Crystal Reports product distribution.

Requirements for using the Crystal Enterprise SAP Edition Java SDKTo use the Crystal Enterprise SAP Edition Java SDK, you must install and configure SAP Java Connector components as described in “SAP Java Connector” on page 27.

SAP requirementsBefore you can enable Single Sign On between SAP and Crystal Enterprise, you must set up your SAP system to accept and create logon tickets. This involves setting two related profile parameters on your SAP server:• login/accept_sso2_ticket• login/create_sso2_ticket

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). For complete details on these profile parameters and configuring SAP to accept and create logon tickets, see the SAP Library > Web Application Server >SAP Web Application Server Security > SAP Web Application Server Security > User Authentication > Using Logon Tickets.

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

Recommended initial installationBefore beginning this installation, ensure that each machine meets the minimum requirements. See “System requirements” on page 23. Log on as an Administrator of the local machine to install any components.

Before running the installer, read “Publishing from BW to Crystal Enterprise” on page 16 and select your publisher configuration. If you choose to install the BW Publisher Service, select a custom installation, and select the BW Publisher Service component. During the installation, you will be prompted for information about your BW system. Ensure that you have selected a Program ID for the BW Publisher component, and that you know the Gateway Host and Gateway Service that you will use for publishing. See “Publishing using the BW Publisher service” on page 17 for details.

You will also be prompted for your Crystal Enterprise Administrator credentials when installing server components from the Add-Ons CDs.



Follow the procedures in this section in order:• Install the core Crystal products first (Crystal Enterprise, Crystal Reports, and

Crystal Analysis Professional, if purchased it).• Next, install the Crystal Enterprise SAP Edition Add-Ons (Disc 1). To install all

features of Crystal Enterprise Enhanced SAP Edition, you must first run the setup program from Add-Ons Disc 1 and then run the setup program from Add-Ons Disc 2.

To install the core Crystal products1 Deploy Crystal Enterprise 10 or upgrade all existing Crystal Enterprise

machines to Crystal Enterprise 10.For details, see the Crystal Enterprise Installation Guide (install.pdf) included on your Crystal Enterprise product distribution.

2 Install Crystal Reports 10.For details, see Installing Crystal Reports (install.pdf) included on your Crystal Reports product distribution.

3 If you are planning to use Crystal Analysis Professional 10 with Crystal Enterprise SAP Edition, install or upgrade to Crystal Analysis Professional 10. For details, see the Crystal Analysis Professional Installation Guide (Install.pdf) included on your Crystal Analysis Professional product distribution.

To install Crystal Enterprise SAP Edition Add-Ons Disc 11 On each Crystal Reports and Crystal Enterprise machine, run the setup

program from Add-Ons Disc 1.Tip: If Autoplay is disabled on your system, double-click Setup.exe on the CD.

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

3 Select the appropriate installation type, depending on the product(s) that are already installed:• If only Crystal Enterprise is installed, select the Server installation type.• If only Crystal Reports is installed, select the Desktop installation type.• If both Crystal Enterprise and a desktop client are installed, or if you want

to select which components will be installed, select the Custom installation type and click Next. In the Select Features dialog box, choose the features that you need, and click Next.

Note: If you are performing a distributed installation of Crystal Enterprise, the setup program detects which Crystal Enterprise components are present and installs the appropriate features of Crystal Enterprise SAP Edition.

4 If you selected a Desktop installation type, proceed through the Setup program’s remaining dialog boxes and follow the instructions on your screen to complete the installation.


Installing on Windows

5 If you selected Server components for your installation, the CMS Logon Info dialog may appear. Type the name of your Crystal Management Server. If you have not yet modified the password for the default Administrator account, leave the Password field blank. Use Enterprise Authentication. If you previously created other administrative users on your Crystal Enterprise system, you can enter the name and password of a user with administrative privileges. Select the appropriate type of authentication for this user account.

6 Click Next.

7 If your installation includes the BW Publisher Service, next you are prompted for information about your BW system. Record the exact value you specify here for the Program ID. You will need this value when you configure the RFC destination on your BW system. See “Configuring a destination for the BW Publisher service” on page 61.• Program ID

Type a descriptive string to identify the BW Publisher service. The Program ID can take any value, but must be 64 characters or fewer, and may not contain spaces. The Program ID is case-sensitive.

• Gateway HostType the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW.

• Gateway ServiceType the port number that the Gateway Host is listening on. For example, type 33##, where ## represents the instance number of your SAP Gateway. Typically, the instance number is 00, and the value for this field is 3300.If you have defined a symbolic name for this port (such as sapgw##), you may use this symbolic name instead.

• Extra (optional)If you plan to enforce Secure Network Communication (SNC) between SAP and Crystal Enterprise, enter the appropriate switches here. For information on how to enable SNC for registered servers, consult the RFC SDK documentation for API RfcAccept. See “Integrating with Secure Network Communication” on page 49 for more information.

8 Proceed through the Setup program’s remaining dialog boxes and follow the instructions on your screen to complete the installation.

To install Crystal Enterprise Enhanced SAP Edition Add-Ons Disc 21 On each Crystal Reports, Crystal Enterprise, and Crystal Analysis Professional

machine, run the setup program from Add-Ons Disc 2.Note: If you did not receive the Add-Ons Disc 2 with your product distribution, you can request it at:

http://www.businessobjects.com/CEESEV10/Disc2



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

3 Select the Complete installation type and click Next.

4 Proceed through the Setup program’s remaining dialog boxes and follow the instructions on your screen to complete the installation.

Installing on UNIXUNIX versions of the following Crystal Enterprise Add-On components are provided for environments where Crystal Enterprise is running on UNIX:• SAP Authentication• BW Publisher• Data Access• Web Content

When installing Crystal Enterprise SAP Edition on UNIX, consider the following:• You install the Crystal Enterprise add-on components by running the

cesap_install1.sh and cesap_install2.sh scripts.For details, see “Installing the UNIX components” on page 28.

• You can expand your deployment by distributing the Crystal Enterprise servers across multiple machines.For details, see “Distributed installation” on page 34.

System requirementsBefore installing any of the Crystal Enterprise SAP Edition components, ensure that your environment meets the following requirements.• Crystal Enterprise must be installed and configured correctly on UNIX before you

install the Crystal Enterprise SAP Edition components. Complete this installation and configuration in accordance with the Crystal Enterprise Installation Guide.

• The following entry must appear in the Services file on the Crystal Enterprise machine (found in /etc)

SapmsSID portnumber/tcp

Replace SID with the system ID of your SAP system, and replace portnumber with the port number of the message server that Crystal Enterprise will log onto (for example, SAPMSQR6 3600/tcp). This standard setting allows Crystal Enterprise to log on to SAP with load balancing.

SAP Java ConnectorCrystal Enterprise SAP Edition web applications (including the web desktop for SAP), and the Crystal Enterprise SAP Edition Java SDK require the SAP Java Connector. The SAP Java Connector is available from http://service.sap.com/connectors.


Installing on UNIX

Please see the SAP MarketPlace for information on licensing SAP Java Connector for use in your development environment.

After you have installed Crystal Enterprise, you must unpack the archive file containing the SAP Java Connector. Copy the librfccm library and the libsapjcorfc library to crystal_root/enterprise/PLATFORM_PATH, where crystal_root is the full path to your crystal directory. For example, PLATFORM_PATH is solaris_sparc for an installation on Solaris.

After you have installed Crystal Enterprise, you must make sapjco.jar available to your Java application server as a shared resource (either by placing sapjco.jar in the application server's shared lib directory, or by adding sapjco.jar to the CLASSPATH environment variable. See “Deploying the web applications” on page 30 or consult your application server documentation for details.)

Note: If you plan to deploy the Java version of the Crystal Enterprise SAP Edition web desktop on Windows, unpack the SAP Java Connector archive. Add the directory containing the SAP Java Connector files to your PATH environment variable, and copy librfc32.dll to your C:\WNNT\system32 directory.

Consult the documentation included with the SAP Java Connector for more information.

SAP requirementsBefore you can enable Single Sign On between SAP and Crystal Enterprise, you must set up SAP to accept and create logon tickets. This involves setting two related profile parameters on your SAP server:• login/accept_sso2_ticket• login/create_sso2_ticket

The parameter values that you set depend upon whether or not the server’s certificate is self-signed or signed by the SAP CA. For complete details on these profile parameters and configuring BW to accept and create logon tickets, see the SAP Library > SAP Web Application Server > Security > SAP Web Application Server Security > User Authentication > Using Logon Tickets.

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

Installing the UNIX componentsOnce you have set up Crystal Enterprise on UNIX, and have installed the SAP Java Connector, you can install the Add-On components. Ensure that Crystal Enterprise is running before you begin the installation. The installation script needs to log on to your Crystal Management Server.

To install SAP Add-Ons Disc 11 Log on to your UNIX system under the crystal user account you created for

your Crystal Enterprise installation.



Note: You may also use another account that has permission to read and write files in the crystal directory and its subdirectories.

2 Copy the install_cesap1.sh script, the licensetext file (included with your product distribution), and the file containing the Crystal Enterprise binaries (with the extension .gz) from the product CD to your crystal directory.Note: If you transfer the .gz files by FTP to the UNIX machine, be sure to specify binary mode for the transfer.

3 Ensure that you are working in your crystal directory:

cd $HOME/crystal

4 Run the installation script:

./install_cesap1.sh

5 When prompted, press Enter to continue.The script displays the product license agreement. Press the spacebar to read through the information in its entirety.

6 Press Enter, and then type yes and press Enter to accept the license agreement and to proceed with the installation.

7 The script prompts you for the absolute path of the installation directory.Press Enter to accept the default, which is your current directory The script notifies you that it has collected all of the required information, and asks you if you are ready to have the installation begin.

8 Type begin and press Enter.The installation script unpacks the archived installation file. This may take a few minutes. When it is done, the installation script automatically starts the postinstall_cesap1.sh script.

9 When prompted, enter the name and port number of your Crystal Management Server. Use the format cmsname:portnum. Note: If you do not specify a port number, the default value of 6400 is used.

10 Next you are prompted for a user name and password to be used to log on to the CMS. Use the Administrator account. If you have not yet modified the password for the default Administrator account, leave the Password field blank.The postinstall_cesap1.sh script continues, and completes the configuration of Crystal Enterprise SAP Edition.

11 Next, the script asks you if you want to restart the CMS. If you choose not to restart the CMS now, you can restart it later using the ccm.sh script. Consult the Crystal Enterprise Administrator’s Guide for details. After you make your selection, the script completes the final installation steps and finishes.


Installing on UNIX

12 Restart your Java application server.After installing Add-Ons Disc 1, you must restart both the CMS and your Java application server to make the SAP authentication application available in the Crystal Management Console.

To install SAP Add-Ons Disc 21 Log on to your UNIX system under the crystal user account you created for

your Crystal Enterprise installation. You may also use another account that has permission to read and write files in the crystal directory and its subdirectories.

2 Copy the install_cesap2.sh script, the licensetext file (included with your product distribution), and the file containing the Crystal Enterprise binaries (with the extension .gz) from the product CD to your crystal directory.Note: If you transfer the.gz files by FTP to the UNIX machine, be sure to specify binary mode for the transfer.

3 Ensure that you are working in your crystal directory:

cd $HOME/crystal

4 Run the installation script:

./install_cesap2.sh

5 When prompted, press Enter to continue.The script displays the product license agreement. Press the spacebar to read through the information in its entirety.

6 Press Enter, and then type yes and press Enter to accept the license agreement and to proceed with the installation.

7 The script prompts you for the absolute path of the installation directory.Press Enter to accept the default, which is your current directory

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

9 Type begin and press Enter.The install_cesap2.sh script continues, and completes the configuration of Crystal Enterprise Enhanced SAP Edition.

Deploying the web applicationsTo deploy the Java version of the Crystal Enterprise SAP Edition web desktop, you must create virtual path mappings on your Java web application server. They map specific URLs to the web application archives (.war files) that implement the web desktop.

Note: Before performing this procedure, ensure that you have deployed the SAP Java Connector as described in “SAP Java Connector” on page 27.


To deploy the Crystal Enterprise SAP Edition web desktop on Tomcat1 Shut down Tomcat if it is running. Type sh $CATALINA_HOME/bin/shutdown.sh

2 Ensure that the sapjco.jar Java archive file is in $CATALINA_HOME/shared/lib (see “SAP Java Connector” on page 27 for details).Substitute the root directory of your Crystal Enterprise installation for crystal_root

3 Open the file $CATALINA_HOME/conf/server.xml, in a text editor such as vi.

4 Add the following lines directly above the line :

<Context path="/crystal/enterprise10/sap/desktoplaunch" docBase="crystal_root/enterprise/java/applications/sap/sap_desktop.war" debug="0" reloadable="false"/>Substitute your Crystal Enterprise install directory for crystal_rootNote: If you are deploying the Java version of the web desktop on Windows, use the .war file found at C:\Program Files\Crystal Decisions\Enterprise 10\java\applications\SAP\sap_desktop.war.

5 Save the file.

6 Check to see if the following file exists:

$CATALINA_HOME/shared/classes/META-INF/authPluginExts.properties

7 If it does not, copy the following file:

crystal_root/enterprise/java/applications/sap/authPluginExts.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 web desktop.

8 Restart Tomcat by typing sh $CATALINA_HOME/bin/startup.sh

9 To test the Crystal Enterprise SAP Edition web desktop, open a web browser and type http://servername:8080/crystal/enterprise10/SAP/desktoplaunch/ePortfolio in its address bar. For servername, substitute the name of the machine where you installed Tomcat. If you did not install on the default Tomcat port, substitute that port number for 8080.The Crystal Enterprise SAP Edition web desktop should start.

10 To test that the SAP authentication module is now available, open a web browser and type http://servername:8080/crystal/enterprise10/admin in its address bar to launch the Crystal Management Console (CMC). For servername, substitute the name of the machine where you installed Tomcat. If you did not install on the default Tomcat port, substitute that port number for 8080.

11 Log on to the CM C using your Administrator account and password. (By default the password is blank when you first install Crystal Enterprise.)

Installing on UNIX

12 Click Authentication, and then SAP. The SAP authentication tab (as shown in “Connecting to SAP entitlement systems” on page 43) should appear. If it does not, ensure that the librfccm library is in your crystal_root/enterprise/PLATFORM directory, and restart your Java application server.Note: For a Windows installation of Crystal Enterprise that uses the Java version of the web desktop, ensure that librfc32.dll is in your C:\WNNT\system32 directory, and restart your Java application server.

To deploy the Crystal Enterprise SAP Edition web desktop on BEA WebLogic1 Make sure that your BEA WebLogic server is not running.

2 Ensure that your CLASSPATH environment variable includes the sapjco.jar archive file. (See “SAP Java Connector” on page 27 for details.)

3 Add the following file to your CLASSPATH environment variable:



4 Start your BEA WebLogic server.

5 Open a web browser, and type http://servername:7001/console in its address bar to open the BEA WebLogic Administrative Console. Substitute the name of the machine where you installed BEA WebLogic for servername. Note: By default, BEA WebLogic uses port 7001. If you configured your application server to use a different port number, substitute that port number in the URL.

6 Deploy the Crystal Enterprise SAP Edition web desktop as a new web application. Use the .war file found at crystal_root/enterprise/java/applications/sap/sap_desktop.war, and set the context root to /crystal/enterprise10/sap/desktoplaunch

Note: • To set the context root for the web application, edit the Web Application

Deployment Descriptor. [Click Edit Web Application Deployment Descriptors. Click WebApp Ext in the left-hand tree menu, then make your changes to the Context Root field. Click Apply].

• If you are deploying the Java version of the web desktop on Windows, use the .war file found at C:\Program Files\Crystal Decisions\Enterprise 10\java\applications\SAP\sap_desktop.war.

7 To test that the Crystal Enterprise User Launchpad deploys correctly, type http://servername:7001/crystal/enterprise10/sap/desktoplaunch in the address bar of a web browser.



8 To test that the SAP authentication module is now available, open a web browser and type http://servername:7001/crystal/enterprise10/admin in its address bar to launch the Crystal Management Console (CMC).

9 Log on to the CMC using your Administrator account and password. (By default the password is blank when you first install Crystal Enterprise.)


To deploy the Crystal Enterprise SAP Edition web desktop on IBM WebSphere1 Make sure that your IBM WebSphere server is not running.

2 Ensure that your CLASSPATH environment variable includes the sapjco.jar archive file. (See “SAP Java Connector” on page 27 for details.)

3 Add the following file to your CLASSPATH environment variable:



4 Start your IBM WebSphere Server, and launch the Administrative Console (at http://servername:9090/admin/). For servername, substitute the name of the machine where you installed IBM WebSphere. If you chose to use a port number other than the default value for the administrative console, substitute that value for 9090.

5 Install the Crystal Enterprise SAP Edition web desktop as a new application. Use the .war file found at crystal_root/enterprise/java/applications/sap/sap_desktop.war, and set the context root to /crystal/enterprise10/sap/desktoplaunch

Note: If you are deploying the Java version of the web desktop on Windows, use the .war file found at C:\Program Files\Crystal Decisions\Enterprise 10\java\applications\SAP\sap_desktop.war.

6 Start the new application.

7 To test that the Crystal Enterprise User Launchpad deploys correctly, type http://servername:9080/crystal/enterprise10/sap/desktoplaunch/ in the address bar of a web browser.


Distributed installation

8 To test that the SAP authentication module is now available, open a web browser and type http://servername:9080/crystal/enterprise10/admin in its address bar to launch the Crystal Management Console (CMC).

9 Log on to the CMC using your Administrator account and password. (By default the password is blank when you first install Crystal Enterprise.)


Distributed installationThe Crystal Enterprise architecture is scalable in that it allows for a multitude of server configurations, ranging from stand-alone, single-machine environments, to large-scale deployments supporting global organizations. The flexibility offered by the product’s architecture allows you to set up a system that suits your current reporting requirements, without limiting the possibilities for future growth and expansion.

Note: This section provides details that are specific to Crystal Enterprise SAP Edition. For general information about distributing the Crystal Enterprise components, see the “Scaling Your System” section of the Crystal Enterprise Administrator’s Guide (admin.pdf in the doc directory of your Crystal Enterprise product distribution).

Installing components on Crystal Enterprise machinesIf you have a distributed installation of Crystal Enterprise, install the listed Crystal Enterprise SAP Edition components on the appropriate machines.

If you select a default server installation of Crystal Enterprise SAP Edition, the setup program detects which elements of Crystal Enterprise are present, and installs the appropriate Crystal Enterprise SAP Edition components.

Components Crystal Enterprise machines

Data Access • Page Server• Report Job Server • Report Application Server (RAS)

BW Publisher (installed as a service)

• Page Server• Report Job Server• RAS



Separating Crystal Enterprise from your web serverThe Crystal Enterprise Installation Guide (install.pdf) included with your Crystal Enterprise product distribution explains how to connect Crystal Enterprise to a web server or Java application server that is running on a different machine.

If you set up your system in this manner, you will need to install the Web Content feature from Crystal Enterprise SAP Edition Add-Ons Disc 1 onto the server that is connected to Crystal Enterprise. This feature includes the files that make up the Crystal Enterprise SAP Edition web application.

Distributing the BW Publisher installation

BW Publisher ServiceYou can load-balance publishing from BW by installing BW Publisher services on two separate machines in the same Crystal Enterprise system.

When you install the BW Publisher on the Crystal Enterprise machines, configure each one to use the same Program ID and SAP Gateway Host and Gateway Service. After you create an RFC destination that uses this Program ID, BW load-balances publishing between the Crystal Enterprise machines. Moreover, if one BW Publisher becomes unavailable, publishing from BW falls over to the remaining BW Publisher.

You can add an additional level of system redundancy to any configuration that includes multiple BW application servers. Configure each BW application server to run an SAP Gateway. For each one, install a separate BW Publisher service on a Crystal Enterprise machine. 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 24 or “To start the BW Publisher on UNIX” on page 61), In this configuration, publishing from BW can continue if either a BW Publisher or an application server fails.

BW Publisher(when installed with a local SAP Gateway)

• Crystal Enterprise SDK

Security • Crystal Management Server• Web Component Server• Crystal Enterprise Java SDK

Web Content • Web Component Server• Crystal Enterprise Java SDK

Components Crystal Enterprise machines


Distributed installation

BW Publisher on a stand-alone SAP GatewayIf you want to separate the BW Publisher from other Crystal Enterprise components, install the BW using a stand-alone SAP Gateway. (See “Selecting your BW Publisher configuration” on page 16 for details of this configuration.)

In this case you must install a local SAP Gateway on the same machine as the BW Publisher. In addition, the BW Publisher requires access to the Crystal Enterprise Software Development Kit (SDK). Thus, if you install the BW Publisher and the local SAP Gateway on a dedicated machine, you must also perform a minimal installation of Crystal Enterprise. Installing any of the Crystal Enterprise client tools, such as the Crystal Publishing Wizard, is sufficient for installing the SDK.

Tip: • Before selecting your BW Publisher configuration, please read “Publishing

from BW to Crystal Enterprise” on page 16• On UNIX, it is not recommended that you use a BW Publisher on a stand-alone

SAP Gateway.

Adding servers to Crystal EnterpriseIf you expand your Crystal Enterprise system after installing Crystal Enterprise SAP Edition, you must install components from Add-Ons Disc 1 and Disc 2, as described in “Installing components on Crystal Enterprise machines” on page 34.


Performing the initial configuration 5

This chapter explains how to configure Crystal Enterpriseand your R/3 or BW system so Crystal Enterprise SAPEdition can process reports and logon requests effectively.


Configuration overview

Configuration overviewOnce you have updated Crystal Enterprise and Crystal Reports with Crystal Enterprise SAP Edition, you must configure your SAP system and Crystal Enterprise. These steps must be performed for both BW and R/3 systems: • Configuring transports• Configuring SAP authentication for Crystal Enterprise• Configuring Data Access

After you have completed these steps on an R/3 system, configuration is complete. You can begin using Crystal Enterprise SAP Edition.

For BW systems, additional configuration is required to enable report viewing and report publishing. After completing these steps, go on to “Integrating Crystal Enterprise and BW” on page 55.

Configuring transportsTo set up the Data Access Kit or BW Publisher component of Crystal Enterprise SAP Edition, you must import the appropriate transports from Add-Ons Disc 1 or Disc 2 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 Crystal Enterprise SAP Edition are located in the transports directory on both Add-Ons CDs. These sections provide you with details on setting up the appropriate transports:• “Types of transports” on page 39• “Selecting which transports to import” on page 40• “Checking for conflicts” on page 40• “Importing the transport files” on page 41

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: Defining Security for the Open SQL driver.

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


5 Performing the initial configuration

Types of transportsCrystal Enterprise Enhanced SAP Edition 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 Crystal Enterprise SAP Edition.

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 both Add-Ons CDs lists the Unicode compatible and ANSI transport files.

Each transport is described here. For details about the contents of each transport file, see Appendix B: Transport Files.• 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 Crystal Enterprise Enhanced SAP Edition.

• Row-level Security Definition transportThis transport provides the Security Definition Editor, which is a tool that serves as a graphical interface to the ZSSAUTH tables in the Open SQL Connectivity transport. It is included only with Crystal Enterprise Enhanced SAP Edition. For details on using the Security Definition Editor, see “Security Definition Editor overview” on page 84.

• Cluster Definition transportThis 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 Crystal Enterprise Enhanced SAP Edition. For details on using the Cluster Definition Tool, see the “Reporting off clusters” section of the Crystal Enterprise SAP Edition User’s Guide.Note: ABAP data clusters are not the same as cluster tables. Cluster tables are already defined in the DDIC.

• InfoSet Connectivity transportThe InfoSet Connectivity transport enables the InfoSet driver to access InfoSets.

• Authentication Helpers transportThis transport provides the Single Sign On enhancement for the InfoSet driver. This enhancement frees users from having to enter their credentials more than once to access any of the Crystal Enterprise, R3, and BW systems.

• Crystal Content Administration Workbench transport


Configuring transports

This transport provides content administration functionality for BW systems. It is available only as a UNICODE transport.

• BW Query parameter personalization transportThis 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 both Add-Ons CDs. This text file lists the names of the files that make up each transport.

Selecting which transports to importImport 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.

Checking for conflictsThe contents of the transport files are registered automatically under the Crystal Decisions namespace when you import the files. The Crystal Decisions namespace is reserved for this purpose within recent versions of R/3. Consequently, there is no need to check for conflicts prior to importing the transport files.

If the function group, any of the function modules, or any of the other objects already exists on the SAP system, then you must resolve the namespace before importing the Crystal Enterprise SAP Edition transport files. Refer to your SAP documentation for the procedures appropriate to your version of SAP.

SAP System Transport Notes

R/3 Open SQL Connectivity• Row-level Security Definition• Cluster Definition

Included only in Crystal Enterprise Enhanced SAP Edition (Add-Ons Disc 2).

InfoSet Connectivity

Authentication Helpers Recommended. Required if you have installed the SAP Solution Tools Plug-in (ST-PI).

BW Open SQL Connectivity• Row-level Security Definition• Cluster Definition

Included only in Crystal Enterprise Enhanced SAP Edition (Add-Ons Disc 2).

InfoSet Connectivity

Authentication Helpers Required.

Crystal Content Administration Workbench Recommended.

BW Query parameter personalization



Importing the transport filesRead the transports_EN.txt file located in the transports directory on both Add-Ons CDs. This text file lists the exact names of the files that make up each transport. (The cofiles and data directories below the transports directory correspond to the .../trans/cofiles and .../trans/data directories on your SAP server.)

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

Note: • After copying files from CD to server, ensure that all files are writable before

you import the transports. Imports fail if the cofiles are read-only.• The transports are binary files. So, if your SAP server is installed on a UNIX

machine, you must add the files by FTP in Binary mode (to avoid file corruption). In addition, you must have write permissions for the UNIX server.

Creating and applying authorizationsNext you must create and apply the authorizations needed by each user to access information using the Data Access Kit. The exact procedures for creating, configuring, and applying authorizations depend upon the version of SAP that you have installed.

Appendix C: Authorizations provides a list of SAP authorizations that, in our experience and in our test environment, are required when carrying out common tasks with Crystal Enterprise SAP Edition. Additional authorization objects or fields may be required, depending upon your individual implementation.

For information on the authorizations needed by content publishers, administrators of the content publishing tool, and users who view reports from within BW, see “Configuring publishing in the Content Administration Workbench” on page 65.

Configuring SAP authentication for Crystal EnterpriseSAP authentication enables SAP users to log on to Crystal Enterprise using their SAP user names and passwords, without storing these passwords in Crystal Enterprise. SAP authentication also allows you to preserve information about user roles in SAP, and to use this role information within Crystal Enterprise to assign rights to perform administrative tasks, or access content.

Creating a user account for Crystal EnterpriseThe Crystal Enterprise system requires an SAP user account that is authorized to access SAP role membership lists, authenticate SAP users, and so on. You will need


Configuring SAP authentication for Crystal Enterprise

this user name and its password when you connect Crystal Enterprise to your SAP system. For general instruction on creating SAP user accounts and assigning authorizations through roles, see your SAP documentation.

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

Finally, add the CRYSTAL user to the CRYSTAL_ENTITLEMENT role.

Tip: If your system policies require users to change their passwords when they first log on to the system, log on now with the CRYSTAL user account and reset its password.

Accessing the SAP authentication application in Crystal EnterpriseAfter installing SAP Authentication, you must provide Crystal Enterprise with information about your SAP system. Crystal Enterprise SAP Edition installs a web application to assist you. This web application is accessible through the main Crystal Enterprise administration tool, the Crystal Management Console (CMC). To access it from the home page of the CMC, select Authentication.

Authorization object Field Value

Authorization for file access (S_DATASET)

Activity (ACTVT) Read, Write (33, 34)

Physical file name (FILENAME)

* (denotes All)

ABAP program name (PROGRAM)

*

Authorization Check for RFC Access (S_RFC)

Activity (ACTVT) 16

Name of RFC to be protected (RFC_NAME)

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

Type of RFC object to be protected (RFC_TYPE)

Function group (FUGR)

User Master Maintenance: User Groups (S_USER_GRP)

Activity (ACTVT) Change, Display (02, 03)

User group in user master maintenance (CLASS)

*

Note: For greater security, you may prefer to explicitly list the user groups whose members require access to Crystal Enterprise.



To log on to the CMC1 Go to the following page:

http://webserver/crystal/enterprise10/admin/

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

2 When the Log On page appears, select Enterprise in the Authentication Type list.Windows NT, Windows AD, LDAP, and SAP authentication may also appear in the list; however, you must map your third-party user accounts and groups to Crystal Enterprise before you can use these types of authentication.

3 Type your User Name and Password.For this example, type Administrator as the User Name. This default Enterprise account does not have a password until you create one.

4 Click Log On.The CMC Home page appears. For an introduction to the CMC, click Help to open the Crystal Enterprise Administrator’s Guide; then see the “Administering Crystal Enterprise” section.

Connecting to SAP entitlement systemsBefore you can import roles or publish BW content to Crystal Enterprise, you must provide information about the SAP entitlement systems that you want to integrate with Crystal Enterprise. Crystal Enterprise uses this information to connect to SAP when it determines role memberships and authenticates SAP users.

To add an SAP entitlement system to Crystal Enterprise1 Go to the Authentication management area of the CMC.

2 Click the SAP tab.



The Entitlement systems tab appears.

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

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

4 In the Client field, type the client number that Crystal Enterprise must use when it logs on to your SAP system.Tip: When you finish these steps, Crystal Enterprise combines your System and Client information, and adds an entry to the “Logical system name” list.

5 Ensure the Disabled check box is clear.Note: The Disabled check box allows you, the administrator, to indicate to Crystal Enterprise that a particular SAP system is temporarily unavailable.

6 If you have set up load balancing such that Crystal Enterprise must log on through a message server, complete the Message server and Logon group fields as appropriate.Note: You must make the appropriate entries in the Services file on your Crystal Enterprise machine to enable load balancing. For details, see “Server requirements for Crystal Enterprise” on page 23.

7 If you have not set up load balancing (or if you prefer to have Crystal Enterprise log on directly to the SAP system), complete the Application server and System number fields as appropriate.

8 Type the Username, Password, and Language for the SAP account that you want Crystal Enterprise to use when it logs on to SAP.



Note: These credentials must correspond to the user account that you created for Crystal Enterprise. For details, see “Creating a user account for Crystal Enterprise” on page 41.

9 Click Update.

10 On the Options tab, ensure that the Enable SAP Authentication check box is selected.Tip: If you add multiple entitlement systems, click the Options tab to specify the system that Crystal Enterprise uses as the default (that is, the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system).

To check that an entitlement system was added correctly1 Click the Role Import tab.

2 From the Logical system name list, select the name of the entitlement system.If the entitlement system was added correctly, the Available roles list will contain a list of roles that you can choose to import. If there are no roles visible in this list, scroll to the bottom of the page and look for error messages. These may give you the information you need to correct the problem.

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

To set SAP Authentication options1 Go to the Authentication management area of the CMC.


3 On the Options tab, review and modify settings as required:• Enable SAP Authentication

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

• Max failed entitlement system accesses and Keep entitlement system disabled [seconds]Use these fields together to configure how Crystal Enterprise handles SAP entitlement systems that are temporarily unavailable. Crystal Enterprise uses these settings to determine when to stop communicating with an SAP system that is unavailable, and when it should resume communication with that system.



In the “Max failed entitlement system accesses” field, type the number of times that Crystal Enterprise should re-attempt contacting an SAP system to fulfill authentication requests. Setting the value to -1 allows Crystal Enterprise to attempt to contact the entitlement system an unlimited number of times before ceasing. Setting the value to 0 limits Crystal Enterprise to making one attempt to contact the entitlement system.In the “Keep entitlement system disabled [seconds]” field, type the number of seconds that Crystal Enterprise should wait before resuming attempts to authenticate users against the SAP system.For example, if you type 3 for “Max failed entitlement system accesses”, Crystal Enterprise allows a maximum of 3 failed attempts to authenticate users against any particular SAP system; the fourth failed attempt results in Crystal Enterprise ceasing its attempts to authenticate users against that system for the amount of time specified by “Keep entitlement system disabled [seconds].

• Automatically import usersSelect this check box if you want Crystal Enterprise to create user accounts and user folders for all role members when you actually import the roles. Clear the check box to have Crystal Enterprise create user accounts and user folders dynamically, when users log on for the first time with valid SAP credentials. For details, see “To import a role to Crystal Enterprise” on page 48.

• Concurrent users / Named UsersUse this option to specify if new user accounts are configured to use concurrent user licenses or named user licenses. Concurrent licenses specify the number of people who can connect to Crystal Enterprise at the same time. This type of licensing is very flexible because a small number of concurrent licenses can support a large user base. For example, depending on how often and how long users access Crystal Enterprise, a 100 user concurrent license could support 250, 500, or 700 users. Named user licenses are associated with specific users and allow people to access the system based on their user name and password. This provides named users with access to the system regardless of how many other people are connected. Note that the option you select here does not change the number or type of user licenses that you have installed in Crystal Enterprise. You must have the appropriate licenses available on your system.

• Default systemIn this list, select the SAP entitlement system that Crystal Enterprise uses as the default (that is, the system that is contacted to authenticate users who attempt to log on with SAP credentials but without specifying a particular SAP system). If this list is empty, see “To add an SAP entitlement system to Crystal Enterprise” on page 43.

4 Click Update.



Importing SAP roles to Crystal EnterpriseBy importing SAP roles into Crystal Enterprise, you allow role members to log on to Crystal Enterprise with their usual SAP credentials. In addition, Single Sign On is enabled so that SAP users can be logged on to Crystal Enterprise automatically when they access reports from within the SAPGUI or an SAP Enterprise Portal.

Note: There are often many requirements for enabling SSO. Some of these might include using a driver and application that are SSO-capable, and ensuring your server and web server are in the same domain. For more information about configuring your system for SSO, refer to the appropriate security documents in SAP and Crystal Enterprise.

For each role that you import, Crystal Enterprise generates a group. Each group is named with the following convention: SystemID~ClientNumber@NameOfRole. You can view the new groups in the Groups management area of the CMC. You can also use these groups to define object security within Crystal Enterprise. For details, see “Setting up folders and security in Crystal Enterprise” on page 56.

Consider three main categories of users when configuring Crystal Enterprise for publishing, and when importing roles to Crystal Enterprise:• Crystal Enterprise administrators

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

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

• Role membersRole members are users who belong to “content bearing” roles. That is, these users belong to roles to which reports are published. They have View, View on Demand, and Schedule rights for any reports published to the roles they are members of. However, regular role members cannot publish new content, nor can they publish updated versions of content.

You must import all content publishing and all content bearing roles to Crystal Enterprise prior to publishing for the first time.

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



To import a role to Crystal Enterprise1 Go to the Authentication management area of the CMC.


3 On the Options tab, select or clear the Automatically import users check box, depending on how you want Crystal Enterprise to handle user accounts when you import roles:• Select the check box to have Crystal 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, Crystal Enterprise dynamically creates additional user accounts and user folders when new role members first log on to Crystal Enterprise with valid SAP credentials.

• Clear the check box to have Crystal Enterprise import roles without immediately creating user accounts and user folders.Crystal Enterprise dynamically creates new user accounts and user folders when role members first log on to Crystal Enterprise with valid SAP credentials.

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

4 On the Options tab, select one of the following:• Concurrent users

New user accounts are configured to use concurrent user licenses. Concurrent licenses specify the number of people who can connect to Crystal Enterprise at the same time. This type of licensing is very flexible because a small number of concurrent licenses can support a large user base. For example, depending on how often and how long users access Crystal Enterprise, a 100 user concurrent license could support 250, 500, or 700 users.

• Named usersNew user accounts are configured to use named user licenses. Named user licenses are associated with specific users and allow people to access the system based on their user name and password. This provides named users with access to the system regardless of how many other people are connected. You must have a named user license available for each user account created using this option.Note that the option you select here does not change the number or type of user licenses that you have installed in Crystal Enterprise. You must have the appropriate licenses available on your system.

5 Click Update.

6 On the Role import tab, select the appropriate entitlement system from the Logical system name list.Note: If this list is empty, see “Connecting to SAP entitlement systems” on page 43.



7 In the Available roles area, select the role(s) that you want to import, and then click Add.

8 Click Update.

To check that roles and users were imported correctly1 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 Crystal Enterprise.

2 Go to the Crystal Enterprise SAP Edition web desktop: http://webserver/crystal/enterprise10/sap/ePortfolio (on Windows)http://webserver:port/crystal/enterprise10/sap/desktoplaunch (on UNIX)

3 Click Log On.

4 Type the user name and password of a mapped user.

5 From the Authentication Type list, select SAP.

6 Click Log On.You should be logged on to the web desktop as the selected user.

Integrating with Secure Network CommunicationCrystal Enterprise SAP Edition supports environments that implement Secure Network Communication (SNC) for authentication and/or for data encryption between SAP components. 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 Crystal Enterprise effectively within your secured environment.

Note: • If you have configured the BW Publisher to use a local SAP Gateway, you

must also configure the local SAP Gateway for SNC (for instance, it must be started with the system profile parameter snc/enable). For details, see the SAP Library > Basis Services/Communication Interfaces > SAP Communication: Configuration > SAP Gateway. Relevant headings include “The SAP Gateway and the SNC Interface” and “Parameterization of the SAP Gateway.”

• If you have configured the BW Publisher to use the BW Publisher Service, you must enable SNC for registered servers. For information on how to enable SNC for registered servers, consult the RFC SDK documentation for API RfcAccept. On Windows, 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 Disc 1” on page 28.

• Use your external SNC security product to create an external name for Crystal Enterprise; then create the corresponding SNC name. You will need this SNC name when configuring Crystal Enterprise.



• For complete details on using SNC, see the SNC User’s Guide, which is available through SAPNet.

To enable SNC support within Crystal Enterprise1 Go to the Authentication management area of the CMC.


3 On the SNC settings tab, select the appropriate entitlement system from the Logical system name list.Note: If this list is empty, see “Connecting to SAP entitlement systems” on page 43.

4 Select Enable Secure Network Communication [SNC].Tip: If you clear this check box to disable SNC at a later time, the CMC retains the rest of your SNC settings.

5 Select Disallow insecure incoming RFC connections if you want Crystal Enterprise to refuse requests that do not use SNC.This option enforces the use of SNC and ensures that the BW Publisher uses SNC when users publish reports. Consequently, this option requires you to enable SNC in the SAP Gateway. Alternatively, you must enable SNC for the registered server if you use the BW Publisher service.In addition, you must provide your SNC information in the definition of the RFC (Remote Function Call) destination. Execute transaction SM59 and set your SNC options on the Logon/Security tab. For details, see the SAP Library.

6 Use the remaining fields to provide the information that corresponds to your SNC implementation.

Field Value

SNC library path Type the absolute path to the library that contains the functions provided by your external security product. This library may be referred to elsewhere as the external library, the gssapi library, or SNC_LIB (for example, C:\WINNT\system32\gssapi32.dll).

Quality of Protection Specify the level of security that Crystal Enterprise should apply when it communicates with your SAP system. This value depends on the SNC product that you have installed.

Tip: The Encryption option corresponds to the level referred to as “Privacy” in some SNC products. The “Max. available” option adjusts the quality of protection, depending on the capabilities of your SNC product.

SNC name of SAP system Type the SNC identity of your SAP system.



7 Click Update.

Configuring Data Access

Processing scheduled reports in SAP’s batch modeYou can run scheduled reports in Crystal Enterprise using SAP’s batch mode. The InfoSet and Open SQL drivers can run reports using SAP’s batch or background mode when specific environment variables are set to 1. The relevant environment variables are:• CRYSTAL_INFOSET_FORCE_BATCH_MODE (for the InfoSet driver)• CRYSTAL_OPENSQL_FORCE_BATCH_MODE (for the Open SQL driver)

However, it is recommended that you use this feature only when you have a distributed installation of Crystal Enterprise. When these environment variables are set to 1, the drivers run reports using SAP’s batch mode, regardless of the reporting component that is actually running the report. Therefore, if you create these environment variables as system environment variables on a machine that is running a combination of Crystal Enterprise servers, the drivers run all reports in batch mode (including on-demand report requests from the Page Server and the Report Application Server).

To ensure that the drivers run only your scheduled reports in batch mode (i.e., reports run by the Report Job Server), avoid setting system environment variables on machines running combinations of Crystal Enterprise servers. Instead, follow these steps to customize the environment variables for each Report Job Server.

Note: SAP users who schedule reports in Crystal Enterprise may require additional authorizations in SAP. For details, see “Creating and applying authorizations” on page 41 and “Scheduling a report in batch mode (with an Open SQL query)” on page 121.

To process scheduled reports in SAP’s batch mode1 Create a batch script (.bat file) in a text editor such as Notepad, with the

following contents:

@echo offset CRYSTAL_INFOSET_FORCE_BATCH_MODE=1set CRYSTAL_OPENSQL_FORCE_BATCH_MODE=1

SNC name of Crystal Enterprise system

This optional field is reserved for future use. It allows you to specify the SNC identity that you have created for Crystal Enterprise. If BW is configured to trust incoming connections from this SNC identity, then SAP users logged on to Crystal Enterprise need not provide their credentials again. This feature is not currently supported by BW 3.0B integration.

Field Value



%*

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

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

3 Start the Crystal Configuration Manager (CCM) from the Crystal Enterprise program group.

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

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

6 On the Properties tab, locate the Command field.This is the startup command for the Report Job Server. For instance, the command might look like this (a single line):

"\\SERVER01\C$\Program Files\Crystal Decisions\Enterprise 10\win32_x86\JobServer.exe" -service -name SERVER01.report -ns SERVER01 -objectType CrystalEnterprise.Report -lib procReport -restart

7 Precede the default command with the full path to the jobserver_batchmode.bat file that you saved on the Report Job Server machine.In this example, the batch file is saved on a machine named SERVER01 as:

C:\Crystal Scripts\jobserver_batchmode.bat

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

"\\SERVER01\C$\Crystal Scripts\jobserver_batchmode.bat" "\\SERVER01\C$\Program Files\Crystal Decisions\Enterprise 10\win32_x86\JobServer.exe" -service -name SERVER01.report -ns SERVER01 -objectType CrystalEnterprise.Report -lib procReport -restart

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 Once you have changed the Command field in the CCM, click OK.

9 Right-click the Crystal Report Job Server and, on the shortcut menu, click Start.Note: If the Report Job Server fails to start, verify your new startup command.

10 On the CCM toolbar, click Enable/Disable Servers, log on with your Crystal Enterprise administrator credentials, and ensure that the Report Job Server is enabled.



Configuring SAP Logon for the Data Access KitWhen 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 machine is restarted, the new SAP system 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.


Integrating Crystal Enterprise and BW 6

This chapter shows how to configure BW to enable andadminister report publishing from BW to CrystalEnterprise. It also includes instructions for configuring thehttp request handler in SAP.


Configuration overview

Configuration overviewThis chapter outlines the configuration steps needed to integrate BW and Crystal Enterprise:• Setting up folders and security in Crystal 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, complete the configuration steps outlined in Chapter 5: Performing the initial configuration.

Setting up folders and security in Crystal EnterpriseWhen you install Crystal Enterprise SAP Edition, the setup program creates a folder named SAP (and a subfolder named 1.0) at the top level of folders in Crystal Enterprise. The top-level SAP folder is created with default security settings: the Administrators group is granted Full Control, and the Everyone group is granted No Access. The diagram below shows the folder structure that forms that basis for the hierarchy of roles, folders, and reports that you publish to Crystal Enterprise from within BW.

Note that you, the administrator, are responsible for creating one system folder (<SID>) for each SAP system that you are running.You must also assign appropriate rights for that folder. Content publishers require Edit, Add, View, and Modify rights for each system folder that corresponds to the SAP system from which they are publishing.

Note: After you have set up folders and security in Crystal Enterprise, complete the tasks in “Configuring the BW Publisher” on page 59, and “Configuring publishing in the Content Administration Workbench” on page 65. Once you have completed those tasks, you can publish content to Crystal Enterprise from BW.


6 Integrating Crystal Enterprise and BW

To create a system folder1 Go to the Folders management area of the CMC.

2 Click SAP, click 1.0, and then click the Subfolders tab.

3 Click New Folder.

4 In the Folder Name field, type the three-character system identification that corresponds to the SAP system you are adding a folder for.

5 Add a description for the folder if you like; then click Update.

To assign publishing rights to a system folder1 In the system folder you created, click the Rights tab.

2 Click Add/Remove.The Add/Remove page appears.

3 In the Select Operation list, select Add/Remove Groups.

4 In the Available groups list, select the group(s) that corresponds to the imported content publishing role(s) whose rights you want to specify.

5 Click the > arrow to grant the group access to this folder; then click OK.You are returned to the Rights tab.

6 Click the group’s Access Level list and select Advanced.The Advanced Rights page appears.

7 In the Explicitly Granted column, select the following rights:• Add objects to the folder• View objects• Edit objects• Modify the rights users have to objects• Delete objects (optional)

8 Click OK.Members of this imported role now have permission to publish content from from BW to Crystal Enterprise. For complete details on the predefined access levels and advanced rights, click Help to see the Crystal Enterprise Administrator’s Guide.

Understanding the default folder security patternsWhen you publish to Crystal Enterprise from SAP, Crystal Enterprise automatically creates the remaining hierarchy of roles, folders, and reports. That is, Crystal Enterprise organizes your Crystal reports in folders that are named according to the System ID, the Client number, and the name of the role.


Setting up folders and security in Crystal Enterprise

The diagram that follows shows how Crystal Enterprise organizes content when you publish two roles from one BW system:• The top-level folders (that is, the SAP and 1.0 folders) are created during the

installation.• You, the administrator, create system folders (<SID>) prior to publishing for

the first time.• Crystal Enterprise creates client folders (<Client>), as necessary, when a role is

published from BW.• The Files folder stores all report objects that are published from this system

and client.• Security is set on each report object, so users can view only the reports that

belong to their roles.• The Roles folder and its subfolders provide an alternative way to browse the

published reports. Each subfolder contains shortcuts to the actual report objects that are stored in the Files folder.

By default, each newly created folder or report inherits security settings from its parent folder. Once you publish a role’s content to Crystal Enterprise, the corresponding Crystal Enterprise group (named SystemID~ClientNumber@NameOfRole) is used to grant additional rights to role members. Role members are granted View to each report object that is published from the role.



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

Configuring the BW PublisherThe BW Publisher allows you to publish Crystal reports (.rpt files) individually or in batches from BW to Crystal Enterprise.

On Windows, you can configure the BW Publisher in one of two ways: • Install the BW Publisher as a service on a Crystal Enterprise machine. The BW

Publisher service will start instances of the BW Publisher as required.• Install a local SAP Gateway to create BW Publisher instances.

You must select the configuration method based on the requirements of your site, after considering the advantages and disadvantages of each configuration. However, in most cases it is recommended that you install the BW Publisher as a service. For details, see “Selecting your BW Publisher configuration” on page 16.

For UNIX installations of Crystal Enterprise, follow the instructions for installing the BW Publisher as a service. However, your system configuration will vary slightly as you must manually start the required number of BW Publisher instances.

Once you have configured the BW Publisher in Crystal Enterprise, you must configure publishing in the Content Administration Workbench. See “Configuring publishing in the Content Administration Workbench” on page 65 for details.

Configuring the BW Publisher as a serviceTo enable publishing of reports from BW to Crystal Enterprise, using the BW Publisher as a service, perform the following procedures:• “Starting the BW Publisher” on page 59• “Configuring a destination for the BW Publisher service” on page 61.

For information on adding system redundancy using multiple BW Publishers, see “Distributing the BW Publisher installation” on page 35.

Starting the BW PublisherOn Windows, use the Crystal Configuration Manager (CCM) to start the BW Publisher service. When you start the BW Publisher service it creates a publisher instance to service publishing requests from your BW system. If the volume of publishing requests increases, the BW Publisher automatically spawns additional publishers to meet the demand.


Configuring the BW Publisher

For more information on the CCM, consult the Crystal Enterprise Administrator’s Guide.

On UNIX, run the BW Publisher script to create a publisher instance or instances to handle publishing requests. It is recommended that you start one publisher instance.

Once the BW Publisher service or script starts, it establishes a connection with the SAP Gateway Service that you specified when you ran the Crystal Enterprise SAP Edition setup program. (See “Recommended initial installation” on page 24 for details.)

To start the BW Publisher service on Windows1 Start the Crystal Configuration Manager (CCM) from the Crystal Enterprise

program group.

2 Right-click the Crystal BW Publisher Service and, on the shortcut menu, click Start.

To check that the BW Publisher has started on Windows1 Open the Windows Task Manager dialog box. (Simultaneously press the Ctrl

+Alt-Del keys, and then click Task Manager.)

2 Click the Processes tab.

3 Ensure that the bwcepubsvc.exe and bcepub.exe processes are running.

4 Open a command window. (Under the Windows Start menu, select Run. Type cmd in the run dialog box.)

5 Type the following command, substituting the port number of the SAP Gateway Service for portnum. Include the quotation marks:

netstat -an | find "portnum"

For example, type 33## for portnum, where ## represents the instance number of your SAP Gateway. Typically, the instance number is 00, and the value for this field is 3300.

6 This command establishes if the BW Publisher has started correctly, and has opened a TCP/IP connection with the BW Gateway Service. The result of this command should be:

TCP IP_BW_Publisher:BWPub_portnum IP_Gateway:portnum

where:• IP_BW_Publisher is the IP address of the machine hosting the BW Publishing

service.• BWPub_portnum is the port number of the BW Publishing service.• IP_Gateway is the IP address of the machine hosting the BW Gateway Host.• portnum is the port number of the Gateway Service.



To start the BW Publisher on UNIX1 Log on to your UNIX system under the crystal user account you created for

your Crystal Enterprise installation.

2 Run the following script to start a publisher instance:

./crystal_root/bwcepub.nogwy num -aPROGID -gGWHOST -xGWSERVICE

where:• crystal_root is the root crystal directory where you installed Crystal

Enterprise and Crystal Enterprise SAP Edition.• num is the number of publisher instances to start.• PROGID is the Program ID of the RFC Destination for the BW Publisher. The

Program ID can take any value, but must be 64 characters or fewer, and may not contain spaces. The Program ID is case-sensitive. Record the exact value you specify here for the Program ID. You will need this value when you configure the RFC destination on your BW system. See “Configuring a destination for the BW Publisher service” on page 61.

• GWHOST is the name of your Gateway Host.• GWSERVICE is the port number of the Gateway Service.

Configuring a destination for the BW Publisher serviceTo enable the BW Publisher, you must configure an RFC destination on your BW server to communicate with the BW Publisher service. If you have a BW cluster, configure the RFC destination on each server, using the central instance of BW as your Gateway Host in every case.

Note: Use this procedure if your BW publisher is running on UNIX.

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

To create the required RFC destination (TCP/IP connection)1 Execute transaction SM59, which allows you to display and maintain RFC

destinations.

2 Click Create and provide the values described in the following table.Tip: You cannot view all of these fields until you provide the Connection type.

Field Value

RFC destination Use a descriptive name.

Note: Do not use the name CRYSTAL_PUBLISHER unless you do not have the Content Administration Workbench. See “Configuring publishing in the Content Administration Workbench” on page 65 for details.



3 After saving your settings, click Test connection.The connection test attempts to contact your BW Publisher service. If the RFC destination is properly configured and can communicate with your BW Publisher service, the result is a list showing how long it took to contact the service on each of four attempts. If the RFC destination cannot contact your BW Publisher service, the result is a connection error.

Note: • The publishing process will not work until the destination is working successfully.• If you plan to enforce Secure Network Communication (SNC) between SAP

and Crystal Enterprise, you must provide your SNC options on the Logon/Security tab for the CRYSTAL_PUBLISHER destination. For details about SNC, see “Integrating with Secure Network Communication” on page 49.

For more information on RFC destinations and TCP/IP connection types, consult your SAP documentation.

Connection type Type T (for TCP/IP connection) and press Enter.

Description Type a short description of the destination.

Activation Type Select “Registered Server Program.”

Program ID Type the descriptive string used to identify the process associated with this destination. You must use the same Program ID that you specified:• On Windows, when you installed Crystal Enterprise SAP Edition on your Crystal Enterprise machines. See “Recommended initial installation” on page 24.• On UNIX, when you started the BW Publisher. See “To start the BW Publisher on UNIX” on page 61.

Tip: Program ID is case-sensitive.

Gateway host Type the name of your BW server. If you have a BW cluster, enter the name of the central instance of BW. You must use the same BW server name here that you specified when you installed Crystal Enterprise SAP Edition on your Crystal Enterprise machines. For details, see:• “Recommended initial installation” on page 24.• “Publishing using the BW Publisher service” on page 17.

Gateway service Type the port number that the Gateway host is listening on. For example, type 33##, where ## represents the instance number of your SAP Gateway. Typically, the instance number is 00, and the value for this field is 3300.If you have defined a symbolic name for this port (such as sapgw##), you may use this symbolic name instead.You must use the same port number or symbolic name here that you specified when you installed Crystal Enterprise SAP Edition on your Crystal Enterprise machines.For details, see:• “Recommended initial installation” on page 24.• “Distributing information over the Web” on page 18

Field Value



Configuring the BW Publisher with a local SAP GatewayTo enable publishing of reports from BW to Crystal Enterprise, using a local SAP Gateway, perform the following procedures:• “Installing a local SAP Gateway” on page 63.• “Configuring a destination for the BW Publisher” on page 64.

It is not recommended that you use this configuration if Crystal Enterprise is installed on UNIX.

Installing a local SAP GatewayA local SAP Gateway must be installed on the machine where you installed the BW Publisher (from Add-Ons Disc 1). (See “Recommended initial installation” on page 24.) It is recommended that an SAP BASIS administrator perform the installation of one of these SAP Gateways.

For up-to-date instructions on installing a local SAP Gateway, see the SAP installation instructions included on your SAP Presentation CD. This section provides complementary instructions, including additional steps that are required when you install a SAP Gateway for use with Crystal Enterprise.

Note: For a detailed list of tested environments for Crystal Enterprise SAP Edition, consult the platforms_EN.txt file included with your product distribution. This file includes specific version and Service Pack requirements for application servers, operating systems, SAP components, etc.

To install a local SAP Gateway1 Log on as an Administrator of the local machine.

2 Install the GWSETUP program according to the SAP installation instructions included on your SAP Presentation CD.If you need to run the installation script (GWSETUP.BAT) file from the network, do so from a mapped network drive.Note: You will be prompted for an SAP System ID (SID). The value that you type is used as the ID for the SAP Gateway instance. These steps use GAT as the system ID, but you can use a different three-character value if necessary.

3 Run the newly installed GWSETUP program according to the SAP installation instructions included on your SAP Presentation CD.To access the setup program, click Start > Programs > SAP System Setup for GAT > SAP Setup - Standalone Gateway.Note: • When prompted for your SAP System ID (SID), type GAT• When prompted to choose an installation type, select “Local installation”

(instead of “Domain installation”).• During the installation, you will set the password for two new Windows

user accounts that are created on the local machine: the SAP system



administrator account (<SID>adm) and the SAP service account (SAPService<SID>). Be sure to make note of the passwords you create.

• If prompted with LDAP Support options, select “No LDAP Support.”

4 When the SAP Gateway installation has finished, ensure that the Windows TMP system environment variable is set to the same value as the Windows TEMP system environment variable.For details on changing environment variables, consult your Windows help.

5 Log off of the local machine, and log back on under the local SAP system administrator account. (The user name is gatadm, and the password is the value you provided during the SAP Gateway installation.)

6 Using regedit, verify the TMP and TEMP registry entries under the HKEY_CURRENT_USER\Environment subkey.Both registry entries should hold the same string value, which must be a valid absolute directory path. If either entry’s value contains the %USERPROFILE% variable, replace it with an absolute directory path. Typically, both registry entries are set to C:\WINNT\TEMP

Configuring a destination for the BW PublisherTo enable the BW Publisher, 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.

To create the required RFC destination (TCP/IP connection)1 Execute transaction SM59, which allows you to display and maintain RFC

destinations.Here you will create a TCP/IP connection.

2 Click Create and provide the values described in the following table.Tip: You cannot view all of these fields until you provide the Connection type.

Field Value

RFC destination Use a descriptive name.

Note: Do not use the name CRYSTAL_PUBLISHER unless you do not have the Content Administration Workbench. See “Configuring publishing in the Content Administration Workbench” on page 65 for details.

Connection type Type T (for TCP/IP connection) and press Enter.

Description Type a short description of the destination.

Activation Type Select “Start on Explicit Host.”



3 After saving your settings, click Test connection.The connection test attempts to contact your BW Publisher on the local SAP Gateway. If the RFC destination is properly configured and can communicate with your BW Publisher, the result is a list showing how long it took to contact the Gateway on each of four attempts. If the RFC destination cannot contact your BW Publisher, the result is a connection error.

Note: • The publishing process will not work until the destination is working successfully. • If you plan to enforce Secure Network Communication (SNC) between SAP

and Crystal Enterprise, you must provide your SNC options on the Logon/Security tab for the CRYSTAL_PUBLISHER destination. For details about SNC, see “Integrating with Secure Network Communication” on page 49.

For more information on RFC destinations and TCP/IP connection types, consult your SAP documentation.

Configuring publishing in the Content Administration Workbench

Once you have set up SAP authentication, and have configured the BW Publisher, 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.• Set up connections to the Crystal Enterprise systems where content is published.• Define which roles can publish to each Crystal Enterprise system.• Publish content from BW to Crystal Enterprise.

If you did not receive the Crystal Content Administration Workbench transport as a part of your Crystal Enterprise SAP Edition installation you can configure

Program Type the absolute path to the BW Publisher program (bwcepub.exe). If you installed it in the default directory on Windows, the value is:C:\Progra~1\Common~1\Crysta~1\2.0\bin\bwcepub.exe

Tip: Use the MS-DOS short path name, as shown here.

Target host Type the fully qualified domain name or IP address of the machine where you installed the BW Publisher. For example: ceserver01.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.” For example: ceserver01

Gateway service Type sapgw##, where ## represents the instance number of your SAP Gateway. Typically, the instance number is 00, and the value for this field is sapgw00

Field Value



publishing from BW using the procedures outlined in Appendix D: Using ABAP to configure publishing. To use this method for configuring publishing, you must name your RFC destination CRYSTAL_PUBLISHER.

Creating roles in BW for designated content publishers and administratorsWhen you are configuring BW for integration with Crystal Enterprise, assess whether or not your current role structure allows you to quickly designate particular BW users as Crystal Enterprise content or system administrators. This section suggests some additional roles that you might want to create, if your current role structure is insufficient.

For example, you might want to allow a subset of your BW users to act as content administrators—users who publish batches of reports on behalf of a number of BW roles. Instead of adding the SAP content administrators to every role, create a new role with a name such as CE_CONTENT_PUBLISHERS, and add each content publisher to the role. Do not add any reports to this role.

Further, you might also want to provide a small number of BW users with system administration rights to Crystal Enterprise. Again, create a new role with a name such as CE_SYSTEM_ADMINISTRATORS, and add each designated administrator to the role.

Tip: In Crystal Enterprise 10 you can assign an administrative user either full system administration rights or a subset of those rights. For more information, consult “Controlling Administrative Access” in the Crystal Enterprise Administrator’s Guide.

To modify the rights that these new roles (or any of your existing roles) are granted in Crystal Enterprise, you must first set up SAP Authentication and import the roles. You can then modify the rights of each imported role through the Crystal Management Console.

For details on creating roles, see your SAP documentation. For more information on the use of roles in administering content, see the following sections:• “Importing SAP roles to Crystal Enterprise” on page 47.• “Setting up folders and security in Crystal Enterprise” on page 56.• “Understanding the default folder security patterns” on page 57.

Configuring access to the Content Administration WorkbenchThere are three types of users who may access the Content Administration Workbench:• Crystal Enterprise administrators, who are able to perform all tasks within

Content Administration Workbench. These tasks include defining Crystal Enterprise systems, publishing reports, and performing report maintenance.

• Crystal Enterprise content publishers, who can view, publish, modify, and (optionally) delete reports from BW.

• Content consumers, who belong to content-bearing roles and who can view reports.



You must apply the appropriate set of authorizations within BW to each type of user, as listed in the following tables.

Authorizations for administrative users

Authorizations for content publishers

Authorization object Field Values

S_RFC RFC_TYPE FUGR

RFC_NAME /CRYSTAL/CE_SYNCH, SH3A, SUNI

ACTVT Execute (16)

S_TCODE TCD /CRYSTAL/RPTADMIN, RSCR_MAINT_PUBLISH

S_TABU_CLI CLIIDMAINT X

S_TABU_DIS ACTVT Change, Display (02, 03)

DICBERCLS &NC&

S_BTCH_JOB JOBACTION DELE, RELE

JOBGROUP ’ ’

S_RS_ADMWB ACTVT Execute (16)

RSADMWBOBJ WORKBENCH

ZCNTADMCES ACTVT Create new, Change, Display, Delete (01, 02, 03, 06)

ZCNTADMJOB ACTVT Create new, Delete (01, 06)

ZCNTADMRPT ACTVT Display, Delete, Activate, Maintain, Check (03, 06, 07, 23, 39)


S_RFC RFC_TYPE FUGR

RFC_NAME /CRYSTAL/CE_SYNCH, SH3A, SUNI

ACTVT Execute (16)

S_TCODE TCD /CRYSTAL/RPTADMIN

S_BTCH_JOB JOBACTION DELE, RELE

JOBGROUP ’ ’



ZCNTADMCES ACTVT Display (03)

ZCNTADMJOB ACTVT (New, Delete) 01, 06

ZCNTADMRPT ACTVT Display, Activate, Maintain, Check (03, 07, 23, 39)Delete (optional) (06)Edit (optional) (02)



Granting content publishers the right to delete reports in the BW Content Administration Workbench is optional. However, be aware that deleting a report in BW also deletes the report in Crystal Enterprise. If publishers do not have sufficient rights to delete reports in Crystal Enterprise, an error results. See “Setting up folders and security in Crystal Enterprise” on page 56 for information on granting rights in Crystal Enterprise.

Content consumers9

Defining a Crystal Enterprise systemYou must create a system definition within the Content Administration Workbench for each Crystal Enterprise system to which you want to publish reports.

To add a Crystal Enterprise system1 Execute the transaction /crystal/rptadmin to access the Content Administration

Workbench.

2 From the Operations pane, select Crystal Enterprise.

3 Double-click Add new system.

4 On the System tab, enter the following values:• Type a descriptive name in the Alias field. Avoid using spaces or special

characters, as these characters need special treatment when the alias name is used while configuring Enterprise Portals.

• Type the name of the machine that is running your Crystal Enterprise CMS. If you configured your CMS to listen on a port other than the default, 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 Crystal Enterprise system. Only one Crystal Enterprise system can be the default. In the list of all available systems, the default system is indicated with a green checkmark.

5 Click Save.


S_RFC RFC_TYPE FUGR

RFC_NAME SH3A, SUNI

ACTVT Execute (16)

S_TCODE TCD /CRYSTAL/RPTADMIN



ZCNTADMRPT ACTVT Display (03)



6 On the RFC Destinations tab, add each RFC destination that is associated with this Crystal Enterprise system. To add a destination, click the Insert Row button. In the list that appears, double-click the name of the RFC destination.Note: A Crystal Enterprise system may have multiple destinations to add system redundancy. See “Distributing the BW Publisher installation” on page 35 for more information.

7 Next, test the destination. Select the destination you just added by clicking the gray box to the left of its name.

8 Click Verify CE definition. This test verifies that BW can contact the specified BW Publisher, and can log on to this Crystal Enterprise system using the Crystal entitlement user account.

9 On the HTTP tab, enter the following values:• Protocol

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

• Web server host and portType the fully qualified domain name or IP address of the web server that hosts your Crystal Enterprise web desktop. For a installation that uses a Java application server, include the port number. For example: ceserver01.crystaldecisions.com:8080

• PathIf you followed a default installation of Crystal Enterprise, type:crystal/enterprise10/sap

This path is essentially the virtual path that your web server uses when referring to the sap subfolder of your Crystal Enterprise web content. Provide an alternate value only if you have customized your web environment and the location of the Crystal Enterprise web content files.Do not include a forward slash at the beginning or at the end of this entry.

• Viewer applicationType the name of your viewer application. If Crystal Enterprise was installed on Windows using the default CSP configuration, type viewreport.csp to use the default viewer. Type viewreport.do to use the default viewer for Crystal Enterprise installations that use the Java version of the web desktop. (All UNIX installations of Crystal Enterprise use the Java web desktop.) Or type the name of your own custom viewer application.

10 On the Languages tab, select the languages of reports that will be published to this Crystal Enterprise system.

11 Use the Roles tab to add the content-bearing roles that you want to associate with this Crystal Enterprise system. See “Importing SAP roles to Crystal Enterprise” on page 47 for more information.

12 Click the Insert Row button.



A list of roles available to add to this Crystal Enterprise system is displayed. Note: Each role can publish to only one Crystal Enterprise system. If the roles that you want to add to this Crystal Enterprise are not displayed in the list, click Cancel to return to the Roles tab. Then click Reassign Roles.

13 Select the roles that you want to publish to this Crystal Enterprise system, and click the Ok button.

14 Next, set the default security settings for content published to this Crystal Enterprise system. Click the Layout tab, and select the security settings that are used by default for reports and roles folders. Consult your Crystal Enterprise Administrator’s Guide for more information about these security settings.Note: • A folder is created automatically in Crystal Enterprise for each role

published to that system. This folder contains shortcuts to the reports published under that role.

• Once you have configured a Crystal Enterprise system, changing the default security levels here will not affect the security levels of published role folders or reports. To change the default security levels for all roles and content published to this Crystal Enterprise, delete the roles folders and shortcuts in Crystal Enterprise. (This will not delete the actual reports.) Then change the security settings here, and republish the roles and reports.

15 Click the Ok button at the bottom to save your settings and create the Crystal Enterprise system in the Content Administration Workbench.

You are now able to publish reports to Crystal Enterprise from BW.

Publishing reports using the Content Administration WorkbenchAfter a report has been saved to BW, you can publish it using the Content Administration Workbench. You can use the Content Administration Workbench to publish individual reports, or you can publish all reports saved to a particular role. Only a user who has the authorizations granted to a Crystal content publisher (see “Creating and applying authorizations” on page 41) can use the Content Administration Workbench to publish and maintain reports.

Publishing roles or reports1 Execute the transaction /crystal/rptadmin to access the Content

Administration Workbench.

2 From the Operations pane, select Publish reports.

3 To find content saved to your BW system, double-click Select reports and roles to publish.



A dialog box designed to help you filter the available roles and reports appears.

4 From the Crystal Enterprise System list, select the Crystal Enterprise system or systems containing content that you want to display. Note: The Crystal Enterprise System list contains all available systems defined on this BW system.

5 Next, filter your results to limit the number of reports and roles that will be displayed. Use these options:• Object version

Selecting “A: active” displays all reports that can be published. Selecting the blank option displays all reports. (The remaining options are SAP reserved terms.)

• Object statusSelect “ACT Active, executable” to display only reports that have been published. Select “INA Inactive, not executable” to display only reports which have not been published. Leave the field blank to display all reports. (The remaining options are SAP reserved terms.)

• Role filterIf you type text in this box, only the roles that match what you type here are displayed. Use * as a wildcard character. For example, to display all roles beginning with the letter d, type “d*”.

• Report description If you type text in this box, only the reports whose descriptions match what you type here are displayed. Use * as a wildcard character to match any number of characters. Use + as a wildcard to match 0 or 1 characters. For



example, to display all reports whose description contains the word revenue, type *revenue* .

6 Click Ok.The list of reports that meet your criteria appears in the right-hand panel.

The reports are arranged in a hierarchy: Crystal Enterprise system > Roles on that system > Reports saved to the role.Each item in the hierarchy is labeled with a red, yellow, or green dot. 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. For example, if one report in a role is yellow (active), but all of the rest are green (published), then the role shows as yellow (active). • Green: The item is fully published. If the item is a Crystal Enterprise system

or a role, all reports in that item are published. • Yellow: The item is active, but not published. If the item is a report, the item

is available for publishing. If the item is a role or a Crystal Enterprise system, at least one of the items it contains is active.

• Red: The item is SAP content, and is not available for publishing using the Content Administration Workbench.



7 Select the reports that you want to publish. To publish all o f the reports in a role, select the role. To publish all roles on a Crystal Enterprise system, select the system. Note: When you select a role (or a system), all reports contained in that role (or system) are selected. To clear this selection, clear the role (or system) checkbox, and then click Refresh.

8 Click Publish.Note: Reports published in the background are processed as system resources become available. To use this option, click “In background” instead of Publish. See “Scheduling background publishing” on page 73 for details.

9 Click Refresh to update the display of the status of Crystal Enterprise systems, roles, and reports in the Content Administration Workbench. Tip: To view a report, right-click the report and select View. To see which queries are used by the report, right-click the report and select Used Queries.

Scheduling background publishing Publishing reports in the background, either immediately or as a scheduled job, conserves system resources. It is recommended that you publish reports in the background to improve system responsiveness.

Publishing reports periodically, as scheduled jobs, synchronizes the report information between BW and your Crystal Enterprise system. It is recommended that you schedule all reports (or roles containing these reports). You can also manually synchronize roles and reports using the Update status option of the Report Maintenance operation. See “Updating the status of reports” on page 75 for details.

To publish a report immediately1 Use the Content Administration Workbench to find the reports or roles that

you want to publish, as described in “Publishing roles or reports” on page 70.

2 In the Content panel, select the roles or reports to publish.Note: Only active (yellow) reports or roles are available to be published.

3 Click In background to publish the selected items as a background process. The “Define Background Job” transaction appears.

4 To publish the item immediately, click Start Condition, and then click Immediate and save the job. The job appears under Scheduled jobs in the Operations tree.A user with administrative privileges may need to release this job (using transaction SM37) before it is published.



To publish a report as a scheduled job1 Use the Content Administration Workbench to find the reports or roles that

you want to publish, as described in “Publishing roles or reports” on page 70.

2 In the Content panel, select the roles or reports to publish.Note: Only active (yellow) reports or roles are available to be published.

3 Click In background to publish the selected items as a background process. The “Define Background Job” transaction appears.

4 To publish the item at a scheduled time, click Start Condition.

5 Click Date/Time and specify when the job should start.

6 Click Periodic job, and then Period values. Use the Period Values dialog to specify how often the job should run.

7 Click Save to save the period values, and then click Save again to save the job.The job appears under Scheduled jobs in the Operations tree.A user with administrative privileges may need to release this job (using transaction SM37) before it is published.

Updating system information for published reportsThe BW Publisher uses the SAP system information entered here to update the data source of published reports. You can choose to use the local BW application server, or the central BW instance if you prefer a load balancing configuration.

To update system information1 Execute the transaction /crystal/rptadmin to access the Content


2 From the Operations pane, select Publish reports.

3 Under SAP system settings, double-click Set BW source parameters.

4 To change an existing BW system, click Display ->Change, and then update the information about the listed system.

5 To add a new BW system (or a load-balanced system), first select any existing entries, and click Delete. Then click New Entries, and add information about the new system.

6 Click Save on the SAP toolbar.

Maintaining reportsReport maintenance tasks include synchronizing information about reports between Crystal Enterprise and BW (Update status), deleting unwanted reports (Delete reports), and updating reports migrated from previous versions of Crystal Enterprise (Post-migration).



Updating the status of reportsIf you make a change to a published report on a Crystal Enterprise system (such as changing which role a report is published to), the change is not reflected in BW until you synchronize Crystal Enterprise and BW. You can schedule a publishing job to periodically synchronize Crystal Enterprise and BW (see “Scheduling background publishing” on page 73), or you can manually update the status of the report using the Report Maintenance tool.

To update reports1 Execute the transaction /crystal/rptadmin to access the Content


2 Under Report Maintenance, double-click Update Status.

3 Use the dialog that appears to filter the list of displayed Crystal Enterprise systems, roles, and reports, as described in “Publishing roles or reports” on page 70.

4 Select the reports you want to update from the displayed list. To select all reports and roles on a Crystal Enterprise system, select the system.

5 Click Version Check.BW connects to the Crystal Enterprise systems containing the reports you have indicated, to synchronize information. If BW cannot contact a Crystal Enterprise system, it returns an error message. You must correct the problem before you can update the status of reports on that system in BW.

Deleting reportsDeleting a published report from BW using the Content Administration Workbench also deletes the report from Crystal Enterprise. Only users who have been granted the authorizations necessary to delete reports on both BW and the Crystal Enterprise system can remove reports.

Note: If a user has rights to delete a report on BW, but not on the Crystal Enterprise system where that report is published, you may encounter an error.

To delete reports1 Execute the transaction /crystal/rptadmin to access the Content


2 Under Report Maintenance, double-click Delete reports.

3 Use the dialog that appears to filter the list of displayed Crystal Enterprise systems, roles, and reports, as described in “Publishing roles or reports” on page 70.

4 Select the reports you want to delete from the displayed list. To select all reports and roles on a Crystal Enterprise system, select the system.


Configuring the SAP http request handler

Note: You cannot delete reports using the Content Administration Workbench if their status dot is red. These reports are SAP content.

5 Click Delete reports.BW connects to the Crystal Enterprise systems containing the reports you have indicated, to delete the reports. If BW cannot contact a Crystal Enterprise system, it returns an error message. You must correct the problem before you can delete these reports.

Completing a report migrationAfter you migrate from Crystal Enterprise 8.5 or Crystal Enterprise 9 to Crystal Enterprise 10, you must update all of your published reports.

To migrate reports1 Execute the transaction /crystal/rptadmin to access the Content


2 Under Report Maintenance, double-click Post-migrationAll Crystal Enterprise systems containing reports that need to be migrated are displayed.

3 Select the systems you want to migrate, and then click Execute post migration.You must update all reports and roles on a system.

BW connects to the Crystal Enterprise systems containing the reports you have indicated, to update the reports. If BW cannot contact a Crystal Enterprise system, it returns an error message. You must correct the problem before you can update these reports and complete the system migration to version 10.

Configuring the SAP http request handlerTo enable viewing of reports in BW or using a Crystal iView, you must configure BW to use the http request handler that is included as part of the Crystal Content Administration Workbench transport. Then, when a BW user opens a Crystal report from within the SAPGUI or an SAP Enterprise Portal, BW is able to route the viewing request over the Web appropriately.

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. You may have to manually activate this service after creating it.


Working with Web Content and Sample Reports 7

This chapter briefly describes the Crystal Enterprise SAPEdition web desktop, which is included with the WebContent feature of Crystal Enterprise SAP Edition.


Crystal Enterprise SAP Edition web desktop

Crystal Enterprise SAP Edition web desktopThe web desktop serves as a window to Crystal Reports on your company’s existing intranet or Internet site. When you use Crystal Enterprise SAP Edition, you can choose the Crystal Enterprise SAP Edition web desktop or a web desktop designed by someone in your company. The web desktop helps organize your reports into logical groups—using folders—and allows you to search for and view reports.

Through the Crystal Enterprise SAP Edition web desktop, you can access all the Crystal reports that have been saved in your SAP roles or included with BW’s predefined Business Content. You can configure your own personal desktop settings and save your favorite reports. Once you have found the reports you want to look at, the web desktop offers report viewers with printing and exporting capabilities.

To access the Crystal Enterprise SAP Edition web desktopGo to the main page of the web desktop for SAP:

http://webserver/crystal/enterprise10/sap/ePortfolio (on Windows)

http://webserver:port/crystal/enterprise10/sap/desktoplaunch (on UNIX)

Replace webserver with the name of the web server that is set up for Crystal Enterprise. For more information about the web desktop, click Help to see the Crystal Enterprise SAP Edition Web Desktop Guide.

Setting up the sample reportsThe 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. By analyzing or modifying these samples, you can create reports that display your SAP data in ways that offer the greatest value to your SAP users.

To analyze the sample reports1 Start Crystal Reports and, on the File menu, click Open.

2 Locate the sample reports folder (usually C:\Program Files\Crystal Decisions\Enhanced SAP Edition 10\Sample Reports\).Depending on which database drivers you installed, you will see up to three subfolders—BW Query Reports, InfoSet Reports, and Open SQL Reports. Each subfolder corresponds to a specific Data Access Kit driver.

3 Browse the subfolders’ contents, select the report that you want to see, and then click Open.The report appears in the Preview tab of Crystal Reports.


7 Working with Web Content and Sample Reports

4 Click the Design tab see how the sections and groups have been used to create the report’s layout.

5 Use the other tools in Crystal Reports—such as the Field Explorer, the Formula Workshop, and the Record Selection Formula Editor—to see how the SAP data has been incorporated and utilized in the report.

To refresh the sample reports against your SAP systemNote: Depending on your current SAP configuration, you may or may not retrieve data when you refresh the sample reports against your SAP system.

1 Start Crystal Reports and, on the File menu, click Open.

2 Locate the sample reports folder (usually C:\Program Files\Crystal Decisions\Enhanced SAP Edition 10\Sample Reports\).

3 Browse the subfolders’ contents, select the report that you want to see, and then click Open.The report appears in the Preview tab of Crystal Reports.

4 On the Report menu, click Refresh Report Data.Note: If the report contains parameters, the Refresh Report Data dialog box prompts you to “Use current parameter values” or “Prompt for new parameter values.” If you are unfamiliar with report parameters, select “Use current parameter values” and click OK.The SAP System Logon dialog box appears.

5 In the Available SAP systems list, select your SAP system; then click Next.The SAP System Logon dialog box prompts you for User Data.Note: If your SAP administrator has not configured SAP Logon, your SAP system will not appear in the Available SAP systems list.

6 In the Client field, type the number appropriate to your SAP system.

7 Type your usual logon information in the User Name, Password, and Language fields. Then, click Next.

8 If you want the SAP Communication Library to create trace files for all client/server communication (for troubleshooting purposes), select the Generate RFC trace files check box.

9 Click Finish.

The report should now be refreshed with data from your SAP system. However, if no data appears in the report, and you receive no database error messages, then it is likely that the report is using tables and fields that are empty in your SAP system. By editing the report’s record selection formula, you may be able to alter the report so that it coincides with your SAP data. To locate the record selection formula, click Report > Selection Formulas > Record.


Verifying configuration options in Crystal Reports

Verifying configuration options in Crystal ReportsThe setup program changes some configuration options of your Report Designer so that it can take advantage of the drivers’ advanced features. These global changes affect your default reporting options; therefore, you may notice slightly altered behaviors when you report off data sources other than SAP.

The driver installation configures the Report Designer to list tables and fields by both name and description. These configuration changes generally improve the experience of reporting off SAP data. Your SAP system may contain thousands of tables, each with a predefined, non-descriptive name. The configuration changes ensure that you can select specific tables for a report without having to search through an immense list. To locate these configuration options in the Report Designer, see “To view configuration options”.

To view configuration options1 On the Crystal Reports File menu, click Options.

2 Click the Database tab.The Database tab shows your current configuration.

3 In the Data Explorer area, select the check boxes for the types of data that you want to make available to the report.Note: InfoSets and ABAP queries are treated as Stored Procedures, so verify that this check box is selected.


7 Working with Web Content and Sample Reports

4 Use the Table name LIKE and/or the Owner LIKE fields to select only a subset of the available data types. Use the following techniques when filtering:• Type full or partial names of tables.• Separate distinct names with commas.• Add wildcards to select multiple queries or InfoSets: use a percentage sign

(%) to denote any number of characters; use an underscore (_) to denote a single character. (The % and _ wildcards correspond respectively to the * and ? wildcards used within Windows.)

• Clear the field and click OK to proceed without filtering. Note, however, that there is a limit to the number of objects that can be displayed in the Data Explorer. If the number of queries or InfoSets in SAP exceeds this limit (which is by default 8000), you may receive an Out of Memory error or a blank Data Explorer.

5 To see both names and descriptions of tables and fields, in the Tables and Fields area, select Both.

6 Click OK.


Verifying configuration options in Crystal Reports


Defining Security for the Open SQL driver 8

This chapter shows how to use the Security DefinitionEditor to define table-level and row-level security forspecific SAP tables when you access them using the OpenSQL driver. The Security Definition Editor enables you tomaintain your current SAP security levels when you deploythe Open SQL driver.


Security Definition Editor overview

Security Definition Editor overviewWhen you deploy the Data Access Kit component and distribute the database drivers, you allow SAP users to access the data stored within your SAP R/3 and BW systems. By default, the Open SQL driver provides an open reporting environment where there are no data access restrictions. (You can, however, easily reverse this default behavior with the Security Definition Editor’s Global Lock feature, which initially restricts users from accessing all SAP tables. For details, see “Choosing your table-level security model” on page 85.)

If you need to deploy a security model that regulates users’ access to SAP data, use the Security Definition Editor (transaction /CRYSTAL/RLS) to restrict data access at the table level and at the row level. The Security Definition Editor defines security for transparent tables, pool tables, cluster tables, and tables containing data clusters (for instance, PCL2). The restrictions that you specify are enforced whenever a user attempts to connect to SAP with the Open SQL driver, whether to design, refresh, or schedule a Crystal report. Thus, in order to design, refresh, or schedule a Crystal report against R/3 or BW, users require access to all of the tables referred to by the report.

Data access restrictions that you define using the Security Definition Editor are applied on a per-client basis. That is, the restrictions you apply affect all users who access SAP using the same client used to define the restrictions.

In previous versions of Crystal Enterprise Enhanced SAP Edition, data access restrictions were client-independent. To preserve restrictions that you defined using earlier versions of this tool, follow the instructions in “Migrating your existing security model” on page 85 before continuing.

This chapter includes the following sections:• “Migrating your existing security model” on page 85• “Choosing your table-level security model” on page 85• “Customizing authorizations for specific tables” on page 87• “Defining table authorizations by group” on page 91• “Applying row-level security” on page 92

Note: The Security Definition Editor is provided by the Security Definition Editor transport, which you import into your SAP system when you set up the Data Access Kit. For details, see “Configuring transports” on page 38.


8 Defining Security for the Open SQL driver

Migrating your existing security modelTo continue to use the data access restrictions that you defined using a previous version of Crystal Enterprise Enhanced SAP Edition (using the ZRLS transaction), you must import these restrictions into client-dependent form using /CRYSTAL/RLS . Import these data restrictions before using /CRYSTAL/RLS to create or modify additional restrictions. Any changes you made using /CRYSTAL/RLS will be overwritten when you import the global restrictions.

To apply your global data access restrictions to additional clients, import these restrictions once for each client.

To migrate data access restrictions1 Enter the transaction /CRYSTAL/RLS in your SAP system.

2 Under the Extras menu, select Import Global Data.A dialog appears, warning you that importing these restrictions will overwrite any restrictions you have defined using /CRYSTAL/RLS.

3 Click Yes.Your global, client-independent data access restrictions are imported.

Choosing your table-level security modelFor enhanced flexibility, the Security Definition Editor provides a Global Lock feature, 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. To customize the model to match your current SAP security configuration, you can prevent users from accessing particular tables on a table-by-table basis. When you first deploy the Data Access Kit, the Global Lock is disabled by default.

• Global Lock enabledThis closed security model initially denies all users access to all tables. To customize the model to match your current SAP security conventions, you can authorize users to access particular tables on a table-by-table basis. Additionally, you can specify a list of custom functions that users can still report off when the Global Lock is enabled. For details, see “Customizing authorizations for specific functions” on page 91 for details.

Once you have enabled or disabled the Global Lock, you can refine the security model by customizing data access authorizations for particular tables. For details, see “Customizing authorizations for specific tables” on page 87.


Choosing your table-level security model

To enable/disable the Global Lock1 From the SAPGUI, execute transaction /CRYSTAL/RLS.

The Security Definition Editor appears.

2 You now have two options:• If you want to enable the Global Lock, select the “Allow access only to the

tables specified above” option.• If you want to disable 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, you can customize authorizations for particular users and tables, thereby allowing or disallowing data access in order to match your SAP security conventions.



Customizing authorizations for specific tablesWhether you have enabled or disabled the Global Lock feature, you may need to customize the data access authorizations for one or more SAP tables. If the Global Lock is enabled, you will need to allow all or some users to access particular tables. (Otherwise, users will be unable to design or refresh reports against the SAP system.) Alternatively, if the Global Lock is disabled, you may need to prevent all or some users from accessing tables that contain sensitive data.

In either case, whether you want to secure a table or to permit access to a table, you must use an authorization object for that purpose. (You can customize a new authorization object, or reuse an existing one.) Then, using the Security Definition Editor, you associate the authorization object with the table in question. Finally, you incorporate the new authorization object into your current configuration of user profiles or roles.

Essentially, by associating an authorization object with an SAP table, you define that table as an exception to the Global Lock settings that you have made within the Security Definition Editor. In other words, once you’ve associated an authorization object with a table, that table is withheld from all users—regardless of your Global Lock settings. 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.

To customize authorizations for a specific table1 Create a new authorization object.

For this example, create an authorization object called ZTABCHK that consists of one authorization field called TABLE. The ZTABCHK authorization is being used to secure the VBAK table from all but a particular subset of users. Note: Use transaction SU21 to create the authorization object, or see the SAPGUI Help for more information on creating authorization objects.

2 From the SAPGUI, execute transaction /CRYSTAL/RLS.


Customizing authorizations for specific tables

The Security Definition Editor screen appears.

You will now associate your new authorization object with an SAP table.

3 In the Table name field, type the name of the table whose security definition you will customize.For this example, type VBAK.

4 Click Create.



The “Authorization entries” screen appears.

5 Click Create.The “Authorization Object entry” dialog box appears.

6 Click Reference to an authorization object.Tip: For details on the second option—Reference to an already defined table or group—see “Defining table authorizations by group” on page 91. Note, however, that this secondary option is not supported in SAP BW at this time.


Customizing authorizations for specific tables

7 Click OK.The “Authorization Object entry” screen appears.

8 In the Authorization object name field, type the name of the authorization object that you created in step 1.For this example, type ZTABCHK.

9 Click Create.The “Authorization field values” screen appears.



10 In the Field value list, type the name of the table whose security definition you want to customize. For this example, type VBAK.

11 Click Save.You have now associated your customized authorization object with a specific SAP table.

12 Exit the Security Definition Editor.

13 Following your usual procedure, incorporate the new authorization object into your configuration of user profiles or roles.For instance, following this example, you would apply the ZTABCHK authorization object to the subset of users who need to access the VBAK table.Depending on the version of R/3 that you are using, and the SAP authorization model that you have already deployed, 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.• Attach the new authorization object to a new profile that you in turn add to

each user’s security profile.The end result is that the authorization is added to the master user data, so the database drivers can adhere to your customized data access restrictions.Note: Regardless of the method you use, ensure that your new authorization holds the name of the correct database table in its TABLE field value. In this example, the VBAK table must be specified.

Customizing authorizations for specific functionsWhen the Global Lock feature is disabled, report designers essentially have the freedom to call any function on the SAP system. To restrict the functions available to report off, enable the Global Lock. This restricts users from calling any functions on the SAP system. In the /CRYSTAL/AUTHFCN table, you can specify a list of functions that are exceptions to the Global Lock. That is, you can specify a list of functions that users are able to call. Use the /CRYSTAL/RLSFCN transaction you created in “Customizing authorizations for specific tables” on page 87 to access the /CRYSTAL/AUTHFCN table.

Defining table authorizations by groupThe 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.The “Reference to an already defined table or group” option is provided in the “Select authorization entry type” screen, which appears in the Security Definition Editor when you create an authorization entry for a table.


Applying row-level security

Note: The “Reference to an already defined table or group” option is not supported in SAP BW at this time.

• You can reference multiple tables to a group table that acts as a security template.To create a group table, execute transaction /CRYSTAL/RLS and specify a nonexistent table name in the Editor. (When the specified table does not exist, the Editor assumes instead that you are creating a group or template.) The main screen listing all the definitions will show the table type as group. You can now share security levels by referencing existing tables to this security template.

Applying row-level securitySometimes 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, while at the same time limiting a subset of those users to a certain portion of the table’s data. To accomplish this, use the Security Definition Editor to define an additional level of security for the individual rows of data.

In general, row-level security is based on a particular field within a table. For instance, you might need to prevent users from seeing data for all customers within a Sales table. To enable this type of restriction, you create an authorization object and use the Security Definition Editor to associate the object with the Customer field in the Sales table. Then, when you apply the new authorization object to each user’s profile or role, you specify the Customer values for those customers whose Sales records the user is permitted to view. When the user designs or refreshes reports against the Sales table, data is returned only for those customers that you have specified.

Essentially, by associating an authorization object with a field within an SAP table, you define that table as an exception to the Global Lock settings that you have made within the Security Definition Editor. In other words, once you’ve associated an authorization object with a field, the parent table is secured from all users—regardless of your Global Lock settings. 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.

There are two ways to secure rows within a table. You can use authorization objects or custom functions.

Securing rows using authorization objectsIn order to define row-level security for tables, you can create an authorization object and use the Security Definition Editor to associate the object with one of the table’s fields. 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. When you apply the authorization object, you specify the rows of data that each user is permitted to access.



To define row-level security using an authorization object1 Create a new authorization object.

For this example, create an authorization object called Z_BUKRS that consists of one authorization field called BUKRS. This authorization is being used to secure the GLT0 table based on the values in the BUKRS (Company Codes) field.Note: Use transaction SU21 to create the authorization object, or see the SAPGUI Help for more information on creating authorization objects.

2 Execute transaction /CRYSTAL/RLS to access the Security Definition Editor.

3 In the Table name field, type the name of the table that contains the rows you want to secure.For this example, type GLT0.

4 Click Create.

5 In the “Authorization entries” screen, click Create.

6 In the “Select authorization entry type” screen, click Reference to an authorization object.

7 Click OK to access the “Authorization Object entry” screen.

8 In the Authorization object name field, type the name of the authorization that you created in step 1.For this example, you would type Z_BUKRS.

9 Click Create.The “Authorization field values” screen appears.

10 In the Field value list, type the equals sign (=) and the name of the field that you want to secure.For this example, you would type =BUKRS.



Tip: To view a list of available fields, right-click the Field value list and, on the shortcut menu, click Possible entries. Double-click the desired field (in this case, BUKRS) to insert it along with the required equals sign (=).

11 Click Save.

12 Exit the Security Definition Editor.

13 Following your usual procedure, apply the new authorization object to the profiles or roles of the appropriate users.For instance, following this example, you would apply the Z_BUKRS authorization object to each user who needs to access rows of data within the GLT0 table. When you apply the authorization object, you enter the appropriate Company Code values into the BUKRS authorization field, thereby specifying the Company Codes that the specified user is authorized to access.Depending on the version of R/3 that you are using, and the SAP authorization model that you have already deployed, 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. • Attach the new authorization object to a new profile that you in turn add to

each user’s security profile.The end result is that the authorization is added to the master user data, so the database drivers can adhere to your customized data access restrictions.

Securing rows using custom security exitsIn addition to, or instead of using authorization-based restrictions for tables, you can secure rows using custom security exits. 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.

Note: • You must give a value (either constant or field-mapped) for all non-optional

parameters.• Make mappings between compatible types. For example, do not link a

function parameter for a date to a number field. Mapping incompatible types results in a failure at runtime.

The following example shows how to map table fields to function parameters in a custom security exit.

To define row-level security using a custom security exit1 Execute transaction /CRYSTAL/RLS.

2 In the Table name field, type the name of the data table whose rows you want to secure.For this example, type PA0000 to secure the rows in that table.



3 Click Create. The “Authorization entries” screen appears.

This screen lists the authorization entries (if any) that are currently applied to the table.

4 Click Custom exit.The “Edit custom function security exit mappings” window appears.

5 In the Function name field, type the name of the function that you want to use to secure the table, and then click Transfer.For this example, type HR_CHECK_AUTHORITY_INFTY.



6 For each necessary parameter, specify a value or field to map to that parameter.In this example make the entries listed in the table below:

7 Click Save.You are returned to the “Authorization entries” screen, which now indicates that there is an active custom security exit for this table.When a user attempts to access a table secured by a custom security exit, the driver checks the appropriate field(s) in the table. The field values you mapped are passed as parameters to the function you selected, in this example HR_CHECK_AUTHORITY_INFTY.

Imported parameter name Field name

INFTY ‘0000’

PERNR =PERNR

SUBTY =SUBTY


Troubleshooting A

This appendix describes some common installation andconfiguration issues in order to assist you in troubleshootingyour Crystal Enterprise SAP Edition implementation.


Troubleshooting overview

Troubleshooting overviewFor the latest troubleshooting information from SAP, search the online SAP Notes for items related to BW, Formatted Reporting, Crystal Enterprise, or Crystal Reports. In particular, search for notes in the BW-BEX-ET-FR or XX-PART-CRR application areas, and check notes 509786 and 510045.

You can also check out the Crystal Care technical support web site for white papers, files and updates, user forums, and Knowledge Base articles:

http://support.businessobjects.com/search/

Locating and generating log filesYou can create and view several log files to help determine the cause of errors. The core Crystal Enterprise server components log information by default to the logging directory of your Crystal Enterprise installation. For details about these system log files, see the Crystal Enterprise Administrator’s Guide (admin.pdf in the doc directory of your Crystal Enterprise product distribution).

Troubleshooting Crystal EnterpriseIn the CMC, you can temporarily disable a connection between Crystal Enterprise and an SAP entitlement system. This may be useful to maintain the responsiveness of Crystal Enterprise in cases such as the scheduled down time of an SAP entitlement system.

To temporarily disable a connection to an SAP entitlement system1 In the CMC, go to the Authorization management area.


3 In the Logical system name list, select the system you want to disable.

4 Select the Disabled check box.

5 Click Update.

Note: See the Crystal Enterprise Administrator’s Guide (admin.pdf in the doc directory of your Crystal Enterprise product distribution) for a number of sections devoted to general system troubleshooting, such as web server configuration, path mapping, report processing, and so on.


A Troubleshooting

Troubleshooting your InfoSet driver installationThis section describes some common installation and configuration issues in order to assist you in troubleshooting an installation of the InfoSet driver.

Reports, tables, and functionsIf the SAP data source does not appear when you create a new report, there may be a problem with the driver installation, or required files may have been deleted since installation. Run the Crystal Reports–SAP Edition installation again.

Errors when importing transport filesIf an error message indicates that the client 800 does not exist, ensure that you specify a valid client when you execute the TP command. (Client 800 is used as the default if you don’t specify one.) Similarly, errors occur if the client that you specify does not exist in the target system.

If the TP command finishes with a return code of 200, or if an error message indicates a problem with the datafile or cofile, verify that the user account running the transport is the SAP administrator account, and ensure that the transport files are writable before you import them.On UNIX systems, verify that the transport files were added by FTP in Binary mode, otherwise the files become corrupted.

Errors when connecting to SAPIf an error message indicates that the RSAQ_REMOTE_FUNCAREA_CATALOG function module was not found, you may be trying to use the InfoSet driver to access a system that is older than R/3 4.6b. The InfoSet driver is supported only for versions 4.6b and later of SAP R/3.

Obtaining Add-Ons Disc 2If you did not receive the Add-Ons Disc 2 with your product distribution, you can request it at:

http://www.businessobjects.com/CEESEV10/Disc2/


Obtaining Add-Ons Disc 2


Transport Files B

This appendix lists the names and contents of the transportsthat are included on both Add-Ons CDs. Also read thetransports_EN.txt file located in the transports directoryon both Add-Ons CDs. This text file lists the names of thefiles that make up each transport.


Overview

OverviewCrystal Enterprise Enhanced SAP Edition 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 Crystal Enterprise SAP Edition.

The contents of each transport are listed here. To determine which transports you need to import, see “Configuring transports” on page 38.

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 both Add-Ons CDs lists the Unicode compatible and ANSI transport files.

Note: When checking for possible installation conflicts, ensure that none of the object names already exists in your SAP system.

Open SQL Connectivity transportThe Open SQL Connectivity transport enables the drivers to connect to and report off the SAP system.

Object Type Description

/CRYSTAL/BC Package Development class

/CRYSTAL/OPENSQL Function group Open SQL functions

/CRYSTAL/OSQL_AUTH_FORMS Program Helper program

/CRYSTAL/OSQL_EXECUTE Program Helper program

/CRYSTAL/OSQL_TYPEPOOLPROG

Program Helper program

/CRYSTAL/OSQL_TYPEPOOLS Program Helper program

/CRYSTAL/OSQL_UTILS Program Helper program

ZSSI Authorization object class

Reporting authorization objects

ZSEGREPORT Authorization object

Reporting authorization object

/CRYSTAL/OSQL_CLU_ACTKEY_ENTRY

Table Cluster meta data

/CRYSTAL/OSQL_FCN_PARAM Table Function meta data


B Transport Files

InfoSet Connectivity transportThe InfoSet Connectivity transport enables the InfoSet driver to access InfoSets. This transport is compatible with R/3 4.6b and later. Do not import this transport if you are running R/3 4.6a or earlier.

/CRYSTAL/OSQL_FCN_PARAM_FIELD

Table Function meta data

/CRYSTAL/OSQL_FIELD_ENTRY Table Table meta data

/CRYSTAL/OSQL_OBJECT_ENTRY

Table Table meta data

/CRYSTAL/OSQL_RLS_CHK_ENTRY

Table RLS meta data

/CRYSTAL/OSQL_RLS_FCN_ENTRY

Table RLS meta data

/CRYSTAL/OSQL_RLS_VAL_ENTRY

Table RLS meta data

ZCLUSTDATA Table Cluster meta data

ZCLUSTID Table Cluster meta data

ZCLUSTKEY Table Cluster meta data

ZCLUSTKEY2 Table Cluster meta data

/CRYSTAL/AUTHCHK Table RLS meta data

/CRYSTAL/AUTHFCN Table RLS meta data

/CRYSTAL/AUTHKEY Table RLS meta data

/CRYSTAL/AUTHOBJ Table RLS meta data

/CRYSTAL/AUTHREF Table RLS meta data

ZSSAUTHCHK Table Old RLS meta data

ZSSAUTHOBJ Table Old RLS meta data

ZSSAUTHKEY Table Old RLS meta data

ZSSAUTHREF Table Old RLS meta data

ZSSAUTH FCN Table Old RLS meta data




/CRYSTAL/FLAT Function group InfoSet wrapper functions

/CRYSTAL/QUERY_BATCH Program Batch mode execution vehicle


Overview

Row-level Security Definition transportThis 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. For details on using the Security Definition Editor, see “Security Definition Editor overview” on page 84.

Cluster Definition transportThis 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. For details on using the Cluster Definition Tool, see the “Reporting off clusters” section of the Crystal Enterprise SAP Edition User’s Guide.

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



/CRYSTAL/TABMNT Function group Function group for table maintenance view for function restrictions

/CRYSTAL/RLSDEF Program Main program

/CRYSTAL/RLS_INCLUDE1

Program Include program containing the module definitions

/CRYSTAL/RLS_INCLUDE2

Program Include program containing the subroutine definitions

TDDAT [/CRYSTAL/AUTHFCN]

Table contents Table maintenance definition

TVDIR [/CRYSTAL/AUTHFCN]

Table contents Table maintenance definition

/CRYSTAL/AUTHFCNS Definition of transport and maintenance object

Table maintenance definition

/CRYSTAL/RLS Transaction Main program transaction

/CRYSTAL/RLSFCN Transaction Helper transaction called internally by main program.


Z001 Package Old development class

ZCIMPRBG Program Main program


B Transport Files

Authentication Helpers transportThis transport provides the Single Sign On enhancement for the InfoSet driver. This enhancement frees users from having to enter their credentials more than once to access any of the Crystal Enterprise, R3, and BW systems.

Crystal Content Administration Workbench transportThis transport provides content administration functionality for BW systems. It is available only as a Unicode compatible transport.

ZCRBGTOP Program Include program

ZCDD Transaction Main program transaction




/CRYSTAL/SECURITY Function group Security helper functions



/CRYSTAL/CL_BW_HTTP_HANDLER

Class Multi CE-aware HTTP request handler

/CRYSTAL/OBJECT_STATUS_DOM

Domain Report activity

/CRYSTAL/OBJ_POLICY_DOM Domain CE object security

/CRYSTAL/OBJECT_STATUS Data element Report activity

/CRYSTAL/OBJ_POLICY Data element CE object security

/CRYSTAL/CE_SYNCH Function group Publisher stubs

/CRYSTAL/CA_MSG Message class Status messages

/CRYSTAL/CE_SYNCH_FORMS Program Program component

/CRYSTAL/CONTENT_ADMIN Program Program component

/CRYSTAL/CONTENT_ADMIN_CLASS_D

Program Program component

/CRYSTAL/CONTENT_ADMIN_CLASS_I


/CRYSTAL/CONTENT_ADMIN_CTREE



Overview

/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


/CRYSTAL/PUBLISH_WORKER Program Program component

/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 Table Application state

/CRYSTAL/CA_JOB Table Application state

/CRYSTAL/CA_JOB2 Table Application state

/CRYSTAL/CA_LANG Table Application state

/CRYSTAL/CA_PARM Table Application state

/CRYSTAL/CA_ROLE Table Application state

/CRYSTAL/CA_SYST Table Application state

/CRYSTAL/MENU_TREE_ITEMS Structure Application state

/CRYSTAL/REPORT_ID Table Application state

/CRYSTAL/RPTADMIN Transaction Main program transaction

/CRYSTAL/EDIT_REPORT Program Wrapper for report edit



B Transport Files

BW Query parameter personalization transportThis transport provides support for personalized and default parameter values in reports based on BW queries.

/CRYSTAL/EDIT_REPORT Function Group

Functions for report edit

Z001 Package Old package for authorization objects

ZSSI Authorization object class

Crystal Authorizations

ZCNTADMCES Authorization object

CE operations

ZCNTADMRPT Authorization object

Report operations

ZCNTADMJOB Authorization object

Background job operations




/CRYSTAL/PERS_VAR Structure Variable definition

/CRYSTAL/PERS_VALUE Structure Value definition

/CRYSTAL/PERS Function Group Personalization functions


Overview


Authorizations C

This appendix provides a list of SAP authorizations that, inour experience and in our test environment, are requiredwhen carrying out common tasks with Crystal EnterpriseSAP Edition. Additional authorization objects or fields maybe required, depending upon your individualimplementation.


Authorizations overview

Authorizations overviewThis appendix provides a list of SAP authorizations that, in our experience and in our test environment, are required when carrying out common tasks with Crystal Enterprise SAP Edition. Additional authorization objects or fields may be required, depending upon your individual implementation.

From each authorization object, you must create an authorization and define the appropriate field values. You then apply the three new authorizations to the profiles (or roles) of your SAP users. The following sections describe the required authorizations and provide you with the necessary field values. For procedural details that are specific to your version of SAP, refer to your SAP documentation.

Note: • The information in this appendix is provided as a guideline only. • The ZSEGREPORT authorization object belongs to the ZSSI object class, which

is installed when you import the Crystal Enterprise Enhanced SAP Edition transport files needed to support Open SQL queries.

Actions in BW

From within Crystal Reports

Logging on to an SAP server

* USER_ROLE denotes the name of any role that the user belongs to. You can enter multiple values in this field

Creating a new report from a query in a BW role


S_RFC RFC_TYPE FUGR

RFC_NAME SUSO, SUNI, RSCR, SH3A, RFC1, RZX0, RZX2

ACTVT 16

S_USER_AGR ACT_GROUP USER_ROLE*

ACTVT 01, 02, 06



ACTVT 01, 02, 06


C Authorizations

* USER_ROLE denotes the name of any role that the user belongs to. You can enter multiple values in this field

* QUERY_OWNER denotes the name of the owner of the query. If you specify a name, you can report off only those queries with that owner. Enter * to report off of queries with any owner.

Opening an existing report from a BW role

S_RFC RFC_TYPE FUGR

RFC_NAME RS_PERS_BOD

ACTVT 16

S_CTS_ADMI CTS_ADMFCT TABL

S_RS_COMP RSINFOAREA 0MKT_MK

RSINFOCUBE 0CRM_MC05

RSZCOMPTP REP

RSZCOMPID ACRM_0

S_RS_COMP1 RSZCOMPID ACRM_0CRM_MC05_Q0001

RSZCOMPTP REP

RSZOWNER QUERY_OWNER*

ACTVT 16



S_RFC RFC_TYPE FUGR

RFC_NAME SUSO, SUNI. RSCR, SH3A, RFC1, RZX0, RZX2, RS_PERS_BOD

ACTVT 16

S_RS_COMP RSINFOAREA INFO_AREA**

RSINFOCUBE INFO_CUBE**

RSZCOMPTP REP

RSZCOMPID COMP_ID**

S_RS_COMP1 RSZCOMPID COMP_ID**

RSZCOMPTP REP


ACTVT 16


Actions in BW

* QUERY_OWNER denotes the name of the owner of the query from which you are creating the report. If you enter the name of the query owner, you can only report off of queries with this owner. Enter * to denote any query owner.

** For INFO_AREA, INFO_CUBE, or COMP_ID enter * to denote any value. If you specify a specific value, you can only report off of queries that contain these info areas, cubes, and component IDs.

Previewing or refreshing a report



Verifying the database (refreshing table definitions in a report)




RSZCOMPTP REP

RSZCOMPID COMP_ID**


RSZCOMPTP REP


ACTVT 16




RSZCOMPTP REP

RSZCOMPID COMP_ID**


RSZCOMPTP REP


ACTVT 16


C Authorizations



Setting the location of the data source


Saving a report to a BW role

Preparing a report for translation while saving to BW


S_RS_COMP RSINFOAREA 0MKT_MK

RSINFOCUBE 0CRM_MC05

RSZCOMPTP REP

RSZCOMPID ACRM_0

S_RS_COMP1 RSZCOMPID ACRM_0CRM_MC05_Q0001

RSZCOMPTP REP


ACTVT 16



ACTVT 01, 02, 06




ACTVT 01



Actions in BW

Saving a report and simultaneously publishing it to Crystal Enterprise



Saving a report as an iView

Exporting a report as a .ivu file



ACTVT 01




RSZCOMPTP REP

RSZCOMPID COMP_ID**

S_RS_COMP1 RSZCOMPID COMP_ID

RSZCOMPTP REP


ACTVT 16



ACTVT 01, 02, 06




ACTVT 01


S_GUI ACTVT 61


C Authorizations

Starting the Business Explorer Query Designer



From within the Crystal Enterprise SAP Edition web desktop

Logging on to Crystal Enterprise with SAP credentials

Viewing an SAP BW report on demand




RSZCOMPTP REP

RSZCOMPID COMP_ID**


RSZCOMPTP REP


ACTVT 16

S_CTS_ADMI CST_ADMFCT TABL


S_ADMI_FCD S_ADMI_FCD STOR, STOM


S_RFC RFC_TYPE FUGR

RFC_NAME SYST, RSOB, SUNI

ACTVT 16



RSZCOMPTP REP

RSZCOMPID COMP_ID**


Actions in BW



Refreshing a report from the viewer



RSZCOMPTP REP

RSZOWNER QUERY_OWNER

ACTVT 16

S_RS_ODSO RSINFOAREA INFO_AREA**

RSODSOBJ 0CRM_OLVM

RSODSPART DATA

ACTVT 03





RSZCOMPTP REP

RSZCOMPID COMP_ID**


RSZCOMPTP REP


ACTVT 16


RSODSOBJ 0CRM_OLVM

RSODSPART DATA

ACTVT 03


C Authorizations


Scheduling a report



Reading dynamic picklists in report parameters


S_RFC RFC_TYPE FUGR

RFC_NAME SYST, RSOB, SUNI

ACTVT 16



RSZCOMPTP REP

RSZCOMPID COMP_ID**


RSZCOMPTP REP


ACTVT 16


RSODSOBJ 0CRM_OLVM

RSODSPART DATA

ACTVT 03


S_RFC RFC_TYPE FUGR

RFC_NAME SYST, RSOB

ACTVT 16


Actions in R/3

Actions in R/3

From within Crystal Reports using the Open SQL driver


Creating a new report

Opening or previewing an existing report



S_RFC RFC_TYPE FUGR

RFC_NAME SYST, /CRYSTAL/OPENSQL

ACTVT 16


S_RFC RFC_TYPE FUGR


ACTVT 16


S_RFC RFC_TYPE FUGR


ACTVT 16

ZSEGREPORT ACTVT 02



ZSEGREPORT ACTVT 02

S_RFC RFC_TYPE FUGR

RFC_NAME /CRYSTAL/OPENSQL

ACTVT 16


C Authorizations


From within Crystal Reports using the InfoSet driver, reporting off InfoSet


Creating a new report from an InfoSet on R/3

Note: Also add enough authorizations to view data rows. For example, P_ORIG or P_APAP (see “Setting the location of the data source” on page 120).



ZSEGREPORT ACTVT 02

S_RFC RFC_TYPE FUGR

RFC_NAME /CRYSTAL/OPENSQL

ACTVT 16


S_RFC RFC_TYPE FUGR

RFC_NAME SYST

ACTVT 16


S_RFC RFC_TYPE FUGR

RFC_NAME /CRYSTAL/FLAT, SKBW, AQRC

ACTVT 16





Actions in R/3


From within Crystal Reports using the InfoSet driver, reporting off an ABAP query


Creating a new report from an ABAP query on R/3



P_ABAP REPID AQTGSYSTGENERATESY, SAPDBPNP

COARS 2


S_RFC RFC_TYPE FUGR

RFC_NAME SYST

ACTVT 16


P_ABAP REPID AQTG02==========P6, SAPDBPNP

COARS 2


S_TABU_DIS ACTVT 03

GROUP Name of table group



S_RFC RFC_TYPE FUGR

RFC_NAME SKBW

ACTVT 16


C Authorizations


From within Crystal Enterprise

Scheduling a report in dialog mode (with an Open SQL query)

Note: The value for CLASS is BLANK.

Scheduling a report in batch mode (with an Open SQL query)



COARS 2


S_RFC RFC_TYPE FUGR

RFC_NAME SKBW

ACTVT 16

S_TABU_DIS ACTVT 03

GROUP Name of table group


COARS 2


S_USER_GRP CLASS

ACTVT 03, 05

S_RFC RFC_TYPE FUGR

RFC_NAME SYST, RFC1, /CRYSTAL/OPENSQL

ACTVT 16

ZSEGREPORT ACTVT 02


S_USER_GRP CLASS

ACTVT 03, 05


Crystal entitlement system

Note: The value for CLASS is BLANK.

Crystal entitlement systemSee “Creating a user account for Crystal Enterprise” on page 41 for a complete listing.

S_RFC RFC_TYPE FUGR

RFC_NAME SYST, RFC1, /CRYSTAL/OPENSQL, SH3A

ACTVT 16

S_BTCH_JOB JOBGROUP ' '

JOBACTION RELE

ZSEGREPORT ACTVT 02

S_BTCH_ADM BTCADMIN Y



Using ABAP to configure publishing D

This appendix describes how to configure the BW Publisherusing an ABAP program. Use this procedure if you do nothave the Content Administration Workbench.


Configuring publishing without the Content Administration Workbench

Configuring publishing without the Content Administration Workbench

This appendix describes how to configure the BW Publisher if you do not have the Content Administration Workbench. The Content Administration Workbench gives you additional functionality, such as the ability to publish to multiple Crystal Enterprise systems per BW system. It is recommended that you use the Content Administration Workbench if it is available.

You can use the ABAP program to configure publishing whether you install the BW Publisher service, or install the BW Publisher on a stand-alone SAP Gateway.

Before beginning, use the appropriate set of instructions to configure the BW Publisher. In either case, create an RFC destination with the name CRYSTAL_PUBLISHER:• “Configuring the BW Publisher” on page 59.• “Configuring the BW Publisher with a local SAP Gateway” on page 63.

Once you have configured the BW Publisher, set the installation parameters as described here.

Setting the installation parametersBW includes an ABAP program that is designed to assist you in setting and checking the Crystal Enterprise installation parameters. This section shows how to use this program (RSCR_CHECK_INSTALLATION_PARAMS) to provide BW with the information it needs about your Crystal Enterprise installation.

The process of setting the installation parameters consists of completing two checks—one check for each of the groups of installation parameters:• The URL Parameter Check provides BW with information about the web

server that is connected to Crystal Enterprise. So, when a BW user opens a Crystal report from within the SAPGUI or an SAP Enterprise Portal, BW is able to route the viewing request over the Web appropriately.

• The Publish Settings Check ensures that reports published from BW to Crystal Enterprise are associated with the appropriate data source. These settings include the Logon Group that provides users with data access privileges.

Note: To set the installation parameters, follow these procedures in order. For more information, consult your BW documentation.

To start the configuration program1 Execute transaction SE38 to access the ABAP Editor.


D Using ABAP to configure publishing

2 In the Program field, type RSCR_CHECK_INSTALLATION_PARAMS and click Execute.This program is provided with BW to assist you in connecting BW to Crystal Enterprise.

When you execute the program, the “Check Crystal Enterprise Installation Parameters” screen appears.

3 In the Checktype column, ensure that Checks is expanded, so you can view the three subfolders: URL Parameter Check, Publish Settings Check, and RFC connection test.Note: Return codes of zero indicate success.

To set the URL parameters1 Select the URL Parameter Check folder; then click Maintain.

The Variable Replacement CR table appears.

2 Complete the table with the appropriate field values, so your BW system is able to locate and send information over the Web to Crystal Enterprise:Note: As of Crystal Enterprise 10, the APS is known as the Crystal Management Server (CMS).

Field Value

APS Name Type the name of the machine that is running your Crystal Enterprise CMS. If you configured your CMS to listen on a port other than the default, type CMSNAME:PORT


Setting the installation parameters

3 Save your changes and return to the RSCR_CHECK_INSTALLATION_PARAMS program.

To set the publishing settings1 Select the Publish Settings Check folder; then click Maintain.

The “Parameter for Publishing on Crystal Enterprise” table appears.

2 Complete the table with the appropriate field values:

Path Prefix If you followed a default installation of Crystal Enterprise, type:crystal/enterprise10/sap

This path prefix is essentially the virtual path that your web server uses when referring to the sap subfolder of your Crystal Enterprise web content. Provide an alternate value only if you have customized your web environment and the location of the Crystal Enterprise web content files.

Note: Do not include a forward slash at the beginning or at the end of this entry.

Log Type http (unless the web server that is connected to Crystal Enterprise is configured to use https).

Crystal Enterprise Server

Type the fully qualified domain name or IP address of the web server where you installed the Web Connector component of Crystal Enterprise. For example: ceserver01.businessobjects.com

APS Cluster Provide this value only if you have set up an CMS cluster. Prefix the name of the CMS cluster with the @ symbol, as in @CLUSTERNAME

Field Value

Field Value

Logon Group Type the name of the logon group that must verify users’ credentials when they schedule reports or refresh them against the BW system.

Tip: If you haven’t set up logon groups in BW, the default SPACE or PUBLIC groups may be available.

Application Server Type the name of your application server. This server will be set as the data source of reports that are published from BW to Crystal Enterprise.

System Number Type the appropriate System Number.

Trace Level (‘on: X’) This optional value determines the amount of information that is logged by the BW system.

Router String to Reach the BW System from CE

Provide this value only if an BW Router separates your application server from Crystal Enterprise. In such cases, a router string allows for effective communication across your network. Consult your SAP documentation for more information.


Index

AABAP queries, reporting off....................................... 15applying authorizations ............................................ 41architecture .............................................................. 12

diagram.............................................................. 14audience, intended..................................................... 2authorizations

applying for Data Access Kit users...................... 41for Crystal Enterprise .......................................... 41rights in Crystal Enterprise .................................. 56

Automatically import users check box ...................... 45

BBusiness Information Warehouse. See BW................ 12BW........................................................................... 12

configuring......................................................... 38integrating with Crystal Enterprise ...................... 56requirements ................................................ 24, 28

BW Publisher...................................................... 12, 16configuring

as a service.............................................. 17, 59on UNIX.................................................. 17, 59using an ABAP program .............................. 124without the Content Administration

Workbench............................................... 124distributing components..................................... 35selecting a configuration .................................... 16using a local SAP gateway.................................. 17

BW Publisher serviceconfiguring......................................................... 59creating RFC destination .................................... 61starting ............................................................... 59

BW queries, reporting off.......................................... 15

Cclient requirements ................................................... 24Cluster Definition tool ...................................... 39, 104Cluster Definition transport............................... 39, 104communication, over TCP/IP .................................... 16components

Cluster Definition tool................................ 39, 104of the product .................................................... 12Security Definition Editor ................................... 84

configuration options, Report Designer..................... 80conflicts, resolving.................................................... 40

content administration.............................................. 66Content Administration Workbench ........................... 9

adding Crystal Enterprise systems....................... 68applying authorizations for ................................ 66defining user access levels ................................. 66deleting reports .................................................. 75migrating reports from earlier versions ............... 76overview of report publishing ............................ 65publishing reports in background....................... 73publishing reports using ..................................... 70synchronizing report information ................. 73, 74updating data source of reports .......................... 74

conventions used in this guide ................................... 5creating authorizations ............................................. 41Crystal Decisions namespace ................................... 40Crystal Enterprise...................................................... 12

adding servers.................................................... 36configuring for SNC ........................................... 49creating account for ........................................... 41distributing components..................................... 34UNIX requirements ............................................ 27Windows requirements ...................................... 23

Crystal Enterprise Enhanced SAP Edition .................... 2Crystal Enterprise SAP Edition..................................... 2Crystal Management Server (CMS)............................ 15Crystal Reports ......................................................... 12

configuration options ......................................... 80requirements...................................................... 24

customizingsample reports ................................................... 78security definitions............................................. 84

DData Access ............................................................. 12Data Access Kit

contents of the transports ................................. 101installation overview.......................................... 38required authorizations ...................................... 41sample reports ................................................... 78

data access restrictions ............................................. 84data sources ............................................................. 15

updating for reports............................................ 74default security patterns............................................ 57defining security....................................................... 84description, of product ............................................. 12disabling SAP authentication .................................... 45


distributingcomponents........................................................34reports over the Web ..........................................18

document conventions................................................5

EEnable SAP Authentication check box.......................45entitlement systems...................................................43

Ffeatures, of the product .............................................12folder security ...........................................................56function groups included in transports ....................102

Gglobal lock feature ....................................................85green checkmark, for default system .........................68groups.......................................................................47GWSETUP ................................................................63

Hhelp

product registration ..............................................4technical support..................................................5

Iimporting roles to Crystal Enterprise ..........................47InfoSet Connectivity transport ...................................39InfoSet driver

sample reports ....................................................78troubleshooting installation ................................99

InfoSets, reporting off ................................................15installation ................................................................22

default security levels .........................................57distributed ..........................................................34recommended ....................................................24troubleshooting ..................................................97

installation types .......................................................22installing ...................................................................22

on UNIX.............................................................27on Windows.......................................................22SAP Gateway on Windows.................................63server components on UNIX...............................28

integrating with SNC.................................................49

JJob Server .................................................................36

KKeep entitlement system disabled field......................45key combinations........................................................5keyboard shortcuts ......................................................5

Llocking down tables.................................................. 85logon tickets ............................................................. 24

Mmapping roles........................................................... 47Max failed entitlement system accesses field............. 45migrating reports from Crystal Enterprise 8.5 or 9 ..... 76minimum requirements

UNIX ................................................................. 27Windows ........................................................... 23

Nnamespace, resolving Crystal Decisions.................... 40

Oobject rights.............................................................. 56objects included in transports ................................. 102Open SQL Connectivity transport ............................. 39Open SQL driver

default security model ........................................ 84defining security................................................. 84sample reports.................................................... 78

Options tab............................................................... 45options, Report Designer configuration..................... 80

PPage Server............................................................... 36prerequisites to installing

UNIX ................................................................. 27Windows ........................................................... 23

product overview...................................................... 12product registration..................................................... 4profile parameters............................................... 24, 49programs included in transports.............................. 102publishing................................................................. 16

all reports in a role or system ............................. 70defining roles for, in BW .................................... 66in the background .............................................. 73multiple reports using roles ................................ 70reports in batch mode ........................................ 51scheduling in background .................................. 73setting up ........................................................... 65to multiple Crystal Enterprise systems................. 68using a local SAP Gateway................................. 17without the Content Administration Workbench .................................................... 124

RR/3............................................................................ 38recommended installation ........................................ 24report designer.......................................................... 12


Report Designer, configuration options .................... 80report maintenance .................................................. 74reporting

configuration options......................................... 80off SAP data ....................................................... 15

reportscreating ............................................................. 15deleting ............................................................. 75migrating from version 8.5 or 9.......................... 76processing on server groups ............................... 78publishing.......................................................... 70

in batch mode............................................... 51overview....................................................... 16

samples ............................................................. 78viewing.............................................................. 78

requirements for installingUNIX ................................................................. 27Windows ........................................................... 23

restrictionsdata access ........................................................ 84row-level ........................................................... 92table-level.......................................................... 85

RFC destinationfor BW Publisher service.................................... 61for local SAP Gateway ....................................... 64

rolescreating for administration ................................. 66importing........................................................... 47

row-level securityauthorization objects, using ............................... 92custom security exits, using ............................... 94overview............................................................ 92

RSCR_CHECK_INSTALLATION_PARAMS.............. 124

Ssample reports

analyzing........................................................... 78refreshing against SAP........................................ 79setting up........................................................... 78

SAP Authentication ............................................ 12, 15distributing components .................................... 36enabling/disabling ............................................. 45

SAP authentication, options...................................... 45SAP BW. See BW ..................................................... 12SAP Gateway

and SNC ............................................................ 49distributing components .................................... 35installing............................................................ 63publishing using a local ............................... 17, 63

SAP Presentation CD, requirements.......................... 23SAP Tools toolbar..................................................... 15SAPGUI requirements .............................................. 24scaling your installation............................................ 34

Secure Network Communication (SNC), integrating with ....................................................49

securitydefault patterns...................................................57defining ..............................................................84global lock feature..............................................85in Crystal Enterprise............................................56migrating from client-independent model...........85preserving existing restrictions ............................85row-level restrictions ..........................................92table-level restrictions.........................................85

Security Definition Editor transport ...................39, 104Security Definition Editor, described .........................84security plug-ins........................................................15server installation................................................28, 36server transports, contents of ...................................101services files

UNIX..................................................................27Windows............................................................23

Single Sign On ..........................................................15importing roles ...................................................47

supportproduct registration ..............................................4technical ..............................................................5web site................................................................5

synchronizing report information ........................73, 75system account .........................................................41system requirements

UNIX..................................................................27Windows............................................................23

Ttable-level security....................................................85tables

customizing authorizations.................................87defining security by group ..................................91included in transports .......................................102locking down .....................................................85

TCP/IP communication .............................................16technical support ........................................................5toolbar, SAP Tools ....................................................15transports

authentication helper........................................105checking for conflicts .........................................40cluster definition...............................................104Content Administration Workbench .................105contents............................................................101importing............................................................41InfoSet connectivity ..........................................103Open SQL Connectivity....................................102parameter personalization ..........................40, 107Row-level security definition ............................104


UUNIX

configuring BW Publisher...................................17installing.............................................................27requirements ......................................................27

user account, creating for Crystal Enterprise ..............41

Vviewing

configuration options..........................................80enabling in BW or IViews...................................76reports ................................................................78

WWeb Content ................................................12, 18, 78

distributing components .....................................36web desktop, Crystal Enterprise SAP Edition..............78web server, distributing.............................................35web sites

consulting.............................................................5Customer Handbook ............................................4technical support..................................................5training.................................................................5

Windowsinstalling.............................................................22requirements ......................................................23


Crystal Enterprise 10

Documents

Transcript of Crystal Enterprise 10