CR for HANA Components Installation, Configuration, and Administration Guide · SAP Crystal Reports, version for SAP HANA Document Version: 1.0 - 2014-09-10 CR for HANA Components

SAP Crystal Reports, version for SAP HANADocument Version: 1.0 - 2014-09-10

CR for HANA Components Installation, Configuration, and Administration Guide

Table of Contents1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Prerequisites and system requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.1 Account permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62.3 Downloading the Crystal Reports for HANA components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

3 Preconfiguring the SAP HANA System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.1 Creating roles for viewing reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Scenario: Granting roles to existing users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4 Installing the Reporting Service component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114.1 Starting the CR for HANA Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.2 Stopping the CR for HANA Reporting Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.3 Customizing the Reporting Service component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

5 Deploying the Connector Delivery Unit component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.1 Deploying the Connector DU using SAP HANA Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155.2 Deploying the Connector DU using SAP HANA Client Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

6 Configuring SAP HANA to work with Crystal Reports for HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . 176.1 Using an IP address in the HTTPDEST file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

6.1.1 Using the online HANA IDE Editor tool to modify the HTTPDEST file. . . . . . . . . . . . . . . . . . . . 186.2 Updating role privileges. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7 Configure HANA for SSO using SAPLogon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207.1 Downloading SAP crypto libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207.2 Configuring HANA SSO for SAPLogon Assertion tickets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207.3 Setting trust store permissions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227.4 Restarting HANA server to accept SSO changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

8 Logging errors in Crystal Reports for HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.1 Disabling logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.2 Enabling logging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248.3 Changing the log level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258.4 Values for sap_trace_level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268.5 Values for sap_log_level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

9 Enabling CR for HANA for SAP Lumira Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2 © 2014 SAP SE or an SAP affiliate company. All rights reserved.CR for HANA Components Installation, Configuration, and Administration Guide

Table of Contents

9.1 Workflow to enable reports for Lumira Server launchpad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289.2 Configuring SQLCC to promote CR content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289.3 Configuring users to list or view Crystal Reports content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299.4 Running promotion script to list Crystal Reports content. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

10 Additional Security and Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3110.1 Enabling SSL for the Reporting Service component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

10.1.1 Setting the keystore for the Reporting Service connection. . . . . . . . . . . . . . . . . . . . . . . . . . . 3110.1.2 Installing the SSL certificate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3310.1.3 Importing the SSL certificate to SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

10.2 Setting up a load balancer for multiple Reporting Service servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3510.2.1 How to use and configure the Apache server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

CR for HANA Components Installation, Configuration, and Administration GuideTable of Contents © 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

1 IntroductionThis document guides you through the installation and configuration of SAP Crystal Reports, version for SAP HANA (CR for HANA) components.

The main component of the CR for HANA solution is the Reporting Service (CR Reporting Service) that is installed on a Linux SUSE 11 (SP1 or higher) server that runs beside a SAP HANA system. The install package contents are extracted to a folder on the server.

The SAP HANA Administrator will run the installer's setup to install the CR Reporting Service and create a new user. After the CR Reporting Service is installed, the administrator will configure it and get it running on the server.

Another component for the CR for HANA solution enables SAP HANA applications to use and embed Crystal Reports. To provide this capability, the CR for HANA Connector Delivery Unit (Connector DU) must be installed on a SAP HANA system and then configured to work with the CR Reporting Service component.

NoteThis guide does not describe how to set up SAP HANA.

1.1 Prerequisites and system requirements

CR for HANA works with other products such as Crystal Reports for Enterprise and Lumira Server.

The following table contains the guides for these other products. The PAM is available for download at http://

service.sap.com/pam . All other documents are available for download at http://help.sap.com/bobi

Document description Document title

Lists the supported platforms, databases, web application servers, web servers, and other systems.

Product Availability Matrix (PAM)

Provides instructions for creating reports to be used with SAP Crystal Reports, version for HANA.

SAP Crystal Reports for Enterprise User Guide 4.1

Provides information on setting up Lumira Server SAP Lumira Server User Guide

1.2 Variables

The following variables are used throughout the guide.

Variable Description<installdir> The directory where the Report Service add-on is installed

<servername> The server name


Introduction

http://help.sap.com/disclaimer?site=http://service.sap.com/pam

http://help.sap.com/disclaimer?site=http://service.sap.com/pam

http://help.sap.com/bobi

Variable Description<SAPHANAinstance> The SAP HANA instance

1.3 Terminology

The following terms are used throughout the guide.

Term Description

Reporting Service CR for HANA Reporting Service component. This compnoent is installed on a Linux system.

Connector DU CR for HANA Connector Delivery Unit. This component is imported into HANA Studio.

Linux A Linux operating sustem running SUSE 11 SP1 or higher

Lumira SAP Lumira Server

CR for HANA Components Installation, Configuration, and Administration GuideIntroduction © 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

2 PreparationThis section provides details for how to prepare for the installation of the Reporting Service add-on.

2.1 Account permissions

To install the Reporting Service add-on on Linux, you must have the following permissions.

Category Required access

Operating system Permission to read, write, and execute scripts in the destination directory.

For a system install, root access is required.

Network ● Network connectivity through appropriate ports to all machines in the deployment.

● Access to shared file system directories.● Appropriate network authentication privileges.

2.2 Commands

In order for the installation program to run correctly, the following utilities must be installed on your system and be available on the /bin/sh path:

awk chown dirname expr

grep gzip hostname id

ping pwd read sed

stty tail tar touch

ulimit uname which

If one of the commands is not available on your system, install a version from your operating system vendor rather than a third-party vendor (such as the GNU project).

