ds_15_admin_nw_en

SAP BusinessObjects Design StudioDocument Version: 1.5 2015-05-27

Administrator Guide: SAP BusinessObjects Design Studiobased on SAP NetWeaver

Content

1 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. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.1 What is SAP BusinessObjects Design Studio?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92.2 Key Components of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

3 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Requirements for SAP NetWeaver BW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 Deployment on the SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

System Requirements for the Deployment of SAP BusinessObjects Design Studio on the SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installing SAP BusinessObjects Design Studio on SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . 12Connecting the Design Tool to SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.3 Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14System Requirements for the Design Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Installing the Design Tool of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . 15Installing the Design Tool from an Installation Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Uninstalling the Design Tool of SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . . . .17

4 Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.1 Upgrading the Deployment on the SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184.2 Upgrading the Design Tool Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

5 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205.1 Administration Tasks for Planning Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205.2 Activating the Query Runtime Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215.3 Setting RSADMIN Parameters for Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225.4 Configuring the Portal for Displaying Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235.5 Creating iViews Based on the Design Studio Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245.6 Setting Permissions for Analysis Application iViews. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255.7 Configuring Permissions for Using SDK Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .265.8 Configuring the Report-Report Interface for Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.9 Using Open Document URL iViews in SAP NetWeaver Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295.10 Configuring the Portal for Mobile Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .295.11 Maintaining Settings in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

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

Content

5.12 Sizing Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.13 More Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

6 Operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366.1 Deploying SDK Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Installing Design Studio SDK Extensions to SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . 36Installing CVOM Chart Extensions for SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . 37Removing Extensions from SAP BusinessObjects Design Studio. . . . . . . . . . . . . . . . . . . . . . . . . . .38Deploying Extensions to SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Removing Extensions from SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

6.2 Uploading Images to the MIME Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .406.3 Uploading Template Files to the MIME Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447.1 Technical System Landscape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447.2 User Management and Authentication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .447.3 Authentication and Single Sign-On. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.4 Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.5 Network and Communication Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Communication at Design Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Communication at Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

7.6 Data Storage Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507.7 Auditing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517.8 Security for Additional Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

8 Language and Regional Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.1 Language of the Design Tool Texts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538.2 Language of Master Data and Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .538.3 Language of Message Texts and Tooltips in Analysis Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .548.4 Translatable Texts in Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Working With Translatable Texts in Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

9 Lifecycle Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .579.1 Working with Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579.2 Working with Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.3 Managing Access Rights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609.4 Transporting Analysis Applications and SDK Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629.5 Transporting Images. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

10 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6410.1 Upgrading the Design Tool Installation (Alternative Procedure). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6410.2 Problems with the iView Layout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Administrator Guide: SAP BusinessObjects Design StudioContent 2015 SAP SE or an SAP affiliate company. All rights reserved. 3

10.3 Activating Runtime Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6510.4 Activating SAP JCo Traces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.5 Viewing And Collecting Statistics Data At Runtime. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6610.6 Collecting Support Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6710.7 Managing Logs in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6810.8 Managing Logs in SAP NetWeaver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

11 Managing Local Mode in the Design Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7011.1 Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7111.2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Creating Connections to BI Back-End Systems in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Switching User for BI Back-End System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Configuring the Report-Report Interface for Analysis Applications in Local Mode. . . . . . . . . . . . . . . 74Configuring the Number of Sessions for Parallel Query Execution in Local Mode. . . . . . . . . . . . . . . .75Maintaining Settings in the Design Tool in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

11.3 Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Technical System Landscape in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80User Management and Authentication in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Authentication and Single Sign-On in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Authorizations When Using Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Network and Communication Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Data Storage Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Data Access Security in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

11.4 Language and Regional Settings in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Supported Languages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86Coordinating the Translation of Translatable Texts in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . 86

11.5 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Collecting Support Information in Local Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Troubleshooting for SAP HANA HTTP Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88


Content

1 About This Guide

1.1 About the Documentation SetThe 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 2015 SAP SE or an SAP affiliate company. All rights reserved. 5

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, and on the connected SAP NetWeaver Business Warehouse system. You also need administrator rights on SAP NetWeaver Portal.

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/nw74 :Related Guide Location

Security Guide for SAP NetWeaver BW Security Information SAP NetWeaver Security GuideSecurity 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 GuideNetwork and Communication Security

SAP NetWeaver Library , chapter Identity Management Application Help SAP NetWeaver Library: Function-Oriented View Security Identity Management


About This Guide

Related Guide Location

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

SAP NetWeaver Library , chapter Unified Framework Page Application Help SAP NetWeaver Library: Function-Oriented View Portal Managing the Portal System Administration Configuring the Display of Portal ContentCreating and Editing a Framework Page Understanding Framework Pages

SAP NetWeaver Library , chapter Creating iViews Application Help SAP NetWeaver Library: Function-Oriented View Enterprise Portal Portal Managing the Portal Content Administration Creating and Editing iViews

SAP NetWeaver Library , chapter Adding Content to a Page Application Help SAP NetWeaver Library: Function-Oriented View Portal Managing the Portal Content Administration Creating and Editing Portal Pages

Chapter User Management and chapter Integration Into Single Sign-On Environments in the Portal Security Guide

Security Information SAP NetWeaver Security GuideSecurity Guides for SAP NetWeaver Functional UnitsSecurity Guides for Enterprise Portal (EP) and EP Core - Application Portal (EPC) Portal Security Guide User Administration and Authentication

SAP NetWeaver Library , chapter Portal Permissions Application Help SAP NetWeaver Library: Function-Oriented View Enterprise Portal Portal Managing the Portal System Administration

