ds13sp01 admin bip en

SAP BusinessObjects Design StudioDocument Version: 1.3 SP01 - 2014-07-30

Administrator Guide: SAP BusinessObjects Design Studiobased on SAP BusinessObjects BI Platform

Table of Contents1 About This Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51.1 About the Documentation Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51.2 Who Should Read This Guide?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3 Related Guides and Documentation Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.1 What is SAP BusinessObjects Design Studio?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.2 Key Components of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.1 BI Platform Add-On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3.1.1 System Requirements for the BI Platform Add-On Installation. . . . . . . . . . . . . . . . . . . . . . . . 103.1.2 Upgrading BI Platform 4.0 to BI Platform 4.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1.3 Choosing an Installation Type for Your Operating System. . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.2 Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.1 System Requirements for the Design Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2.2 Installing the Design Tool of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . 183.2.3 Installing the Design Tool from an Installation Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.4 Uninstalling the Design Tool of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . 21

4 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.1 Upgrading the BI Platform Add-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224.2 Upgrading the Design Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

5 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.1 Creating and Managing Data Source Connections in SAP BusinessObjects Business Intelligence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5.1.1 Creating BW System Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265.1.2 Creating SAP HANA System Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.1.3 Creating Universes for Use in Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285.1.4 Reloading Connections in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

5.2 BI Platform Configuration for Universes in Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.3 Maintaining Settings on the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

5.3.1 Checking the Status of the Analysis Application Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.3.2 Maintaining the Maximum Number of Client Sessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315.3.3 Creating a User Group and Adding View Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .325.3.4 Adding View Rights for Universe Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335.3.5 Adding Users to the Design Studio Administrators Authorization Group. . . . . . . . . . . . . . . . . 345.3.6 Setting RSADMIN Parameters for Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

5.4 Configuration Tasks for Mobile Usage of Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2 © 2014 SAP SE or an SAP affiliate company. All rights reserved.Administrator Guide: SAP BusinessObjects Design Studio

Table of Contents

5.4.1 Creating a Mobile Category on the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365.4.2 Assigning Analysis Applications to the Mobile Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . .375.4.3 Configuring the BI Platform for Display of Analysis Applications on SAP BusinessObjects Mobile for Mobile Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

5.5 Administration Tasks for Planning Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.6 Configuring the Hosts File for Universes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.7 Providing the Web Service URL to Application Designers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395.8 Activating the Query Runtime Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .395.9 Enabling JavaScript Compression to Enhance BI Platform 4.1 Performance. . . . . . . . . . . . . . . . . . . . . 405.10 Maintaining Settings in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.11 Sizing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455.12 More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466.1 Deploying SDK Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

6.1.1 Installing Design Studio SDK Extensions to Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . 466.1.2 Removing Extensions from Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.1.3 Deploying Extensions to the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486.1.4 Removing Extensions from the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

7 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.1 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.2 User Management and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.3 Authentication and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .517.4 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .537.5 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

7.5.1 Communication at Design Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547.5.2 Communication at Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

7.6 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607.7 Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.8 Security for Additional Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617.9 General Security Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

8 Language and Regional Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638.1 Language of the Design Tool Texts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638.2 Language of Master Data and Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .638.3 Language of Message Texts and Tooltips in Analysis Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

8.3.1 Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648.4 Regional Formats for Numbers, Dates and Times. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

8.4.1 Formatting of Date and Time with SAP HANA Data Sources. . . . . . . . . . . . . . . . . . . . . . . . . 668.5 Business Case: Defining English as the Preferred Language of an Analysis Application. . . . . . . . . . . . . .66

9 Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Administrator Guide: SAP BusinessObjects Design StudioTable of Contents © 2014 SAP SE or an SAP affiliate company. All rights reserved. 3

9.1 Working with Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

9.2 Working with Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

9.3 Working with Data Source Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

9.4 Working with Universes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

9.5 Managing Access Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

9.6 Transporting Analysis Applications, Images, Data Source Connections and Universes. . . . . . . . . . . . . . 75

10 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

10.1 Upgrading the Design Tool Installation (Alternative Procedure). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

10.2 Setting Network Connections If Logon Problems Occur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

10.3 Activating Runtime Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

10.4 Activating SAP JCo Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

10.5 Viewing And Collecting Statistics Data At Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

10.6 Downloading Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

10.7 Collecting Support Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

10.8 Problems with Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

10.9 Managing Logs in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

10.10 Managing Logs on the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84

11 Managing Local Mode in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

11.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

11.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

11.2.1 Creating Connections to BI Back-End Systems in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . 86

11.2.2 Switching User for BI Back-End System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

11.2.3 Maintaining Settings in the Design Tool in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

11.3 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

11.3.1 Technical System Landscape in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

11.3.2 User Management and Authentication in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

11.3.3 Authentication and Single Sign-On in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

11.3.4 Authorizations When Using Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

11.3.5 Network and Communication Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

11.3.6 Data Storage Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

11.3.7 Data Access Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

11.4 Language and Regional Settings in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

11.4.1 Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

11.5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

11.5.1 Collecting Support Information in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99


Table of Contents

1 About This Guide

1.1 About the Documentation Set

The documentation set for SAP BusinessObjects Design Studio comprises the following guides and online help products:

TipThe guides and tutorials are regularly updated and enhanced. Make sure that you have the latest version by checking the SAP Help Portal on a regular basis.

Administrator Guide

The Administrator Guide contains detailed information, which users need in order to install, configure and manage SAP BusinessObjects Design Studio. The guide is available on the SAP Help Portal at http://help.sap.com/boad

Application Designer Guide

The Application Designer Guide contains the conceptual information, procedures and reference material, which application designers need in order to create analysis applications. The guide is available on the SAP Help Portal at http://help.sap.com/boad

End User Guide

The End User Guide contains procedures and background information for users working with analysis applications. This guide is available on the SAP Help Portal at http://help.sap.com/boad.

Developer Guide

The Developer Guide: Design Studio SDK contains procedures, reference material and background information, which enables developers to create 3rd-party components with the Design Studio SDK and enhance the analysis applications with custom components. The guide is available on the SAP Help Portal at http://help.sap.com/boad.

Administrator Guide: SAP BusinessObjects Design StudioAbout This Guide © 2014 SAP SE or an SAP affiliate company. All rights reserved. 5

http://help.sap.com/boad





What's New Guide

The What's New Guide lists new and modified features in SAP BusinessObjects Design Studio that have been implemented since the previous release. The guide is available on the SAP Help Portal at http://help.sap.com/boad

Online Help

The Online Help contains the same information as the Application Designer Guide and the Developer Guide: Design Studio SDK, plus an additional chart properties guide called Charts: Additional Information. Choose Help Help Contents to open the guides in the design tool. You can also set the online help as a view within the design tool. Choose View Help .

1.2 Who Should Read This Guide?

This guide is intended for system administrators.

To manage SAP BusinessObjects Design Studio, you need administrator rights on the local machines where the design tool of SAP BusinessObjects Design Studio is installed, on the connected SAP NetWeaver Business Warehouse systems, and on the connected SAP HANA systems. You also need the Administrator user in the BI platform for managing integration with the BI platform.

1.3 Related Guides and Documentation Sets

This guide contains references to additional guides and documentation sets for further details on specific tasks.

The following list will help you to find the related guides on the SAP Help Portal at http://help.sap.com/bobip:

Related Guide Location

Business Intelligence Platform Installation Guide Installation, Upgrade, Deployment

Web Application Deployment Guide Installation, Upgrade, Deployment

Business Intelligence Platform Administrator Guide System Administration and Maintenance Information

Lifecycle management console for SAP BusinessObjects Business Intelligence 4.0 User Guide

System Administration and Maintenance Information

Data Access Guide Data Access and Semantic Layer Data Access

Information Design Tool User Guide Data Access and Semantic Layer Universes

The related guide is located on the SAP Help Portal at http://help.sap.com/boaolap41:


About This Guide



http://help.sap.com/bobip

http://help.sap.com/boaolap41


SAP BusinessObjects Analysis, edition for OLAP Administrator Guide

System Administration and Maintenance Information

The related guide is located on the SAP Help Portal at http://help.sap.com/bomobileios:


Administrator and Report Designer's Guide: SAP BusinessObjects Mobile for iOS

Installation, Administration, Customization and Report Designing Information

User Guide: SAP BusinessObjects Mobile for iOS End User Guides - Application Help

Mobile Security Guide System Administration and Maintenance

The following list will help you to find the related guides on the SAP Help Portal at http://help.sap.com/hana_appliance:


SAP HANA Database - Client Installation and Update Guide Installation and Upgrade Information SAP HANA Client

Installation Guide

SAP HANA Security Guide Security Information

SAP HANA Developer Guide Development Information

The following list will help you to find the related guides on the SAP Help Portal at http://help.sap.com/nw74 :


Security Guide for SAP NetWeaver BW Security Information SAP NetWeaver Security Guide

Security Guides for SAP NetWeaver Functional Units

Chapter “Transport Layer Security” and chapter “Network and Communication Security” in the SAP NetWeaver Security Guide

Security Information SAP NetWeaver Security Guide

Network and Communication Security

SAP NetWeaver Library , chapter “Identity Management” Application Help SAP NetWeaver Library: Function-

Oriented View Security Identity Management

SAP NetWeaver Library , chapter “Authorizations” in the “Business Warehouse” section

Application Help SAP NetWeaver Library: Function-

Oriented View Business Warehouse Data Warehousing

Data Warehouse Management Authorizations

SAP NetWeaver Library , chapter “Trace Tool Environment” in the “Business Warehouse” section

Application Help SAP NetWeaver Library: Function-

Oriented View Business Warehouse Generic Tools and

Services Test and Trace Tools

The graphics in this guide correspond to the graphical notation of the Fundamental Modeling Concepts (FMC). For

more information about this notation, see www.fmc-modeling.org .

Administrator Guide: SAP BusinessObjects Design StudioAbout This Guide © 2014 SAP SE or an SAP affiliate company. All rights reserved. 7

http://help.sap.com/bomobileios

http://help.sap.com/hana_appliance


http://help.sap.com/nw74

http://help.sap.com/disclaimer?site=http://www.fmc-modeling.org/notation_reference

2 Getting Started

2.1 What is SAP BusinessObjects Design Studio?

SAP BusinessObjects Design Studio enables application designers to create analysis applications and dashboards - based on BW, SAP HANA and universe data sources - for browsers and mobile devices (iPads, for example). It is the product of choice when full support for BW and HANA data models and engine capabilities is required. The product offers a design tool that allows you to create applications easily and intuitively without the need for native HTML and iPad UI programming skills.

SAP BusinessObjects Design Studio can be used locally and integrated in the following platforms:

● SAP BusinessObjects Business Intelligence (BI platform)● SAP NetWeaver● SAP HANA

NoteIn local mode, you can create demo analysis applications for presenting and evaluating SAP BusinessObjects Design Studio with users at customer locations.

Besides analysis applications, application designers can also create planning applications that support both manual and automated data entry and changes to data. The application user can enter the planning data manually in the crosstab (in cells or rows) or use planning functions and planning sequences (also known as planning objects) in SAP NetWeaver BW Integrated Planning to enter data automatically. For planning data, you have to use a BW backend system as the planning system.

For creating planning applications, the following conditions must be met:

● The design studio is used with BI Platform or SAP NetWeaver as the platform● A BW back end system is used as the planning system● A BW query or query view, which is defined as a planning query in the BEx Query Designer, is used as a data

source● A desktop browser application is used as planning application

In addition to the standard palette of components in Design Studio, which are used to visualize data and enable user interaction, you can develop 3rd party components with the Design Studio SDK and enhance your analysis applications with custom components. You can store and provide access to the analysis applications containing the 3rd party components on any of the supported platforms.

Related Information

Managing Local Mode in the Design Tool [page 85]


Getting Started

2.2 Key Components of SAP BusinessObjects Design Studio

This section provides an overview of the software components and supporting systems used by SAP BusinessObjects Design Studio:

Component Relevance

SAP BusinessObjects Business Intelligence platform Used as the central content management system for analysis applications. Also used as a platform for managing universes and OLAP data source connections required for communication with SAP HANA systems or SAP NetWeaver BW systems.

BI launch pad Installed with the BI platform. Used to access analysis applications and organize them to suit the users' preferences.

Provides access to various applications (if you have the appropriate licenses and access rights), for example:

● Analysis applications● BEx Web applications● BI workspaces● SAP Crystal Reports

SAP BusinessObjects Mobile Mobile solution that provides access to various BI content types in a single mobile app. The BI content supported by this mobile app includes analysis applications created with SAP BusinessObjects Design Studio, Web Intelligence, Interactive Crystal Reports and Dashboards.

SAP BusinessObjects Design Studio for BI platform setup BI platform add-on installation, which makes it possible to display and execute analysis applications in the BI launch pad. It also allows communication between the design tool and the BI platform in order to save and launch analysis applications in the design tool.

Design tool of SAP BusinessObjects Design Studio Tool for creating analysis applications.

Information Design Tool Tool for creating universes.

SAP NetWeaver Business Warehouse Used as a back-end system, providing the business data for data analysis in analysis applications.

SAP HANA Used as a back-end system, providing the business data for data analysis in analysis applications.

Administrator Guide: SAP BusinessObjects Design StudioGetting Started © 2014 SAP SE or an SAP affiliate company. All rights reserved. 9

3 InstallationSAP BusinessObjects Design Studio consists of the following installable components:

Component Description

SAP BusinessObjects Design Studio for BI platform setup BI platform add-on installation, which makes it possible to display and execute analysis applications in the BI launch pad or on mobile devices. It also allows communication between the design tool and the BI platform, in order to save and launch analysis applications in the design tool. TheSAP BusinessObjects Design Studio for BI platform setup has to be installed on the host machine(s) with the BI platform server.

Design tool setup of SAP BusinessObjects Design Studio Tool for creating analysis applications. The design tool has to be installed on the client machines of the application designers who need to create analysis applications.

3.1 BI Platform Add-On

3.1.1 System Requirements for the BI Platform Add-On Installation

SAP BusinessObjects Business Intelligence platform 4.0 or 4.1 must be correctly installed before the SAP BusinessObjects Design Studio for BI platform setup can be installed on the BI platform. Make sure that the following conditions are met:

● You have administrative rights on the machine.● The machine has a 64-bit operating system.

A list of all supported operating systems and Web browsers for SAP BusinessObjects Design Studio is available in

the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/pam .Here you can enter SBOP DESIGN STUDIO in the search field to retrieve the information.

The SAP BusinessObjects Design Studio for BI platform setup consists of the following features:

Setup Feature Description

Analysis Application Web Components This feature makes it possible to display analysis applications in the BI launch pad, and use OpenDocument links in order to send direct links for analysis applications to other recipients. It also allows communication between the design tool and the BI platform, in order to save and launch analysis applications.

Analysis Application Service This feature includes the Analysis Application Service running in the Adaptive Processing Server. The Analysis Application Service makes it possible to execute analysis applications.


Installation

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

Setup Feature Description

Analysis Application support for Mobile Services This feature adds mobile support to analysis applications, integrating analysis applications into SAP BusinessObjects Mobile. It allows application users to access analysis applications on mobile devices.

You can install the features of the SAP BusinessObjects Design Studio for BI platform setup on different host machines. Depending on the host machine and the components installed on it, optional pre-requisites might become mandatory.

The following components need to be installed:

Required Component Description

BI Platform Server The minimum version required is SAP BusinessObjects Business Intelligence platform 4.0 Support Package 8 or SAP BusinessObjects Business Intelligence platform 4.1 Support Package 0.

Adaptive Processing Server The setup feature Analysis Application Service requires Adaptive Processing Server to be installed. If you install this setup feature on your machine, the optional component Adaptive Processing Server becomes mandatory.

BI Platform Web Applications The setup feature Analysis Application Web Components requires BI platform Web applications to be installed. If you install this setup feature on your machine, the optional component BI Platform Web Applications becomes mandatory.

Mobile Services The setup feature Analysis Application support for Mobile Services requires Mobile Services to be installed. If you install this setup feature on your machine, the optional component Mobile Services becomes mandatory. The component Mobile Services is necessary to integrate analysis applications into the SAP BusinessObjects Mobile solution.

Before installing the SAP BusinessObjects Design Studio for BI platform setup on the BI platform, see the following guides for information relevant to your deployment:

● Business Intelligence Platform Installation Guide ● Business Intelligence Platform Administrator Guide ● Business Intelligence Platform Web Application Deployment Guide

The guides are available on the SAP Help Portal at http://help.sap.com/bobip41.

3.1.2 Upgrading BI Platform 4.0 to BI Platform 4.1

SAP BusinessObjects Design Studio BI platform add-on supports version 4.0 and 4.1 of SAP BusinessObjects Business Intelligence platform by providing a setup file for each BI Platform version.