NoteThe output from a GNU version of a utility can differ significantly from the version provided by your operating system vendor. To prevent the installation program from encountering output in an unexpected format, ensure that no GNU utilities are used in the installing user account's environment.


Preparation

2.3 Downloading the Crystal Reports for HANA components

Context

There are two components to download: CR for HANA Reporting Service and CR for HANA Connector Delivery Unit. The Reporting Service component must be installed on a separate Linux system. The Reporting Service delivery unit (Connector DU) component is installed by using SAP HANA Studio (or SAP HANA Lifecycle Manager) to import the DU.

Procedure

1. On the support site (http://support.sap.com), select Software Downloads Installations and Upgrades .

2. Click A–Z Alphabetical List of my Products C .The Installations and Upgrades - C dialog box appears.

3. Select SAP CR for HANA SAP CR for HANA 1.0 .Optional: review the information on the Info Page before continuing.

4. Select Installation.5. Select the package titled SAP Crystal Reports for HANA 1.0 Reporting Service LINUX 64B and then follow the

instructions on the website to download and extract the package.6. Select the package titled SAP Crystal Reports for HANA 1.0 Connector Delivery Unit and then follow the

instructions on the website to download and extract the package.

Next Steps

If you did not download to Linux, copy the Reporting Service component to Linux before continuing with the installation.

CR for HANA Components Installation, Configuration, and Administration GuidePreparation © 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

3 Preconfiguring the SAP HANA SystemBefore you can install the Crystal Reports for HANA solution, ensure that you have the following:

● Administrator access to an SAP HANA system.● A separate server that is running SUSE11 SP1 (or higher).

You will use this server to host the SAP Crystal Reports for HANA Reporting Service.● SAP HANA Studio with an active connection to the SAP HANA system.● Data and models installed and configured on the SAP HANA system.

3.1 Creating roles for viewing reports

Context

To provide users with the necessary privileges and enable them to view reports, you must create the following roles:

● sap.bi.cr.roles::CrystalReportConsumer● sap.bi.cr.roles::CrystalReportDesigner

Procedure

1. In SAP HANA Studio, open the SAP HANA Administration Console perspective.2. In the System view, expand the Security folder.3. Right-click Roles and select New Role.4. Create the following roles; remember to deploy and save the first role configuration before you create the next

role.

○ Role name: sap.bi.cr.roles::CrystalReportConsumer

○ Object privileges

○ _SYS_BI with SELECT privilege○ _SYS_BIC with SELECT privilege

○ Analytic privileges

NoteGranting privileges in this role will give access to all users. To limit the access, set the analytic privileges in the user's account.

○ Package privilegesIf you add packages in this role, then the following privileges will be required.

○ REPO.READ


Preconfiguring the SAP HANA System

NoteGranting privileges in this role will give access to all users. To limit the access, set the package privileges in the user's account.

○ Role name: sap.bi.cr.roles::CrystalReportDesigner

○ Granted rolessap.bi.cr.roles::CrystalReportConsumer

○ Object privileges

○ REPOSITORY_REST (SYS) with EXECUTE privilege○ Analytic privileges

NoteGranting privileges in this role will give access to all users. To limit the access, set the analytic privileges in the user's account.

○ Package privilegesIf you add packages in this role, then the following privileges will be required.

○ REPO.READ○ REPO.EDIT_NATIVE_OBJECTS○ REPO.ACTIVATE_NATIVE_OBJECTS○ REPO.MAINTAIN_NATIVE_OBJECTS

NoteGranting privileges in this role will give access to all users. To limit the access, set the package privileges in the user's account.

5. To save these role configurations, activate the roles.

3.2 Scenario: Granting roles to existing users

The following scenario is an example of how the CR for HANA roles could be assigned to users.

You have two users who need access to the CR for HANA roles: Jane Doe, who only views reports from a web browser; and John Smith, who designs reports using the Crystal Reports designer. The following scenarios show the roles and privileges for the two users.

NoteIn order to view reports in Lumira Launchpad, you must select the SAP Assertion Ticket. The role descriptions explain where to select the ticket.

CR for HANA Components Installation, Configuration, and Administration GuidePreconfiguring the SAP HANA System © 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

Jane Doe

Jane Doe is a Consumer. She views reports, but not from the Crystal Reports designer.

Option Value

Granted role sap.bi.cr.roles::CrystalReportConsumer

Package privileges

If you add packages in this role, then the following privileges will be required.

● REPO.READ

Other information In the Authentication section, select SAP Assertion Ticket

John Smith

John Smith is a Report Designer.

Option Value

Granted role sap.bi.cr.roles::CrystalReportDesigner

Package privileges

If you add packages in this role, then the following privileges will be required.

● REPO.READ● REPO.EDIT_NATIVE_OBJECTS● REPO.ACTIVATE_NATIVE_OBJECTS● REPO.MAINTAIN_NATIVE_OBJECTS

Other information In the Authentication section, select SAP Assertion Ticket

Note● The privilege _SYS_BIC is not recommended as it potentially gives users more than intended access.● Users must be granted sufficient privileges to select data in the analytic and calculation views they need to

refresh report data.● Assigning both CrystalReportConsumer and CrystalReportDesigner roles to the user is not recommended.


Preconfiguring the SAP HANA System

4 Installing the Reporting Service componentPrerequisites

Before you install the Reporting Service component, ensure that you have done the following:

● Downloaded the Reporting Service installation package to your Linux system, and extracted the files.● Determined where you will install the add-on and what username and password you will use.

For the example script, we use the following information:

○ installdir: /crforhana○ username: cruser○ password: Password1

Procedure

1. In a terminal window, change to the directory that has the installation script.2. Run the setup script: ./setup.sh <installdir> <username> <password>

Example:

./setup.sh /crforhana cruser Password1

During installation, the cursor continuously switches between the forward slash and the backslash.

Results

The following directory structure will be created:

● <installdir>/InstallData/● <installdir>/license/● <installdir>/LJS/● <installdir>/uninstall.sh/

4.1 Starting the CR for HANA Reporting Service

Context

The CR for HANA Reporting Service is installed on a separate Linux system. Use the terminal console window on Linux to start the server.

CR for HANA Components Installation, Configuration, and Administration GuideInstalling the Reporting Service component © 2014 SAP SE or an SAP affiliate company. All rights reserved. 11

Procedure

1. Switch to the user that was created during the Reporting Service install.Example:

su cruser

2. Change to the directory that contains the required scripts.Example:

cd /crforhana/LJS

3. To start the server, use daemon.shExample:

./daemon.sh start

This can take one to two minutes to complete.

Results

The server will run until you shut it down.

4.2 Stopping the CR for HANA Reporting Service

The Reportng Service server continues to run until you shut it down.

Procedure

1. Open a terminal window and swithc to the user account that was used to start the Reporting Service.Example:

su cruser

2. Switch to the server folder.Example:

cd /crforhana/LJS

3. To check if the server is running type ./daemon.sh status

○ To stop the server, type ./daemon.sh stopThe server stops.

○ To restart the server, type ./daemon.sh restartThe server restarts.


Installing the Reporting Service component

4.3 Customizing the Reporting Service component

An SAP HANA Administrator can configure the CR for HANA Reporting Service component by modifying different aspects of the service.

When the CR for HANA Reporting Service is first installed, the LJS folder contains the configuration settings that can be customized.

You will find the configuration settings under the following folder: /<installdir>/LJS/

NoteThe configuration settings must be done before the reporting service is started. If it is already started, you will need to shut it down, change the configuration settings, and then restart the reporting service.

Default HTTP port number

In the default-server.xml file for the Tomcat application server, the port value in the <Connector server> section will need to be changed from the default value port="8080" to the new value.

The default default-server.xml file can be found in the following folder: /LJS/config_master/org.eclipse.gemini.web.tomcat/

In the default-server.xml file, modify the following section:

<Connector port="8080" protocol="HTTP/1.1" maxThreads="250" connectionTimeout="20000" enableLookups="false" acceptCount="100" redirectPort="8443" server="SAP"/>

Tomcat session timeout value

In the web.xml file for the Tomcat application server, the session-timeout value will need to be changed from the default value of 5 minutes to the new value.

The default web.xml file can be found in the following folder:

/LJS/config_master/org.eclipse.gemini.web.tomcat/

In the web.xml file, modify the following section:

<session-config> <session-timeout>5</session-timeout> </session-config>

CR for HANA Components Installation, Configuration, and Administration GuideInstalling the Reporting Service component © 2014 SAP SE or an SAP affiliate company. All rights reserved. 13

Modify LJS Java heap size (memory usage)

The LJS server that ships with CR for HANA comes preconfigured with a 4GB (4096MB) java heap size. The Hana Administrator can change this configuration by editing the -Xmx value in the props.ini file.

The props.ini file is found in the folder: /LJS/props.ini

In the props.ini file, modify the following setting:

-Xmx4096m


Installing the Reporting Service component

5 Deploying the Connector Delivery Unit componentThere are two methods to use to deploy the Connector Delivery Unit (Connector DU):

1. Using the Lifecycle Manager in SAP HANA Studio2. Using hdbalm.bat in SAP HANA Client Tools

5.1 Deploying the Connector DU using SAP HANA Studio

Deploy the CR for HANA Connector DU by using the Lifecycle Manager in SAP HANA Studio.

Prerequisites

Download or copy the CR for HANA Connector DU package to the computer that has SAP HANA Studio.

Start SAP HANA Studio and connect to a HANA system.

Procedure

1. In Hana Studio, select the Systems tab.

2. Right-click the system, select Lifecycle Management Platform Lifecycle Management , and then choose SAP HANA lifecycle manager.

3. Click Deploy HANA Content.4. Browse to the Connector DU package and then select the package.5. Click through the remaining screens until the package is validated.6. To deploy the contents, click Run.

CR for HANA Components Installation, Configuration, and Administration GuideDeploying the Connector Delivery Unit component © 2014 SAP SE or an SAP affiliate company. All rights reserved. 15

5.2 Deploying the Connector DU using SAP HANA Client Tools

Deploy the CR for HANA Connector DU by using the hdbalm.bat file on a machine that has SAP HANA Client Tools.

Prerequisites

Install HDB Client.

Download or copy the CR for HANA Connector DU package to a local directory.

Start a command line session.

Procedure

1. Run the hdbalm.bat program: <installdir>\sap\hdbclient\hdbalm.bat --user=<user> --host=<host> --port=<port> install <source archive>

Command Argument Description

--user=<user> User that has the following role: sap.hana.xs.lm.roles::Administrator

--host=<host> XSEngine host

--port=<port> XSEngine port

<source archive> Location of the CR for HANA Connector DU package

Example:

C:\Program Files\SAP\hdbclient\hdbalm.bat" --user=SYSTEM --host=lsles11sp3x64 --port=8000 install SAP_CR_HANA_CONN_UNT.zip

2. Provide the user password when prompted.3. To verify that the poduct was installed, use the product list command.

Example:

C:\Program Files\SAP\hdbclient\hdbalm.bat" --user=SYSTEM --host=lsles11sp3x64 --port=8000 product list

Results

The CR for HANA Connector DU is deployed.


Deploying the Connector Delivery Unit component

6 Configuring SAP HANA to work with Crystal Reports for HANA

Context

To configure the SAP HANA system to use the Reporting Service, use the HANA Admin tool to modify the HTTPDEST file.

NoteTo access the Admin tool, you must have the sap.hana.xs.admin.roles::HTTPDestAdministrator role granted to you.

NoteIf you must use an IP address instead of a server name, see Using an IP address in the HTTPDEST file [page 18] for instructions.

Procedure

1. Access the HANA Admin tool by going to the following URL: http://<server>:<port>/sap/hana/xs/admin

2. In the Admin tool, navigate to the sap bi cr reportservice package and select the CRVRemoteServletProxy.xshttpdest file.

This file is read-only.3. To extend the file so that it can be edited, do the following:

a) Scroll to the bottom of the page and click Extend.b) Save the extended file to your own package.