SAP NetWeaver Library , chapter Editing User Defaults and Options

Application Help SAP NetWeaver Library: Function-Oriented View Security Identity Management User and Role Administration of Application Server ABAPAdministration of Users and Roles User Administration

SAP NetWeaver Library , chapter Adding Language-Specific URLs

Application Help SAP NetWeaver Library: Function-Oriented View Enterprise Portal Portal Managing the Portal Content Administration Creating and Editing iViews Creating iViews Creating Web-Based URL iViews

URL iView Editor Selecting the Source URLSAP NetWeaver Library , chapter Setting Up Standard Authorizations in the Business Warehouse section

Application Help SAP NetWeaver Library: Function-Oriented View Business Warehouse Data Warehousing

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

Related Guide Location

Data Warehouse Management Authorizations Standard Authorizations

SAP NetWeaver Library , chapter Transporting BW Objects in the Business Warehouse section

Application Help SAP NetWeaver Library: Function-Oriented View Business Warehouse Generic Tools and Services Transporting BW Objects, and Creating, Delivering and Copying BI Content

SAP NetWeaver Library , chapter Log Viewer SAP NetWeaver System Administration and Maintenance Information Technical Operations for SAP NetWeaver Administering Application Server JavaMonitoring Monitoring and Displaying Log Files Log Viewing

SAP NetWeaver Library, chapter Setting Permissions in the Permission Editor

Application Help SAP NetWeaver Library: Function-Oriented View Enterprise Portal Portal Managing the Portal System Administration Portal PermissionsUsing the Permission Editor

SAP NetWeaver Security Guide, chapter Auditing and Logging

Security Information SAP NetWeaver Security GuideSecurity Aspects for Lifecycle Management

SAP NetWeaver Library , chapter Analysis of Statistics Data in the Business Warehouse section

Application Help SAP NetWeaver Library: Function-Oriented View Business Warehouse Generic Tools and Services BW Statistics BEx Query Runtime Statistics

SAP NetWeaver Library , chapter Maintenance of Statistics Properties in the Business Warehouse section

Application Help SAP NetWeaver Library: Function-Oriented View Business Warehouse Generic Tools and Services BW Statistics BEx Query Runtime Statistics

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 .


About This Guide

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 SAP 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 SAP 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.A Real-Time package, also available with SAP BusinessObjects Design Studio, allows application designers to create visualizations with streaming data (push based), and to create visualizations, which have a near Real-Time connection to SAP HANA or SAP BW (pull based). Real-Time dashboards apply in the area of operational systems, where data may only be relevant as it occurs and where it may not be neccessary to persist the data - for example, utility companies monitoring smart buildings and the financial capital markets.In addition to the standard palette of components in SAP BusinessObjects 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. Besides SDK components that visualize data from a data source, you can also create SDK components that act as data sources for SDK components themselves. This enables SDK components to access a broad range of data sources such as local files, Web services, or new types of backend system. 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 70]

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

2.2 Key Components of SAP BusinessObjects Design StudioThis section provides an overview of the software components and supporting systems used by SAP BusinessObjects Design Studio:Component Relevance

Design tool of SAP BusinessObjects Design Studio Tool for creating analysis applications.SAP NetWeaver Business Warehouse Used as a repository to store analysis applications and

images, and also as a back-end system, providing the business data for data analysis in analysis applications.

SAP NetWeaver Portal Used to access analysis applications and organize them to suit the users' preferences.


Getting Started

3 Installation

SAP BusinessObjects Design Studio consists of the following installable components:Component Description

Deployment of SAP BusinessObjects Design Studio on SAP NetWeaver Portal

SCA file that must be deployed on the SAP NetWeaver Portal. This deployment makes it possible to display and execute analysis applications in SAP NetWeaver Portal.

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 Requirements for SAP NetWeaver BWIf you are using SAP NetWeaver as your platform, you can only connect to one SAP NetWeaver BW system. Application designers can only add data sources to their analysis applications from one BW system.

TipIf you need more than one BW system, we recommend using SAP BusinessObjects Business Intelligence as the platform for SAP BusinessObjects Design Studio. For more information, see the Administrator Guide: SAP BusinessObjects Design Studio based on SAP BusinessObjects BI platform on SAP Help Portal at http://help.sap.com/boad.

You need to apply SAP Note 1811747 . This describes the required SAP NetWeaver support packages and manual steps for integrating analysis applications into the BW system. In the design tool, application designers can then save, delete and load analysis applications from the connected BW system.

3.2 Deployment on the SAP NetWeaver Portal

3.2.1 System Requirements for the Deployment of SAP BusinessObjects Design Studio on the SAP NetWeaver Portal

Before deploying SAP BusinessObjects Design Studio on SAP NetWeaver Portal, make sure that the following prerequisites are met: SAP NetWeaver is installed with the BI Java or Enterprise Portal Core usage type

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

If the BI Java usage type is installed, you need to activate it and perform the wizard-based configuration for this usage type. For more information, see Automatically Configuring BI Java on SAP Help Portal at http://help.sap.com/netweaver.

NoteIf you are using SAP Business Explorer Web, BI Java is already configured and you do not need to configure it for SAP BusinessObjects Design Studio again.

If the Enterprise Portal Core usage type is installed, you need to perform the manual configuration steps described under Manual Configuration in Automatically Configuring BI Java on SAP Help Portal at http://help.sap.com/netweaver.

SAP GUI is installed on the local machines of your application designers.This is required to run SAP logon and add the SAP NetWeaver BW system.