After SAP BusinessObjects Business Intelligence platform has been upgraded from 4.0 to 4.1, Design Studio will not work. You need to install the corresponding SAP BusinessObjects Design Studio BI platform add-on after upgrading the BI platform.

Administrator Guide: SAP BusinessObjects Design StudioInstallation © 2014 SAP SE or an SAP affiliate company. All rights reserved. 11

http://help.sap.com/bobip41

3.1.3 Choosing an Installation Type for Your Operating System

The installation procedure you follow depends on the operating system on your host machines.

Related Information

Installing the BI Platform Add-On on Microsoft Windows [page 12]Installing the BI Platform Add-On on UNIX [page 15]

3.1.3.1 Installing the BI Platform Add-On on Microsoft Windows

Procedure

1. Go to SAP Service Marketplace at http://service.sap.com SAP Support Portal Software DownloadsInstallations and Upgrades .

Note

Support packages and patches are available under SAP Support Portal Software DownloadsSupport Packages and Patches .

2. In the A - Z Index, click D.The SAP BusinessObjects Design Studio BI platform add-on installation is available for download at SBOP DESIGN STUDIO 1.3.

3. Under Installation, download the installation package SBOP DESIGN STUDIO 1.3 BIP ADD ON 1.3 for WINDOW X86_64 to a folder on your PC.

For more information, see SAP Note 1948049 .4. After the download is complete, unzip the installer.5. Follow the instructions on the screen and choose Install.6. After the installation, go to the folder where you installed the package.7. Under DATA_UNITS\DS_BIP_ADD_ON_<version number>_WINDOWS_X64, choose the required BI platform

version. There are two installers, one for BOE 4.0 (folder 41) and another one for BOE 4.1 (folder 41).8. Double-click setup.exe.

9. Select a setup language. This is the language for the installation wizard.10. Click OK.11. If necessary, resolve the critical pre-requisites issues before continuing the installation.


Installation

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

http://help.sap.com/disclaimer?site=https://service.sap.com/sap/support/notes/1948049

NoteDepending on the host machine and the features installed on it, optional pre-requisites might become mandatory. The BI platform Web applications are mandatory for example, if you want to install the analysis application Web features on this machine (see step 15).

12. Click Next.13. In the welcome dialog box, click Next.14. Read and accept the License Agreement, then click Next.

The detected directory is based on your SAP BusinessObjects Business Intelligence platform installation directory. You cannot install the SAP BusinessObjects Design Studio for BI platform setup in an alternative directory.

NoteThe default path is C:\Program Files (x86)\SAP BusinessObjects\.

15. Click Next.16. Select the features to install.

Depending on your system landscape, you can install the following features:

Option Description

Full Installation The full installation includes all features: Analysis Application Web Components, Analysis Application Service and Analysis Application support for Mobile Devices.

Analysis Application Web Components

This feature makes it possible to display analysis applications in the BI launch pad, and use OpenDocument links to send direct links for analysis applications to other recipients. It also allows communication between the design tool and the BI platform, in order to save and launch analysis applications.

Analysis Application Service

This feature includes the Analysis Application Service that runs on the Adaptive Processing Server. The Analysis Application Service makes it possible to execute analysis applications.

Analysis Application support for Mobile Services

This feature adds mobile support to analysis applications, integrating analysis applications into SAP BusinessObjects Mobile. It allows application users to access analysis applications on mobile devices, such as the iPad.

17. Click Next.18. Enter your Central Management Console (CMS) logon credentials:

○ CMS name○ CMS port number○ Password of the CMS Administrator user

19. Click Next.20. Click Next to start the installation.21. Check whether you have to perform the following post-installation step:

BI platform Web applications are modified by this installation. You need to deploy Web applications to all your Web application server nodes manually by using the WDeploy tool in the following cases:

○ You have multiple Web application server nodes and you wish to deploy the Design Studio Add-On on more than one server node.


○ You do not use the default Tomcat.○ You do not use Web Application Container Service (WACS).

The WDeploy tool automates the deployment of Web applications to supported Web application servers. For more information, see the Web Application Deployment Guide on the SAP Help Portal at http://help.sap.com/bobip41.

22. Click Next.23. If you want to launch the WDeploy tool after installation, select the Automatically launch WDeploy tool after

install checkbox.24. Click Finish.

Results

Once the Analysis Application Web Components and Analysis Application Service have been installed on either one or two host machines, the SAP BusinessObjects Design Studio BI platform add-on is then completely installed. It enables the CMS to recognize analysis applications. When the BI platform add-on is installed together with the design tool of SAP BusinessObjects Design Studio, you can save, open and execute analysis applications.

If you have also installed Analysis Application support for Mobile Services, application users can view analysis applications on mobile devices, using the SAP BusinessObjects Mobile solution.

3.1.3.1.1 Running a Silent Installation

You can set every option in the installation wizard using the command line. This type of installation is known as a silent install. Installation options can be specified directly in the command line as a parameter, or can be stored in a response file.

For complete instructions on the silent installation procedure, refer to the silent installation section of the Business Intelligence Platform Installation Guide on the SAP Help Portal at http://help.sap.com/bobip41.

3.1.3.1.2 Modifying, Repairing or Removing the BI Platform Add-On Installation

Prerequisites

You have installed the SAP BusinessObjects Design Studio BI platform add-on on the BI platform.

Context

You can repair, modify or remove this installation.


Installation




Procedure

1. In the Windows Control Panel, choose Programs and Features.A list of installed applications appears.

2. Double-click SAP BusinessObjects Design Studio for BI Platform.3. In the Application Maintenance dialog box, select the required option:

Option Description

Modify Allows you to change the selected components (Full Installation, Analysis Application Web Components, Analysis Application Service and Analysis Application support for Mobile Services).

Repair Reinstalls the SAP BusinessObjects Design Studio BI platform add-on, according to the preset parameters.

Remove Uninstalls the SAP BusinessObjects Design Studio BI platform add-on from this machine.

4. Click Next.5. Depending on your selection in the Application Maintenance dialog box, proceed as follows:

○ To modify the installation, change the selected components as required and proceed with the installation steps.

○ To repair the installation, enter your CMS logon credentials and proceed with the installation steps.○ To remove the installation, click Next, enter your CMS logon credentials and click Finish.

Results

The SAP BusinessObjects Design Studio BI platform add-on installation has now been modified, repaired or uninstalled.

3.1.3.2 Installing the BI Platform Add-On on UNIX

Procedure


Note


2. In the A - Z Index, click D.The SAP BusinessObjects Design Studio BI platform add-on installation is available for download at SBOP DESIGN STUDIO 1.3.

3. Under Installation, download the required installation package for your operating system to a folder on your PC. There are the following packages:



○ DESIGN STUDIO 1.3 BIP ADD ON 1.3 for AIX PPC64○ DESIGN STUDIO 1.3 BIP ADD ON 1.3 for LINUX X86_64○ DESIGN STUDIO 1.3 BIP ADD ON 1.3 for SOLARIS SPARC

For more information, see SAP Note 1948049 .4. The installer is in .exe format. After the installation package download is complete, unzip the installer.5. Follow the instructions on screen to choose a destination folder and choose Install.6. After the installation, go to the folder where you installed the package.7. Transfer the installer to UNIX server.8. Under DATA_UNITS, choose the required platform for your operating system (DS_BIP_ADD_ON_<version

number>_AIX_PPC64, DS_BIP_ADD_ON_<version number>_LINUX_X64 or DS_BIP_ADD_ON_<version Number>_SOLARIS_64).

9. Choose the required BI platform version and launch setup.sh.

10. Select the language for the installation.11. Specify the destination folder for the installation. This must be the same installation folder that contains SAP

BusinessObjects Business Intelligence platform 4.0 or 4.1.

A pre-requisites check screen appears. If the installer detects that critical and optional installation pre-requisites are missing, a list of missing components appears.

12. If necessary, resolve the critical pre-requisites issues before continuing the installation.The following screens appear:

○ Welcome to the installation wizard for SAP BusinessObjects Design Studio for BI Platform○ SAP BusinessObjects License Agreement

13. Once you have read the agreement, press ENTER to accept.14. Press SPACE to expand the feature tree and select the features you want to install in the directory you

specified:Option Description

Full Installation The full installation includes all features: Analysis Application Web Components, Analysis Application Service and Analysis Application support for Mobile Devices.

Analysis Application Web Components

This feature makes it possible to display analysis applications in the BI launch pad, and use OpenDocument links to send direct links for analysis applications to other recipients. It also allows communication between the design tool and the BI platform, in order to save and launch analysis applications.

Analysis Application Service

This feature includes the Analysis Application Service that runs in the Adaptive Processing Server. The Analysis Application Service makes it possible to execute analysis applications.

Analysis Application support for Mobile Services

This feature adds mobile support to analysis applications, integrating analysis applications into SAP BusinessObjects Mobile. It allows application users to access analysis applications on mobile devices, such as the iPad.

15. Press ENTER.16. In the Existing CMS Deployment Information screen, enter the following information:

○ Central Management Console (CMS) Name○ Port Number○ User Name○ Password of the CMS Administrator user


Installation


17. Press ENTER.18. To start the installation, press ENTER.19. Check whether you have to perform the following post-installation step:

BI platform Web applications are modified by this installation. You need to deploy Web applications to all your Web application server nodes manually by using the WDeploy tool in the following cases:

○ You have multiple Web application server nodes.○ You do not use the default Tomcat.○ You do not use Web Application Container Service (WACS).

The WDeploy tool automates the deployment of Web applications to supported Web application servers.20. Press ENTER.21. To exit the installation, press ENTER.22. If necessary, start the WDeploy tool to deploy the affected Web applications to the Web application servers.

For more information, see the Web Application Deployment Guide on the SAP Help Portal at http://help.sap.com/bobip41.

Results

Once Analysis Application Web Components and Analysis Application Service have been installed on either one or two host machines, the SAP BusinessObjects Design Studio BI platform add-on is then completely installed. It enables the CMS to recognize analysis applications. When the BI platform add-on is installed together with the design tool of SAP BusinessObjects Design Studio, you can save, open and execute analysis applications.

If you have also installed Analysis Application support for Mobile Services, application users can view analysis applications on mobile devices, using the SAP BusinessObjects Mobile solution.

3.1.3.2.1 Uninstalling the BI Platform Add-On on UNIX

Procedure

1. To uninstall the SAP BusinessObjects Design Studio BI platform add-on, launch setup.sh.

2. Select the language of the installation.3. Specify the destination folder of the installation. This must be the same installation folder that contains SAP

BusinessObjects Business Intelligence platform 4.0 or 4.1.4. To move to the field Remove, press TAB.5. Press ENTER.6. To confirm the uninstallation, press ENTER.7. In the Existing CMS Deployment Information screen, enter the following information:

○ Central Management Console (CMS) Name○ Port number




○ User name○ Password of the CMS Administrator user

8. Press ENTER.9. To exit the uninstallation, press ENTER.

Results

The SAP BusinessObjects Design Studio BI platform add-on is removed from your system.

3.2 Design Tool

3.2.1 System Requirements for the Design Tool Installation

Before installing the design tool of SAP BusinessObjects Design Studio, make sure that the following components are installed on the local machines of your application designers:

● 32-bit version of Java Runtime Environment 1.6 or 1.7 (http://java.com/en/download/index.jsp )● Internet Explorer 9.0

During installation, the SAP BusinessObjects Design Studio setup checks whether Microsoft redistributable runtime DLLs VS2010 SP1 (x86) is installed. If it is not installed, the setup installs this component automatically.

We recommend installing the design tool on a machine where SAP GUI is installed. Otherwise problems might occur with connections to SAP NetWeaver BW systems that communicate through a message server.

A list of all supported operating systems and Web browsers for SAP BusinessObjects Design Studio is available in

the Product Availability Matrix (PAM) on SAP Service Marketplace at http://service.sap.com/pam . Here you can enter SBOP DESIGN STUDIO in the search field to retrieve the information.

For more information about the system requirements, see SAP Note 1698927 .

3.2.2 Installing the Design Tool of SAP BusinessObjects Design Studio

Context

The installer for SAP BusinessObjects Design Studio is available as a single executable file (for downloading and installing on your local PC or a shared location).


Installation

http://help.sap.com/disclaimer?site=http://java.com/en/download/index.jsp



Procedure


Note


2. In the A - Z Index, click D.The SAP BusinessObjects Design Studio client installation is available for download at SBOP DESIGN STUDIO 1.3.

3. Under Installation, download the installation package SBOP DESIGN STUDIO 1.3 to a folder on your PC.This package consists of the following parts:

○ DS_CLIENT_1.3○ DS_HANA_1.3○ DS_NW_1.3

For more information, see SAP Note 1948049 .4. After the download is complete, unpack the installation package.

NoteThe installation package is compressed in ZIP file format.

5. After unpacking the ZIP file, go to the folder where the package is located.6. Under DATA_UNITS\DS_CLIENT<version number>, start the SapDsSetup.exe file.

The SAPSetup installation wizard appears.7. To allow installation of SAP BusinessObjects Design Studio, click Yes.8. Close all SAP applications and click Next.9. Select SAP BusinessObjects Design Studio in the component list of the SAP Front End Installer dialog box.10. Click Next.

The SAP Front End Installer prompts you to confirm or change the target directory for SAP BusinessObjects Design Studio.

NoteThe default path is C:\Program Files (x86)\SAP BusinessObjects\Design Studio.

11. Confirm or change the target directory and click Next to start the installation.12. In the confirmation screen, click Done.




Results

The design tool of SAP BusinessObjects Design Studio is now installed and ready to use.

Users can access the design tool in the Windows Start menu under Design Studio or in the Windows directory under Start All Programs SAP Business Intelligence SAP BusinessObjects Design Studio Design Studio .

3.2.3 Installing the Design Tool from an Installation Server

Context

The design tool is installed on an installation server, which you can use on many different clients. All necessary files are copied from the server to the client during installation.

Running the installation process on an installation server makes it easier to install support packages, for example.

Procedure

1. Navigate to the SAPDsSetup.exe file you have downloaded from SAP Service Marketplace to your PC.

2. Extract the .exe file using the command line /Extract <target path>.

3. Navigate to <target path>\Setup and execute NwCreateInstServer.exe.

4. Follow the wizard instructions.

Results

For more information, see the SAPSetup Guide 9.0 at http://service.sap.com/sltoolset Software Logistics Toolset 1.0 SAPSetup .


Installation

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

3.2.4 Uninstalling the Design Tool of SAP BusinessObjects Design Studio

Prerequisites

Before uninstalling, make sure that the design tool is not running.

Procedure

1. In the Windows Control Panel, choose Programs and Features.A list of installed applications appears.

2. Double-click SAP BusinessObjects Design Studio.The SAP Front End Installer dialog box appears.

3. Click Next.4. In the confirmation screen, click Close.

Results

The design tool of SAP BusinessObjects Design Studio has now been uninstalled.


4 Upgrade

4.1 Upgrading the BI Platform Add-On

Context

To upgrade the SAP BusinessObjects Design Studio BI platform add-on on SAP BusinessObjects Business Intelligence platform, you need to download the BI platform add-on installation from SAP Service Marketplace and start the installation file.

Procedure

1. Double-click setup.exe or setup.sh (depending on your operating system).

2. Follow the instructions described in the relevant installation chapters of this guide.

Next Steps

If your users work with analysis applications on their mobile devices (using the mobile app of the SAP BusinessObjects Mobile solution), you need to change a property in the zen.properties file on the BI platform server after the upgrade.

Related Information

Installing the BI Platform Add-On on Microsoft Windows [page 12]Installing the BI Platform Add-On on UNIX [page 15]Configuring the BI Platform for Display of Analysis Applications on SAP BusinessObjects Mobile for Mobile Devices [page 37]


Upgrade

4.2 Upgrading the Design Tool Installation

Context

You can upgrade your design tool installation.

Procedure

1. Double-click SapDsSetup.exe.The SAPSetup installation wizard appears.

2. Close all SAP applications and click Next.3. Select SAP BusinessObjects Design Studio in the component list of the SAP Front End Installer dialog box.4. Click Next.

The component is updated.5. After the deployment and re-configuration of the SAP BusinessObjects Design Studio component, click Close.

Administrator Guide: SAP BusinessObjects Design StudioUpgrade © 2014 SAP SE or an SAP affiliate company. All rights reserved. 23

5 Configuration

5.1 Creating and Managing Data Source Connections in SAP BusinessObjects Business IntelligenceSAP BusinessObjects Design Studio uses SAP BusinessObjects Business Intelligence platform 4.0 or 4.1 as the central content management system for analysis applications, and as a platform for managing OLAP data source connections as well as universes.

Before designers can add data sources to the analysis applications they design, you have to create OLAP data source connections to SAP HANA systems or BW systems, or universes.

OLAP Data Source Connections

An OLAP data source connection is a BI platform repository object that contains all the information required for SAP BusinessObjects Design Studio to connect to a data source. This connection object is then linked to an analysis application.

You can create connections to individual BEx queries, BEx query views or InfoProviders of the BW system. You can also create connections to individual analytic views or calculation views of the SAP HANA system, or to BW or SAP HANA systems containing a large number of these objects. If a designer adds a data source to an analysis application, the designer must then choose an individual query or query view from the BW system connection. With SAP HANA connections, the application designer can choose individual analytic views or calculation views.

You create new data source connection objects and manage existing connection objects for SAP HANA or BW systems with one of the following tools:

● The Information Design Tool (IDT)● The module OLAP Connections in the Central Management Console (CMC) of the business intelligence

platform

CautionThe module OLAP Connections is only available in the CMC if you have SAP BusinessObjects Analysis, edition for OLAP installed with your BI platform installation. In order to use the module OLAP Connections, the Multidimensional Analysis Service of the BI platform must be enabled.

Connections can be saved to a single folder, or you can create subfolders to help group your connection objects together and manage access rights. For example, you could create a folder for SAP NetWeaver BW data source connections, and another folder for SAP HANA data source connections, and grant users access to only one of the folders.

NoteIn the design tool of SAP BusinessObjects Design Studio, all data source connections are shown in a flat list, even if you organize them by folders in the CMC.OLAP connections are shared with other applications, such as SAP BusinessObjects Analysis, edition for Microsoft Office, SAP BusinessObjects Analysis, edition for OLAP, and SAP Crystal Reports.


Configuration

For more information about creating and managing connections in SAP BusinessObjects Business Intelligence platform, see:

● “Creating an OLAP connection” in the Information Design Tool User Guide at http://help.sap.com/bobip41.● “Data Source Connections” and “Connection settings for SAP NetWeaver Business Warehouse data sources”

in the SAP BusinessObjects Analysis, edition for OLAP Administrator Guide at http://help.sap.com/boaolap41.

Universes

A universe is an organized collection of metadata objects that enable business users to analyze and report on corporate data in a non-technical language. These objects include dimensions, measures, hierarchies, attributes, pre-defined calculations, functions, and queries. The metadata object layer, referred to as the business layer, is built on a relational database schema; the objects map directly to the database structures by means of SQL expressions. A universe includes connections that identify the data sources so that queries can be run on the data.

You create universes and the corresponding relational connections using the Information Design Tool (IDT) and publish them to the BI platform.

For more information about creating universes and defining relational connections, see “Creating Universes” in the Information Design Tool User Guide at http://help.sap.com/bobip41.

NoteThe BI platform server needs to be SAP BusinessObjects Business Intelligence 4.1. If you want to use universe queries as data sources in your analysis applications, you cannot use SAP BusinessObjects Business Intelligence 4.0.

Universes can be saved to a single folder, or you can create subfolders to help group your universes and OLAP connection objects together and manage access rights. For example, you could create a folder for universes and the corresponding relational connection, a folder for SAP NetWeaver BW data source connections, and another folder for SAP HANA data source connections, and grant users access to only one of the folders.

NoteIn the design tool of SAP BusinessObjects Design Studio, all universes and data source connections are shown in a flat list, even if you organize them by folders in the CMC.

Related Information

Creating BW System Connections [page 26]Creating SAP HANA System Connections [page 27]Creating Universes for Use in Analysis Applications [page 28]

Reloading Connections in the Design Tool [page 29]

Administrator Guide: SAP BusinessObjects Design StudioConfiguration © 2014 SAP SE or an SAP affiliate company. All rights reserved. 25


http://help.sap.com/boaolap41


5.1.1 Creating BW System Connections

Prerequisites

Make sure that the machine where the Adaptive Processing Server (APS) of the BI platform is installed can communicate with the connected BW systems. If the BW system uses a message server, this machine must specify the service name of the message server in the system's services file. In Microsoft Windows, the system's services file is located in %windir%\system32\drivers\etc\services. For more information on the location

of the system's services file in other operating systems, see SAP Note 52959 . Configure the system's services file on your APS machine accordingly.

Context

To create a connection to a BW system, you have the following options:

● Create a connection to the BW system● Create a connection to a BEx query, BEx query view, or InfoProvider of the BW system

Procedure

1. In the Central Management Console under OLAP Connections, click New Connection.2. Enter the name of the BW system.3. Enter the server information.4. If you want to define the connection to a query, query view or InfoProvider, click Connect.5. In the Cube Browser dialog box, select the required BW object and click Select.6. In the Authentication list, select SSO or Pre-Defined. If you select Pre-Defined, enter a user name and

password.

NoteThe option Prompt is not supported.

7. Click Save.

Results

The BW system connections you have created appear in the list of connections in the Select Connection dialog box. This dialog box opens when you click Browse... in the Add Data Source dialog box (in the design tool of SAP BusinessObjects Design Studio). Your application designers can add the data sources of these connections to their analysis applications.


Configuration


Application users can access all BEx queries and BEx query views of the connected BW system. The prerequisite is that the users are authorized to view the data of these queries or query views by the BW authorization concept.

5.1.2 Creating SAP HANA System Connections

Context

To create a connection to a SAP HANA system, you have the following options:

● Create a connection to the SAP HANA system● Create a connection to an analytic view or a calculation view of the SAP HANA system

CautionSAP BusinessObjects Design Studio can only use analytic views or calculation views with the MultiDimensional Reporting property set to true. For more information, see “Creating Analytic Views” in the SAP HANA Developer Guide on SAP Help Portal at http://help.sap.com/hana_appliance.

NoteWith SAP BusinessObjects Busines Intelligence platform 4.0, SAP HANA system connections need to be configured using authentication type “Pre-defined”. You need to specify a fixed user name and password.

Procedure

1. In the Central Management Console under OLAP Connections, click New Connection.2. Enter the name of the SAP HANA system.3. Enter the server name and port.4. If you want to define the connection to an analytic view or a calculation view, click Connect.5. In the Cube Browser dialog box, select the required analytic view or calculation view and click Select.6. In the Authentication list, select the following settings (depending on your BI platform version):

○ With BI platform 4.0, select Pre-Defined and enter a user name and password.○ With BI platform 4.1, select SSO.

Application users can access SAP HANA data sources when opening analysis applications without entering their credentials.

NoteApplication designers accessing SAP HANA data sources in the design tool need to log on with their credentials. The SSO setting is currently not supported in the design tool. It is only supported at runtime. When choosing Application Execute on BI Platform in the design tool, for example, application designers can access the SAP HANA data sources without entering their credentials.



7. Click Save.

Results

The SAP HANA system connections you have created appear in the list of connections in the Select Connection dialog box. This dialog box appears when you click Browse... in the Add Data Source dialog box (in the design tool of SAP BusinessObjects Design Studio). Your application designers can add the data sources of these connections to their analysis applications.

Application users can access the SAP HANA data of the connected SAP HANA system in the analysis applications.

RestrictionWith BI platform 4.0, all users accessing analysis applications with data from the pre-defined SAP HANA connection have the same data authorizations as the user specified for this connection. With BI platform 4.0, it is not possible to give users different rights for viewing SAP HANA data in analysis applications. With BI platform 4.1, you can configure data access for individual users using the SSO option in the Authentication list.

5.1.3 Creating Universes for Use in Analysis Applications

If your application designers want to use universe queries as data sources for analysis applications, you need to create the universes and the corresponding relational connections using the Information Design Tool (IDT) and publish them to the BI platform.

NoteThe BI platform server needs to be SAP BusinessObjects Business Intelligence 4.1. If you want to use universe queries as data sources in your analysis applications, you cannot use SAP BusinessObjects Business Intelligence 4.0.

In Design Studio you can use universes that meet the following prerequisites:

● relational universes● single-source universes● universes with the following as underlying databases:

○ Microsoft SQL○ Sybase IQ○ Microsoft Excel○ CSV○ ERP system○ Oracle DB○ IBM DB2○ Teradata


Configuration


5.1.4 Reloading Connections in the Design Tool

Context

Once you have created data source connections or universes on the BI platform, you can reload the new connections or universes in the design tool. This function allows application designers to continue their work in the design tool without closing and opening it again.

NoteIf you create the data source connections or the universes on the BI platform before application designers start working with the design tool, they do not need to reload the connections. The design tool adds the new connections or universes automatically.

Procedure

1. Start the design tool in the BI platform startup mode.

NoteIf you use universes, the BI platform server needs to be SAP BusinessObjects Business Intelligence 4.1.

2. Choose Tools Preferences Application Design Backend Connections .3. Click Reload All Connections.

Results

The new connections and universes are added to the corresponding tables in the Preferences dialog box.

The connections and universes will be listed in the Select Connection dialog box, which appears when browsing for a connection in the Add Data Source dialog box. For more information, see the Application Designer Guide: Designing Analysis Applications under Help Help Contents in the design tool.

5.2 BI Platform Configuration for Universes in Design Studio

We recommend that you use JDBC data sources for universes in Design Studio.



Make sure that the Adaptive Connectivity Service is running on the Adaptive Processing Server of the BI platform. This is required to support universes based on JDBC data sources in the design tool of SAP BusinessObjects Design Studio.

For more information about connection servers and configuration, see the Data Access Guide at http://help.sap.com/bobip41.

5.3 Maintaining Settings on the BI Platform

After installing the SAP BusinessObjects Design Studio BI platform add-on on the BI platform, perform the following configuration steps:

● Check the status of the Analysis Application Service● Specify the maximum number of client sessions● Create a user group and add view rights to allow users to work with analysis applications● Add view rights for universe data sources to allow users to work with universe queries as data sources in

analysis applications● Add users to the Design Studio Administrators group to allow users to deploy SDK extensions to the BI

platform● Set RSADMIN parameters in the Central Management Console for analysis applications

5.3.1 Checking the Status of the Analysis Application Service

Context

You can check if the Analysis Application Service has been successfully initialized.

Procedure

1. Log on to the Central Management Console (CMC).2. Choose Servers.3. Expand the Service Categories node and choose Analysis Services.4. Select Adaptive Processing Server and choose Properties in the context menu.

NoteIf the Adaptive Processing Server does not exist, you need to create it.

1. Press the Create new server toolbar button.2. Select Analysis Services as the service category.


Configuration



3. Select Analysis Application Service as the service.4. Choose Next and Next again.5. Choose Create.

5. In the Analysis Application Service area at the bottom of the page, check the status of the service. The following messages are displayed here:Message Description

Service is healthy.

The Analysis Application Service started and was successfully initialized.

NoteThis message is displayed on BIP 4.0 installations only. It does not appear from BIP 4.1 onwards.

Service initialization failed.

The Analysis Application Service could not be initialized. If a log ID is available, it is displayed next to this message. You can check the server log files to repair the service.

On Windows platforms, the default location for the Logging directory is: Program Files <INSTALLDIR>\SAP BusinessObjects Enterprise XI 4.0\logging. On Unix, the directory is located in: <INSTALLDIR>/sap_bobj/logging.

For more information, see “Managing and Configuring Logs” in the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip41.

RestrictionThis status message refers to the first initialization of the Analysis Application Service only. The system does not check the status of the service on a regular basis. If the service has been initialized successfully, but stops running later on, the message Service is healthy will not disappear.

6. Choose Save & Close.

5.3.2 Maintaining the Maximum Number of Client Sessions

Context

You can configure the maximum number of client sessions for the Analysis Application Service.

Procedure

1. Log on to the Central Management Console (CMC).2. Choose Servers.3. Expand the Service Categories node and choose Analysis Services.4. Select Adaptive Processing Server and choose Properties in the context menu.5. Under Analysis Application Service Configuration in the Analysis Application Service area at the bottom of the

page, check the maximum number of client sessions and change the number if required.



6. Choose Save & Close.

5.3.3 Creating a User Group and Adding View Rights

Context

Before application designers and application users can work with analysis applications, you need to create a user group, add this group to the Design Studio Runtime application and assign access level View. After creating users, you need to add them to the user group.

Procedure

1. In the Central Management Console under Users and Groups Group List , click Create new group.2. Enter a group name, Design Studio User for example, and a description.

3. Click OK.4. In the Central Management Console under Applications, select User Security in the context menu of Design

Studio Runtime.5. In the User Security:AAD.Plugin dialog box, click Add Principals.6. Select the group name you created in step 2 (Design Studio User for example) and add it to the selection.7. Click Add and Assign Security.8. In the Assign Security dialog box, select the access level View and add it to the selection.9. Click Apply and OK.

10. In the Central Management Console under Users and Groups User List , click Create new user.11. Enter the required data in the New User dialog box and click Create & Close.12. Select Join Group in the context menu for the new user.13. In the Join Group: <user name> dialog box, select the group name you created in step 2 (for example, Design

Studio User) and add it to the selection.14. Click OK.

Results

Your users have view rights for the Design Studio runtime. You also need to give them the appropriate rights for the defined OLAP connections and for the folders on the BI platform. For more information, see “Setting Rights” in the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip41.


Configuration


Related Information

Managing Access Rights [page 75]

5.3.4 Adding View Rights for Universe Data Sources

Context

If your application users and your application designers want to work with analysis applications based on universe data sources, you need to assign to them the necessary view rights. With universe data sources, you need to assign the access level View On Demand for the required universe and also for the corresponding relational connection used by this universe.

NoteThe BI platform server needs to be SAP BusinessObjects Business Intelligence 4.1. If you want to use universe data sources in your analysis applications, you cannot use SAP BusinessObjects Business Intelligence 4.0.

Procedure

1. Log on to the Central Management Console (CMC).2. Choose Universes.3. Select the required universe and choose User Security in the context menu.4. Select the required user or user group and choose Assign Security.5. In the Assign Security dialog box, select the access level View On Demand and add it to the selection.6. Click Apply and OK.7. Close the User Security dialog box.8. To find the corresponding relational connections of this universe, select the universe and choose Properties in

the context menu.9. In the Properties dialog box, choose Connections.

Under Connection Name you see the corresponding relational connections of this universe.10. Close the Properties dialog box.11. In the Central Management Console, choose Connections.12. Select the required relational connection and choose User Security in the context menu.13. Select the required user or user group and choose Assign Security.14. In the Assign Security dialog box, select the access level View On Demand and add it to the selection.15. Click Apply and OK.


16. Close the User Security dialog box.

5.3.5 Adding Users to the Design Studio Administrators Authorization Group

Context

Before application designers can add or remove SDK extensions on the BI platform, you need to add the designers to the Design Studio Administrators group. Only BI platform administrators and members of this Design Studio Administrators group are allowed to add or remove SDK extensions on the BI platform. All other users have read-only access to the SDK extensions on the BI platform.

Procedure

1. In the Central Management Console under Users and Groups User List , double click on the required user.You may have to page forward to see the particular user.

2. Select Member Of Join Group .3. Add Design Studio Administrators to Destination Groups and choose OK.

Results

The selected user is now part of the Design Studio Administrators group. When the users of this group start the design tool in the BI platform mode and go to the Platform Extensions dialog box, the Install on Platform and Uninstall from Platform buttons are enabled.

After a user has been added to the Design Studio Administrators group, this user does not need to restart the design tool. The user only needs to launch the Platform Extensions dialog box again by choosing ToolsPlatform Extensions .

Related Information

Installing Design Studio SDK Extensions to Design Studio [page 46]

Removing Extensions from Design Studio [page 47]


Configuration

5.3.6 Setting RSADMIN Parameters for Analysis Applications

RSADMIN parameters can be set for analysis applications in the following location:

Choose Central Management Console Servers Analysis Services Properties Analysis Application Service Configuration .

Note● All string values should be limited to 30 characters to match existing RSADMIN.

The following table details the descriptions and default values for the RSADMIN parameters:

Parameter Description Default

Display Mixed Values Display this setting as Boolean, if the number of a mixed value is displayed

false

Display Unauthorized Values as: Display this string as String for the values, for which the user is not authorized

NO_AUTHORIZATION

Display Division by Zero as: Display this string as String for division by zero values

DIF0

Display Nonexistent Values as: Display this string as String for values, which cannot be determined

NOT_EXIST

Display Values with Mixed Units as: Display this string as String for values, which consist of mixed currencies and units

*

Display Overflow Values as: Display this string as String for values with a numerical overflow

OVERFLOW

Display Attribute Texts Even if Blank Display attribute text when the checkbox is selected, even if attribute text is blank

False

Related Information

Maintaining Settings on the BI Platform [page 30]


5.4 Configuration Tasks for Mobile Usage of Analysis Applications

Before users can access analysis applications on the mobile app of the SAP BusinessObjects Mobile solution, you need to check whether a mobile category exists on the BI platform. If no mobile category exists, you need to create one. Then you need to assign the analysis applications to this category.

NoteThe default name of the mobile category is Mobile. Administrators can change the category name in the mobi.properties file on the Mobile server under[<WebAppServer>_Home]\webapps\MobileBIService\WEB-INF\mobi.properties. For more information, see “Configuring Categories on the Mobile Server” in the Administrator and Report Designer's Guide: SAP BusinessObjects Mobile for iOS at http://help.sap.com/bomobileios.

If your application users want to access analysis applications on their mobile devices, you need to change a property in the zen.properties file on the BI platform server.

5.4.1 Creating a Mobile Category on the BI Platform

Prerequisites

Check whether a mobile category exists on the BI platform. If this category does not exist, you need to create one.

Procedure

1. In the Central Management Console under Categories, choose Manage New Category .2. When prompted, type Mobile as the name for the new category.3. Click OK.

Next Steps

For more information on configuring categories, see “Configuring Categories on the Mobile Server” in the Administrator and Report Designer's Guide: SAP BusinessObjects Mobile for iOS at http://help.sap.com/bomobileios.


Configuration





5.4.2 Assigning Analysis Applications to the Mobile Category

Context

Before users can access analysis applications on a mobile device using the SAP BusinessObjects Mobile solution, you need to assign the analysis applications to the mobile category on the BI platform.

Procedure

1. In the BI launch pad, go to the folder that contains the analysis application that you want to assign to the mobile category.

2. Select the analysis application and click More Actions Categories .The Categories dialog box appears.

3. Choose the mobile category.4. Click OK.

5.4.3 Configuring the BI Platform for Display of Analysis Applications on SAP BusinessObjects Mobile for Mobile Devices

Context

Before application users can view analysis applications on their mobile devices (using the mobile app of the SAP BusinessObjects Mobile), you need to change a property in the zen.properties file on the BI platform server.

Procedure

1. On the BI platform server, navigate to the <SAP BusinessObjects Installation directory>\Tomcat\webapps\MobileBIService\WEB-INF\classes\internal\zen.properties file.

2. Change the document.supported.devices property as follows:

○ document.supported.devices = ipad, iphone, androidtablet, androidphone3. Stop the Tomcat server.4. Clear the cache of the Tomcat server.5. Restart the Tomcat server.


Next Steps

After updating the SAP BusinessObjects Design Studio BI platform add-on, you need to execute the steps described above again.

For more information about Android version support, see the Product Availability Matrix (PAM) on SAP Service

Marketplace at http://service.sap.com/pam Here you can enter SBOP DESIGN STUDIO in the search field to retrieve the information.

5.5 Administration Tasks for Planning Applications

Before application designers can create desktop browser applications for planning business data based on BW queries or query views, you need to configure the BW system as described in the SAP NetWeaver BW documentation on SAP Help Portal:

● Administration Tasks for Analytical Services● Planning Business Data with BW Integrated Planning

If you use planning models of SAP Business Planning and Consolidation, version for SAP NetWeaver, see the BPC documentation on SAP Help Portal at Administration.

5.6 Configuring the Hosts File for Universes

Context

If your application designers want to use universe queries as data sources in their analysis applications and you are using a BI platform server with IP address (usually a fenced virtual machine), you need to add the following mappings to the hosts file:

● IP address - fully-qualified host name of BI platform● IP - host name of BI platform

Procedure

1. On the machine where the design tool is installed, navigate to your hosts file under %windir%\System32\drivers\etc\hosts, for example.

2. Add the following line to the hosts file:


Configuration


http://help.sap.com/saphelp_nw74/helpdata/en/fa/c1194276e0de2ce10000000a1550b0/content.htm?frameset=/en/16/a6fe41b227096fe10000000a155106/frameset.htm&current_toc=/en/df/ae301529db2b47b079c0c23ad13460/plain.htm&node_id=9

http://help.sap.com/saphelp_nw74/helpdata/en/4c/bb4ebeed80606be10000000a42189e/frameset.htm

http://help.sap.com/saphelp_bopacnw101/helpdata/en/unified/82/f51cf12cfc48c58975b9b5e6fba9aa/frameset.htm

○ <IP> <fully-qualified host name of BI platform> <host name of BI platform>

For example: 10.192.168.10 myhost.sap.corp myhost3. Save the hosts file.

5.7 Providing the Web Service URL to Application Designers

When logging on to the design tool, application designers need to enter the Web Service URL in the Logon to SAP BusinessObjects BI Platform dialog box.

The Web Service URL describes the connection to the BI platform. It consists of information about the host and port of the BI platform: http(s)://<host>:<port>/dswsbobje/services/Session.

Provide your application designers with the Web Service URL to your BI platform server. Once a Web Service URL has been added to the Logon to SAP BusinessObjects BI Platform dialog box, it is listed in the Web Service URL dropdown box. If you have several BI platform servers, the application designers can select the one they require in the Web Service URL dropdown box.

5.8 Activating the Query Runtime Statistics

Context

Design Studio supports the query runtime statistics of SAP NetWeaver BW. Using the query runtime statistics, you can find out how much time is required to execute certain user actions in Design Studio and in the BW analytic engine. The system records the performance-critical processing parts (statistics events). It calculates the net times by calculating the runtime of an event using the difference between the start time and end time (minus the times for other events called from within the event).

Procedure

1. In the BW system, open the Maintenance of Statistics Properties screen (transaction RSDDSTAT).

2. Select the objects you want to change.

NoteYou can activate objects on the Query and the InfoProvider tab page. With Design Studio, the other tab pages (Web Template and Workbook) do not apply and are therefore not supported.


3. To activate the statistics for the selected object, choose X On in the Settings dropdown box.

NoteFor queries, you can also specify the detail level for the statistics.

4. To apply the settings to the list, choose Replace Values.5. Save your entries.

Results

For more information, see Maintenance of Statistics Properties on the SAP Help Portal at http://help.sap.com.

Next Steps

After you have run the required workflow in Design Studio using the query or the InfoProvider for which statistics were enabled, you can access the statistics by calling transaction SE16 and viewing table RSDDSTAT_OLAP.

For more information, see Analysis of Statistics Data on the SAP Help Portal at http://help.sap.com.

5.9 Enabling JavaScript Compression to Enhance BI Platform 4.1 Performance

SAP BusinessObjects Business Intelligence platform 4.1 can be configured to compress many different file types in order to increase performance and reduce server/client transfer times. To reduce the file transfer size during the initial load of an application, it is recommended that application/javascript compression is enabled. This is located in the Business Intelligence platform server.xml file in the following directory: InstallPath\SAP BusinessObjects\tomcat\conf\server.xml. Within this file you must locate the Connector xml element and append application/javascript onto the compressableMimeType element attribute. The final attribute should look similar to compressableMimeType=text/html,text/xml,text/plain,text/css,text/javascript,text/json, application/json, application/javascript. After appending and saving the server.xml file, you must restart Tomcat.

Note

For more information on performance, you can refer to SAP Note 1931691 .


Configuration

http://help.sap.com/saphelp_nw74/helpdata/en/43/e37f8a6df402d3e10000000a1553f7/content.htm?frameset=/en/89/71b01ce1f44e95a860a6c3f7dda911/frameset.htm

http://help.sap.com/saphelp_nw74/helpdata/en/43/e3807a6df402d3e10000000a1553f7/content.htm?frameset=/en/89/71b01ce1f44e95a860a6c3f7dda911/frameset.htm


5.10 Maintaining Settings in the Design Tool

You can define settings for the design tool in the Preferences dialog box. To start the Preferences dialog box, choose Tools Preferences Application Design .

Change the default values as required and choose Apply to make the entered values effective. If you want to reset the default values, choose Restore Defaults. To close the Preferences dialog box, choose OK.

The following settings are available:

General

You can switch the startup mode. In the default setting, the design tool starts in local mode after installation. If you want to use SAP BusinessObjects Design Studio integrated into one of the supported platforms, select the required platform:

● SAP BusinessObjects BI Platform● SAP HANA● SAP NetWeaver

After restarting the design tool, you need to log on to the selected platform.

NoteIn the Logon to <selected platform> dialog box, you can still decide to log on locally by clicking Skip, even if the startup mode is set to one of the supported platforms. The design tool starts in local mode.

In the Undo History Size field, you can change the default value 50 and enter a number between 20 and 999. This value defines how often application designers can undo their changes when working in the design tool.

Embedded Web Server

You can define the network port for the embedded Web server of the design tool. Enter a number between 1024 and 65535. When an application is executed, the port number can be seen in the URL. If the port is set to 5555 for example, the URL is http://localhost:5555/aad/web.do?APPLICATION=MYAPP. If you leave the default value 0, the system automatically assigns a network port.

TipIf users create bookmarks for their applications, the network port has to be set to a fixed number. Auto-assigning the network port does not guarantee that the bookmarks will work properly.


Application Preview

The language of message texts and tooltips is defined by the language setting in the BI launch pad or the Web browser. The format for numbers, dates and times varies according to the defined language setting. To preview the analysis applications in the required language and formatting, application designers can switch between the preferred viewing locale of the BI launch pad (BI Platform User Settings radio button) or the Web browser language (Web Browser radio button).

Application Recovery

In the default setting, the system automatically saves unsaved applications every minute. You can configure the auto-save time interval as required. Select the Save application recovery information every <1> minute checkbox and enter the required number for the auto-save time interval.

TipThe design tool needs to be restarted for the new interval to become active.

There is a background job that searches for unsaved applications during the specified interval. If unsaved applications are found, the system extracts their XML code and stores it under <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen. The content of this file is encrypted using Eclipse secure store technology.

NoteThe auto-save function does not replace saving an application. Saving an application or closing it and answering the Save changes? question with either Yes or No will delete the XML from the autosaves file.

In the event of a system crash, the auto-saved XML persists. When restarting the design tool and opening the affected application again, the designer is informed that an auto-saved version of the application exists.

● If the designer decides to restore the auto-saved version, the system takes the stored XML, saves the application and opens the application in the layout editor. The auto-saved XML is removed.

● If the designer decides to discard the auto-saved version, the auto-saved XML is removed as well.

Member Selection

Application designers need to pick single members of a dimension when using statements like setFilter for a dropdown box, for example. They can pick the members in the content assistance of the Script Editor dialog box or in the Select Member dialog box. The Select Member dialog box can list a small or large number of members, depending on the maximum threshold number of members. You can set the default threshold in the Preferences dialog box.

● You can define the maximum number of members that are displayed in the Select Member dialog box. Enter the required number in the Maximum number of members to fetch from backend in dialog checkbox. The default threshold is 1000.


Configuration

● You can define the maximum number of members that are displayed in the content assistance of the Script Editor dialog box. Enter the required number in the Maximum number of members to fetch from backend in content assistance checkbox. The default threshold is 20. If the number of available members exceeds this threshold number, the content assistance does not list single members. Instead it offers the Select Member... entry, which opens the Select Member dialog box.

TipDesigners can access the content assistance in the script editor by pressing CTRL + SPACE .

You can also decide whether the system should display warnings in the script editor whenever designers manually enter non-existent values. To activate the warnings, select the Display warnings for manually entered invalid values checkbox.

Prompt Handling

In the Prompts dialog box, application designers and application users set values for prompts. For SAP NetWeaver BW data sources, prompts are defined as variables. In SAP HANA, prompts are defined as input parameters or variables. When working with data sources with defined variables, application designers might be prompted to set the required values before continuing their work in the design tool (if there are mandatory variables without default values, or if variables have invalid default values, for example). SAP BusinessObjects Design Studio stores all valid prompt values of each analysis application in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. This provides application designers with a smooth workflow in the design tool. If this was not the case, the Prompts dialog would appear when designers reload an analysis application or modify the initial state of the data source in the Initial View dialog box, for example.

In the Preferences dialog box, you can specify whether the Prompts dialog box should appear when an analysis application is executed locally:

● If you want to simulate how an application user opens the analysis application, leave the checkbox deselected (default setting). When you execute an analysis application locally, the Prompts dialog box appears and you can set the prompt values in the same way an end user would do.

● If you want to use the prompt values from the cache file, select the Use cached prompt values for local execution checkbox. The Prompts dialog box does not appear and application designers can test their analysis applications quickly.

NoteIf the Prompts dialog box still appears even if this setting is activated, check if the Force Prompts On Startup property of the analysis application is set to true. This property always forces the Prompts dialog box to appear, regardless of whether the Use cached prompt values for local execution checkbox is selected.

If you want to clear the prompt values of an analysis application in the cache file, press Clear Prompt Value Cache.... You can select the required analysis application(s) for this cache deletion. When you reload the application, the Prompts dialog box will appear and you can set new values, for example.


Paths

SAP BusinessObjects Design Studio includes a set of templates that offer designers an easy way to get started. When creating new applications, designers can choose between different templates that are optimized for desktop Web browser applications or mobile applications in the New Application dialog box ( ApplicationNew... ). For more information, see “Creating a new analysis application” in the Application Designer Guide: Designing Analysis Applications under Help Help Contents in the design tool.

In the Preferences dialog box, you see the default path to the folder where these templates are stored. You can change the path by clicking the Browse... button.

Backend Connections

Under Tools Preferences Application Design Backend Connections , you can reload new connections or universes in the design tool. This function allows application designers to continue their work in the design tool without closing and opening it again.

Network Connections

Under Tools Preferences Application Design Network Connections , you can specify the proxy settings to be used when opening connections. For more information, see “Network Connection Preferences” in the online help. You can access this chapter by pressing F1 or the Help button in the Preferences dialog box.

Support Settings

Under Tools Preferences Application Design Support Settings , you can specify the amount of information stored in a log file and activate functions to record traces or collect statistics data.

Related Information

Reloading Connections in the Design Tool [page 29]Setting Network Connections If Logon Problems Occur [page 79]

Activating Runtime Traces [page 80]Activating SAP JCo Traces [page 80]

Viewing And Collecting Statistics Data At Runtime [page 81]


Configuration

5.11 Sizing Guidelines

You can find recommendations on sizing and optimizing the performance of analysis applications in SAP Note

1177020 .

5.12 More Information

For more information about configuration, update and setup of SAP BusinessObjects Design Studio, see SAP

Note 1948049 . This note contains up-to-date information that could not be included in this guide.




6 Operations

6.1 Deploying SDK Extensions

In addition to the standard palette of components in Design Studio, you can install 3rd-party components developed with the Design Studio SDK. Adding these 3rd-party components, known as Design Studio SDK extensions, to your Design Studio installation enables you to create and execute local analysis applications containing these SDK extensions.

Before application users can launch analysis applications containing SDK extensions from the BI platform, you need to deploy these locally installed extensions to the BI platform.

For more information about creating SDK extensions using the Design Studio SDK, see the Developer Guide: Design Studio SDK on the SAP Help Portal at http://help.sap.com/boad.

Related Information

Installing Design Studio SDK Extensions to Design Studio [page 46]

Deploying Extensions to the BI Platform [page 48]

6.1.1 Installing Design Studio SDK Extensions to Design Studio

Context

You can add extensions developed with the Design Studio SDK to your Design Studio installation as new components.

Procedure

1. In Design Studio, choose Tools Install Extension to Design Studio... .2. Depending on where the SDK extension is located, proceed as follows:

○ For locally saved extensions, choose Archive... and select the archive file containing the SDK extension, under C:\SampleExtension.zip, for example.


Operations


○ For extensions stored on a Web server, enter the URL of the Web server.3. Choose OK.4. Select the required feature, SampleExtensionFeature, for example.5. Select the Design Studio extensions that you want to install.6. Choose Finish to proceed with the installation.7. Choose Next and again Next to confirm the installation.8. Accept the terms of the license agreement and choose Finish.9. Choose Yes to allow Design Studio to restart.

Results

The SDK extensions appear in the Components view of Design Studio as new components.

The components are stored under <user home directory>\Analysis-config.

6.1.2 Removing Extensions from Design Studio

Context

You can remove SDK extensions that you have added to your Design Studio installation.

Procedure

1. In Design Studio, choose Help About... .2. Click the Installation Details button.3. Select the feature containing the SDK extension, for example, SampleExtensionFeature.4. Choose Uninstall....5. In the Uninstall wizard, choose Finish.6. Choose Yes to allow Design Studio to restart.

Results

The SDK extensions are removed from the Components view of Design Studio.

Administrator Guide: SAP BusinessObjects Design StudioOperations © 2014 SAP SE or an SAP affiliate company. All rights reserved. 47

6.1.3 Deploying Extensions to the BI Platform

Context

Before application users can launch analysis applications containing SDK extensions from the BI platform, you first need to deploy these locally installed extensions to the BI platform. In order to do so, you need BI platform administrator rights or your administrator must add you to the Design Studio Administrators group.

Procedure

1. Start the design tool in the BI platform mode and choose Tools Platform Extensions .2. Select the required extensions that are installed on your local computer.3. Choose Install on Platform.4. In order to complete the installation process, you have to manually restart the BI platform Adaptive

Processing Servers that host the Analysis Application Service. Accept the warning in the design tool.The selected extensions appear under Extensions Installed on Platform.

5. Choose Close.6. Restart the BI platform Adaptive Processing Servers that host the Analysis Application Service.

Related Information

Adding Users to the Design Studio Administrators Authorization Group [page 34]

6.1.4 Removing Extensions from the BI Platform

Procedure

1. Start the design tool in the BI platform mode and choose Tools Platform Extensions .2. Under Extensions Installed on Platform, select the extensions you want to remove from the BI platform.3. Choose Uninstall from Platform.4. Confirm the uninstallation by choosing Yes.


Operations

5. In order to complete the uninstallation process, you have to manually restart the Adaptive Processing Servers of the BI platform that host the Analysis Application Service. Accept the corresponding warning in the design tool.The selected extensions are removed from the table Extensions Installed on Platform.

6. Choose Close.7. Restart the Adaptive Processing Servers of the BI platform that host the Analysis Application Service.

Administrator Guide: SAP BusinessObjects Design StudioOperations © 2014 SAP SE or an SAP affiliate company. All rights reserved. 49

7 Security

7.1 Technical System Landscape

The following graphic shows the system landscape for SAP BusinessObjects Design Studio with SAP BusinessObjects Business Intelligence as a platform:

Related Information

Communication at Design Time [page 54]Communication at Runtime [page 57]

7.2 User Management and Authentication

You have to configure user accounts in the following systems:

● The connected SAP NetWeaver BW systemsFor more information, see “Identity Management” in the SAP NetWeaver Library at http://help.sap.com/netweaver.

● The connected SAP HANA systems


Security

http://help.sap.com/saphelp_nw74/helpdata/en/06/371640b7b6dd5fe10000000a155106/frameset.htm


For more information, see “User Management” in the SAP HANA Security Guide at http://help.sap.com/hana_appliance.

● The BI platformFor more information, see “Managing Users and Groups” in the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip41.

7.3 Authentication and Single Sign-On

Single Sign-On when using SAP NetWeaver BW data sources

Once users are logged on to SAP BusinessObjects Business Intelligence platform, Single Sign-On enables users to access SAP NetWeaver BW systems without having to provide their logon credentials. Single Sign-On works if the following conditions are met:

● SAP BusinessObjects Business Intelligence is configured correctly for Single Sign-On . For more information, see “Configuring SAP authentication” under “SAP Authentication” in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip41.

● In the Central Management Console, under OLAP Connections, the Authentications parameter is set to SSO for the BW systems that should be used with Single Sign-On.

● In the Central Management Console, under Users and Groups User List , the BI platform user accounts need to be mapped to the BW user accounts: In the Properties dialog box of a BI platform user, click Assign Alias... to add the corresponding BW user.

● The SAP NetWeaver BW system is configured as an external authentication system. Proprietary SAP tokens (assertion tickets) are used to provide a mechanism that supports Single Sign-On for design studio users connecting to BW systems. For more information, see “Setting up single sign-on to the SAP system” under “SAP Authentication” in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip41.

With Single Sign-On, application designers sign on once to SAP BusinessObjects Business Intelligence with their credentials when starting the design tool of SAP BusinessObjects Design Studio.

Application users accessing analysis applications in the BI launch pad also sign on once to SAP BusinessObjects Business Intelligence.

Both user types can access BW data without needing to log on again.

NoteAlternatively, you can configure the OLAP connection to SAP NetWeaver BW with authentication type “Pre-defined”. Specify a fixed user name and password. Note that all users accessing analysis applications with data from the pre-defined SAP NetWeaver BW connection have the same data authorizations as the specified user for this connection.

Administrator Guide: SAP BusinessObjects Design StudioSecurity © 2014 SAP SE or an SAP affiliate company. All rights reserved. 51







Single Sign-On when using SAP HANA data sources configured on BI platform 4.0

With SAP BusinessObjects Business Intelligence 4.0, Single Sign-On is not supported for SAP HANA system connections.

In the Central Management Console, under OLAP Connections, SAP HANA system connections need to be configured with authentication type “Pre-defined”, and a fixed user name and password.

Application designers and application users do not need to enter user credentials when accessing SAP HANA data sources.

RestrictionAll users accessing analysis applications with data from the pre-defined SAP HANA connection have the same data authorizations as the specified user for this connection. It is not possible to give users different rights for viewing SAP HANA data in analysis applications.

Single Sign-On when using SAP HANA data sources configured on BI platform 4.1

With SAP BusinessObjects Business Intelligence 4.1, Single Sign-On works if the following conditions are met:

● In the Central Management Console, under Applications SAP HANA Authentication , a new SAP HANA authentication connection has been configured and the generated certificate has been imported to the SAP HANA system. Proceed as follows:

1. Select SAP HANA Authentication and choose Configure SAP HANA Connections in the context menu.2. To add a new SAP HANA authentication connection, choose Create a connection.3. Enter the hostname, port and the unique identity provider ID of your SAP HANA system.4. Press Generate.5. After the certificate has been generated, copy it to your SAP HANA deployment's trust.pem file. For

more information, see “Configuring SAML Identity Providers” in the SAP HANA Administration Guide at http://help.sap.com/hana_appliance.

For more information about configuring SAP HANA authentication connections, see “Configuring SAP HANA single sign-on” under “Application-specific settings” in the “Managing Applications” chapter of the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip.

● In the Central Management Console, under OLAP Connections, the Authentications parameter is set to SSO for the SAP HANA systems that should be used with Single Sign-On.

With Single Sign-On, application users accessing analysis applications in the BI launch pad sign on once to SAP BusinessObjects Business Intelligence. They can access SAP HANA data without needing to log on again.

Application designers accessing SAP HANA data sources in the design tool need to log on with their credentials. Single Sign-On with SAP HANA data sources is currently not supported in the design tool. It is only supported at runtime. When choosing Application Execute on BI Platform in the design tool, for example, application designers can access SAP HANA data without entering their credentials.


Security



Single Sign-On when using universe data sources

You can configure single sign-on when using universe data sources from the BI platform 4.1. For more information, see “Single Sign-On Support” under “Learning Data Access Specifics” in the Data Access Guide at http://help.sap.com/bobip.

Related Information

Creating Connections to BI Back-End Systems in Local Mode [page 86]

7.4 Authorizations

For security reasons, make sure that users do not have administrator rights on the client PCs. Otherwise, these users could access trace files of other users on the client PC.

For data access management, SAP BusinessObjects Design Studio uses the authorization concept of the corresponding back end system.

● With SAP NetWeaver BW, users need analysis authorizations to view the data of authorization-relevant characteristics in a query or query view, which is used as a data source in an analysis application. For more information, see “Authorizations” in the SAP NetWeaver Library at http://help.sap.com/netweaver.

● With SAP HANA, the authorization concept depends on the platform version:

○ With SAP BusinessObjects Business Intelligence 4.1, users need analytic privileges to view the data of the SAP HANA data sources that are used in analysis applications. For more information, see “Analytic Privileges”, under “SAP HANA Authorization”, in the SAP HANA Security Guide, at http://help.sap.com/hana_appliance.

○ With SAP BusinessObjects Business Intelligence 4.0, all users are authorized to view the same data as the user specified for an SAP HANA connection on the CMC. It is not possible to give different users different rights for viewing SAP HANA data in analysis applications. The user specified in the CMC for an SAP HANA connection needs analytic privileges to view the data of the SAP HANA data sources used in analysis applications. For more information, see “Analytic Privileges”, under “SAP HANA Authorization”, in the SAP HANA Security Guide, at http://help.sap.com/hana_appliance.

For content management of analysis applications, images and data source connections, SAP BusinessObjects Design Studio uses the authorization concept of the BI platform. For more information on configuring authorizations for the folders containing these objects, see “Setting Rights”, in the Business Intelligence Platform Administrator Guide , at http://help.sap.com/bobip41.

To deploy SDK extensions to the BI platform, users need to have BI platform administrator rights or they need to be members of the Design Studio Administrators group.

If your users want to use universe data sources in your analysis applications, you need to assign your users the access level View On Demand for the required universe and also for the corresponding relational connection used by this universe.



http://help.sap.com/saphelp_nw74/helpdata/en/4a/4ce95baef40451e10000000a421937/content.htm?frameset=/en/c5/f1c99abdd3fb4aa7febe103b5d77e5/frameset.htm





Related Information

Managing Access Rights [page 75]Adding Users to the Design Studio Administrators Authorization Group [page 34]

Adding View Rights for Universe Data Sources [page 33]

7.5 Network and Communication Security

Your network infrastructure is extremely important for protecting your system. Your network needs to support the communication necessary for your business needs without allowing unauthorized access.

With SAP BusinessObjects Design Studio, we distinguish between the following communication scenarios:

● Communication at design time: Application designers working with the design tool● Communication at runtime (desktop): Application designers executing analysis applications on the BI

platform, or application users accessing analysis applications in the BI launch pad● Communication at runtime (mobile device): Application users accessing analysis applications on a mobile

device using the SAP BusinessObjects Mobile solution

7.5.1 Communication at Design Time

The following diagram illustrates the components involved and provides an overview of the communication channels at design time:


Security

Figure 1: Components at design time

At design time, the following components are involved:

● The client tier with the Web browser and the design tool on the local computer of the application designer● The Web tier of the BI platform with the Web services provider● The processing tier with Connection Server or Adaptive Connectivity Service for accessing universes and the

Central Management Server (CMS) for accessing the BI platform repository.● The storage tier with the BI back end systems (SAP NetWeaver BW, SAP HANA and supported databases as

source systems for universes) and the BI platform repository.


The communication sequence works as follows:

Creating new analysis applications

The application designer starts the design tool and logs on to the BI platform. The application designer creates a new application. The embedded Web browser in the design tool's layout editor opens. The browser connects with the design tool's embedded Web server. HTTP(S) is used as the communication protocol.

The new application is automatically saved in the BI platform repository. The design tool connects to the BI platform Web services provider using HTTP(S) as the protocol. The Web services provider forwards the information to the CMS using CORBA as the protocol. For more information on securing this communication channel, see “Securing the BI platform”, in the Business Intelligence Platform Administrator Guide , at http://help.sap.com/bobip41.

Opening analysis applications

When analysis applications are opened, the design tool connects to the Web services provider to fetch the analysis application, which is stored in the BI platform repository. For more information on securing this communication channel, see “Securing the BI platform”, in the Business Intelligence Platform Administrator Guide , at http://help.sap.com/bobip41. The analysis application is displayed in the embedded Web browser in the design tool's layout editor. The browser connects with the design tool's embedded Web server. This communication is carried out using HTTP as the protocol.

Adding data sources to analysis applications

When the application designer adds data sources to the application (by adding a new data source or by selecting members in the script editor, for example), the design tool connects to the Web services provider. The Web services provider fetches the connection information, which is stored in the BI platform repository. If the OLAP connection is defined with Single Sign-On, the required SAP token (assertion ticket) is retrieved through the BI platform Web services provider. For more information on securing this communication channel, see “Securing the BI platform”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip41.

The design tool reads the connection information to identify which BI back end system is used and fetches the business data from this BI back end system.

With SAP NetWeaver BW as the BI back end system, this communication is performed using a synchronous JCo Remote Function Call (RFC) connection. You can protect this RFC connection using Secure Network Communications (SNC). For more information, see “Transport Layer Security”, in the SAP NetWeaver Security Guide , at http://help.sap.com/netweaver.

With SAP HANA as the BI back end system, this communication is performed using a Java Database Connectivity (JDBC) connection. You can protect this connection using the Secure Sockets Layer (SSL) protocol. For more information, see “Securing Data Communication”, in the SAP HANA Security Guide , at http://help.sap.com/hana_platform.

With universes as data sources, the data is accessed using the Connection Server or Adaptive Connectivity Service. This communication is performed using CORBA as the protocol. The Connection Server retrieves the


Security





http://help.sap.com/saphelp_nw74/helpdata/en/5f/0f558b8a7841049139f0fb558ac62c/content.htm?frameset=/en/4a/af6fd65e233893e10000000a42189c/frameset.htm

http://help.sap.com/hana_platform


data from the underlying database of the used universe by using its specific protocol. For more information about the Connection Server, see the Data Access Guide at http://help.sap.com/bobip41.

Executing analysis applications

If the application designer chooses Application Execute Locally , a new Web browser window opens outside the design tool. It connects with the design tool's embedded Web server. This communication is carried out using HTTP as the protocol.

For more information on executing analysis applications on the BI platform, see the following chapter.

Related Information

Communication at Runtime [page 57]Creating and Managing Data Source Connections in SAP BusinessObjects Business Intelligence [page 24]BI Platform Configuration for Universes in Design Studio [page 29]

7.5.2 Communication at Runtime

The following diagram illustrates the components involved and provides an overview of the communication channels at runtime:



Figure 2: Components at runtime

At runtime, the following components are involved:

● The Web browser on the local computer of the application designer● The native SAP Business Object Mobile client application on the mobile device (iPad or iPhone)● The Web tier of the BI platform with the BI launch pad or Open Document Web application● The SAP Business Objects Mobile server as Web tier● The processing tier containing the Analysis Application Service on the Application Processing Server (APS)

and the Central Management Server for accessing the BI platform repository.● The storage tier with the BI back end systems (SAP NetWeaver BW, SAP HANA and supported databases as

source systems for universes) and the BI platform repository.

The communication sequence works as follows:

Executing analysis applications in the design tool

When an application designer chooses Application Execute on BI Platform , the application is displayed in a separate Web browser window (using the document link of the application and the current session of the BI platform). The application designer does not have to log on to the BI platform when executing the application on the BI platform.

When applications are executed on the BI platform, the BI launch pad/Open document Web application forwards the request to the Analysis Application Service using CORBA. The BI platform adapter of the Analysis Application


Security

Service fetches the connection information (and any images used) from the BI platform repository. This communication is carried out using CORBA. For more information on securing this communication channel, see “Securing the BI platform”, in the Business Intelligence Platform Administrator Guide , at http://help.sap.com/bobip41.

The Analysis Application Service reads the connection information to identify which BI back end system is used and fetches the business data from this BI back end system.

With SAP NetWeaver BW as the BI back end system, this communication is performed using a synchronous JCo Remote Function Call (RFC) connection. You can protect this RFC connection using Secure Network Communications (SNC). For more information, see “Transport Layer Security”, in the SAP NetWeaver Security Guide, at http://help.sap.com/netweaver.

With SAP HANA as the BI back end system, this communication is performed using a Java Database Connectivity (JDBC) connection. You can protect this connection using the Secure Sockets Layer (SSL) protocol. For more information, see “Securing Data Communication”, in the SAP HANA Security Guide, at http://help.sap.com/hana_platform.

With universes as data sources, the data is accessed through the BI platform Connection Server in library mode from Analysis Application Service (see BI Platform Configuration for Universes in Design Studio [page 29]). The data is retrieved from the underlying database of the used universe by using its specific protocol. For more information about the Connection Server, see the Data Access Guide at http://help.sap.com/bobip41.

The Analysis Application Service forwards the information to the OpenDocument Web application and the analysis application is displayed in the Web browser.

Executing analysis applications in the BI launch pad

Application users start an analysis application in the BI launch pad by clicking Open in the context menu of an application, or by clicking the application in the BI launch pad.

In this case, the same communication process applies as described above. The analysis application is displayed in a new tab in the BI launch pad (which is running in the Web browser). If you are using BI platform 4.0 and Internet Explorer as a Web browser, the analysis application is displayed in a new window.

Executing analysis applications in the native SAP Business Object Mobile client application on the mobile device (iPad or iPhone)

Application users start the SAP BusinessObjects Mobile client application and log on to the SAP BusinessObjects Mobile server. They start an analysis application from this mobile client application. HTTP(S) protocol is used to communicate with the SAP BusinessObjects Mobile server. The analysis application is displayed in this mobile client application.

The Mobile server delegates incoming requests to Analysis Application Service using CORBA communication. This communication and all the following steps are performed as described above.

The application users do not need to log on to the SAP BusinessObjects Mobile server or to the BI platform separately.




http://help.sap.com/saphelp_nw74/helpdata/en/5f/0f558b8a7841049139f0fb558ac62c/content.htm?frameset=/en/4a/af6fd65e233893e10000000a42189c/frameset.htm




For more information on securing communication channels for SAP BusinessObjects Mobile, see “Network and Communication Security” in the Mobile Security Guide at http://help.sap.com/bomobileios.

7.6 Data Storage Security

Analysis applications

Application designers store the analysis application files in folders on the BI platform. They can also store images and icons they use in their analysis applications on the BI platform.

TipWe recommend using a common root folder for all images and icons used in analysis applications on all BI platform instances. This will make it simpler to transport analysis applications and the referenced images or icons between different BI platform systems.

You can restrict access to the analysis application files by assigning access rights to the folders. For more information on configuring the authorizations for the folders containing analysis applications, see “Setting Rights”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip41.

Application designers can also use images and icons in their analysis applications from the Internet or intranet. Your application designers should be aware that using icons and images from the Internet could be a security risk.

Analysis applications history

The analysis applications history in the Application menu of the design tool is persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.

Data source history

The data source history in the Add Data Source dialog box of the design tool is persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.

Prompt values

All valid prompt values of each analysis application are persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.


Security



Related Information

Transporting Analysis Applications, Images, Data Source Connections and Universes [page 75]

7.7 Auditing

Auditing allows you to keep a record of significant events on servers and applications. This provides you with an overview of what information is being accessed, how it is being accessed and modified, and who is performing these operations.

SAP BusinessObjects Design Studio uses the auditing capabilities of the BI platform for all accessed content located on the BI platform. SAP BusinessObjects Design Studio generates the following common audit events:

● Login● Logout

Analysis applications, running on the BI platform, generate the following common audit event:

● View:

○ View file size○ View client side

Analysis applications, running on the BI platform, generate the following application specific event:

● Cube connection

Note● In SAP BusinessObjects Design Studio design time, client side operations or workflows will not be audited.● View Cube is not implemented in Design Studio 1.3.

For more information, see “Auditing” in the Business Intelligence Platform Administrator Guide at http://help.sap.com/bobip

7.8 Security for Additional Applications

SAP BusinessObjects Design Studio takes the data for the data sources from SAP NetWeaver Business Warehouse or SAP HANA.

For more information on security aspects of SAP NetWeaver BW, see the Security Guide for SAP NetWeaver BW in the SAP NetWeaver Library, at http://help.sap.com/netweaver.

For more information on security aspects of SAP HANA, see the SAP HANA Security Guide, at http://help.sap.com/hana_appliance.




http://help.sap.com/saphelp_nw74/helpdata/en/39/fadbc91fba4dba858eefe232c78704/frameset.htm



SAP BusinessObjects Design Studio uses SAP BusinessObjects Business Intelligence as its content management system. For more information on security aspects when working with the BI platform, see “Securing BI Platform”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip.

7.9 General Security Recommendations

Virus scanner activation

As users upload analysis application files from SAP BusinessObjects Design Studio to the BI platform document repository, we recommend using a virus scanning application to protect your BI platform server. You should only allow your users to store the files in a specific folder in the BI platform. Configure a virus scan for this folder, using a virus scanning application installed on the same server as the BI platform. Whenever a file is added or modified in this folder, the virus scanner automatically scans the file.

If no virus scanning application is used, there is the risk of the server being contaminated by viruses contained in uploaded files. These viruses can be spread by users downloading the infected files.


Security


8 Language and Regional SettingsIn SAP BusinessObjects Design Studio, different text types are displayed in a single user interface. This applies to the design tool user interface and to the user interface texts in the executed analysis applications.

8.1 Language of the Design Tool Texts

The texts in the design tool user interface are available in English only.

8.2 Language of Master Data and Metadata

The texts of the data from the back-end systems (such as master data and metadata of the selected data source) are visible in the design tool's layout editor and in the executed analysis applications.

These texts are language-dependent and are displayed in the default language configured in the user settings in the back-end system (SAP HANA or SAP NetWeaver BW). If you define a language in the OLAP connection to the back-end system in the BI platform's Central Management Console (CMC), this language setting overrides the language from the user settings in the back-end system, and the language defined for the OLAP connection is used for all users using this connection.

With universe data sources, you can use multilingual universes. The language of the texts depends on the parameters set in the information design tool. For more information, see “Multilingual universes” under “Creating universes” in the Information Design Tool User Guide at http://help.sap.com/bobip.

8.3 Language of Message Texts and Tooltips in Analysis Applications

The language of message texts and tooltips is defined by the language setting (in the BI launch pad or the Web browser) based on the following rule:

● If you define a language in the BI launch pad under Preferences Locales and Time Zone Preferred Viewing Locale , this language is used.

● If you select Use browser locale under Preferences Locales and Time Zone Preferred Viewing Locale , the Web browser language is used.

Administrator Guide: SAP BusinessObjects Design StudioLanguage and Regional Settings © 2014 SAP SE or an SAP affiliate company. All rights reserved. 63


Preview of analysis applications

To preview the analysis applications in the required language, application designers can switch between these two settings in the Preferences dialog box in the SAP BusinessObjects Design Studio design tool. Under ToolsPreferences Application Design Application Preview , they can choose between the preferred viewing locale of the BI launch pad (BI Platform User Settings radio button) or the Web browser language (Web Browser radio button).

NoteThese language settings are not available in local mode in the design tool.

Related Information

Supported Languages [page 64]

8.3.1 Supported Languages

Message texts and tooltips in the executed analysis applications are available in the following languages:

Language value Description

deDE German

enUS English

esES Spanish

frFR French

jaJP Japanese

ptBR Portuguese

ruRU Russian

zhCN Chinese

iwIW Hebrew (Iwrit)

arAR Arabic

8.4 Regional Formats for Numbers, Dates and Times

The format for numbers, dates and times varies according to the defined language setting in the BI launch pad or the Web browser.


Language and Regional Settings

● If you define a language in the BI launch pad under Preferences Locales and Time Zone Preferred Viewing Locale , this language is used, and numbers, dates and times are displayed in the appropriate format.

● If you select Use browser locale under Preferences Locales and Time Zone Preferred Viewing Locale , the Web browser language is used, and numbers, dates and times are displayed in the appropriate format.

ExampleGerman formatting

If you select German as the preferred viewing locale in the BI launch pad, the following parts of the analysis application are affected:

● Message texts and tooltips are displayed in German● Numbers are displayed in format 11.111,111, for example 43.484,018.● Dates are displayed in format DD.MM.YYYY, for example 29.07.2012.● Times are displayed in format hh:mm, for example 10:30.

ExampleEnglish formatting

If you select English as the preferred viewing locale in the BI launch pad, the following parts of the analysis application are affected:

● Message texts and tooltips are displayed in English● Numbers are displayed in format 11,111.111, for example 43,484.018.● Dates are displayed in format MM/DD/YYYY, for example 07/29/2012.● Times are displayed in format hh:mm AM/PM, for example 10:30 AM.

Preview of analysis applications

To preview the analysis applications in the required language and appropriate formatting, application designers can switch between these two settings in the Preferences dialog box in the SAP BusinessObjects Design Studio design tool. Under Tools Preferences Application Design Application Preview , they can choose between the preferred viewing locale of the BI launch pad (BI Platform User Settings radio button) or the Web browser language (Web Browser radio button).

NoteThese language settings, which also affect the formatting, are not available in local mode in the design tool.


8.4.1 Formatting of Date and Time with SAP HANA Data Sources

With SAP HANA data sources, the presentation of dates and times works as follows:

Presentation of date and time data

SAP HANA supports date and time data only as characteristics, not as key figures. Unlike SAP NetWeaver BW, SAP HANA does not allow different formats of date and time characteristics.

Dates and times from SAP HANA data sources are always presented in the following way:

YYYY:MM:DD - for example 2012:07:29hh:mm:ss (with an hour range from 0 to 23) - for example 10:30:25

The selected language in the BI launch pad or the Web browser does not affect the presentation of date and time characteristics from SAP HANA data sources.

Relevance of the time zone setting

SAP NetWeaver BW only supports the data types DATE and TIME. Both are independent of time zones.

SAP HANA supports the data types DATE and TIME as well as a TIMESTAMP data type with implicit UTC time zone. The selected time zone in the BI launch pad (under Preferences Locales and Time Zone Current Time Zone ) does not affect the presentation of time characteristics from SAP HANA data sources. These are always presented as UTC times.

8.5 Business Case: Defining English as the Preferred Language of an Analysis Application

Context

To present an analysis application in one language for all text types, and the appropriate formats for dates, times and numbers, the different settings need to be defined consistently. If you want to present an analysis application in English, perform the following steps:


Language and Regional Settings

Procedure

1. Define English as the language in the OLAP connection to SAP NetWeaver BW.Master data and metadata, such as descriptions of characteristics and key figures, are displayed in English. These texts appear as column or row headers in a crosstab, or series and category names in a chart.

2. If you do not define a language in the OLAP connection, select English in the user settings in the BW system. Do this for all users who will receive this analysis application.

3. Select English as the preferred viewing locale in the BI launch pad.Message texts and tooltips are displayed in English. Numbers, dates and times are displayed according to English formatting conventions.

CautionIf you select Use browser locale as the preferred viewing locale, the Web browser language is used for these texts. Depending on the users' language setting in their Web browser, they might encounter inconsistent texts and formatting in the analysis application.


9 Lifecycle ManagementLifecycle of analysis applications, images and data source connections

Application designers create analysis applications that allow users to analyze business data from SAP NetWeaver BW and SAP HANA systems. Image resources and defined connections to SAP NetWeaver BW or SAP HANA systems are vital elements of analysis applications. The following sections provide an overview of the lifecycles of these objects and outline how application designers and administrators manage them.

Managing access rights

Administrators need to give application designers and application users the required access rights.

Transporting analysis applications, images and data source connections

To transport analysis applications, images and data source connections, administrators use the promotion management of the BI platform.

Related Information

Working with Analysis Applications [page 68]Working with Images [page 72]Working with Data Source Connections [page 73]Managing Access Rights [page 75]Transporting Analysis Applications, Images, Data Source Connections and Universes [page 75]

9.1 Working with Analysis Applications

Creating analysis applications

Application designers create analysis applications by choosing Application New... in the SAP BusinessObjects Design Studio design tool.


Lifecycle Management

Changing analysis applications

Application designers can change their analysis applications by choosing Application Open... in the design tool. As long as the design tool is running, application designers can undo or redo their changes. Once the design tool has been closed, it is not possible to return to previously saved states of an analysis application.

RestrictionSimultaneous modification of analysis applications by more than one application designer is not supported. If several application designers open the same application, change it and want to save it on SAP BusinessObjects BI only the one saving the application first can save his/her changes. All other application designers will receive a warning informing them that a newer version exists on the platform when saving the application. They can save their version as a copy (by choosing Application Save As... ). If they choose Application Save As... , thereby saving the application with the same name as the original application, they overwrite the version saved previously by their colleague, and the system does not inform this colleague.

CautionChanging analysis applications in a text editor and re-uploading them to the platform is not supported.

Deleting analysis applications

Application designers can delete their analysis applications by opening the application in the design tool and choosing Application Delete . The analysis applications are permanently deleted. They cannot be restored.

RestrictionIf several application designers open the same application simultaneously, and one of them deletes the application, the other designers do not receive a system notification. They only see a warning when trying to save the application. They can save the application by choosing Application Save As... . The system saves the application with a new CUID.

Uploading analysis applications

If application designers have created analysis applications in local mode in the design tool, they can upload these locally stored applications to SAP BusinessObjects BI by choosing Tools Upload Local Application... in the design tool.

The application designers also need to change the data source connections in the Properties view of the data sources in the design tool. Connections from local mode have to be replaced by data source connections of the platform.

Administrator Guide: SAP BusinessObjects Design StudioLifecycle Management © 2014 SAP SE or an SAP affiliate company. All rights reserved. 69

If images are included in these applications, the application designers need to upload these images to the platform as well. They then need to change the paths to the images in the Properties view of the Image components.

RestrictionUploading locally stored analysis applications to the BI platform as local files in the launch pad or Central Management Console is not supported.

Downloading analysis applications

Application designers can download analysis applications from SAP BusinessObjects BI to their PC by choosing Help Support Download... in the design tool. This function makes it possible to provide the original source

code of analysis applications to SAP, and helps us to resolve problems that you report to SAP in customer messages.

Moving analysis applications between folders

Application users can move analysis applications from one folder to another by choosing Cut in the context menu of an application and choosing Paste in the context menu of the target folder in the BI launch pad. Administrators can perform the same operation in the Central Management Console.

Copying analysis applications

Application users can copy analysis applications from one folder to another by choosing Copy in the context menu of an application and choosing Paste in the context menu of the target folder in the BI launch pad. Administrators can perform the same operation in the Central Management Console.

Executing analysis applications

Application users have the following options for running analysis applications:

● Application users run the applications by choosing Open in the context menu of an application, or by clicking the application in the BI launch pad. Each analysis application is displayed in a new tab in the BI launch pad. If you are using BI platform 4.0 and Internet Explorer as a Web browser, the analysis application is displayed in a new window.

● Application users can open an application directly without navigating in the BI launch pad. In the Documents tab in the BI launch pad, users can choose Document Link in the context menu of an application. The URL of the application is displayed. Users can copy this URL, send it in an e-mail and run the URL on their mobile device. If they want to add this URL to their bookmarks, they have to add it manually instead of pressing the corresponding button.



● Application users can open an application with SAP BusinessObjects Mobile client if the application is assigned to the mobile category (as described in Assigning Analysis Applications to the Mobile Category [page 37]). All applications assigned to this category are listed in a thumbnail grid. Users can launch an application by tapping on the application thumbnail. The analysis application is displayed in the mobile client application. For more information, see the User Guide: SAP BusinessObjects Mobile for iOS at http://help.sap.com/bomobileios

NoteThis is necessary because the original URL is immediately forwarded to a generic URL, keeping the application reference in the session. When bookmarking and opening this generic URL that lacks the application reference, the Web browser will show an error page only.

Application designers have the following additional options for running analysis applications:

● In the design tool, application designers can choose Application Execute Locally . The application is displayed in a separate Web browser window, using a local Web server embedded in the design tool.

● In the design tool, application designers can choose Application Execute on BI Platform . The application is displayed in a separate Web browser window, using the document link of the application and the current session of the BI platform. The application designer does not have to log on to the BI platform when executing the application on the BI platform. The analysis application is run with the credentials that the application designer provided when logging on to the design tool.

● In the design tool, application designers can click Send to Mobile Device (using QR Code®). Clicking the QR code causes a new Web browser window to open. The application designer may be prompted to log on to SAP BusinessObjects BI.

● In the design tool, application designers can click Send to Mobile Device (using QR Code®). To copy the document link to the clipboard they can press CTRL + C . They can paste the URL and send it in an e-mail, and execute the URL on their mobile device. If they want to add this URL to their bookmarks, they have to add it manually instead of pressing the corresponding button.

NoteThis is necessary because the original URL is immediately forwarded to a generic URL, keeping the application reference in the session. When bookmarking and opening this generic URL that lacks the application reference, the Web browser will show an error page only.

Related Information

Managing Access Rights [page 75]Transporting Analysis Applications, Images, Data Source Connections and Universes [page 75]




9.2 Working with Images

Creating images

In the design tool, application designers can upload images in the Properties view for the Image and Button components.

Administrators (or application designers) can upload images on the Documents tab in the BI launch pad by choosing New Local Document in the context menu for the folder, or in the Central Management Console by choosing Add Local Document in the context menu for the folder.

NoteIn the Central Management Console or the BI launch pad, make sure that you upload the image with a MIME type, for example image/gif or image/jpg. Otherwise the image will not be available in the design tool's Open Image dialog box.

Changing images

The content of an image cannot be changed. You need to delete the image and upload a new one.

NoteMake sure that you use the same name and location for the new image. Otherwise, the references to the images in the analysis applications will not work any more.

Deleting images

When deleting an image, make sure that it is not being used any more in analysis applications.

Related Information

Transporting Analysis Applications, Images, Data Source Connections and Universes [page 75]Managing Access Rights [page 75]



9.3 Working with Data Source Connections

Creating connections

Administrators create data source connections to SAP HANA or BW systems in the BI platform's Central Management Console.

NoteMake sure that the machine where the Adaptive Processing Server (APS) of the BI platform is installed can communicate with the connected BW systems. If the BW system uses a message server, this machine must specify the service name of the message server in the system's services file. In Microsoft Windows, the system's services file is located in %windir%\system32\drivers\etc\services. For more information on

the location of the system's services file in other operating systems, see SAP Note 52959 . Configure the system's services file on your APS machine accordingly.

Changing connections

Administrators can change data source connections in the BI platform's Central Management Console under OLAP Connections.

Deleting connections

When deleting a data source connection, make sure that the connection is not used any more in analysis applications. Connections are referenced in analysis applications by their CUID. The CUID is unique for each connection. Deleting the connection deletes the CUID as well.

CautionIf a connection that is still being used by an analysis application is deleted, the analysis application will not work anymore - even if you create a new connection to the same back end system with the same name and locate it in the same folder as the deleted connection. You have to change the connection assignment of the application to the new connection or use the promotion management tool to transport the original connection into this system again.

Moving connections between folders

If you move a connection to a new folder, the analysis applications using this connection will still work. However, if the connection access rights are inherited from the containing folder, you have to make sure that the application designers and the application users still have view rights for the connection.



Related Information

Creating and Managing Data Source Connections in SAP BusinessObjects Business Intelligence [page 24]Managing Access Rights [page 75]Transporting Analysis Applications, Images, Data Source Connections and Universes [page 75]

9.4 Working with Universes

Creating, changing, publishing and deleting universes

Administrators create or change universes (and the corresponding relational connections) using the information design tool (IDT) and publish them to the BI platform.

They can delete published universes in the information design tool or in the BI platform's Central Management Console under Universes. When deleting universes, make sure that the universe is no longer used in analysis applications. Universes are referenced in analysis applications by their CUID. The CUID is unique for each universe. Deleting the universe also deletes the CUID.

CautionIf a universe that is still being used by an analysis application is deleted, the analysis application will not work anymore, even if you create a new universe with the same name and locate it in the same folder as the deleted universe. You have to change the universe assignment of the application to the new universe or use the promotion management tool to transport the original universe into this system again.


Moving universes between folders

If you move a universe to a new folder, the analysis applications using this universe will still work. However, if universe access rights are inherited from their containing folder, you have to make sure that the application designers and the application users still have the View On Demand rights for the universe (and also for the corresponding relational connection used by this universe).

Related Information

Creating Universes for Use in Analysis Applications [page 28]




Adding View Rights for Universe Data Sources [page 33]

9.5 Managing Access Rights

Application designers need the following rights:

● View rights for executing analysis applications (and the embedded images)● Edit rights for modifying analysis applications● Add rights for folders (for creating analysis applications in these folders)● View rights for the image folder and all folders above this folder (in the folder hierarchy)● View rights for data source connections● View On Demand rights for universes and the corresponding relational connections

Application users need the following rights:

● View rights for executing analysis applications (and the embedded images)● Add rights for folders (for copying analysis applications and moving them between these folders)● View rights for the image folder and all folders above this folder (in the folder hierarchy)● View rights for data source connections● View On Demand rights for universes and the corresponding relational connections

SAP BusinessObjects Design Studio uses the BI platform authorization concept for content management of analysis applications, images and data source connections. For more information on configuring the authorizations for the folders containing these objects, see “Setting Rights”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip.

Related Information

Creating a User Group and Adding View Rights [page 32]Adding View Rights for Universe Data Sources [page 33]

9.6 Transporting Analysis Applications, Images, Data Source Connections and Universes

If you are running multiple BI platform instances in your system landscape (for development, testing and productive use, for example), you can transport objects from one instance to another. To transport analysis applications, images, universes and data source connections, use the promotion management of the BI platform. For more information, see “Promotion Management”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip.




When an analysis application is transported, the following related entities need to be considered:

● the analysis application● the OLAP connections defined in CMC● the universes with relational connections● the images used in the analysis application

When you transport analysis applications, the referenced OLAP connections, universes, relational connections and images are not automatically transported. These entities need to be added to the transport manually.

Make sure you perform the following actions:

Update data source connections

A data source connection has the fields Name, ID and CUID. The Name can be entered by the administrator, whereas the ID is issued by the system, and the CUID is constant, even after the connection has been transported.

If you use different BW or SAP HANA systems for testing and productive usage, you need to update the transported connections in the target BI platform instance, by entering the connection information for the associated BW or SAP HANA system. The constant CUID ensures that the connection is working properly after the transport. The transported analysis applications use the connection CUID to read the appropriate connection information, and SAP BusinessObjects Design Studio builds the connection to the target system or object.

NoteYou have to make sure that the BW entities used by the analysis applications (InfoProviders, queries, query views) are available in the BW system, which is accessed by the target BI platform system. With SAP HANA, the relevant SAP HANA data sources (analytic views, calculation views) must exist in the corresponding SAP HANA system.

Update universes

A universe and its relational connections have the fields Name, ID and CUID. The Name can be entered by the administrator, whereas the ID is issued by the system, and the CUID is constant, even after the universe has been transported.

For more information, see the Data Access Guide and the Information Design Tool User Guide at http://help.sap.com/bobip.

Making images available on the target BI platform

Images are referenced by their name and location in analysis applications. After transporting analysis applications to the target BI platform, you need to transport the referenced images to the same location on the target platform and keep the same names.





TipWe recommend using a common root folder for all images and icons used in analysis applications on all BI platform instances. This will make it simpler to transport analysis applications (and the referenced images or icons) between different BI platform systems.

NoteMake sure that the BI platform instances are installed with the same language. Otherwise it might not be possible to find certain folder names in the different instances.


10 Troubleshooting

This section provides information about troubleshooting options. For more information, see SAP Note 1773751 .

10.1 Upgrading the Design Tool Installation (Alternative Procedure)

Context

If you encounter problems when upgrading your design tool installation, you can perform an alternative procedure.

Procedure

1. Uninstall the design tool.

NoteCheck if the folder where the design tool installation files were located is now empty.

2. Install the new version of the design tool.

Related Information

Upgrading the Design Tool Installation [page 23]Uninstalling the Design Tool of SAP BusinessObjects Design Studio [page 21]Installing the Design Tool of SAP BusinessObjects Design Studio [page 18]


Troubleshooting


10.2 Setting Network Connections If Logon Problems Occur

Context

After installing or deinstalling SDK extensions and restarting the design tool, ou might not be able to log on to your BI platform. The Authentication dropdown box in the logon dialog box for the design tool is disabled.

This problem occurs when exceptions are specified with a "*" wildcard character in the proxy settings of Internet Explorer under Internet options Connections LAN settings Advanced Exceptions .

ExampleThe exceptions are defined as localhost;127.0.0.1;*.mycompany.com.

To communicate with the BI platform, Design Studio uses a third-party library, which can experience connectivity problems when "*" wildcard characters are used.

To solve this issue, proceed as follows:

Procedure

1. Start the design tool in local mode by pressing Skip in the logon dialog box.

2. Navigate to Tools Preferences Application Design Network Connections .3. Choose one of the following options:

○ Set the Active Provider to Direct. This disables proxies completely.○ Set the Active Provider to Manual and specify the proxy manually, omitting the problematic "*" entries.

4. Restart the design tool.

Results

This procedure only needs to be performed once.

For more information, see “Network Connection Preferences” in the online help. You can access this chapter by pressing F1 or the Help button in the Preferences dialog box.

Administrator Guide: SAP BusinessObjects Design StudioTroubleshooting © 2014 SAP SE or an SAP affiliate company. All rights reserved. 79

10.3 Activating Runtime Traces

Context

You can record traces to analyze problems in the design tool.

Procedure

1. In the design tool, choose Tools Preferences Application Design Support Settings .2. Select the Activate runtime trace checkbox.3. Click OK.

Results

The system will create a trace file on your local hard drive. The trace file is a text file that contains a log of the activities performed in the design tool's layout editor and in the executed analysis application. It is stored in the C:\<user>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\logs\RSTT folder.

The design tool also connects to the SAP NetWeaver BW system. This checks if the user requesting the trace has sufficient authorization to log traces (standard authorization object S_RS_RSTT). If this is the case, the SAP NetWeaver BW trace tool environment (transaction code RSTT in the connected BW system) is activated. In the BW system, a new trace containing your navigation steps will be created. For information on how to replay and maintain this trace, see “Trace Tool Environment ” in the SAP NetWeaver Library , at http://help.sap.com/netweaver.

The recorded traces help us to resolve problems that you report to SAP as customer messages.

10.4 Activating SAP JCo Traces

Context

You can record SAP JCo traces to analyze problems in the design tool.


Troubleshooting

http://help.sap.com/saphelp_nw74/helpdata/en/42/ed1942bcb35433e10000000a155106/content.htm?frameset=/en/89/71b01ce1f44e95a860a6c3f7dda911/frameset.htm

http://help.sap.com/saphelp_nw74/helpdata/en/42/ed1942bcb35433e10000000a155106/content.htm?frameset=/en/89/71b01ce1f44e95a860a6c3f7dda911/frameset.htm

Procedure

1. In the design tool, choose Tools Preferences Application Design Support Settings .2. Select the Activate SAP JCo Trace checkbox.3. Click OK.4. Restart the design tool to enable the SAP JCo trace.

Results

The SAP JCo trace is activated and the trace level is set to 8. You can collect all the SAP JCo trace files using the Collect Support Information function. The recorded traces help us to resolve problems that you report to SAP.

Related Information

Collecting Support Information [page 83]

10.5 Viewing And Collecting Statistics Data At Runtime

Context

If you encounter performance issues in your analysis applications, you can activate a runtime profiling function for your applications, which helps you to analyze the performance-critical processing steps.

Procedure

1. In the design tool, go to Tools Preferences Application Design Support Settings and choose Activate Runtime Profiling.

2. Execute the required analysis application either in local mode, or on your platform (SAP NetWeaver or BI platform).The system automatically adds the following parameter to the URL: PROFILING=X

You can also add this parameter to the URL manually without activating the runtime profiling setting in the Preferences dialog box.


3. In the analysis application, a Statistics dialog box appears, where you can view the following statistics data:

○ Under Java Statistics, you can view how much time is required to process each navigation step (and initial loading) on the server. This includes the processing time on the backend system (SAP NetWeaver BW or SAP HANA) and on the used platform (BI platform or SAP NetWeaver).

○ Under Rendering Statistics, you can view how much time is required to render the components of an analysis application in the Web browser for each navigation step (and initial loading).

4. After reproducing the performance-critical navigation steps in your analysis application, choose Refresh.All the relevant statistics data is downloaded and displayed.

5. To download the statistics data, choose Download as Csv or Download as Text.

Results

You can attach the recorded statistics data (*.csv or *.txt file) to customer messages that you send to SAP.

10.6 Downloading Analysis Applications

Context

Application designers can download analysis applications from the platform (SAP NetWeaver, SAP HANA or SAP BusinessObjects BI) to their PC. This function makes it possible to provide the original source code of analysis applications to SAP and helps us to resolve problems that you report to SAP as customer messages.

Procedure

1. Choose Help Support Download... in the design tool.2. In the Download Application dialog box, select the required analysis application.3. Click Download.4. In the Browse for Folder dialog box, select the required folder on your local PC.5. Click OK.

Results

You can attach the analysis application file to your customer message.


Troubleshooting

10.7 Collecting Support Information

Context

If you encounter problems in the design tool, you can collect the relevant information to send to SAP in a zip file.

Procedure

1. In the design tool, choose Help Support Collect Support Information... .2. Select the target folder for the zip file.3. Click OK.

The support information is saved in the file DS_Support.zip.

4. To view the content of the zip file, click View....5. Click OK.

Results

You can attach the zip file to a customer message and send it to SAP.

10.8 Problems with Connections

If your connection between the SAP BusinessObjects Design Studio design tool and the SAP NetWeaver BW system uses a message server, make sure that the message server port is set in the services file for the client PC (where the design tool is installed). The services file is located under <WINDOWS ROOT>\windows\system32\drivers\etc\services. If the services file does not contain the message server port, the system cannot connect to the BW system and the following error message appears: com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Connect to message server host failed.

In this case, we recommend installing the design tool on a client PC with SAP GUI installed. SAP GUI automatically provides the necessary information about the message server in the services file.


Related Information

Creating Connections to BI Back-End Systems in Local Mode [page 86]System Requirements for the Design Tool Installation [page 18]

10.9 Managing Logs in the Design Tool

Defining the Log Level

You can specify how much information is stored in the log file. Under Tools Preferences Support Settings , the following options are available :

● Warning: The system stores exceptions, error messages, and warnings in the log file. This is the default option.

● Error: The system stores exceptions and error messages in the log file.● Information: The system stores exceptions, error messages, warnings, and information messages in the log

file.● Debugging Information: The system stores exceptions, error messages, warnings, information messages and

debugging information in the log file.

Viewing Error Messages

You can view error messages in the design tool's Error Log view. To open this view, choose View Error Log .

Saving Error Messages

Press the Export Log button (in the upper right corner of the Error Log view) to save the error messages.

The exported error log files help us to resolve problems that you report to SAP in customer messages.

10.10 Managing Logs on the BI Platform

For logging and tracing, SAP BusinessObjects Design Studio uses the mechanisms of the BI platform.

For more information, see “Managing and Configuring Logs”, in the Business Intelligence Platform Administrator Guide, at http://help.sap.com/bobip.


Troubleshooting


11 Managing Local Mode in the Design ToolFrom local mode to full mode in SAP BusinessObjects Design Studio

When the SAP BusinessObjects Design Studio design tool starts after installation, it is launched in local mode in the default setting. You start by using local mode to create analysis applications for presenting and evaluating SAP BusinessObjects Design Studio with users at the customer's location. You can save the analysis applications on your local machine. In local mode, the technical prerequisites are minimal and the evaluation can be performed quickly and easily. The key users of a company - possibly together with consultants - investigate whether SAP BusinessObjects Design Studio can cover their company's analysis and reporting requirements. After a successful evaluation phase and the decision has been made to implement SAP BusinessObjects Design Studio, the requirements for the chosen platform need to be provided.

Once the platform infrastructure has been set up, application designers who have been working in local mode can easily switch the default startup mode in the Preferences dialog box and connect to the required platform. Application designers can then upload their locally saved analysis applications to the platform. For more information, see “Working with the Local Mode of the Design Tool”, in the Application Designer Guide: Designing Analysis Applications , under Help Help Contents in the design tool.

RestrictionLocal mode in the design tool was not designed with offline use of the design tool in mind. You should not use it for downloading analysis applications from the platform, changing and saving them locally, and uploading the applications again to the platform.

Different administration tasks for local mode

This section provides information on differences you may encounter when installing and configuring SAP BusinessObjects Design Studio in local mode. Administration tasks that are similar to SAP BusinessObjects Design Studio when connected to a platform are not listed separately in this section. The relevant information is contained in the sections above.

Related Information

Maintaining Settings in the Design Tool in Local Mode [page 88]

11.1 Installation

To use SAP BusinessObjects Design Studio in local mode, you need to install the SAP BusinessObjects Design Studio design tool. Depending on the back end systems you want to use, you may also need to install SAP GUI or SAP HANA Database Client (in addition to the design tool).

Administrator Guide: SAP BusinessObjects Design StudioManaging Local Mode in the Design Tool © 2014 SAP SE or an SAP affiliate company. All rights reserved. 85

● Before you configure SAP NetWeaver BW connections, you need to install SAP GUI for Windows. This is required to run SAP logon and add SAP NetWeaver BW data sources.

NoteIf the saplogon.ini file is stored in a virtual SAP GUI application, for example, and not on your PC, then Design Studio cannot find the file or display SAP NetWeaver BW connections in the design tool. In this case, you can specify the location of the saplogon.ini file by adding the following lines to the SAPDesignStudio.ini file:

-aadSaplogoniniPath

<path to your ini file copy>

Add these lines directly before the -vmargs line. Note that there must be a line break separating the argument from its value.

If the path points to a folder, the file name in this folder must be saplogon.ini. The path can also point directly to a file. In this case, you can choose any file name.

● Before you configure SAP HANA connections, you need to install the SAP HANA Database Client. This is required to use the ODBC Data Source Administrator and add SAP HANA data sources.For more information, see the SAP HANA Database - Client Installation and Update Guide at http://help.sap.com/hana_appliance.

Related Information

Installing the Design Tool of SAP BusinessObjects Design Studio [page 18]

11.2 Configuration

11.2.1 Creating Connections to BI Back-End Systems in Local Mode

Context

Before designers can add data sources to their analysis applications, you have to create connections to the BI back-end systems containing the business data. SAP BusinessObjects Design Studio can access SAP HANA systems or SAP NetWeaver BW systems as BI back-end systems.

NoteIf you have already added SAP NetWeaver BW systems in the SAP Logon dialog box, these systems are automatically available in the design tool.


Managing Local Mode in the Design Tool



Procedure

1. Open the design tool and choose Tools Preferences Application Design Backend Connections .2. Decide whether you want to create a SAP NetWeaver BW connection or a SAP HANA connection.

○ For SAP NetWeaver BW connections, click Launch SAP Logon in the upper right corner of the Connections maintained in SAP Logon area.

1. In the SAP Logon dialog box, click New .2. Add the required system parameters.

○ For SAP HANA connections, click ODBC Data Source Administrator in the upper right corner of the SAP HANA Connections maintained in ODBC Data Source Administrator area.

1. Press Add....2. Select the driver HDBODBC32.

NoteThis driver is only available if the SAP HANA Database Client (32-bit) is installed on your local machine.

3. If the SAP HANA Database Client (64-bit) is installed on your machine, select the driver HDBODBC.4. Press Finish.5. Enter the SAP HANA system in the Data Source Name field.6. Enter the corresponding server and port in the Server:Port field.7. Press OK. Then press OK again.

3. To display new connections in the corresponding table, click Reload All Connections.4. To close the dialog box, press OK.

Results

The new connections are listed in the Select Connection dialog box, which appears when you browse for a connection in the Add Data Source dialog box. For more information, see the Application Designer Guide: Designing Analysis Applications under Help Help Contents in the design tool.


11.2.2 Switching User for BI Back-End System

Context

In local mode, you can log off from the BI back-end system you have been working with (using the Preferences dialog box). This allows you to log on with a different user (for example, a user with different authorizations) to this BW or SAP HANA system and proceed with your work without restarting the design tool.

Procedure

1. In the design tool in local mode, choose Tools Preferences Application Design Backend Connections .

2. Press Clear Cached Logon Credentials....3. In the Clear Cached Credentials dialog box, select the connections from which you want to log off.4. Click OK.5. To close the Preferences dialog box, click OK.

Next Steps

NoteAlternatively, you can open the Clear Cached Credentials dialog box by pressing Ctrl+Shift+Del in the design tool, without opening the Preferences dialog box. You must be logged on to at least one BI back-end system, otherwise the Clear Cached Credentials dialog box will not open.

11.2.3 Maintaining Settings in the Design Tool in Local Mode

You can define settings for the design tool in the Preferences dialog box. To start the Preferences dialog box, choose Tools Preferences Application Design .

Change the default values as required and choose Apply to make these values effective. If you want to reset the default values, choose Restore Defaults. To close the Preferences dialog box, press OK.



General

You can switch the startup mode. In the default setting, the design tool starts in local mode after installation. If you want to use SAP BusinessObjects Design Studio integrated into one of the supported platforms, select the required platform:

● SAP BusinessObjects BI Platform● SAP HANA● SAP NetWeaver

After restarting the design tool, you need to log on to the selected platform.

NoteIn the Logon to <selected platform> dialog box, you can still decide to log on locally by clicking Skip, even if the startup mode is set to one of the supported platforms. The design tool starts in local mode.

In the Undo History Size field, you can change the default value 50 and enter a number between 20 and 999. This value defines how often application designers can undo their changes when working in the design tool.

Embedded Web Server

You can define the network port for the embedded Web server of the design tool. Enter a number between 1024 and 65535. When an application is executed, the port number is shown in the URL. If the port is set to 5555 for example, the URL is http://localhost:5555/aad/web.do?APPLICATION=MYAPP. If you leave the default value 0, the system automatically assigns a network port.

TipIf users create bookmarks for their applications, the network port has to be set to a fixed number. Auto-assigning the network port does not guarantee that the bookmarks will work properly.

If you want to test your application on a mobile device, you need to allow external access to the embedded Web server. Select the Allow external access to embedded Web server checkbox. The design tool must be running on your PC.

CautionNote that allowing external access is a security risk. Everyone connected to the same network can potentially access all of your applications and can see the same data that you can (as the applied data authorizations are the same).

RestrictionBefore other users can open the analysis application on a mobile device, the Logon to <BW or SAP HANA system> dialog box always appears on the PC with the design tool that is running.

● SAP HANA data sources used in the analysis application: the application designer of the PC that the design tool is running on has to enter his/her credentials and click Log on in the Logon to <SAP HANA system> dialog box.


● BW data sources used in the analysis application: activate Single-Sign On. The application designer of the PC that the design tool is running on has to confirm the client and language (or has to change these entries if required) and then click Log on in the Logon to <BW system> dialog box.

Application Recovery

In the default setting, the system automatically saves unsaved applications every minute. You can configure the auto-save time interval as required. Select the Save application recovery information every <1> minute checkbox and enter the required number for the auto-save time interval.

TipThe design tool needs to be restarted for the new interval to become active.

There is a background job that searches for unsaved applications in the given interval. If unsaved applications are found, the system extracts their XML code and stores it under <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen. The content of this file is encrypted using Eclipse secure store technology.

NoteThe auto-save function does not replace saving an application. Saving an application or closing it and answering the Save changes? question with either Yes or No will delete the XML from the autosaves file.

In the event of a system crash, the auto-saved XML persists. When restarting the design tool and opening the affected application again, the designer is informed that an auto-saved version of the application exists.

● If the designer decides to restore the auto-saved version, the system uses the stored XML, saves the application and opens the application in the layout editor. The auto-saved XML is removed.

● If the designer decides to discard the auto-saved version, the auto-saved XML is removed as well.

Member Selection

Application designers need to pick single members of a dimension when using statements like setFilter for a dropdown box, for example. They can pick the members in the content assistance of the Script Editor dialog box or in the Select Member dialog box. The Select Member dialog box can list a small or large number of members, depending on the maximum threshold number of members. You can set the default threshold in the Preferences dialog box.

● You can define the maximum number of members that are displayed in the Select Member dialog box. Enter the required number in the Maximum number of members to fetch from backend in dialog checkbox. The default threshold is 1000.

● You can define the maximum number of members that are displayed in the content assistance of the Script Editor dialog box. Enter the required number in the Maximum number of members to fetch from backend in content assistance checkbox. The default threshold is 20. If the number of available members exceeds this



threshold number, the content assistance does not list single members. Instead it offers the Select Member... entry, which opens the Select Member dialog box.

TipDesigners can access the content assistance in the script editor by pressing CTRL + SPACE .

● You can also decide whether the system should display warnings in the script editor whenever designers manually enter non-existent values. To activate the warnings, select the Display warnings for manually entered invalid values checkbox.

Prompt Handling

In the Prompts dialog box, application designers and application users set values for prompts. For SAP NetWeaver BW data sources, prompts are defined as variables. When working with data sources with defined variables, application designers might be prompted to set the required values before continuing their work in the design tool (if there are mandatory variables without default values, or if variables have invalid default values, for example).SAP BusinessObjects Design Studio stores all valid prompt values of each analysis application in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. This provides application designers with a smooth workflow in the design tool. If this was not the case, the Prompts dialog would appear an analysis application is reloaded, or when the initial state of the data source is modified in the Initial View dialog box, for example.

In the Preferences dialog box, you can specify whether the Prompts dialog box appears when an analysis application is executed locally:

● If you want to simulate how an application user opens the analysis application, leave the checkbox deselected (This is the default setting). When you execute an analysis application locally, the Prompts dialog box appears and you can set the prompt values like an end user would do.

● If you want to use the prompt values from the cache file, select the Use cached prompt values for local execution checkbox. The Prompts dialog box does not appear and application designers can test their analysis applications quickly.

NoteIf the Prompts dialog box appears despite this setting, check if the Force Prompts On Startup property of the analysis application is set to true. This property forces the Prompts dialog box to appear, regardless of your choice for the Use cached prompt values for local execution checkbox.

If you want to clear the prompt values of an analysis application in the cache file, press Clear Prompt Value Cache.... You can select the required analysis application(s) for this cache deletion. When the application is reloaded, the Prompts dialog box will appear and you can set new values, for example.

Paths

SAP BusinessObjects Design Studio includes a set of templates that offer designers an easy way to get started. When creating new applications, designers can choose between different templates that are optimized for


desktop Web browser applications or mobile applications in the New Application dialog box ( ApplicationNew... ). For more information, see “Creating a new analysis application” in the Application Designer Guide: Designing Analysis Applications under Help Help Contents in the design tool.

In the Preferences dialog box, you see the default path to the folder where these templates are stored. You can change the path by clicking the Browse... button.

Network Connections

Under Tools Preferences Application Design Network Connections , you can specify the proxy settings to be used when opening connections. For more information, see “Network Connection Preferences” in the online help. You can access this chapter by pressing F1 or the Help button in the Preferences dialog box.

Support Settings

Under Tools Preferences Application Design Support Settings , you can specify the amount of information stored in a log file and activate functions to record traces or collect statistics data.

Related Information

Activating Runtime Traces [page 80]Activating SAP JCo Traces [page 80]

Viewing And Collecting Statistics Data At Runtime [page 81]

11.3 Security

11.3.1 Technical System Landscape in Local Mode

The following graphic shows the system landscape for SAP BusinessObjects Design Studio used in local mode:



Related Information

Network and Communication Security in Local Mode [page 95]

11.3.2 User Management and Authentication in Local Mode

You have to configure user accounts in the following systems:

● Connected SAP NetWeaver BW systemsFor more information, see “Identity Management”, in the SAP NetWeaver Library , at http://help.sap.com/netweaver.

● Connected SAP HANA systemsFor more information, see “SAP HANA User and Role Management”, in the SAP HANA Security Guide , at http://help.sap.com/hana_appliance.

11.3.3 Authentication and Single Sign-On in Local Mode

Single Sign-On when using SAP NetWeaver BW data sources

Single Sign-On works if the following conditions are met:

● Secure Network Communications (SNC) is installed on each client PC. For more information, see “Secure Network Communications (SNC)”, in the SAP NetWeaver Security Guide , at http://help.sap.com/netweaver.

● Each user (application designer or application user) has a user account in the connected SAP NetWeaver BW system. For more information, see “Identity Management”, in the SAP NetWeaver Library, at http://help.sap.com/netweaver.

● You have selected the Activate Secure Network Communication checkbox for the relevant SAP NetWeaver BW system connection in the SAP Logon dialog box.





http://help.sap.com/saphelp_nw74/helpdata/en/aa/38ff4fa187622fe10000000a44176d/content.htm?frameset=/en/f3/780118b9cd48c7a668c60c3f8c4030/frameset.htm



Users sign on once to the client-based Secure Network Communications (SNC) with their credentials.

When inserting a BW data source in the design tool, application designers can connect to the BW systems without having to enter their BW user name and password in the Logon to <BW system> dialog box . They can change the client and the language of the BW system in this dialog box however.

When analyzing BW data in analysis applications, application users can connect to the BW systems without having to enter their BW user name and password.

RestrictionWhen you use external access to enable other users to view your analysis applications, on an iPad or an iPhone for example (click the Allow external access to embedded Web server checkbox in the Preferences dialog box), Single Sign-On activated for your BW data sources does not work as expected. The application designer for the PC where the design tool is running has to confirm client and language (or change these entries if required) and click Log on in the Logon to <BW system> dialog box. This must happen before other users open the analysis application on an iPad or on an iPhone. Due to technical restrictions, the Logon to <BW system> dialog box always appears on the PC where the design tool is running.

Single Sign-On when using SAP HANA data sources

Single Sign-On is currently not supported for SAP HANA system connections.

Application designers have to enter their user credentials in the Logon to <SAP HANA system> dialog box when inserting a SAP HANA data source in the design tool.

Application users have to enter their user credentials when analyzing SAP HANA data in analysis applications.

RestrictionWhen you use external access to enable other users to view your analysis applications, on an iPad or an iPhone for example (click the Allow external access to embedded Web server checkbox in the Preferences dialog box), the application designer for the PC where the design tool is running has to enter his/her credentials and click Log on in the Logon to <SAP HANA system> dialog box. This must happen before other users open the analysis application on an iPad or on an iPhone.

11.3.4 Authorizations When Using Local Mode

For security reasons, make sure that users do not have administrator rights on client PCs. Otherwise, users could access other user's analysis applications or trace files.

For data access management, SAP BusinessObjects Design Studio uses the authorization concept of the corresponding back-end system.

● With SAP NetWeaver BW, users need analysis authorizations to view the data of authorization-relevant characteristics in a query or in a query view that is used as a data source in an analysis application. For more information, see “Authorizations” in the SAP NetWeaver Library at http://help.sap.com/netweaver.



http://help.sap.com/saphelp_nw74/helpdata/en/4a/4ce95baef40451e10000000a421937/content.htm?frameset=/en/c5/f1c99abdd3fb4aa7febe103b5d77e5/frameset.htm

● With SAP HANA, users need analytic privileges to view the data of the SAP HANA data sources (Analytic Views or Calculation Views) that are used in an analysis application. For more information, see “Analytic Privileges”, under “SAP HANA Authorization”, in the SAP HANA Security Guide, at http://help.sap.com/hana_appliance.

11.3.5 Network and Communication Security in Local Mode

Your network infrastructure is extremely important for protecting your system. Your network needs to support the communication required for your business needs without allowing unauthorized access.

The following diagram illustrates the components involved and provides an overview of the communication channels when using SAP BusinessObjects Design Studio in local mode:

Figure 3: Components at design time

The following components are involved:

● The Web browser and the design tool on the application designer's local computer● The storage tier with the BI back-end systems (SAP NetWeaver BW or SAP HANA)

The communication process is as follows:

The application designer creates a new application or opens an existing one. The embedded Web browser in the layout editor of the design tool opens. It connects with the embedded Web server of the design tool. This communication is performed using HTTP as the protocol.




If the application designer chooses Application Execute Locally , the same communication process applies as described above. The only difference is that the analysis application is displayed in a separate Web browser window outside the design tool.

Each time the application designer inserts BW data into the application (by adding a new data source or selecting members in the script editor for example), the design tool on the client PC requests data from the BW server. This communication is performed using a synchronous JCo Remote Function Call (RFC) connection. You can protect this RFC connection using Secure Network Communications (SNC). For more information, see “Transport Layer Security”, in the SAP NetWeaver Security Guide , at http://help.sap.com/netweaver.

Every time the application designer inserts SAP HANA data into the application, the design tool on the client PC requests data from the SAP HANA server. This communication is performed using a Java Database Connectivity (JDBC) connection. You can protect this connection using the Secure Sockets Layer (SSL) protocol. For more information, see “Securing Data Communication”, in the SAP HANA Security Guide, at http://help.sap.com/hana_appliance .

11.3.6 Data Storage Security in Local Mode

Analysis applications

Application designers store the analysis application files in the <user home directory>\Analysis-workspace\com.sap.ip.bi.zen\repository folder. They can also store the images and icons that they use in their analysis applications in this folder, in a subfolder of this directory, or on the Internet/intranet.

You can restrict access to the analysis application files by assigning access rights. To ensure that the locally stored analysis applications cannot be viewed by non-authorized users, we advise against giving users administrator rights on client PCs.

CautionNote that allowing external access to the embedded Web server of the design tool (in the Preferences dialog box under Tools Preferences Application Design Embedded Web Server ) is a security risk. Everyone connected to the same network can potentially access all of this user's applications and can see the same data as this user (since the assigned data authorizations are the same).

Analysis applications history

The analysis applications history in the Application menu is persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.



http://help.sap.com/saphelp_nw74/helpdata/en/5f/0f558b8a7841049139f0fb558ac62c/content.htm?frameset=/en/f3/780118b9cd48c7a668c60c3f8c4030/frameset.htm



Data source history

The data source history in the Add Data Source dialog box is persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.

Prompt values

All valid prompt values of each analysis application are persisted in the user's cache file in <user home directory>\Analysis-workspace\.metadata\.plugins\com.sap.ip.bi.zen\cache. The content of this file is encrypted using Eclipse secure store technology.

Related Information

Data Access Security in Local Mode [page 97]

11.3.7 Data Access Security in Local Mode

Allowing external access to the embedded Web server of the design tool is a security risk. You can activate external access in local mode in the Preferences dialog box, under Tools Preferences Application DesignEmbedded Web Server .

When this function is activated, and the design tool is running, everyone connected to the same network can potentially access all of this user's applications (using the application launch URL, which is displayed in the Web browser when you execute the application).

The applied data authorizations for external access are the same as for the user that you specified in the back-end connections. Everyone can therefore see the same data that this user can.

NoteNote that this does not just apply to applications that are currently running. It affects all applications that the user has created in his/her workspace.

11.4 Language and Regional Settings in Local Mode

The following chapter describes settings that are different in local mode.


Language of master data and metadata

Texts for data from the back-end systems, such as master data and metadata of the selected data source, are visible in the design tool's layout editor and in the analysis applications that are running. These texts are language-dependent and are displayed in the language specified for the back-end system.

Application designers can specify the language of the back-end system when adding a data source to an analysis application. After selecting the required system in the Select Connection dialog box, application designers can enter the required language in the logon dialog box. If the application designer does not enter a language value in the logon dialog box, the data texts are displayed in English.

Language of message texts in analysis applications

The language of message texts and tooltips is defined by the language setting in the Web browser.

Regional formats for numbers, dates and times

The format for numbers, dates and times varies according to the defined language setting in the Web browser.

11.4.1 Supported Languages

Message texts and tooltips in the executed analysis applications are available in the following languages:

Language value Description

deDE German

enUS English

esES Spanish

frFR French

jaJP Japanese

ptBR Portuguese

ruRU Russian

zhCN Chinese

iwIW Hebrew (Iwrit)

arAR Arabic



11.5 Troubleshooting

11.5.1 Collecting Support Information in Local Mode

Context

If you encounter problems in the design tool, you can collect the relevant information to send to SAP in a zip file.

Procedure

1. In the design tool, choose Help Support Collect Support Information... .2. Select the target folder for the zip file.3. Click OK.4. Choose the analysis applications you want to add.5. Click Package.

The support information is saved in the file DS_Support.zip.

6. To view the content of the zip file, click View....7. Click OK.

Results

You can attach the zip file to a customer message and send it to SAP.


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/

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