Do not save the file in the sap.cr.reportservice package.

4. Refresh the browser to update the Admin tool.5. In the Admin tool, browse to the package where you saved the extended file, and click on the file to open it.6. In the General Data section, beside the Host field, click the pencil icon to edit the field and then do the

following:a) Enter the name of the server where the Reporting Service is installed.

b) In the Authentication section, ensure the following:

○ The Authentication Type is set to SAP Assertion Ticket (when you are not using the Admin tool, verify that the value is authType=AssertionTicket;.

○ The SAP SID is using the correct value.7. Save your changes.

CR for HANA Components Installation, Configuration, and Administration GuideConfiguring SAP HANA to work with Crystal Reports for HANA © 2014 SAP SE or an SAP affiliate company. All rights reserved. 17

6.1 Using an IP address in the HTTPDEST file

The Host field in the HTTPDEST file only accepts server names. If you must use an IP address, use one of the following methods for modifying the HTTPDEST file.

6.1.1 Using the online HANA IDE Editor tool to modify the HTTPDEST file

Context

When modifying the HTTPDEST file, if you must use an IP address for the Host field, use the online HANA IDE Editor tool instead of the HANA Admin tool.

NoteTo use the online HANA IDE Editor tool, you must have one of the following roles granted to you:

● sap.hana.xs.ide.roles::Developer● sap.hana.xs.ide.roles::EditorDeveloper

Use the HANA Admin tool to modify the HTTPDEST file so that the SAP HANA system is configured to use the Reporting Service.

Procedure

1. Access the online IDE Editor tool by going to the following URL: http://<server>:<port>/sap/hana/xs/ide/editor

2. In the online IDE Editor tool, navigate to sap bi cr reportservice and select CRVRemoteServletProxy.xshttpdest.

3. Modify the file by doing the following:a) In the Host field, enter the IP address of the server where the Reporting Service is installed.b) Update the Port field as required.c) Set the Authentication Type to SAP Assertion Ticket.d) Ensure that the SAP SID is using the correct value.