For more information about the supported SAP NetWeaver releases, see the Product Availability Matrix (PAM) on SAP Support Portal at http://support.sap.com/pam . Here you can enter SBOP DESIGN STUDIO in the search field to retrieve the information.

Related Information

Configuring the Portal for Displaying Analysis Applications [page 23]

3.2.2 Installing SAP BusinessObjects Design Studio on SAP NetWeaver Portal

Context

You need to download the DESIGNSTUDIONW.sca file from SAP Support Portal and deploy it on SAP NetWeaver Portal using the Software Update Manager (SUM).

Procedure

1. Go to the SAP Software Download Center on SAP Support Portal at http://support.sap.com/swdc and choose Installations and Upgrades.

NoteSupport packages and patches are available under Support Packages and Patches.

2. In the A - Z Index, click D.The SAP NetWeaver add-on installation is available for download at SBOP DESIGN STUDIO 1.5.


Installation

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

For more information, see SAP Note 2133992 .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_NW_, you can view the DESIGNSTUDIONW.sca file.7. Deploy the DESIGNSTUDIONW.sca file to SAP NetWeaver Portal using the Software

Update Manager (SUM).

You can download SUM from http://support.sap.com/swdc Support Packages and Patches A Z Index S SL Toolset SL Toolset Entry by Component Software Update Manager (SUM)For more information about the Software Update Manager, see http://service.sap.com/sltoolset

Software Logistics Toolset System Maintenance Updating SAP Systems Using Software Update Manager .

3.2.3 Connecting the Design Tool to SAP NetWeaverPrerequisites

Before connecting the design tool to SAP NetWeaver, you need to add the required SAP NetWeaver BW system to your SAP Logon dialog box.

Procedure

1. Start the design tool of SAP BusinessObjects Design Studio.2. Choose Tools Preferences Application Design .3. Select SAP NetWeaver as the preferred startup mode.4. Click OK.5. When prompted, click Restart to restart the design tool.6. In the Logon to SAP NetWeaver dialog box, select the SAP NetWeaver BW system.

If the required SAP NetWeaver BW system is not available in the dropdown box, make sure that this system is added to the SAP Logon dialog box on your local machine.


7. Enter the client of the BW system, your user name and password.8. Enter the required language of the BW system.

The master data and metadata of the BW data sources will be displayed in this language.9. Click OK.

Results

You can create, save, and load analysis applications in the design tool.

Next Steps

To run the analysis applications directly on SAP NetWeaver, choose Application Execute on SAP NetWeaver Portal . The URL that you see in the browser window is also the one that you can publish for end users.

3.3 Design Tool

3.3.1 System Requirements for the Design Tool InstallationBefore 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: Internet Explorer 9.0, 10 or 11 For 64-bit version of design tool installer: 64-bit version of Windows For 64-bit version of design tool installer: 64-bit Secure Login Client of SAP NetWeaver Single-Sign On

NoteTo avoid storage bottlenecks, we recommend using the 64-bit version.

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 Support Portal at http://support.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 .


Installation

3.3.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).

Procedure

1. Go to the SAP Software Download Center on SAP Support Portal at http://support.sap.com/swdc and choose Installations and Upgrades.

NoteSupport packages and patches are available under Support Packages and Patches.

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

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

For more information, see SAP Note 2133992 .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, start the .exe file for the required version:

SapDsSetup.exe for 32-bit SapDsSetup64.exe for 64-bit

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 for 32-bit is C:\Program Files (x86)\SAP BusinessObjects\Design Studio and for 64-bit the path is C:\Program Files\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.3.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 Support Portal to your PC.2. Extract the .exe file using the command line /Extract .3. Navigate to \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

3.3.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 Deployment on the SAP NetWeaver PortalProcedure

1. Download the .sca file from SAP Support Portal as described in the installation chapter.2. Deploy the .sca file to the SAP NetWeaver Portal using the Software Update Manager (SUM).

You can download SUM from http://support.sap.com/swdc Support Packages and Patches A Z Index S SL Toolset SL Toolset Entry by Component Software Update Manager (SUM)For more information about the Software Update Manager, see http://service.sap.com/sltoolset

Software Logistics Toolset System Maintenance Updating SAP Systems Using Software Update Manager .

Related Information

Installing SAP BusinessObjects Design Studio on SAP NetWeaver Portal [page 12]

4.2 Upgrading the Design Tool InstallationContext

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.


Upgrade

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

Administrator Guide: SAP BusinessObjects Design StudioUpgrade 2015 SAP SE or an SAP affiliate company. All rights reserved. 19

5 Configuration

5.1 Administration Tasks for Planning ApplicationsBefore 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.

Cell Locking

Application users can lock input-ready cells in the crosstab if they want to protect these cells from being changed by other users. They can set the cell lock at runtime for the current result set. These front-end cell locks are local cell locks in a query.Administrators can manage the cell locks in the back-end system for one individual input-ready query or all input-ready queries of the planning application. Locking a cell in all queries of the planning application means a cell that is locked in one query can be displayed as locked in other queries and can be handled as locked. These back-end cell locks are global cell locks in a planning application.To activate the global cell lock on the back end, you need to set a parameter in the table RSADMIN. You can use the program SAP_RSADMIN_MAINTAIN to do this. Set the following parameter: OBJECT = RSPLS_PQ_BACKEND_CELL_LOCKING VALUE = X

These cross query cell locks can be particularly useful if a planning application contains multiple tabs or pages, and its queries are closely linked but are used for different aspects of the planning application.

CautionOnce you have activated the global cell lock on the back end, the local cell lock will not work any more on the front end (Design Studio).