4. Save the file.


Configuring SAP HANA to work with Crystal Reports for HANA

6.2 Updating role privileges

After the CR for HANA Connector DU is installed, the CrystalReportConsumer role will need to be updated to include the SAP_BI_CR object privilege.

Prerequisites

Verify that the CrystalReport Consumer role has been created. For more information, see Creating roles for viewing reports [page 8]

Procedure

1. In SAP Hana Studio, edit the sap.bi.cr.roles::CrystalReportConsumer role.

2. In the Object Privileges tab, add SAP_BI_CR with SELECT privilege.3. Save and activate the changes to the role.

CR for HANA Components Installation, Configuration, and Administration GuideConfiguring SAP HANA to work with Crystal Reports for HANA © 2014 SAP SE or an SAP affiliate company. All rights reserved. 19

7 Configure HANA for SSO using SAPLogonTo be able to use SAP Assertion Tickets, the SAP HANA system must be configured for HANA SSO to establish trust with the CR Reporting Services .

SAP Assertion Tickets allow the CR Reporting Service to authenticate with SAP HANA. To establish trust with the CR Reporting Service, the SAP crypto libraries must be installed and configured to create the necessary trust stores.

7.1 Downloading SAP crypto libraries

The SAP crypto libraries that include both sapgenpse and libsapcrypto are available from the Software Download Center (http://service.sap.com/swdc).

Procedure

1. In the Sofware Download Center, expand Support Packages and Patches and select Browse our Download Catalog.

2. Choose SAP Cryptographic Software.3. Expand SAPCryptolib for Installation and choose SAPCRYPTOLIB 5.5.5 (or the latest version available.4. Download the package that matches your system; for example, Linux on x86_64 64bit.

7.2 Configuring HANA SSO for SAPLogon Assertion tickets

Using the crypto library packages, create the trust stores.

Prerequisites

Download the appropriate crypto library package.

Procedure

1. From the crypto library package, copy libsapcrypto.so and sapgenpse to the following folder on the HANA system:/usr/sap/<SID>/SYS/global/security/lib/


Configure HANA for SSO using SAPLogon

Example:

/usr/sap/LM1/SYS/global/security/lib/

2. Start a Terminal session and navigate to the /lib/ folder mentioned in the previous step.

3. Provide execute permission for the two files:

○ chmod 755 libsapcrypto.so○ chmod 755 sapgenpse

4. Set an environment variable for the /lib/ path.

Example:

export LD_LIBRARY_PATH=/usr/sap/LM1/SYS/global/security/lib

5. Switch to your HANA SID user name for the remaining steps in this procedure.

Example: su lm1adm

NoteIf you do not change to the HANA SID user name, the trust stores will not be created as expected.

6. Create the sec folder under /usr/sap/<SID>/HDB<InstanceNum>/<servername>

Example:

mkdir /usr/sap/LM1/HDB00/<servername>/sec

7. Navigate to the folder that contains the crypto libraries.

Example:

cd /usr/sap/LM1/SYS/global/security/lib/

8. Create three trust stores using the following certificate specifications.

○ CN = servername○ C = country○ S = state○ O = company○ OU = department

NoteIf you see a loading error message, check that the permissions on the crypto files are set correctly.

NoteThe “-x” option is used to assign a PIN for the store. In these commands, the option prevents the store form interactively propmting the user.

○ sapsrv.pse

./sapgenpse gen_pse –p /usr/sap/<LM1>/HDB<00>/<servername>/sec/sapsrv.pse –x "" "CN=<servername>,C=CA,S=BC,O=SAP-AG,OU=CR"

CR for HANA Components Installation, Configuration, and Administration GuideConfigure HANA for SSO using SAPLogon © 2014 SAP SE or an SAP affiliate company. All rights reserved. 21

○ sapcli.pse

./sapgenpse gen_pse –p /usr/sap/<LM1>/HDB<00>/<servername>/sec/sapcli.pse –x "" "CN=<servername>,C=CA,S=BC,O=SAP-AG,OU=CR"

○ saplogonSign.pse

./sapgenpse gen_pse –a DSA –p /usr/sap/<LM1>/HDB<00>/<servername>/sec/saplogonSign.pse –x "" "CN=<servername>,C=CA,S=BC,O=SAP-AG,OU=CR"

NoteIt is very important to use DSA as the signing algorithm; for example, -a DSA.

7.3 Setting trust store permissions

In HANA Studio, edit configuration settings for trust store access.

Prerequisites

Create paths for the PSE trust stores.

For information about the trust store paths, see Configuring HANA SSO for SAPLogon Assertion tickets [page 20] .

Procedure

1. Open the SAP HANA Administration Console perspective.2. From the System view, right-click a system and then click Administration.

The Administration designer opens.3. Select the Configuration tab.4. Expand indexserver.ini and then expand authentication.

a) Right-click saplogontickettruststore and select Change.b) Enter the path to saplogonSign.pse.