For more information, see: Back-End Cell Locks in the Application Designer Guide: Designing Analysis Applications on SAP Help Portal

at http://help.sap.com/boad Global Cell Locks in a Planning Application (Back End) in the SAP BW documentation on SAP Help Portal at

http://help.sap.com/


Configuration

5.2 Activating the Query Runtime Statistics

Context

SAP BusinessObjects 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 SAP BusinessObjects 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 SAP BusinessObjects 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 SAP BusinessObjects 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.

Administrator Guide: SAP BusinessObjects Design StudioConfiguration 2015 SAP SE or an SAP affiliate company. All rights reserved. 21

5.3 Setting RSADMIN Parameters for Analysis ApplicationsBy using a set of RSADMIN parameters available for analysis applications, you can specify how data cell values are displayed in your analysis applications.In the BW system connected to SAP BusinessObjects Design Studio, use ABAP report SAP_RSADMIN_MAINTAIN to set RSADMIN parameters for your analysis applications that are stored in this BW system.1. Call transaction SE38, enter SAP_RSADMIN_MAINTAIN under Program and choose Execute.2. Enter the relevant parameter under OBJECT and the required value under VALUE.

NoteAll string values should be limited to 30 characters to match the existing RSADMIN.

The following table contains the descriptions and default values for the RSADMIN parameters:Parameter Description Default Value

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

false

Display Unauthorized Values as: (DISPLAY_VALUE_NO_AUTHORIZATION)

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

NO_AUTHORIZATION

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

DIF0

Display Nonexistent Values as: (DISPLAY_VALUE_NOT_EXIST)

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

NOT_EXIST

Display Values with Mixed Units as: (DISPLAY_VALUE_MIXED_VALUE)

Display this string as String for values, which consist of mixed currencies and units

*

Display Overflow Values as: (DISPLAY_VALUE_OVERFLOW)

Display this string as String for values with a numeric overflow

OVERFLOW

Display Attribute Texts Even if Blank (BICS_ATTRIBUTE_TEXT_DISPLAY)

Display attribute text if the checkbox is selected, even if attribute text is blank

False

Maximum Number of Cells (BICS_DA_RESULT_SET_LIMIT_DEF)

Maximum number of cells returned per data source.You can set the parameter either lower or higher than the default value.

NoteIf the result set for a data source exceeds the limit set,

500000


Configuration

Parameter Description Default Value

then no data will be returned, and a warning is displayed in the crosstab.

These RSADMIN parameters are central parameters that can also be used by other BI client tools. If you use these parameters for SAP BusinessObjects Design Studio and also for another client tool, for example BEx Web, and you want to use different settings in the two tools, you can override the existing settings with a Design Studio-specific setting that will be ignored by other tools. In this case, you need to add the prefix AAD_ to the relevant parameter name. The parameters for overriding the existing RSADMIN parameters are listed below: AAD_DISPLAY_MIXED_VALUES AAD_DISPLAY_VALUE_NO_AUTHORIZA AAD_DISPLAY_VALUE_DIFF0 AAD_DISPLAY_VALUE_NOT_EXIST AAD_DISPLAY_VALUE_MIXED_VALUE AAD_DISPLAY_VALUE_OVERFLOW AAD_BICS_ATTRIBUTE_TEXT_DISPLA AAD_BICS_DA_RESULT_SET_LIMIT_D

NoteIt is only necessary to use this prefix if you want a different behavior in SAP BusinessObjects Design Studio than in other tools.

For each of these parameters, the following logic is applied: If the AAD_ (Design Studio-specific) parameter is set, the system takes this value. If the AAD_ (Design Studio-specific) parameter is not set, the system checks the base parameter. If this is set,

the system takes the value for the base parameter. If neither parameter is set, then the system uses the default value for the parameter.

5.4 Configuring the Portal for Displaying Analysis Applications

By default, the portal uses Internet Explorer quirks mode, which cannot properly render HTML5 Web applications like the analysis applications of SAP BusinessObjects Design Studio. With Internet Explorer 9, you may find that you only see an empty page and JavaScript errors are displayed.To avoid this, you can choose one of the following configuration procedures: You can embed the page with the analysis application in a headerless popup window.

For more information, see SAP Note 2077647 . Instead of using the standard portal framework page, you can use the unified portal framework page, which is

able to display standard mode content only.


For more information, see Unified Framework Page on the SAP Help Portal at http://help.sap.com.

NoteIf you want to use BEx Web applications created with SAP Business Explorer together with analysis applications in the Portal, you need to use the standard portal framework page. BEx Web applications cannot be displayed in the unified portal framework page. In this case, you need to embed the page with the analysis application in a headerless popup window.

5.5 Creating iViews Based on the Design Studio TemplateContext

Before application users can access analysis application in the SAP NetWeaver Portal, you need to create iViews based on the Design Studio template.

Procedure

1. In the Content Administration of the SAP NetWeaver Portal, choose Portal Content.2. Select your folder and, in the context menu, choose New iView iView from Template .3. In the list of available templates, select Design Studio.4. Follow the instructions in each step to complete the iView Wizard.5. Under Properties, enter the following information:

Option DescriptionAnalysis Application Enter the name of the analysis application.Application Parameters If required, enter the URL parameters of the analysis application.

For more information, see Creating iViews on the SAP Help Portal at http://help.sap.com/netweaver

Next Steps

Once you have created the iView, customized its properties, and tested it, you can make it available to your application users.You cannot assign iViews directly to users. Instead you must either assign the iView to a portal page and in turn assign the page to a role, or assign the iView directly to a role as a full-page application. After the role is assigned to a user, the user obtains the iView at runtime.You can also combine the analysis application iViews as part of a portal page with other iViews from other systems.