Example: /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/saplogonSign.pse5. Expand xsengine.ini and then expand authentication.

NoteIf the authentication section and key do not exist, you will have to manually create them.

a) Right-click saplogontickettruststore and select Change.


Configure HANA for SSO using SAPLogon

b) Enter the path to saplogonSign.pse.

Example: /usr/sap/<SID>/HDB<InstanceNum>/<servername>/sec/saplogonSign.pse

7.4 Restarting HANA server to accept SSO changes

After SSO configuration is complete, restart the server.

Procedure

1. .In the System view, right-click on the system and select Stop.2. After the system has stopped, select Start.

CR for HANA Components Installation, Configuration, and Administration GuideConfigure HANA for SSO using SAPLogon © 2014 SAP SE or an SAP affiliate company. All rights reserved. 23

8 Logging errors in Crystal Reports for HANALogging errors can help troubleshoot errors that may occur when viewing reports. By default, logging is disabled.

The log trace files are generated as .glf files at this location: \LJS\cr_logs

8.1 Disabling logging

Procedure

1. From the LJS folder, open the cr_logging.ini file.

2. Scroll to the bottom of the file and change sap_trace_level and sap_log_level to the following:

sap_trace_level = trace_none;

sap_log_level = log_none;

3. Save your changes.

8.2 Enabling logging

Procedure


2. Scroll to the bottom of the file and change sap_trace_level and sap_log_level to the following:

sap_trace_level = trace_error;

sap_log_level = log_error;

When you use these settings, only critical events such as failures will be logged. For information about using different levels of logging, see Changing the log level [page 25].


Results

Crystal Reports for HANA now generates log trace files are as .glf files at this location: \LJS\cr_logs


Logging errors in Crystal Reports for HANA

8.3 Changing the log level

Context

You can change the sensitivity level of the logging by specifying different values for sap_trace_level and sap_log_level.

Procedure


2. Change the log level to one of the following levels by setting sap_trace_level and sap_log_level as described in the table:

Level Description sap_trace_level sap_log_level

On Only critical events such as failures will be logged.

NoteIt is recommended that you use this level if you only want to log errors.

trace_error log_error

Low Warnings and status messages are ignored.

trace_info log_error

Medium Only status messages with least importance are ignored.

trace_path log_warn

High All messages are included in the log.

trace_debug log_info

NoteFor more information about the values for sap_trace_level and sap_log_level, see Values for sap_trace_level [page 26] and Values for sap_log_level [page 26].


CR for HANA Components Installation, Configuration, and Administration GuideLogging errors in Crystal Reports for HANA © 2014 SAP SE or an SAP affiliate company. All rights reserved. 25

8.4 Values for sap_trace_level

sap_trace_level is a message that has been classified as a developer trace.

The following table describes all the possible values for sap_trace_level:

Severity Configuration values Description

DEBUG trace_debug Information that is only valuable to developers, for analyzing the internal status of a program.

PATH trace_path Information that is valuable to developers and support engineers, for understanding the execution flow of the following method calls:

● program.entering()● exiting()● throwing()● catching()

INFO trace_information or trace_info

Information that is valuable to support engineers and developers, for understanding and tracing the business logic. For example, business document numbers, status changes, and so on.

ERROR trace_error Uncorrectable error conditions in program execution, which terminate the current application without fulfilling the desired task. The application remains usable afterwards. assertion() method calls may be used to test a Boolean expression and stop with an error if it is not fulfilled.