Configuration

For more information, see Adding Content to a Page on the SAP Help Portal at http://help.sap.com/netweaver.

NoteFor more information about configuring iViews for SAP BusinessObjects Design Studio, see SAP Note 2077647

and the attached Howto: Design Studio iView Configuration document.

Before your application users can launch the analysis application iViews, you must set the required permissions for the iViews as described in the topics listed below.

Related Information

Setting Permissions for Analysis Application iViews [page 25]

5.6 Setting Permissions for Analysis Application iViews

Context

In the default setting, only administrator users can launch analysis application iViews and portal components. To enable your application users to launch the analysis application iViews in the portal, you must configure the security zone NetWeaver.DesignStudio.

Procedure

1. In the System Administration of the SAP NetWeaver Portal, choose Permissions.2. Under Portal Content, choose Security Zones sap.com NetWeaver.DesignStudio .3. Select the low_safety folder and, in the context menu, choose Open Permissions .4. In the Assign New Permissions area, search for the required user group, for example, search for Everyone in

Group.5. Choose Go.6. Select the found group and choose Add.7. In the Assigned Permissions area, select the checkbox in the End User column for the added group.8. Choose Save.


Results

Your application users now have runtime authorization for analysis application iViews. They can access and view the analysis applications in the portal.For more information, see Setting Permissions in the Permission Editor on SAP Help Portal at http://help.sap.com/netweaver.

5.7 Configuring Permissions for Using SDK ExtensionsContext

If your users run analysis applications using Design Studio SDK extensions, you need to configure the necessary permissions on the SAP NetWeaver Portal and in SAP NetWeaver BW. A technical bw_service portal user is used (during the startup of the Design Studio archives) to load all SDK extensions from the BW system to the portal using RFC calls.

NoteIf your Portal UME is configured to take all users from R/3 systems using logon method SAPLOGONTICKET, then it is not possible to configure a mapping for the bw_service user. For a workaround, see SAP Note 1894594 .

Procedure

1. Configure the bw_service portal user:a. Check if the bw_service user exists in the portal.

If the bw_service user does not exist in the portal, the user is automatically created during the startup of the Design Studio archives, which have been deployed to the portal using the DESIGNSTUDIONW.sca file.

NoteIf you also use SAP Business Explorer Web applications that run on the portal, the bw_service user already exists in the portal.

b. To ensure that the bw_service user has at least read authorization for the BW system in the portal system landscape, start the iView User Administration Identity Management .

c. Choose Create Group.d. Under General Information, enter a name (for example BW_SERVICE_GROUP) and a description.e. Under Assigned Users, search for the bw_service user and choose Add.f. Start the iView System Administration System Landscape .


Configuration

g. Under System Landscape Overview, navigate to the BW system and choose Configure.h. Under Permissions, search for the group you created (for example BW_SERVICE_GROUP), select the

group and choose Add.i. Under Assigned Permissions, select the checkbox in the End User column and select Read in the

Administrator column for this group.2. Configure the BW user:

a. In the BW system, assign the permissions required for authorization object S_RS_ZEN to a service user. Your BW user needs display and execute permissions for object type 11. For more information, see Managing Access Rights [page 60]Ensure that this user has a Service user type.

b. In the BW system, in transaction SU01, grant this BW user permission to execute RFC calls in function group RSAO_CORE.For more information, see User and Role Administration of Application Server ABAP on SAP Help Portal at http://help.sap.com.

3. Map the bw_service portal user to the BW user:a. Log on to the portal.b. Start the iView Identity Management.c. From the dropdown box, choose User.d. Enter bw_service as the user and choose Go.e. Select bw_service and choose Modify.f. On the User Mapping for System Access tab, under System, choose the system alias of the BW system.g. Under Mapped User ID, enter the technical user name of the BW user.h. Under Mapped Password, enter the required password.i. Save your entries.

4. To load all SDK extensions, restart the portal.5. Before your users can work with analysis applications containing SDK extensions, you need to create the

necessary roles and configure the authorization object S_RS_ZEN for the different user roles in the BW system. For more information, see Managing Access Rights [page 60].

Related Information

Deploying Extensions to SAP NetWeaver [page 39]

5.8 Configuring the Report-Report Interface for Analysis Applications

Context

Before application users can use the report-report interface (RRI) in analysis applications, you need to configure the jump targets for the query that is used as data source in the analysis application. For more information, see


Using the Report-Report Interface on SAP Help Portal at http://help.sap.com BEx Query as Recipient on SAP Help Portal at http://help.sap.com

If the jump target, which is configured for the data source query, is also a query, the target query is launched as a BEx Web application by default. In order to avoid this and ensure that the jump is handled by Design Studio and the target query is displayed as an analysis application, you need to specify a generic analysis template on your platform.

Procedure

1. In the design tool, create an analysis application that can be used as the generic analysis template.As this analysis application will be used for all query jumps, it should be a very generic application, which can handle basic analysis of an arbitrary query. In general, it must conform to the following constraints: Contains only one data source, which is loaded in script. Accepts query ID as URL parameter XQUERY. Loads the single data source (usually in the On Startup script) by calling assignDataSource() and

passing the XQUERY and XSYSTEM parameters to the corresponding parameters of assignDataSource().

TipA good starting point, and an example of a valid generic analysis template, would be to select Generic Analysis Template when creating an application in the design tool. Note that you do not need to assign a data source to this Generic Analysis Template. When application users jump to the target query, the necessary query information is automatically added to the Generic Analysis Template as URL parameters (XQUERY, XSYSTEM).