This severity level also shows technical context information in exception handling situations.

NONE trace_none No log messages.

8.5 Values for sap_log_level

sap_log_level is a message that has been classified as an administrative log.


Logging errors in Crystal Reports for HANA

The following table describes all the possible values for sap_log_level:

Severity Configuration values Description

INFO log_info or log_information Information about an event that does not need or have any follow-up activity. This information can help you understand normal operation. It can also provide further information for later reviews, audits, or investigations.

WARNING log_warn or log_warning Information about how to avoid error situations in the future. The application processing can and will proceed, but follow-up activity is required to avoid problems in the future.

ERROR log_error Information about how to solve a problem that has caused the application processing to terminate without completing the desired tasks. The application is still usable, but corrective actions are required to avoid the erroneous termination in the future. If not, customers will need to open problem messages to solve the problem.

FATAL log_fatal Information that indicates when the application processing terminates without completing the desired tasks, and the application is not usable anymore. In these situations, the application cannot be started without corrective actions by experts. Customers will normally need to open problem messages to solve the problem.

NONE log_non No log messages.

CR for HANA Components Installation, Configuration, and Administration GuideLogging errors in Crystal Reports for HANA © 2014 SAP SE or an SAP affiliate company. All rights reserved. 27

9 Enabling CR for HANA for SAP Lumira ServerThe following section describes how users can list and view Crystal Reports content in the Lumira Server lanuchpad.

9.1 Workflow to enable reports for Lumira Server launchpad

To enable Crystal Reports content to be listed and viewed from the Lumira Server launchpad, there are specific configuration steps that must be taken in order for the integration to work.

The following is the basic workflow to enable reports to be listed or viewed in the launchpad:

1. Report authors save reports to the SAP HANA system.2. Promote reports in HANA.

To promote a report, the report designer or another administrator needs to run a script in the web browser.The user settings need to be configured in the Hana SQL Connection Configuration (SQLCC).

3. After the reports are promoted, users browse to the Lumira Server Launchpad to see the list and view the reports.

Accounts can be created and assigned to roles in SAP HANA Studio. In addition, users must be granted sufficient permissions to select data in analytic and calculation views that they need to access in SAP Lumira Server.

9.2 Configuring SQLCC to promote CR content

Procedure

1. Create a new user that will have permission to configure HANA SQLCC.a) In HANA Studio, open the SAP HANA Administration Console perspective.b) In the System view, expand the Security folder.c) Right-click Users and select New User.d) Enter a descriptive user name suchs as LUMIRA_CR_PROMOTION.e) Give the user a default password; this password will need to be changed upon first use.f) Grant the user the following role: sap.bi.common::BI_TECH_USER

2. Deploy the user (save and activate).3. To make the account functional, reset the user's initial password.

a) Browse to the Lumira Server launchpad: http://<hana host name>:<XS engine port>/sap/bi/launchpad

b) Log in with the new user account (for example, LUMIRA_CR_PROMOTION).c) When prompted, change the password.


Enabling CR for HANA for SAP Lumira Server

d) Log out from the launchpad.4. Grant the SYSTEM user the followng roles:

sap.hana.xs.admin.roles::RuntimeConfAdministratorsap.hana.xs.sqlcc::Administrator

5. Log into the Hana SQLCC tool and configure with the new user information.a) Browse to: http://<hana server name>:<XS engine port>/sap/hana/xs/sqlcc/b) Log in with the SYSTEM account.c) Select the following folder: sap.bi.activationplugin.logic.lib::ActivationRepoConnectiond) In the User field, type LUMIRA_CR_PROMOTIONe) Click Save.

9.3 Configuring users to list or view Crystal Reports content

For each user that will access the Lumira Server launchpad to list and view Crystal Reports content, grant them the sap.bi.common::BI_DATA_CONSUMER role.

Alternatively, the sap.bi.cr.roles::CrystalReportConsumer role can be granted the sap.bi.common::BI_DATA_CONSUMER role. This will automatically give all users that have been granted the sap.bi.cr.roles::CrystalReportConsumer role access to Lumira Server launchpad.

Related Information

Creating roles for viewing reports [page 8]

9.4 Running promotion script to list Crystal Reports content

The promotion script is used to display the latest version of reports in the Lumira Server launchpad.

Context

The promotion script must be run whenever a report is updated and saved to SAP HANA; the report should be made available to launchpad users.

Example: An SAP Hana Administrator could schedule the script to run at certain times, such as once an hour. Before running the script, the Administrator needs to consult the SAP HANA documentation for how to configure the scheduled task in HANA.

CR for HANA Components Installation, Configuration, and Administration GuideEnabling CR for HANA for SAP Lumira Server © 2014 SAP SE or an SAP affiliate company. All rights reserved. 29

Procedure

1. To run the promotion script, use the following URL:http://<hana server name>:<XS engine port>/sap/bi/activationplugin/activate

2. Log in with a user that has the sap.bi.common::BI_DATA_CONSUMER role granted.

○ If there is an activated report not yet promoted in Lumira, then the script automatically executes and returns the following message: Activation Successful

○ If there are no activated reports or all activated reports have already been promoted, the script returns the following message: No objects to activate.


Enabling CR for HANA for SAP Lumira Server

10 Additional Security and Configuration OptionsThere are other modifications that can be made to the CR for HANA components such as enabling SSL and setting up load-balancing.

10.1 Enabling SSL for the Reporting Service component

Before you can change the SSL configuration, you must have SAP Lumira launchpad setup and be able to to view reports in the SAP Lumira launchpad viewer. To enable SSL for the Reporting Service component, do the following:

1. Create a keystore on the system that has the Reporting Service2. Install the certificate3. Import the certificate into HANA

10.1.1 Setting the keystore for the Reporting Service connection

Use the following procedure to enable SSL communication between the SAP HANA connector and the CR for HANA Reporting Service server.

Prerequisites

Log into the system that your Reporting Service is installed on and open a terminal window.

Procedure

1. Switch to your SAP HANA admin user (<SID>adm).Example:

root@ljshost:~> su -l ljsadmljsadm@ljshost~>

2. Use the Java keytool to generate a new keystore for the admin user.

For the first and last name, you must use the Reporting Service server hostname that the HANA server uses.

CR for HANA Components Installation, Configuration, and Administration GuideAdditional Security and Configuration Options © 2014 SAP SE or an SAP affiliate company. All rights reserved. 31

Example:

ljsadm@ljshost:~> ./LJS/sapjvm_7_jre/bin/keytool -genkey -alias tomcat -keyalg RSAEnter keystore password: Re-enter new password: What is your first and last name? [Unknown]: <server hostname>What is the name of your organizational unit? [Unknown]: <org_unit>What is the name of your organization? [Unknown]: <org_name>What is the name of your City or Locality? [Unknown]: <city>What is the name of your State or Province? [Unknown]: <state>What is the two-letter country code for this unit? [Unknown]: <country>Is CN=<server hostname>, OU=<org_unit>, O=<org_name>, L=<city>, ST=<state>, C=<country> correct? [no]: yes Enter key password for <tomcat> (RETURN if same as keystore password): ljsadm@ljshost:~>

3. In your tomcat configuration directory, make the following change to the default-server.xml file: remove the non-SSL port connector 8080 and replace it with the SSL port connector 8443.Example:

<Connector port="8443" protocol="HTTP/1.1" maxThreads="250" connectionTimeout="20000" enableLookups="false" acceptCount="100" server="SAP" scheme="https" secure="true" SSLEnabled="true" keystoreFile="${user.home}/.keystore" keystorePass="THE_KEYSTORE_PASSWORD_THAT_YOU_SET" clientAuth="false" sslProtocol="TLS"/>

4. Save the file and restart the Reporting Service server.Example:

ljsadm@ljshost:~/LJS/config_master/org.eclipse.gemini.web.tomcat> cdljsadm@ljshost:~> sudo ./LJS/daemon.sh restartroot's password:Stopping LJS_Daemon Service LJS_Daemon stoppedStarting LJS_DaemonLJS_Daemon started.ljsadm@ljshost:~>

NoteIf sudo ./LJS/daemon.sh restart gives you an error saying the user is not in the sudoers file, type visudo to add the current user to the file.

The Reporting Service server is now ready to accept connections in SSL mode.

Next Steps

Install the Reporting Service certificate.


Additional Security and Configuration Options

10.1.2 Installing the SSL certificate

Retrieve and install the CR for HANA Reporting Service certificate.

Prerequisites

You have created the keystore for the certificate. For more information, see Setting the keystore for the Reporting Service connection [page 31].

Procedure

Navigate to the certificate.

○ Using Chrome:

1. Browse to the CR for HANA Reporting Service: https://<server ip address>:8443/2. Click the lock icon beside the URL to display the context menu and then select Certificate Information.3. To retrieve the certificate, do one of the following:

○ On Windows, select the Details tab and click Copy to File.The Certificate Export Wizard appears.

○ Save the certificate as the following type: DER encoded binary X.509 .cer file○ Using Internet Explorer:

1. Browse to the CR for HANA Reporting Service: https://<server ip address>:8443/com.sap.cr.reportservice

2. Click Continue to this website (not recommended)You will see an error message (HTTP Status 404); this is expected.

3. Click Certificate Error.The Untrusted Certificate window appears.

4. Click View certificates.

Next Steps

Import the certificate into SAP HANA.


10.1.3 Importing the SSL certificate to SAP HANA

Import the SSL certificate for CR for HANA Reporting Service into HANA.

Prerequisites

In SAP HANA, your user must have the following role: sap.hana.xs.admin.roles::TrustStoreAdministrator

Your SYSTEM account must have the following role: sap.hana.xs.ide.roles::Developer

Procedure

1. Access the HANA Admin tool by going to the following URL: http://<server>:<port>/sap/hana/xs/admin

2. If you do not have a Trust Store, create one.3. Select the Trust Store and then click Browse.4. Find the certificate file (.cer) that you saved from the CR for HANA Reporting Service.5. Click Import Certificate.

The details of the certificate are displayed in the certificate list.6. Open a new browser tab and navigage to the SAP HANA IDE editor (/sap/hana/xs/ide/editor).

7. Edit the CRVRemoteServletProxy.xshttpdest file and add the following line to the bottom of the file:

useSSL = true;

8. Click Save.9. In the SAP HANA XS Administration Tool, select XS Applications.

10. Navigate to sap bi cr reportservice and select the CRVRemoteServletProxy.xshttpdest file.

11. Select the new trust store.12. Change the port to 8443.

Results

You should now be able to view reports in Lumira Launchpad with an SSL connection to the Reporting Service.



10.2 Setting up a load balancer for multiple Reporting Service servers

CR for HANA is designed to support an environment where a single SAP HANA system will use multiple CR for HANA Reporting Service servers to process report requests. This allows improved report processing performance by adding additional Reporting Service servers to scale the system.

You can use any type of load balancer that you or your administrator know how to use and configure.

Use the following guidelines for your load balancer:

● Use client-affinity (also known as sticky-sessions) with the CR for HANA Reporting Service.● Configure all instances of the Reporting Service servers that will be used by the load balancer.● Allow requests for /com.sap.cr.reportservice/CRVRemoteServlet.

The load balancer should not allow requests for other URLs.● Configure xsHttpDest to point to the IP of the load balancer.

10.2.1 How to use and configure the Apache server

The following components are required when using an Apache server:

● Reporting Service● Apache httpd server● mod_jk module● SUSE 11 SP2 x64

To set up the load-balancing system, you need to modify the Tomcat component inside every Reporting Service server that you use.

10.2.1.1 Installing Apache httpd and mod_jk

Context

The mod_jk module allows for communication between the server and the Tomcat component inside the Reporting Service server. (The version of mod_jk depends on the server.)

These instructions describe the installation process for SUSE Linux.


Procedure

1. Select YaST (Control Center) Software Software Management .2. Select the RPM Groups tab.

The left pane displays Package Groups.

3. Select Productivity Networking Web .4. Install apache2-mod_jk.

5. As the root user, run the following command: a2enmod jk6. To run Apache, use the following command: rcapache2 start

If needed, you can also use the restart and stop commands.

Next Steps

You can now configure the Apache server.

10.2.1.2 Configuring the Apache server

Add and modify the following configuration files: httpd.conf, mod_jk.conf, and workers.properties.

Procedure

1. Switch to /etc/apache2/conf.d and edit httpd.conf.

If the file does not exist, create it and open it for editing.2. Add the following text:

# Include mod_jk configuration file

Include /etc/apache2/mod_jk.d/mod_jk.confServername localhost

3. Save the httpd.conf file.

4. Create the folder /etc/apache2/mod_jk.d5. Switch to /etc/apache2/mod_jk.d, create mod_jk.conf, and open it for editing.

6. Copy the following code into the mod_jk.conf file:

# http://tomcat.apache.org/connectors-doc/reference/apache.html

# Path to worker config file

JkWorkersFile /etc/apache2/mod_jk.d/workers.properties



# Logging and memory files

JkShmFile /var/log/apache2/mod_jk.shm

JkLogFile /var/log/apache2/mod_jk.log

# Jkloglevel [debug/error/info]

JkLogLevel info

JkRequestLogFormat "%w %V %T"

# Jkoptions for forwarding

JkOptions +ForwardURIProxy +ForwardDirectories +ForwardKeySize

# Map localhost/index* urls for load balancer to handle

JkMount /* balancer

7. Save the file.8. Create workers.properties and open it for editing.

9. Copy the following code into the workers.properties file:

# http://tomcat.apache.org/connectors-doc/reference/workers.html

# Define our workers

# worker.list=worker1,worker2

worker.list=balancer # The load balancer takes care of which workers to use

worker.balancer.type=lb # The balancer is a load balancer type (lb)

worker.balancer.balance_workers=worker1,worker2,worker3

worker.balancer.method=N # This method specifies the type of scheduling: B(usyness), N(ext), R(equest), S(ession), T(raffic)# N can be used to test your setup.

worker.balancer.sticky_session=True # Requests with the same session id are routed to the same worker

worker.worker1.port=8009 # this is the default port

worker.worker1.host=10.162.201.229

worker.worker1.type=ajp13 # this is required for every worker

# worker.worker1.lbfactor=2 # lbfactor is optional; it defines how many more requests one server should get (twice as many in this case)

worker.worker2.port=8009



worker.worker2.type=ajp13

# worker.worker2.lbfactor=1

worker.worker3.port=8009


worker.worker3.type=ajp13

# worker.worker3.lbfactor=1

10. Save the file.

10.2.1.3 Configuring the Reporting Service server

Add code to the Reporting Service server to allow for load balancing.

Procedure

1. Navigate to the Tomcat folder: <installdir>/LJS/config_master/org.eclips.gemini.web.tomcat2. Open the default-server.xml file for editing and add the following information:

a) Below the Connector element (<Connector port="8888" protocol "HTTP/1.1"...), add the following lines:



<Connector port="8009" protocol="AJP/1.3" redirectPort="9443" />

b) In the Engine element, add jvmRoute="worker1"Example:

<Engine name="Catalina" defaultHost="localhost" jvmRoute="worker1">

The worker value should be changed for each additional Reporting Service server.3. Save the file.



10.2.1.4 Integrating the load balancer with SAP HANA

Redirect SAP HANA from a Reporting Service server to an Apache server.

Context

After you set up the Apache server and the load balancing for the Reporting Service servers, change the properties so that SAP HANA uses an Apache server instead of a Reporting Service server.

Procedure

1. Open the CRVRemoteServletProxy.xshttpdest file for editing.

2. Reset the host to match your Apache server IP.3. Change the port to 80.


Important Disclaimers on Legal AspectsThis document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.

AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document.

Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.

Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. Regarding link classification, see: http://help.sap.com/disclaimer.


Important Disclaimers on Legal Aspects

http://help.sap.com/disclaimer/

http://help.sap.com/disclaimer/

CR for HANA Components Installation, Configuration, and Administration GuideImportant Disclaimers on Legal Aspects © 2014 SAP SE or an SAP affiliate company. All rights reserved. 41

www.sap.com/contactsap

© 2014 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.

http://www.sap.com/contactsap

http://www.sap.com/corporate-en/legal/copyright/index.epx

http://www.sap.com/corporate-en/legal/copyright/index.epx

Documents

CR for HANA Components Installation, Configuration, and Administration Guide · SAP Crystal Reports, version for SAP HANA Document Version: 1.0 - 2014-09-10 CR for HANA Components