2. Save your generic analysis template on the platform.3. To configure the runtime in order to use this analysis application as the generic analysis template for query

jumps, proceed as follows:a. In the BW system connected to Design Studio, call transaction SE38, enter SAP_RSADMIN_MAINTAIN

under Program and choose Execute.b. Enter AAD_ANALYSIS_TEMPLATE under OBJECT and the name of the deployed generic analysis template

under VALUE.4. Restart the SAP NetWeaver Portal component com.sap.ip.bi.designstudio.nw.portal.

After the restart, the Design Studio archives, which have been deployed to the portal with the DESIGNSTUDIONW.sca file, will reload all RSADMIN parameters (including this AAD_ANALYSIS_TEMPLATE parameter) from the corresponding BW system.

Results

In addition to the XQUERY and XSYSTEM URL parameters, which are passed to the receiving application, the filters and selection context are also passed, which are needed for dimensions relevant to the target query from the


Configuration

sending application. The mappings from source to target query are processed on the BW system, and the application of the appropriate filter values are processed by the Design Studio runtime.

Restriction Only query targets that are on the same system as the source query can be launched as analysis

applications. All other targets are processed as BEx Web applications. When the design tool is running in SAP NetWeaver mode, RRI query jumps to analysis applications are only

supported when executing the source analysis application on the platform, and not when executing the application in local mode.

5.9 Using Open Document URL iViews in SAP NetWeaver Portal

You can embed analysis applications as Open Document URL iViews into SAP NetWeaver Portal.Note the following: Make sure that you configure the Portal correctly when using Microsoft Internet Explorer. Note that the language of message texts and tooltips in Open Document URL iViews is defined by the

language setting in the BI launch pad or the Web browser. It is independent of the settings in the SAP NetWeaver Portal.

Related Information

Configuring the Portal for Displaying Analysis Applications [page 23]Language of Message Texts and Tooltips in Analysis Applications [page 53]

5.10 Configuring the Portal for Mobile UsageContext

With SAP NetWeaver as platform, you can use SAP Enterprise Portal to access analysis applications on mobile devices. The capability of SAP Enterprise Portal to support mobile usage of portal content is referred to as portal on device.Portal on device provides the following capabilities: Content administration - the ability to configure different content for different devices System administration - the ability to configure which portal desktop to display according to the device being

used to access the portal


Dedicated framework pages for use on smartphone devices and tablet devicesTo use portal on device, you need to create portal content that has been designed for mobile users and has been tailored for display on mobile devices. For more information about SAP recommendations for designing analysis application for mobile usage, see Creating Analysis Applications for Mobile Devices in the Application Designer Guide: Designing Analysis Applications on SAP Help Portal at http://help.sap.com/boad.After creating the content for portal on device, you need to tag this content so that it is filtered for display on mobile devices only.The following steps outline the necessary tasks with references to the detailed SAP Enterprise Portal documentation.

Procedure

1. Configure the support for HTML5.The framework page for portal on device is based on HTML5. By default, SAP Enterprise Portal does not support HTML5. To use portal on device, you must enable support for HTML5 in SAP NetWeaver Administrator by setting the value of the html5.compliant property to iViewDependent.See: Configuring Support for HTML5

2. Enable the filtering of portal content by the portal desktop.To enable the filtering of portal content by the portal desktop on which it is displayed, you must set the FilterbyDesktopView property to true. This setting enables you to use a filter ID string to tag a portal desktop, and then use the same filter ID to tag all the portal content to display in that desktop.See: Enabling Filtering Portal Content by Desktop

3. Configure the properties of the mobile framework pages according to your needs.The portal provides the following framework pages for use on mobile devices: Smartphone Framework Page and Tablet Framework Page.In the Framework Page Configuration tool, you can configure properties such as the following: Displaying the header Displaying a logo or a title in the center of the header Displaying the action button in the header Actions to display in the action bar or menu, such as Add to Favorites, Refresh, Log Off Enabling the toolbox Displaying the search bar In the Tablet Framework Page, you can also determine the location of the search bar: in the header or in

the toolboxSee: Configuring Properties of Mobile Framework Pages

4. Create device groups.A device group is an object that contains one or more user agent definitions. You can create as many device groups as you require. For each device group, you define its priority for runtime evaluation, its type, and the user agents that belong to the device group. You can then use the device groups in rule collections, to define which desktop should be displayed for users using access devices that belong to a certain device group.See: Creating Device Groups


Configuration

5. Configure desktop display rules for mobile devices.Portal on device comes with display rules for that associate between the out-of-the-box Smartphone Portal Desktop and Tablet Portal Desktop and the device types Smartphone and Tablet, respectively.You can use device groups and device types in rule collections to assign a specific desktop at runtime, according to the user agent of the browser being used to access the portal. Using device types in the rule collection enables you to assign the same desktop to more than one device group (of the same type) using a single IF statement.See: Configuring Desktop Display Rules for Mobile Devices

6. Optional: Configure filter IDs for mobile desktops.Portal on device comes with the following portal desktops: Smartphone Portal Desktop and Tablet Portal Desktop, configured with the following filter ID valuescom.sap.portal.smartphone and com.sap.portal.tablet, respectively. You can change the filter ID values, or add additional values.See: Configuring Filter IDs for Mobile Desktops

7. Configure the use of logon screens adapted for mobile devices.When accessing the portal with a smartphone or tablet device, portal on device uses logon screens that are adapted for display on a mobile device. The use of these logon screens is configured using the Logon Screen per Device property in SAP NetWeaver Administrator.See: Configuring the Use of Logon Screens Adapted for Mobile Devices

8. Create a mobile role.Portal on device comes with the Every User Mobile Role role. You can create your own mobile role.See: Creating a Mobile Role

9. Create and configure a Home page.You can use either an iView or a page to define a Home page. You first configure its properties for portal on device and then, you add the Home page to your mobile role.See: Configuring a Home Page

10. Define and configure the launcher.To define the Launcher, you use one of the portal container objects: role folder, role, or workset. First, you set the value of the Mobile Perspective property of the object to Launcher. Then, you add the Launcher to your mobile role. Finally, you add the content items to display in the Launcher. For each content item, you need to configure whether it opens in the portal content area, or in a new portal window. You can also specify custom icons for each item in the Launcher, instead of the default icons that are provided for an application and a folder.See: Configuring the Launcher

5.11 Maintaining Settings in the Design ToolYou 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 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 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 minute checkbox and enter the required number for the auto-save time interval.


Configuration

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

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

Application Templates

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.Application designers can also create analysis applications and provide them as templates for other application designers. Under Tools Preferences Application Design Application Templates , you can add the path to the folder where these templates are stored. Here you can also define your own template categories that indicate the target device types recommended for a specific template. The template categories are then listed in the New Application dialog box ( Application New... ), and also in the Export Application As Template dialog box ( Application Export as Template... ). For more information, see Exporting Applications As Templates in the Application Designer Guide: Designing Analysis Applications under Help Help Contents in the design tool.


Configuration

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 65]Activating SAP JCo Traces [page 66]Viewing And Collecting Statistics Data At Runtime [page 66]

5.12 Sizing GuidelinesYou can find recommendations on sizing and optimizing the performance of analysis applications in SAP Note 1177020 .

5.13 More InformationFor more information about configuration, update and setup of SAP BusinessObjects Design Studio, see SAP Note 2133992 . This note contains up-to-date information that could not be included in this guide.


6 Operations

6.1 Deploying SDK ExtensionsIn addition to the standard palette of components in SAP BusinessObjects 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 SAP BusinessObjects Design Studio installation enables you to create and execute local analysis applications containing these SDK extensions.Furthermore, you can install new chart types developed with the SAP Lumira SDK. These SDK extensions, also known as CVOM chart extensions, are added to the list of additional chart types for the standard chart component. You can create and execute local analysis applications containing these new chart types.Before application users can launch analysis applications containing SDK extensions from SAP NetWeaver Portal, you need to deploy these locally installed extensions to SAP NetWeaver BW and trigger the reload process for these extensions in SAP NetWeaver Portal.

NoteSDK extensions are supported by specific SAP NetWeaver support packages. For more information, see SAP Note 1945541 .

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.For more information about creating CVOM chart extensions using the SAP Lumira SDK, see the SAP Lumira SDK Getting Started Guide on SAP Help Portal at http://help.sap.com/lumira.

Related Information

Installing Design Studio SDK Extensions to SAP BusinessObjects Design Studio [page 36]Installing CVOM Chart Extensions for SAP BusinessObjects Design Studio [page 37]Deploying Extensions to SAP NetWeaver [page 39]

6.1.1 Installing Design Studio SDK Extensions to SAP BusinessObjects Design Studio

Context

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


Operations

Procedure

1. In SAP BusinessObjects 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.

For extensions stored on a Web server, enter the URL of the Web server.3. Choose OK.4. Select the required feature, for example, SampleExtensionFeature.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 SAP BusinessObjects Design Studio to restart.

Results

The SDK extension components appear in the Components view of SAP BusinessObjects Design Studio as new components.The components are stored under \Analysis-config.

6.1.2 Installing CVOM Chart Extensions for SAP BusinessObjects Design Studio

Context

You can add CVOM chart extensions, developed with the SAP Lumira SDK, to your SAP BusinessObjects Design Studio installation as new chart types for the standard chart component.

Procedure

1. In SAP BusinessObjects Design Studio, choose Tools Install CVOM Chart Extension... .2. Depending on where the CVOM chart extension is located, proceed as follows:

For locally saved extensions, choose Archive... and select the archive file containing the extension, for exampleC:\SampleChartExtension.zip.

For extensions stored on a Web server, enter the URL of the Web server.

Administrator Guide: SAP BusinessObjects Design StudioOperations 2015 SAP SE or an SAP affiliate company. All rights reserved. 37

3. Choose OK and then chooseOK again to confirm the installation.4. To restart SAP BusinessObjects Design Studio, choose Yes.

Results

When you create or open an analysis application with a chart component, the CVOM chart extensions you have added are listed as new chart types.

Next Steps

In the Properties view of the chart component, under Chart Type, choose Additional Chart Types.... The CVOM chart extensions are listed as new chart types in the Additional Charts dialog box.

6.1.3 Removing Extensions from SAP BusinessObjects Design Studio

Context

You can remove SDK extensions that you have added to your SAP BusinessObjects Design Studio installation as follows:

Procedure

1. In SAP BusinessObjects 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 SAP BusinessObjects Design Studio to restart.

Results

The SDK extension components are removed from the Components view of SAP BusinessObjects Design Studio. CVOM chart extensions are removed from the list in the Additional Charts dialog box.


Operations

6.1.4 Deploying Extensions to SAP NetWeaver

Prerequisites

You need to configure the bw_service portal user before proceeding. For more information, see Configuring Permissions for Using SDK Extensions [page 26].

Context

Before application users can launch analysis applications containing SDK extensions from SAP NetWeaver Portal, you first need to deploy the extensions (which you have added to your SAP BusinessObjects Design Studio installation) to SAP NetWeaver BW and trigger the reload process for these extensions in SAP NetWeaver Portal.

Procedure

1. Start the design tool in SAP NetWeaver mode and choose Tools Platform Extensions .2. Select the required extensions on your local computer.3. Choose Install on Platform.4. In order to complete the installation process, you have to manually restart the SAP NetWeaver Portal server.

Accept the warning in the design tool.The selected extensions appear under Extensions Installed on Platform.

5. Choose Close.6. Restart the SAP NetWeaver Portal component com.sap.ip.bi.designstudio.nw.portal.

After the restart, the Design Studio archives, which have been deployed to the portal with the DESIGNSTUDIONW.sca file, will reload all available SDK extensions from the corresponding BW system.

Results

The SDK extensions are available in the SAP NetWeaver BW system and on the SAP NetWeaver Portal. Application users can launch the analysis applications containing these SDK extensions from the portal.


6.1.5 Removing Extensions from SAP NetWeaver

Procedure

1. Start the design tool in SAP NetWeaver mode and choose Tools Platform Extensions .2. Under Extensions Installed on Platform, select the extensions you want to remove from SAP NetWeaver.3. Choose Uninstall from Platform.4. Confirm the uninstallation by choosing Yes.5. In order to complete the uninstallation process, you have to manually restart the SAP NetWeaver Portal

server. Accept the warning in the design tool.The selected extensions are removed from the table Extensions Installed on Platform.

6. Choose Close.7. Restart the SAP NetWeaver Portal server that hosts your SAP BusinessObjects Design Studio Add-On.

After the restart, the SAP BusinessObjects Design Studio archives, which have been deployed to the Portal with the DESIGNSTUDIONW.sca file, will reload all remaining SDK extensions from the corresponding BW system.

Results

The selected SDK extensions are deleted in the SAP NetWeaver BW system. These extensions will also no longer be loaded in the SAP NetWeaver Portal.

6.2 Uploading Images to the MIME Repository

Prerequisites

In order to use the MIME repository (for uploading and accessing images), the relevant authorization profiles (your profile, the profiles of your application designers and the profiles of your application users) need authorization object S_DEVELOP. For more information, see Authorizations [page 45].

Context

Before application designers can insert images into their analysis application (using the Image component or an icon in the Button component), the images need to be available as MIME objects in the MIME repository of the BW system. Depending on the SAP NetWeaver release version, there are different ways to upload the images: You upload the images in the design tool


Operations

For more information, see chapters Image or Button in the Application Designer Guide: Designing Analysis Applications, under Help Help Contents in the design tool.

NoteFor more information about the required SAP NetWeaver release versions for direct upload in the design tool, see SAP Note 2111546 .

You upload the images in the ABAP Workbench of the BW systemWith older SAP NetWeaver versions, proceed as follows:

Procedure

1. In the SAP Easy Access initial screen of the BW system, choose SAP Menu Tools ABAP WorkbenchOverview Object Navigator , or choose transaction SO2_MIME_REPOSITORY.

2. Under MIME Repository, you can store your MIME objects (images or icons) anywhere under SAP BW . To create a new folder, select BW and in the context menu, choose Create Folder... . Enter a name

and a description, Design Studio, for example, and save your entries. To store MIME objects, select the folder and in the context menu, choose Import MIME Objects.

Results

Application designers can click on the Browse button next to the Image or the Icon property. The Open Image dialog box appears where they can select the image or icon from the MIME repository.

NoteMIME objects are only stored in the Web browser cache (client cache). The retention period for MIME objects in the Web browser cache is specified using the back-end profile parameter icm/HTTP/server_cache_0/expiration; the retention period is specified in seconds. The default value for this parameter is 86400, but you can change this value as required. If you want the changes to the MIME objects to take effect before the end of the retention period, you can manually delete the original MIME objects from the Web browser cache.1. In your Web browser, choose Tools Internet Options General Delete Files .2. In the Delete Files dialog box, select Delete all offline content and choose OK.


6.3 Uploading Template Files to the MIME RepositoryContext

NoteThe procedure described below is only necessary with specific SAP NetWeaver release versions. For more information, see SAP Note 2111546 .

We recommend that you use the Export Application As Template function under Application Export as Template... instead.

Before application designers can use the predefined templates in the design tool and make their generated analysis applications available on SAP NetWeaver, specific template files need to be uploaded to the MIME repository of SAP NetWeaver BW.

Procedure

1. Log on to the design tool in SAP NetWeaver mode and create an analysis application from the required template (Basic Analysis Template, for example).When you save the analysis application, the corresponding content.biapp file is automatically uploaded to the SAP NetWeaver BW system. Due to technical restrictions, it is not possible to upload the corresponding images and other files automatically. You need to do this manually.

2. On your PC, navigate to the folder where your SAP BusinessObjects Design Studio installation files are stored.3. Choose plugins com.sap.ip.bi.zen.content_ templates .4. Open the required folder (Desktop, iPad or iPhone) and choose the template you used for your analysis

application (TEMPLATE_ADHOC_ANALYSIS, for example).5. Select the following files and upload them to the MIME repository of the BW system:

all images in the images folder *.css file *.eot file *.ttf file

6. Return to your analysis application in the design tool. In the Properties view under Custom CSS, enter the path to the *.css file in the MIME repository.

7. If you use a template with images, click on an image in the template. In the Properties view under Image, enter the path to the corresponding imag

ds_15_admin_nw_en

Documents

Transcript of ds_15_admin_nw_en