SAP for iOS BusinessObjects Mobile Administrator's Guide

SAP BusinessObjects Mobile for iOS

Document Version: 6.1.18 – 2015-04-10

Administrator's Guide

Content

1

2

3

About this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6

Target Readership. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7

About the Application and the Supported BI Content Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8

4 What's New in 6.1?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11

5

5.1

5.2

Administering SAP BusinessObjects Mobile for iOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

Solution Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16

SAP BusinessObjects Mobile Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17

SAP BusinessObjects Mobile Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

SAP BusinessObjects Business Intelligence (BI) Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18

Platform Support for the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19

Support on iPhones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

20

5.3 Language Support in the App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21

5.4 Installing the Required Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

Installing the SAP BusinessObjects Mobile Application For iOS . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

5.5

Installing the SAP BusinessObjects Mobile Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22

Installing the SAP BusinessObjects BI Platform Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25

Installing the Configuration Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25

Creating and Configuring Server Connections (Including BIOD and Sybase Afaria). . . . . . . . . . . . . . . .

25

Creating, Importing and Sharing Server Connections Using the App on Device. . . . . . . . . . . . . . . . .

25

Configuring Connections for Importing to Mobile for iOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

26

Using SAP BI URLs For Managing Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

27

5.6 Single Sign On (SSO) Support on the Mobile BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

31

Configuring the Mobile Server for SSO Using Trusted Authentication (REMOTE_USER or

USER_PRINCIPAL or X509 Certificate). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

32

5.7

Configuring the Mobile Server for SSO Using CA SiteMinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

35

Configuring the Mobile Server for SSO Using SAP Logon Tickets. . . . . . . . . . . . . . . . . . . . . . . . . .

38

Connecting to the SAP Mobility Platform (SMP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

41

Installing the SAP Mobility Platform (SMP). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Configuring SMP for Use With the Mobile Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

42

Configuring Mobile Server to Connect to the SMP Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

48

Adding IMO- and REST-Based SMP Connections to the Application On Device. . . . . . . . . . . . . . . . .

49

Removing an SMP Connection from the App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

50

Configuring Single Sign-On (SSO) in SMP Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

51

Restrictions of the SMP BOE-Legacy Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

54

2

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Content

5.8 Using SAP BI URLs For Managing Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56

Creating an SAP BI URL To Add a Corporate Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

56

Creating an SAP BI URL To Add an SUP Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

57

Using URLs To Delete Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

58

Creating a URL to Modify a Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

59

Creating SAP BI URLs to Add Single Sign On Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

60

5.9 Configuring Application's Behavior by Specifying Properties on the Server. . . . . . . . . . . . . . . . . . . . . .

62

Using URLs To Delete Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

63

5.10 Granting Users the SAP BusinessObjects Mobile Application Rights on the BI Platform . . . . . . . . . . . . .

64

5.11 Customizing Application's Interface Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

65

Mobile Server and Property File Locations Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

66

Using the CMC to Define Properties on BI Platform 4.1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

66

Configuring the Thumbnail Background Image of BI Documents. . . . . . . . . . . . . . . . . . . . . . . . . . .

68

Configuring Document-Specific Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

70

Configuring the Collaboration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

70

Configuring the Visibility of BI Document Samples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

72

Configuring QR Code Scanning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73

Configuring the Session Timeout Duration of the Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

73

Configuring the Auto Update option for BI documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

74

Configuring the Auto Refresh (polling) option for BI documents list. . . . . . . . . . . . . . . . . . . . . . . . .

76

Configuring the display of nested categories on the Home screen. . . . . . . . . . . . . . . . . . . . . . . . . .

78

5.12 Configuring Categories on the Mobile Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

78

5.13 Generating SAP BI URLs for Opening BI Documents. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

82

Creating SAP BI URLs For Opening Specific BI Documents or Reports. . . . . . . . . . . . . . . . . . . . . . .

83

Creating SAP BI URLs For Opening The Latest Instance of BI Documents. . . . . . . . . . . . . . . . . . . .

84

Creating SAP BI URLs For Opening BI Documents With Prompts. . . . . . . . . . . . . . . . . . . . . . . . . .

85

Creating SAP BI URLs for Opening Specific Sections of the BI Documents With Sections. . . . . . . . .

86

Creating SAP BI URLs for Opening the Latest Available Version of a BI document or Its Instance

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

87

5.14 Understanding the Security Implementation in the App. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

88

Features of Application Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

88

Support for Security Deployments On the Web Application Server. . . . . . . . . . . . . . . . . . . . . . . . .

90

User Data Protection and Privacy Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

93

5.15 MDM Configuration Support for iOS 7 Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

94

5.16 Working With Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

95

6 Creating Personal Views of Web Intelligence Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

100

7

7.1

Managing the Mobile support for Dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105

Using the Mobile Compatibility panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105

7.2 Supported components in mobile dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

106

Using components in mobile dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

109

Administrator's Guide

Content

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

3

7.3

7.4

8

8.1

Unsupported features in mobile dashboards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111

Saving mobile dashboards to BI platform folders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112

Managing the Mobile support for Information Spaces and Information Views. . . . . . . . . . . . . . .

114

Valid Data Format for Augmented Views. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

114

9

9.1

Managing the Mobile Support for Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

116

116

9.2 Configuration Tasks for Mobile Usage of Analysis Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

116

Creating a Mobile Category on the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

117

Assigning Analysis Applications to the Mobile Category. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

117

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

118

9.3 Creating Analysis Applications in SAP BusinessObjects Mobile for Mobile Devices. . . . . . . . . . . . . . . .

119

9.4 Further information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

119

10 Managing the Mobile Support for SAP Lumira Server or SAP Lumira Cloud. . . . . . . . . . . . . . . . .

120

10.1 Configuring the Connection to SAP Lumira server or SAP Lumira Cloud. . . . . . . . . . . . . . . . . . . . . . .

120

10.2 Further Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

120

11 Troubleshooting Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

121

11.1 Troubleshooting the Mobile Server Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

121

An internal server error occurred while processing the client request (MOB00022). . . . . . . . . . . . .

121

Connection to the server could not be established; contact your administrator if the problem persists (MOB06004). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122

Connection to the server could not be established; try again or contact your administrator

(MOB06005). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

122

The request has timed out; try again or contact your system administrator (MOB06006). . . . . . . .

122

You are not authorized for this request (MOB06008). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123

Your request is invalid; verify the connection details or contact your administrator (MOB06009)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123

Internal server error occurred while processing your request; try again or contact your system administrator (MOB06010). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

123

Missing prompt value; select at least one value for the prompt (MOB06011). . . . . . . . . . . . . . . . . .

124

Verify network connectivity (MOB06021). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

Connection to the server could not be established; try again or contact your administrator

(MOB06031). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

124

Server returned an error while downloading the document (MOB06060). . . . . . . . . . . . . . . . . . . .

124

This action cannot be performed; verify network connectivity (MOB08002). . . . . . . . . . . . . . . . . .

125

An internal server error occurred while processing your request on hierarchical data; the document will be closed; contact your administrator for more information (MOB09001). . . . . . . . .

125

There was a problem in opening the document; download the document again or contact your administrator (MOB06061). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

126

Maximum character file size limit exceeded. The document is too large to be processed by the server. Contact your BusinessObjects administrator (WIS 30272) . . . . . . . . . . . . . . . . . . . . . . . .

126

4

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Content

11.2 Troubleshooting the Mobile Client Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

127

Email is not configured on this device (MOB07001). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

127

Internal server error occurred while processing your request; contact your administrator

(MOB07002). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

127

Server error prevented the document from refreshing; try again (MOB07003). . . . . . . . . . . . . . . .

127

11.3 Configuring Trace Logs for Monitoring on the BI Platform. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

128

Administrator's Guide

Content

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

5

1 About this Document

6

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

About this Document

2 Target Readership

This guide is designed to help the following types of users:

● IT administrators who:

○ Install and configure the various components of the SAP BusinessObjects Mobile for iOS solution including the application on the user's device (iPhone or iPad), the SAP BusinessObjects Mobile server and the SAP BI platform server.

○ Configure various application properties and server properties using the property files on the Mobile server or by using the CMC (Central Management Console) on the BI platform.

○ Troubleshoot errors

● Business Intelligence administrators who:

○ Manage user rights and permissions for accessing documents and performing actions on BI reports.

○ Manage the accessibility and security of BI documents.

Administrator's Guide

Target Readership

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

7

3 About the Application and the Supported

BI Content Types

The SAP BusinessObjects Mobile application for iOS provides access to multiple SAP BusinessObjects Business

Intelligence (BI) content types to users of the iPhone and iPad devices through a single mobile app.

The SAP BusinessObjects Business Intelligence (BI) content supported by the app includes Web Intelligence,

Crystal Reports, hyperlinks, Dashboards, Analysis applications, Explorer information spaces/exploration views, and BI HANAbased visualizations (based on the SAP Lumira Server and SAP Lumira Cloud).

Using the SAP BusinessObjects Mobile application for iOS, users can:

1. Create connections to the SAP BusinessObjects BI platform server and access the various BI documents and analytics content available on the server.

2. Search, view, and download documents on their iPhone and iPad devices.

3. Access notifications, refresh documents, bookmark documents, filter document data, drill on document data, view document information in sections, and effectively collaborate with other business users for informed decision-making.

SAP BusinessObjects Web Intelligence

Following are some of the key features of SAP BusinessObjects Web Intelligence reports:

1. Web Intelligence reports offer capabilities such as filtering, drilling down, displaying data in charts, and displaying data based on formulas.

2. Data of Web Intelligence reports comes from a variety of data sources, including:

Universes (which organize data from relational and OLAP databases into objects)

Personal data providers (such as CSV files or Microsoft Excel spreadsheets)

Bex queries (based on SAP Info Cubes)

Web services

Advanced analysis workspaces

SAP HANA

SAP Crystal Reports

Following are some of the key features of SAP Crystal Reports:

1. SAP Crystal Reports can be based on virtually any data source.

2. Formulas, cross-tabs, subreports, conditional formatting, geographic maps and graphs in SAP Crystal

Reports communicate information visually and effectively.

8

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

About the Application and the Supported BI Content Types

SAP BusinessObjects Analysis Applications

Analysis applications are Web applications that allow users to analyze data from SAP NetWeaver Business

Warehouse (BW) and SAP HANA. They are created using the SAP BusinessObjects Design Studio.

The design studio uses latest technologies including HTML 5 rendering and the Eclipse plug-in for designers.

SAP BusinessObjects Dashboards

SAP BusinessObjects Dashboards (created with a Dashboard Builder) are corporate dashboards with analytics based on Universe queries. They are rich in look and feel, and provide support for the following features on Mobile:

● Query pane based data connectivity

● Hierarchies in tables

● Add-on components

● Maps, radar charts, bubble charts, waterfall charts, menus (such as Picture Menu, Accordion menu), listbuilder selectors, and checkboxes.

● The Nova style theme

Hyperlink Objects

Hyperlink objects can be created in the BI LaunchPad. A hyperlink object has a name and a URL. On tapping a hyperlink document in the app, it opens a Web view within the application to render the URL contents (by default, the hyperlink does not open the browser on device).

Note

If you want the report to open in a Safari (browser) window, append the parameter

<SAPBI_target>

with the value _blank to the URL. If you do not use this parameter, the target report always opens within the application container itself.

Visualizations (Based on the SAP Lumira Server and SAP Lumira Cloud

Application)

The SAP Lumira Cloud application allows users to explore datasets and create visualizations that are stored on the cloud. It also allows you to upload, share, and delete SAP Lumira documents (.svid), SAP Crystal Reports documents, Design Studio files, Microsoft PowerPoint files, Microsoft Excel worksheets, and CSV files. It also allows you to share visualizations with other individual users.

Note

Files can only be shared with individuals using the iPad app, not with teams. For more information on the SAP

Lumira Server, refer to the SAP Lumira Cloud User guide available at http://help.sap.com/boall_en

Administrator's Guide

About the Application and the Supported BI Content Types

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

9

Note

For more information on the above BI content types, refer to the documentation available on the SAP Help

Portal-> http://help.sap.com/boall_en

10

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

About the Application and the Supported BI Content Types

4 What's New in 6.1?

User Experience Improvements

● The application now aligns with the flat UI design of iOS 7. All categories and sub-categories of BI documents appear as a flat list in the "Browse" panel.

● There is support for nested categories in the Browse panel of the application. If you have enabled category nesting in the application and you tap on a category, the available sub-categories appear on a new screen within the panel. Tapping on the sub-category again opens the lower sub-categories. This is similar to the behavior of categories on BI LaunchPad and is indicated in the below figure:

Note

By default this property is disabled in the application and all categories and their sub-categories appear as a flat list. If you want sub-categories to appear on tapping a category on device, set the value of the feature.home.category.nested.enabled property to true using client settings on the server. For information on how to edit client settings on the server, refer to the Configuring Application's Behavior by

Specifying Properties on the Server chapter in this guide.

● If you have opened a chart in zoom mode, you can return to the report by double tapping the chart on device.

Enhancements to Home Screen Refresh and Notifications

● The application Home screen is now auto-refreshed every 15 minutes. When an auto-refresh takes place, the

BI documents are re-listed on the Home screen such that they are synchronized with the server. (BI documents may be added, removed or updated on the server.)

● When you refresh the Home screen (using the pull-down gesture) or when it is auto-refreshed, the

(

Notifications

) icon appears in the tool-bar if server updates are available for your downloaded BI documents.

Administrator's Guide

What's New in 6.1?

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

11

You can view and fetch document updates using the panel that appears on tapping the (Notifications) icon. The notifications displayed in the panel include:

○ Notifications for downloaded documents that are updated on the server.

○ Notifications for downloaded documents that are removed from the server or are no longer assigned to the Mobile category.

○ Notifications for mobile-enabled documents that are added new on the server, and are thus available on the Home screen of the application.

Note

○ You can configure the auto-refresh duration on the server. For this, you need to set a positive value for the client setting

<feature.notification.polling.interval>

on the server. If you set this property to zero or a negative value, auto-refresh is disabled. For information on how to edit client settings on the server, refer to the Configuring Application's Behavior by Specifying Properties on the

Server chapter in this guide.

○ The value passed for

<feature.notification.polling.interval>

(auto-refresh duration) is considered in minutes and can be in decimals. It is recommended that you do not specify a very small value for this setting as frequent auto-refresh of the Home screen puts load on the server when user traffic is high.

● The application provides you with an

Auto Update

option that you can enable using the application Settings.

With each refresh of the Home screen, if you want the documents with available updates to be redownloaded from the server, without explicitly fetching the updates from the Notifications panel, set

Auto Update

to ON.

The figure below displays how the "Notifications" panel appears on tapping when auto update is OFF and when it is ON:

12

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

What's New in 6.1?

Note

By default, the auto-update feature is available in the application. If you want to disable it, you can set the value of the client setting

<feature.autoupdate.enabled>

to 'false'. For information on how to edit client settings on the server, refer to the Configuring Application's Behavior by Specifying Properties on the

Server chapter in this guide.

● Whenever there are refresh updates available for your downloaded BI documents, the application icon on the device screen displays a notification badge as shown in the below image:

The number that appears over the badge is a summation of notifications from all server connections that you have added in the application. For example, if you have added 3 server connections, and there is 1 update available on first server, 1 update available on the second server and 2 updates available on the third server, the Notifications badge displays the sum of all notifications, which is 4.

This number changes dynamically and is always in synchronization with the (

Notifications

) icon that appears in the tool-bar of the application.

Note

For more information on the behavior of notifications, see the related topic provided at the bottom.

Administrator's Guide

What's New in 6.1?

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

13

Generic Functional Enhancements

● Embedded images are now supported in the header cells of tables. Earlier, they were only supported in cells of the table body.

● You can access downloaded hyperlink content in “Work Offline” mode of the application. However, this may require internet access based on the URL used in hyperlink.

Note

This feature is not available in the app by default. To enable this feature, you need to specify the property

“feature.hyperlink.offline.enabled=true” using client settings on the server. For information on how to edit client settings on the server, refer to the Configuring Application's Behavior by Specifying Properties on the

Server chapter in this guide.

● You can now control the accessibility of Explorer artifacts and Dashboard documents in the application.

Earlier, all Dashboard and Explorer artifacts that existed on the server were listed in the application on device, irrespective of whether or not they were assigned to the Mobile category. However, you can now restrict

Explorer artifacts and Dashboard documents to appear in the application only if they are assigned to the

Mobile category on the server. To accomplish this, you need to define the following properties in the mobi.properties file on the server:

○ For Dashboard documents: Set default.listing.xcelsius.category.only=true

○ For Explorer artifacts: Set default.listing.explorer.category.only=true

● You can clear HTTP cache in the application by accessing the following setting:

Application Settings Additional Settings Clear Data Remove Application Cache Data

Web Intelligence Enhancements

● The application supports Report Element Linking (REL) on stacked bar charts and on tables with breaks. With the introduction of this feature, REL is now supported on all types of report parts.

● OpenDocument URL enhancements:

○ OpenDoc URL can be opened within Lumira stories.

○ The sReportPart and mode parameters are supported in the URL.

○ Navigation to a report part within a section is possible using the OpenDocument URL.

● The application supports input controls defined on variables with a custom list of values (LOV) defined by the report designer.

● The application supports colors of hyperlink and report element link that are custom defined by the report designer. For example, the report designer may have defined specific color for a visited and for an unvisited link.

For more information on the Web Intelligence enhancements, see the Mobile BI Report Designer's Guide available on http://help.sap.com/bomobileios

14

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

What's New in 6.1?

Related Information

Working With Notifications [page 95]

Administrator's Guide

What's New in 6.1?

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

15

5 Administering SAP BusinessObjects

Mobile for iOS

5.1 Solution Overview

The SAP BusinessObjects Mobile solution for iOS allows end users to access the SAP BusinessObjects Business

Intelligence (BI) content through their iPhone and iPad devices. It is suited to running ad-hoc query reporting and analysis.

This solution contains three essential components:

● SAP BusinessObjects Mobile client (SAP BI app)

● SAP BusinessObjects Mobile server

● SAP BusinessObjects Business Intelligence (BI) platform server

Besides the above mandatory components, you can also have the following optional elements for enhanced security in your landscape:

● A reverse proxy server

● A Sybase Unwired Platform server (with a relay server)

The overall SAP BusinessObjects Mobile architecture for server versions XI 3.1 and 4.0 is shown in the following illustration:

16

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

For Business Intelligence platform 4.1, the architecture includes the SAP BusinessObjects Explorer server in the

BI platform. The architecture is shown in the following illustration:

Related Information

SAP BusinessObjects Mobile Client [page 17]

SAP BusinessObjects Mobile Server [page 18]

SAP BusinessObjects Business Intelligence (BI) Platform [page 18]

5.1.1 SAP BusinessObjects Mobile Client

The SAP BusinessObjects Mobile app for iOS is the client. Using this app, professionals can access Business

Intelligence content from their iPad and iPhone devices. The application gives its users access to the following types of BI documents:

●

SAP BusinessObjects Web Intelligence

●

SAP BusinessObjects interactive Crystal Reports

●

SAP BusinessObjects Dashboards

●

SAP BusinessObjects Analysis applications

●

SAP BusinessObjects Explorer information spaces/exploration views

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

17

●

SAP BusinessObjects Lumira server and cloud content (HANA visualizations)

The documents are displayed on an iPad or iPhone with user interactivity appropriate to the device.

The app offers the following functions: document viewing, refreshing, document sharing, navigation, data drilling, data filtering (using prompts and input controls), report data viewing (in sections), and collaboration options.

The SAP BusinessObjects Mobile solution runs on data infrastructures based on Wi-Fi, 3G, and 3G+ networks.

5.1.2 SAP BusinessObjects Mobile Server

The SAP BusinessObjects Mobile server is a Web application that can do the following:

● Receive requests sent by the SAP BusinessObjects Mobile client and pass them to the SAP BusinessObjects

BI platform server.

Note

The SAP BusinessObjects Mobile client is the "SAP BI" application installed on a client device such as iPhone, iPad, Android phone/tablet, or Blackberry.

● Receive the responses (for example, Web intelligence or CR documents, report data or parameter values) from the SAP BusinessObjects BI platform and send them to the SAP BusinessObjects Mobile client (app installed on mobile device).

● Optimize the responses of the Business Intelligence (BI) platform, thus making it suitable for use with the

Mobile client.

● Provide flexibility and customization options for client applications such as the types of BI documents, and the document layout to be displayed on the device.

● Provide additional security options such as restricting users from downloading confidential documents.

Note

The application administrator can configure app security and customization options using the various properties files on the server. The required configuration details are provided in this document.

5.1.3 SAP BusinessObjects Business Intelligence (BI)

Platform

The SAP BusinessObjects BI platform server gives you access to all data captured from corporate databases and data warehouses by business intelligence (BI) documents. It handles the whole document life cycle including creation, catalog, refresh, content delivery, and report interactivity.

The SAP BusinessObjects BI platform server processes requests sent by SAP BusinessObjects Mobile client through the SAP BusinessObjects Mobile server, and sends back responses.

18

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Related Information

Installing the SAP BusinessObjects BI Platform Server [page 25]

5.2 Platform Support for the Application

1. Device Support

The SAP BusinessObjects Mobile application for iOS is supported on the following devices:

● iPhone 4 and above

● iPad mini

● iPad 2 and above

Note

1. iPad 1 is deprecated.

2. Certain application features are not supported on iPhones. For more information, see the relevant section of this chapter:

Support on iPhones [page 20]

2. Operating System Support

The application is supported on iOS 6.0 and all higher versions up to iOS 7.1

Note iOS versions older than 6.0 are not supported by the application.

3. Web Application Server Support

The Mobile server and BI platform server can be based on one of the following Web Application servers:

● Apache Tomcat

● IBM Websphere

● SAP NetWeaver

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

19

3. BI Platform Dependency

To ensure that you can use the complete application functionality, you require SAP BusinessObjects BI platform

4.0 Support Package 8 or 4.1 Support Package 2. However, the application is backward compatible and the legacy features of the application still work on older server versions (including XI 3.1 SPXX, 4.0 SPXX).

For information on the application features-versus-server compatibility for new features of the application, refer to the relevant section of this chapter. For the detailed compatibility matrix including legacy features of the application, refer to the Application Features versus the BI platform Server Compatibility guide at http:// help.sap.com/bomobileios

Note

The application is also supported on the Crystal Report SAP BusinessObjects Edge 4.0 and SAP

BusinessObjects Edge 4.1. For information on SAP BusinessObjects Edge, refer to http://help.sap.com/ boall_en/

4. Data Sources Support

To create a Web Intelligence document or add new data to a document, use queries to

retrieve data from a data source

to the document.

Depending on the interface you are using, you can create queries based on:

1. Universes, which represent data in relational or OLAP databases as objects.

2. Local data sources such as text files or Microsoft Excel files

3. SAP Info Cubes in a SAP BW Business Warehouse by using BEx queries.

4. Pioneer data sources

5. Web services

All the above Web Intelligence data sources and HANA are now supported by the application.

5.2.1 Support on iPhones

Users can now install and use the SAP BusinessObjects Mobile application for accessing SAP BI data on iPhone devices. All application features are supported on the iPhone except for:

● Annotation

● SAP JAM and SAP StreamWork collaboration (discussions and activities)

● "Page layout" model of displaying report parts on the device screen

● Exploration views (created using the SAP BusinessObjects Explorer server)

● Dashboards

20

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

On the iPhone, each app page (single screen) accommodates one report part. If blank cells are hooked to a report part, they appear along with the report part on the same screen. For information on configuring blank cells in reports, see the Mobile BI Report Designer's Guide.

5.3 Language Support in the App

The SAP BusinessObjects Mobile application for iOS provides support for the following language locales:

● Simplified Chinese

● Japanese

● Russian

● Polish

● French

● German

● Portuguese

● Spanish

● Arabic

● Hebrew

Note

Design Studio content is not supported in the Hebrew language.

Note

Both Product locale and the Viewing locale (as configured on device) are supported in the app.

● You configure the product locale on an iPad by choosing the following option:

Settings General International Language

● You configure the viewing locale on an iPad by choosing the following option:

Settings General International Region Format

The Product locale and the Viewing locale settings that you make on the device take precedence over the settings you make for the same parameters in the BI LaunchPad.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

21

5.4 Installing the Required Components

5.4.1 Installing the SAP BusinessObjects Mobile Application

For iOS

You install the

SAP BusinessObjects Mobile

application on your iOS device by downloading the application directly from the iTunes app store to your device.

Note

If you delete the existing app version from your device and install the latest version, you need to add new server connections, and all your password information and downloaded documents are lost. However, if you upgrade the application, your data and the server connections remain as they are.

5.4.2 Installing the SAP BusinessObjects Mobile Server

Pre-requisite:

Your Web Application server has the the same version as the SAP BusinessObjects BI platform server.

Note

The SAP BusinessObjects Mobile server can be installed on the same Web application server on which other

SAP BusinessObjects BI platform Web applications are deployed.

For BusinessObjects Enterprise XI 3.1, SP xx, and BI platform server versions up to 4.0, Support Package 4

For information on how to deploy the SAP BusinessObjects Mobile server based on the BI platform version, your

Web application server, and your operating system, refer to the Installation and Deployment Guide:

● http://help.sap.com/bomobilexi31 (for XI 3.1)

● http://help.sap.com/bomobile40 (for BI 4.0)

For BI platform 4.1, BI platform 4.0, Support Package 5 and higher

In version 4.0, Support Package 5 of the SAP BusinessObjects Mobile server and higher, and on BI 4.1, the

MobileBIService.war and MOBIServer.war files are auto-deployed. For more information on how to autodeploy the SAP BusinessObjects Mobile server, refer to the Installation and Deployment Guide:

22

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

● http://help.sap.com/bomobile41 (for BI 4.1)

● http://help.sap.com/bomobile40 (for BI 4.0)

Note

In release 5.1 and higher, the SAP BusinessObjects Mobile application for iOS only allows connections to trusted servers. A trusted server is a server with secure server certificates signed by certificate authorities

(CAs) that are trusted by iOS. If the server is not trusted and users try to add a server connection in the application, they encounter an error. For more information, refer to the related topic below.

Related Information

Ensuring that the Mobile Server is Trusted [page 23]

5.4.2.1 Ensuring that the Mobile Server is Trusted

If you are using HTTPS to connect to your SAP BusinessObjects Mobile server, the SAP BI application (for iOS and

Android) only allows connections to trusted servers. In order for the application to establish successful connections to a server, it is essential that one of the following conditions is met:

● Your server is trusted. This means that the server has secure server certificates from a Certificate Authority

(CA), and these CAs are trusted by iOS (such as Verisign, Thawte and others listed at http:// support.apple.com/kb/ht5012 )

● The root certificate of your server is installed on the client device (iPhone or iPad) as a profile, which means when the connection to the server is added in the application, the device can verify the server certificate.

If one of the above conditions is not met, and you try to add a server connection in the application, you encounter an error like this:

Connection to the server could not be established (MOB06031) (HTTP-1202) Details: The certificate for this server is invalid. You might be connecting to a server that is pretending to be <server1.servers.xxcompany.com>, which could put your confidential information at risk.

If you are not using a root certificate that is preinstalled on the user's device (such as a self-signed root certificate created by your company), you can distribute it in one of the following ways:

● Using the Mobile Device Management (MDM) tools

● Sending the root certificate as an email attachment

● Hosting the root certificate on a server and sharing the link

For example, to retrieve the root certificate of a trusted server and to share it with other users, follow the procedure below:

1. Open your browser settings and open the certificates (depending on your browser, the Manage Certificates or

Certificates option may appear in one of the tabs).

2. In the Certificates window, access the

Trusted Root Certification Authorities

tab as shown in the figure below:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

23

3. Select the trusted root certificate corresponding to your server, and choose

Export

. The Certificate Export wizard appears.

4. Follow the prompts to export the certificates.

The certificate is saved on your machine. Attach the certificate to an e-mail and send it to the required recipients.

Alternatively, host the root certificate on a server and send the URL to the users.

When users receive the certificate on their iOS device, they can choose the

Install

option when they tap the file or

URL. Once installed, the certificate appears on the device as a profile, and users can check the installation on their iPhone or iPad:

Settings General Profiles

.

Note

The SAP BusinessObjects Mobile application temporarily provides you with an option to bypass the verification of server certificate. However, this option should only be used in exceptional situations. We recommend that you install all the root certificates required for your servers on the device. Alternatively, get your current servers signed by a CA trusted by iOS. For a list of certificate authorities trusted by iOS, refer to http:// support.apple.com/kb/ht5012

This temporary option will be removed in a future release of the application.

To bypass the verification of server certificate and to establish connections to an uncertified server through the application, access

Application Settings Additional Settings Security Exceptions

and add the names or

24

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

the IP addresses (of the servers that you want to be ignored for verification) to the IGNORE SERVER TRUST

CERTIFICATE field.

5.4.3 Installing the SAP BusinessObjects BI Platform Server

For more information about installing the SAP BusinessObjects BI platform server, see the Business Intelligence

Platform Administrator Guide on the SAP Help Portal at http://help.sap.com/boall_en

Note

The SAP Business Objects Business Intelligence (BI) platform was previously known as the SAP

BusinessObjects Enterprise (BOE).

5.4.4 Installing the Configuration Server

To enable users to import connections from the Mobile server to the client application on their devices, you need to install a configuration server on your network.

Ensure that you have the same version of the Web application server and the SAP BusinessObjects BI platform server. To install a configuration server, perform the following steps:

1. Stop your Web application server.

2. Copy the MOBIServer.war from the following SAP BusinessObject BI platform location to the

<Web_app_server home directory>\webapps folder on your Web app server:

[Installation directory]\BusinessObjects Enterprise 12.0\java\applications

3. Start the Web app server again.

5.5 Creating and Configuring Server Connections (Including

BIOD and Sybase Afaria)

5.5.1 Creating, Importing and Sharing Server Connections

Using the App on Device

Refer to the User guide(available on the SAP Help portal at http://help.sap.com/bomobileios ) for information on the following:

1. How to configure BI platform server connections, BI On demand connections and SMP connections using the application on the device.

2. How to import connections from the Configuration server and the Sybase Afaria server to the application.

3. How to share configured connections with other users;

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

25

5.5.2 Configuring Connections for Importing to Mobile for iOS

Pre-requisite

You have the Configuration server/Sybase Afaria server installed on your network.

Configuring connections on the Configuration Server

To allow users to directly import mobile server connections to the iOS application, you need to update the following file on the Configuration server:

<webapps ROOT FOLDER>\MOBIServer\WEB-INF\server.properties

First make a back-up of the server.properties file. Set the following connection properties in the file for every connection that you want to make available for importing:

● DisplayName (mandatory)

● BOBJ_MOBILE_URL

● BOBJ_MOBILE_CMS

● BOBJ_MOBILE_AUTH_METHOD

● BOBJ_MOBILE_CONNECTION_TYPE_STRING

<AuthenticationType>

can have one of the following values:

● secEnterprise for Enterprise

● secLDAP for LDAP

● secWinAD for Windows AD

● secSAPR3 for SAP

<Connection Types>

can be set to one of the following values:

● BOESMP for SUP REST connection

● SUP for SUP legacy connection

Note

If you do not specify a value, it defaults to an Enterprise (BI platform) connection

For example, you can add a connection to the properties file as follows: mobi.connections=connection1 connection1.DisplayName=SAMPLE Connection connection1.BOBJ_MOBILE_URL=http://11.22.33.44:8080 connection1.BOBJ_MOBILE_CMS=55.66.77.88

connection1.BOBJ_MOBILE_AUTH_METHOD: secEnterprise connection1.BOBJ_MOBILE_CONNECTION_TYPE:1

26

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

Several users of the SAP BusinessObjects BI platform might have common user names. Therefore, when you configure BOBJ_MOBILE_USER_NAME, create a unique username.

Configuring connections on the Sybase Afaria server

To enable users to import connections from the Sybase Afaria server, you need to perform the following configuration:

1. In Sybase Afaria server, navigate to

Policy Edit iOS Enterprise Application Configuration

.

2. In the view that appears, upload and

save

the following XML file (in text format):

<?xml version="1.0" encoding="UTF-8"?>

<configuration_parameters>

<version>

123

</version>

<mobi>

<connections>

<connection id="connectionId1">

<property key ="BOBJ_MOBILE_URL" value = "http://10.50.111.111:8080"/>

<property key ="BOBJ_MOBILE_CMS_LOCKED" value = "true"/>

<property key ="BOBJ_MOBILE_CONNECTION_TYPE" value = "Default"/>

<property key ="BOBJ_MOBILE_AUTH_METHOD" value = "secEnterprise"/>

<property key ="BOBJ_MOBILE_CMS" value = "10.50.111.111"/>

<property key ="DisplayName" value = "connection name"/>

</connection>

<connections>

</mobi>

<configuration_parameters>

For each connection, set the connection properties as shown above. The properties for each connection are the same as in the server.properties file on the Configuration server.

Once you save this file on the Afaria server configuration, users can import connections from Sybase Afaria using the Mobile for iOS application.

5.5.3 Using SAP BI URLs For Managing Connections

5.5.3.1 Creating an SAP BI URL To Add a Corporate

Connection

By creating an SAP BI URL and making it available to users of the SAP BusinessObjects Mobile for iOS application, you enable users to easily add connections from the Mobile client to the SAP BusinessObjects BI platform server.

Users access the SAP BI URL on their iOS device (iPhone or iPad) and launch the

Connection

details screen. This screen is pre-populated with the values for all required input parameters (set by you). The users then save the connection.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

27

This avoids user errors made when a connection is created manually. This can occur when the user enters the input parameter values on the

Connection

details screen of the app, for example. Possible errors include an invalid

<Connection name>

, incorrect

<Server URL>

, invalid

<Server name>

.

To create the URL for a Corporate connection, you need to specify values for the required parameters using the following format: sapbi://addconnection?

ConnectionType=BOEConnection&name=ConnectionName&server_url=ServerName/

IP:Port&cms=ServerName/IP:Port&authType=AuthenticationType&default=yes/no where

<AuthenticationType>

can have one of the following values:

●

secEnterprise

for Enterprise

●

secLDAP

for LDAP

●

secWinAD

for Windows AD

●

secSAPR3

for SAP

For example, assume you are using the following parameters:

● Connection Name = Manufacturing

● Server URL = https://yoda.corp.com:8080

● CMS: Luke77

The corresponding URL for the above parameter values would be: sapbi://addconnection?name=Manufacturing&server_url=https://yoda.corp.com:

8080&cms=Luke77&authType=secEnterprise&default=no

Once the SAP BI URLis created, you can share it with users by e-mailing it to them.

Guidelines for URL Parameters

Connection Type

The connection type for a Corporate connection is a constant value: BOEConnection

Connection Name

You can use alphanumerics, hyphens, underscores, periods, and round brackets; the maximum number of characters allowed is 20.

Server URL

● You can use alphanumerics, hyphens ('-'), underscores ('_'), periods ('.'), colons (':'), and forward slashes ('/'); the maximum number of characters allowed is 281.

● If you want to connect to the mobile server in HTTPS mode, use HTTPS in the server URL. For example, https://<hostname>:<port> or https://<IP>:<port>.

● If you want to connect to the mobile server with reverse proxy, add the proxy context path after the port in the server URL. For example, http://<hostname>:<port>/<context path> or http://<IP>:<port>/<context path>.

28

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

5.5.3.2 Creating an SAP BI URL To Add an SUP Connection

Like Corporate connections, you can create a URL that allows users to create valid connections to the mobile server by using the Sybase Unwired Platform (SUP). This means, you prevent users from creating connections manually and thereby, from unintentionally creating invalid connections.

An SUP URL should have this format: sapbi://addconnection?

ConnectionType=SUPConnection&Application_ID=MobiApp&Sec_Config=MobiSec&server_url=10.5

3.129.243&SUP _Port=5001&SUP_Farm_ID=0

For an explanation of the parameter values in the above URL, refer to the following topic:

Adding IMO- and REST-Based SMP Connections to the Application On Device [page 49]

Related Information

Connecting to the SAP Mobility Platform (SMP) [page 41]

5.5.3.3 Using URLs To Delete Connections

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP Mobile for iOS app installed on their iPhone or iPad device.

Deleting all connections

To delete all active connections including Corporate, BIOD and SUP, use (or provide) the URL:

Sapbi://DeleteConnection?ConnectionType=ALL

Deleting specific Corporate connections

To remove a specific Corporate connection from the application, append the URL with the specific details of the connection as shown below:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

29

sapbi://DeleteConnection?

ConnectionType=BOEConnection&name=Tom&server_url=10.53.10.10:8080&cms=10.53.10.10&auth

Type=secEnterprise&default=no&user=UserName

Deleting a Sybase connection

To delete a Sybase connection, use the URL:

Sapbi://DeleteConnection?ConnectionType=SUPConnection

Deleting a BIOD connection

To delete a BIOD connection, use the URL:

Sapbi://DeleteConnection?ConnectionType=BIOD

Note

Before you delete an SUP connection, ensure that you

Deregister

from SUP using the

Settings

screen of the app. Otherwise, problems may occur when creating connections in future.

5.5.3.4 Creating a URL to Modify a Connection

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP Mobile for iOS app installed on their iPhone or iPad device.

Modifying Corporate Connections

To modify an existing Corporate connection, create a URL with the following format: sapbi://ModifyConnection?ConnectionType=BOEConnection&ConnectionName_Prev=Conn1&

ConnectionName_New=Conn2&Server_Url_Prev=10.53.10.10:8080&Server_Url_New=10.10.10.10

:1010&

CMS_Prev=10.53.10.10&CMS_New=10.10.10.10&AuthType_Prev=secEnterprise&AuthType_New=se cLDAP

&default=yes&UserName_Prev=Administrator

For every parameter in the URL, you need to include

30

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

1. <Parameter_Name>_Prev

Previous (current) value of the parameter

2. <Parameter_Name>_New

New value for the parameter

Note

Previous values of connection parameters in the URL help identify the specific Corporate Connection to be modified on the device.

Tapping this URL on the device, overwrites the parameter values of the existing Corporate connection with new values and the connection is modified.

Modifying SUP Connections

To modify an SUP connection, you need to pass the new parameter values in the SUP connection URL. Here is an example: sapbi://ModifyConnection?

ConnectionType=SUPConnection&Application_ID=MobiApp1&Sec_Config=MobiSec1&server_url=10

.10.10.10&SUP_Port=5001&SUP_Farm_ID=0

Tapping this URL on the device, overwrites the parameter values of the existing SUP connection with the new values passed in the URL and the connection is modified.

Note

Because only one SUP connection can exist for the SAP BI application on the device, the old values of the connection parameters do not need to be included in the URL. Passing the new values in the URL simply overwrites the old values with the new values.

To understand how an SUP Connection URL is generated, follow the link below.

Related Information

Adding IMO- and REST-Based SMP Connections to the Application On Device [page 49]

5.6 Single Sign On (SSO) Support on the Mobile BI Platform

This topic elaborates the Single Sign On support in the SAP BI application and the Mobile BI landscape.

The SAP BusinessObjects BI platform supports the Single Sign On capability with the following authentication types:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

31

● SAP

● LDAP

● WinAD

● Enterprise

The Mobile server and the SAP BI application do not support WinAD with SSO. Other authentication types are supported in the following ways:

1. SAP authentication in SSO is supported through SAP Logon tickets:

○ Through custom applications that log on to SAP systems, generate the required SAP logon token, and pass it back to the Mobile BI client (the SAP BI application).

○ Through a FORM-based URL (such as the SAP portal) that authenticates the user, and gives him/her the required MYSAPSSO2 cookie to proceed.

2. LDAP authentication in SSO is supported through CA SiteMinder.

3. Enterprise authentication in SSO is supported through trusted authentication (via X509 certificate,

REMOTE_USER or USER_PRINCIPAL).

The sub-sections of this chapter explain how to configure the Mobile server for SSO with various authentication types.

5.6.1 Configuring the Mobile Server for SSO Using Trusted

Authentication (REMOTE_USER or USER_PRINCIPAL or

X509 Certificate)

Deployment Options

● Basic or FORM authentication configured on the Mobile Server (required for REMOTE_USER or

USER_PRINCIPAL).

● SSL configured with certificate challenge (required for X509 certificate SSO)

Pre-requisites

1. The SAP BusinessObjects BI platform is configured for trusted authentication.

Note

For information on how to configure the BI platform for trusted authentication, refer to the following sources:

○ For BI platform server version 4.1, Support Package 3 (latest version), see section 9.2 in http:// help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp3_bip_admin_en.pdf

○ For BI platform server version 4.0, Support Package 9 (latest version), see section 8.2 in http:// help.sap.com/businessobject/product_guides/boexir4/en/xi4sp9_bip_admin_en.pdf

2. The required server certificates are installed on the BI platform key store and Mobile Server key store.

32

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

For information on how to install the server certificates, refer to the following sources:

○ For BI platform server version 4.1, Support Package 3 (latest version), see section 8.13 in http:// help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp3_bip_admin_en.pdf

○ For BI platform server version 4.0, Support Package 9 (latest version), see section 7.13 in http:// help.sap.com/businessobject/product_guides/boexir4/en/xi4sp9_bip_admin_en.pdf

Configuring the Mobile Server (MobileBIService) for Single-Sign-On Using

Trusted Authentication

You need to modify the authscheme.properties and sso.properties files on the Mobile server.

Note

1. By default, these properties files are deployed at the following location on the server machine:

<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config\default

Note

The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0

2. We recommend that you make a backup of these files before modifying them. Alternatively, save the files in a custom folder, and then modify them. For example, <WebAppsROOT>\webapps\MobileBIService

\WEB-INF\config\custom

Updating the authscheme.properties File

Open the authscheme.properties file and uncomment one of the following lines based on your requirements:

# allows you to configure User Principal with Trusted connection to BOE

#

TRUST_USER_PRINCIPAL=com.businessobjects.mobilebi.server.logon.impl.TrustedAuthUserP

rincipal

# allows you to configure X509 certificate with Trusted connection to BOE

# TRUST_X509=com.businessobjects.mobilebi.server.logon.impl.TrustedAuthX509

Updating the sso.properties File

Open the sso.properties file and define your CMS alias with the properties for your SAP BusinessObjects back end (for SSO through trusted authentication). To do this, uncomment the lines and specify the required parameters as described in the following table:

File (sso.properties) Parameter default.cms.identifier

Purpose

Specifies the default CMS ID

Example default.cms.identifier = cms1

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

33

File (sso.properties) Parameter

<id>.aliases

Purpose

Specifies the IP Address/Qualified name/Alias for your CMS

Example cms1.aliases = 10.X.X.X

Note

You can pass the FQN of the SAP

BusinessObjects back end server as well.

<id>.authentication.scheme

Specifies the authentication scheme

<id>.trusted.auth.sharedsec

ret

<id>.trusted.auth.user.retr

ieval

(set to 'TRUST_X509' for trust-based authentication mechanisms)

<id>.authentication.scheme= cms1.authentication.scheme=

TRUST

Specifies the secret key that is generated on the BI platform server for trusted authentication .

cms1.trusted.auth.sharedsec

ret=<Shared secret key configured with Business

Objects Backend>

Specifies the mechanism of retrieving user ID:

● Set to "REMOTE_USER" for

HttpServletRequest.getRe

moteUser() .

● Set to "USER_PRINCIPAL" for user principal.

● Set to "X509" when the authentication scheme is

TRUST_X509 cms1.trusted.auth.user.retr

ieval=REMOTE_USER

<id>.product.locale

<id>.preferred.viewing.loca

le

<id>.authentication.type

Specifies the default product locale

Specifies the preferred viewing locale cms1.product.locale=en cms1.preferred.viewing.loca

le=en

Specifies the authentication type (such as 'secLDAP'/

'secEnterprise'/'secSAPR3') cms1.authentication.type=se cSAPR3

Configuring the Client (Configuration Server) for Single-Sign-On Using Trusted

Authentication

Users can only add Single-Sign-On (SSO) connections in the application by importing connections from the configuration server. They cannot manually create connections. To enable users to import SSO connections using trusted authentication into the application, you need to create the required connections on the Mobile

Configuration server. Connections on the configuration server are created by updating the server.properties file.

To create connections on the Configuration server, perform the following steps:

1. Access the server.properties file at <WebAppsROOT>\webapps\MOBIServer\WEB-INF\config

\default

34

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

○ Before modifying the properties file, we recommend that you make a backup of the existing file. Save the default file in a custom folder (<WebAppsROOT>\MobileBIService\WEB-INF\config\custom) and then do your modifications.

○ The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0.

2. Add (or modify the values of) the following lines in the server.properties file and save the file:

SSOTrustedAuthBasicUserPrincipal.DisplayName:SSO_Trusted_Auth_Basic_UserPrincipal

SSOTrustedAuthBasicUserPrincipal.BOBJ_MOBILE_URL: http://10.X.X.X:port

SSOTrustedAuthBasicUserPrincipal.BOBJ_MOBILE_CMS: 10.X.X.X or FQN of the SAP

BusinessObjects Backend

SSOTrustedAuthBasicUserPrincipal.BOBJ_MOBILE_SSO_ENABLED:true

SSOTrustedAuthBasicUserPrincipal.BOBJ_MOBILE_SSO_TYPE:TRUSTED_AUTH_Basic

Note

The following parameters are mandatory for specifying the single-sign-on-trusted-authentication connection:

○ BOBJ_MOBILE_SSO_ENABLED:true

○ BOBJ_MOBILE_SSO_TYPE:TRUSTED_AUTH_Basic

Note

For a form-based trusted authentication setup, the SSO_TYPE is TRUSTED_AUTH_FORM. For example, for an X509 certificate setup, you specify the following configuration:

SSOX509Mandatory.BOBJ_MOBILE_SSO_ENABLED:true

SSOX509Optional.BOBJ_MOBILE_SSO_TYPE:X509Certificate

SSOX509Optional.BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORK:CertificateO ptional

The parameters SSOTrustedAuthBasicUserPrincipal and SSOX509Mandatory are user-defined and can have any name.

5.6.2 Configuring the Mobile Server for SSO Using CA

SiteMinder

Deployment Options

The application supports both Basic and Form based protected URL access, using the SiteMinder Web agent.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

35

Pre-requisites

1. You have configured the SAP BusinessObjects BI platform for LDAP authentication (using SiteMinder).

Note

For information on how to configure the BI platform for LDAP authentication, refer to the following sources:

○ For BI platform server version 4.1, Support Package 3 (latest version), see section 9.3 in http:// help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp3_bip_admin_en.pdf

○ For BI platform server version 4.0, Support Package 9 (latest version), see section 8.3 in http:// help.sap.com/businessobject/product_guides/boexir4/en/xi4sp9_bip_admin_en.pdf

2. You have configured the SiteMinder Web agent with the SiteMinder policy server that grants access to applications requiring URL access.

Configuring the Mobile Server (MobileBIService) for Single-Sign-On Using

SiteMinder

You need to modify the authscheme.properties and sso.properties files on the Mobile server.

Note

1. By default, these properties files are deployed at the following location on the server machine: C:

\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\MobileBIService\WEB-

INF\config\default

2. We recommend that you make a backup of these files before modifying them. Alternatively, you can modify these files and save them in a custom folder. For example, C:\Program Files\Apache Software

Foundation\Tomcat 6.0\webapps\MobileBIService\WEB-INF\config\custom

Updating the authscheme.properties File

Open the authscheme.properties file, and enable the SiteMinder authentication scheme by uncommenting the following line:

SiteMinder=com.businessobjects.mobilebi.server.logon.impl.SiteMinder

Updating the sso.properties File

Open the sso.properties file and define your CMS alias with the properties for your SAP BusinessObjects back end (for SiteMinder SSO). To do this, un-comment the lines and specify the required parameters as described in the following table:

File (sso.properties) Parameter default.cms.identifier

<id>.aliases

Purpose

Specifies the default CMS ID

Specifies the IP Address/Qualified name/Alias for your CMS

Example default.cms.identifier = cms1 cms1.aliases = 10.X.X.X

36

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

File (sso.properties) Parameter

<id>.cookie.name

Purpose Example

Note

You can also pass the FQN of the

SAP BusinessObjects back end server.

Specifies the name of cookie if it is not default.

Note

SiteMinder default cookie is

SMSESSION cms1.cookie.name=SMSESSION

<id>.product.locale

<id>.preferred.viewing.loca

le

<id>.authentication.type

Specifies the default product locale

Specifies the preferred viewing locale

Specifies the authentication type (such as 'secLDAP'/ 'secEnterprise') cms1.product.locale=en cms1.preferred.viewing.loca

le=en cms1.authentication.type=se cLDAP

Configuring the Client (Configuration Server) for Single-Sign-On Using

SiteMinder

Users can only add Single-Sign-On (SSO) connections in the application by importing connections from the configuration server. They cannot manually create connections. To enable users to import SSO connections into the application, you need to create the required connections on the Mobile Configuration server.

To create connections on the Configuration server, perform the following steps:

1. Access the server.properties file at <WebAppsROOT>\webapps\MOBIServer\WEB-INF\config

\default

Note

○ Before modifying the properties file, we recommend that you make a backup of the existing file.

Alternatively, modify the default file and save it in the custom folder (<WebAppsROOT>

\MobileBIService\WEB-INF\config\custom)

○ The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0

2. Add the following lines to the server.properties file and save it:

SiteMinder_Basic.DisplayName:SSO_SiteMinder_Basic

SiteMinder_Basic.BOBJ_MOBILE_URL:http://10.X.X.X:<port>

SiteMinder_Basic.BOBJ_MOBILE_CMS: 10.X.X.X //or FQN of the SAP BusinessObjects back end

SiteMinder_Basic.BOBJ_MOBILE_AUTH_METHOD:secLDAP //(authentication type)

SiteMinder_Basic.BOBJ_MOBILE_SSO_ENABLED:true

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

37

SiteMinder_Basic.BOBJ_MOBILE_SSO_TYPE:SiteMinder_BASIC

Note

The following parameters are mandatory for specifying a SiteMinder SSO connection:

SiteMinder_Basic.BOBJ_MOBILE_SSO_ENABLED:true

SiteMinder_Basic.BOBJ_MOBILE_SSO_TYPE:SiteMinder_BASIC

.

The parameter name SiteMinder_Basic is user-defined and can have any name.

Note

For a form-based SiteMinder setup, the SSO_TYPE is SiteMinder_FORM.

5.6.3 Configuring the Mobile Server for SSO Using SAP

Logon Tickets

Deployment Options

● You can use a custom application that logs into SAP systems, generates the required SAP logon token, and passes it back to the Mobile BI client.

● You can use a form-based URL (such as the SAP portal) that authenticates users, and gives them the required

MYSAPSSO2 cookie to proceed.

Pre-requisites

1. The SAP BusinessObjects BI platform is configured for SAP authentication.

Note

For information on how to configure the BI platform for SAP authentication, refer to the following sources:

○ For BI platform server version 4.1, Support Package 3 (latest version), see section 9.5 in http:// help.sap.com/businessobject/product_guides/sbo41/en/sbo41sp3_bip_admin_en.pdf

○ For BI platform server version 4.0, Support Package 9 (latest version), see section 8.5 in http:// help.sap.com/businessobject/product_guides/boexir4/en/xi4sp9_bip_admin_en.pdf

2. SAP systems are configured to generate SAP Logon tickets.

3. You must have one of the following:

○ A custom application deployed on an application server.

Note

The application should be capable of taking the authentication details through URL query parameters, or basic authentication. The application should then be able to connect to SAP systems, log on and

38

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

generate the SAP logon ticket, and should be able to pass the MYSAPSSO2 cookie back to the Mobile

BI client application. This cookie will be used for all future communications with the Mobile Server.

○ A form-based URL (such as the SAP portal) to log on and generate the required MYSAPSSO2 cookie.

Note

The URL can be a portal URL itself, but we recommend that you use a separate form-based URL for authentication.

Configuring the Mobile Server (MobileBIService) for Single-Sign-On Using SAP

Logon Tickets

You need to modify the authscheme.properties and sso.properties files on the Mobile server.

Note

1. By default, these properties files are deployed at the following location on the server machine: C:

\Program Files\Apache Software Foundation\Tomcat 6.0\webapps\MobileBIService\WEB-

INF\config\default

2. We recommend that you make a backup of these files before modifying them. Alternatively, you can modify these files and save them in a custom folder. For example, C:\Program Files\Apache Software

Foundation\Tomcat 6.0\webapps\MobileBIService\WEB-INF\config\custom

Updating the authscheme.properties File

Open the authscheme.properties file and uncomment the following line:

MYSAPSSO2=com.businessobjects.mobilebi.server.logon.impl.MySapSSO2

Updating the sso.properties File

Open the sso.properties file and define your CMS alias with the properties for your SAP BusinessObjects back end (for SSO via SAP Logon tickets). To do this, uncomment the lines and specify the required parameters as described in the following table:

File (sso.properties) Parameter default.cms.identifier

<id>.aliases

Purpose

Specifies the default CMS ID

Specifies the IP Address/Qualified name/Alias for your CMS

Example default.cms.identifier = cms1 cms1.aliases = 10.X.X.X

Note

You can also pass the FQN of the

SAP BusinessObjects back end server.

<id>.cookie.name

Specifies the name of cookie if it is not default.

cms1.cookie.name=MYSAPSSO2

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

39

File (sso.properties) Parameter Purpose

Note

SAP Logon ticket default cookie is

MYSAPSSO2

Example

<id>.product.locale

<id>.preferred.viewing.loca

le

<id>.authentication.type

Specifies the default product locale

Specifies the preferred viewing locale cms1.product.locale=en cms1.preferred.viewing.loca

le=en

Specifies the authentication type (such as 'secLDAP'/ 'secEnterprise') cms1.authentication.type=se cSAPR3

Configuring the Client (Configuration Server) for Single-Sign-On Using SAP

Logon Tickets

Users can only add Single-Sign-On (SSO) connections in the application by importing connections from the configuration server. They cannot manually create connections. To enable users to import SSO connections into the application, you need to create the required connections on the Mobile Configuration server. Connections on the configuration server are created by updating the server.properties file file.

To create connections on the Configuration server, perform the following steps:

1. Access the server.properties file at <WebAppsROOT>\webapps\MOBIServer\WEB-INF\config

\default

Note

○ Before modifying the properties file, we recommend that you make a backup of the existing file.

Alternatively, modify the default file and save it in the custom folder (<WebAppsROOT>

\MobileBIService\WEB-INF\config\custom)

○ The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0

2. 1. If you are using a custom application in your setup:

Add (or modify the values of) the following lines in the server.properties file and save the file:

SSOSAPCustomAppQueryString.DisplayName:SSO_SAP_Custom_App_QueryString

SSOSAPCustomAppQueryString.BOBJ_MOBILE_URL: http://10.X.X.X:port

SSOSAPCustomAppQueryString.BOBJ_MOBILE_CMS: 10.X.X.X or FQN of the SAP

BusinessObjects Backend

SSOSAPCustomAppQueryString.BOBJ_MOBILE_SSO_ENABLED:true

SSOSAPCustomAppQueryString.BOBJ_MOBILE_SSO_TYPE:SSO2COOKIE_QueryString

SSOSAPCustomAppQueryString.BOBJ_MOBILE_SSO_QUERY_URL =http://10.X.X.X:port/

CustomApp/SSO2Servlet?<param1>=val1&<param2>=val2

SSOSAPCustomAppQueryString.BOBJ_MOBILE_<PARAM1>=

SSOSAPCustomAppQueryString.BOBJ_MOBILE_<PARAM2>=

The parameter name SSOSAPCustomAppQueryString is user-defined and can have any name.

40

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

If you specify SSO2COOKIE_QueryString as the value for connection.BOBJ_MOBILE_SSO_TYPE, you require a custom application that is enabled to generate the MYSAPSSO2 cookie on successful authentication. Authentication is successful when the user provides parameter values that match what you have defined for param1 and param2 in BOBJ_MOBILE_SSO_QUERY_URL.

An example of <PARAM1> and <PARAM2> parameters is User name and Password. When the client

(user) provides the User name and Password values that match the values you have specified in your configuration, your custom application should be able to generate the MYSAPSSO2 cookie.

2. If you are using a form-based URL in your setup:

Add (or modify the values of) the following lines in the server.properties file and save the file:

SSOSAPCustomAppForm.DisplayName:SSO_SAP_Custom_App_Form

SSOSAPCustomAppForm.BOBJ_MOBILE_URL: http://10.X.X.X:port

SSOSAPCustomAppForm.BOBJ_MOBILE_CMS: 10.X.X.X or FQN of the SAP

BusinessObjects Backend

SSOSAPCustomAppForm.BOBJ_MOBILE_SSO_ENABLED:true

SSOSAPCustomAppForm.BOBJ_MOBILE_SSO_TYPE:SSO_Form

SSOSAPCustomAppForm.BOBJ_MOBILE_SSO_Form_URL =http://10.X.X.X:port/CustomApp/ index.html

SSOSAPCustomAppForm.BOBJ_MOBILE_SSO_COOKIE_NAME=MYSAPSSO2

SSOSAPCustomAppForm.BOBJ_MOBILE_<PARAM1>=

SSOSAPCustomAppForm.BOBJ_MOBILE_<PARAM2>=

The parameter name SSOSAPCustomAppForm is user-defined and can have any name.

Note

For SSO_Form, you require a custom application configured on the SAP J2EE application Server for form-based authentication. The app must be capable of generating the SAP Logon Ticket (similar to

SAP portal). The client (mobile application) opens the form in the application and asks users to log on

(by passing values for param1 and param2). When the user provides values for these form parameters, your custom application should be able to generate the MYSAPSSO2 cookie on successful authentication. Once generated, the MYSAPSSO2 cookie is used for all future communications with the Mobile Server.

5.7 Connecting to the SAP Mobility Platform (SMP)

To enable users of the mobile client applications to connect to the SAP BusinessObjects Mobile server using the

SAP Mobility Platform (SMP), you need to perform certain configuration steps. These include the following:

1. Install SMP on a machine on your network.

2. Configure SMP for use with the SAP BusinessObjects Mobile server.

3. Configure the SAP BusinessObjects Mobile server to connect to the SMP server.

As of the current application release, the SAP BusinessObjects Mobile BI landscape supports two types of SMP connections:

● SMP BOE Legacy (IMO-based traditional connection)

The following BI content types are supported for this connection type:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

41

○ Web Intelligence (HTML and as PDFs)

○ Crystal Reports (as PDFs)

○ Dashboards

○ Explorer (information spaces and exploration views)

● SMP BOE (REST-based new and recommended connection)

The following BI content types are supported for this connection type:

○ Web Intelligence (HTML and as PDFs)

○ Crystal Reports (HTML and as PDFs)

○ Dashboards

○ Explorer (information spaces and exploration views)

○ Analysis applications (created using the Design Studio)

○ Hyperlink objects

Note

1. You can use REST-based connections (connection type: "SMP BOE Connection") only if your SAP Mobility

Platform (SMP) version is:

○ SUP 2.2, Support Package 4, Patch 10391 or above

○ SUP 2.2, Support Package 5, Patch 10397 or above

○ SUP 2.3, Support Package 3, Patch 10398 or above

2. You can add multiple REST-based SMP connections in the application on an iOS device, but only a single

IMO-based (legacy) SMP connection at a time.

3. Do not add a combination of IMO- and REST-based connections in the application, as this may cause issues in rendering HTML content in the application.

4. All configuration details in the sub-topics of this chapter likewise apply to both IMO- and REST-based SMP connections. However, if you want to configure an SMP REST connection, you need to perform several additional steps of URL white-listing while configuring SMP for use with the SAP BusinessObjects Mobile server. These steps are clearly listed in the second sub-chapter (Configuring SMP for use with the SAP

BusinessObjects Mobile server).

5.7.1 Installing the SAP Mobility Platform (SMP)

For detailed information on installing the SAP Mobility Platform, go to http://infocenter.sybase.com/help/index.jsp

and navigate to

SAP Mobility Platform 2.1 ESD #1

Installation Guide for Runtime 2.1

5.7.2 Configuring SMP for Use With the Mobile Server

●

Creating a Security Configuration

To connect to a Mobile server, you are required to create a security configuration. To create a security configuration perform the following steps:

1. On the SMP server machine, launch the

Mobility Server Cluster Management View

.

42

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

2. In the

Mobility Platform Cluster

panel that appears on the left, select

Security

.

3. Choose

New

in the

General

tab on the right-side panel.

The

Create Security Configuration

window appears.

4. Enter a name for the new security configuration (for example

<MobiSec>

), and choose

OK

.

The new security configuration appears within the

Security

folder on the left panel.

Note

Make a note of the security configuration name. You need this name to configure the SMP connection on the client application.

5. Select the new security configuration in the

Mobility Platform Cluster

panel.

6. Select the

Authentication

tab on the right panel and choose

New

.

The

Add Provider

window appears.

7. In the Authentication Provider drop-down, select

HttpAuthenticationLoginModule

.

8. In the properties that appear beneath the dropdown, enter a URL in this format: http://<Mobile BI Server>/MobileBIService/SUP/VerifyUser/<Security Config name>

For example: http://10.10.10.10:8080/MobileBIService/SUP/VerifyUser/MobiSec

9. Choose OK to close the

Add Provider

window.

The authentication provider you have added appears in the Authentication tab of the new Security

Configuration.

10. Go to the

General

tab and choose

Validate

. This allows you to validate the changes to the security configuration before applying them to the SMP server. Then choose

Apply

.

The security configuration you have added is saved on the Mobility platform server.

Note

You can connect to multiple Mobile servers by creating a security configuration for each one.

●

Creating an Application

1. On the SMP server machine, launch the

Mobility Server Cluster Management View

.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

43

2. In the

Mobility Platform Cluster

panel on the left, select

Applications

.

3. Choose

New

in the

Applications

tab on the right-side panel.

The

Application Creation

window appears.

4. In the

Application ID

field, enter MobiApp.

5. In the Display name field, enter a display name.

6. Select the security configuration from the drop-down (

<MobiSec>

configured in step one).

7. Choose

Finish

to complete the procedure.

●

Creating an Application Connection Template

To create a connection between your Mobile server and the Application ID (MobiApp), you are required to create an application connection template.

Note

You can either create a (new) application connection template or you can

edit

the existing application connection template that is automatically created when you create the application (in the last procedure).

To create an application connection template, perform the following steps:

1. In the

Mobility Platform Cluster

panel on the left, choose

Applications

.

2. Choose

Application Connection Template

.

3. Choose

New

.

The Template pop up appears.

44

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

4. In the

Template name

field, enter the name for the template.

5. In the

Base template

field, choose Default.

6. Choose

Application Settings

, and perform the following substeps:

1. In the

Application Identifier

field, choose MobiApp as the value.

2. In the

Domain

field, choose Default as the value.

3. In the

Security Configuration

field, choose the security configuration you want to connect to.

Note

Since you are creating a new application connection template, the

Security Configuration

should be different from the value (Mobisec) configured while creating the application. If the Application

identifier (application ID), the Domain and the Security Configuration values that you enter in this step are the same as the ones you specified while creating the application, the system does not allow you to proceed.

7. Select

Proxy

, in the

Application Endpoint

, enter the URL of the Mobile Server provided by your administrator. The value should have the format: http://<Mobile BI Server>/MobileBIService/MessageHandlerServlet

For example, http://10.10.10.10:8080/MobileBIService/MessageHandlerServlet

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

45

8. Choose

Ok

.

Whitelisting the Application Endpoint URL (for an SMP BOE Legacy connection)

This section is applicable to you if you are using the SMP server version 2.2.

If your SMP server version is 2.2, you need to whitelist the application end point URL.

To whitelist a URL, perform the below procedure:

1. After creating the application connection template, in the "Mobility Server Cluster Management View", choose

Domains

>

Default

>

Connections

.

2. In the

Manage Connections

section that appears within the Connections tab on the right of the window, choose

New

.

3. The

Add Connection Pool

window appears as shown below:

46

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

4. Perform the following substeps in the

Add Connection Pool

window:

Enter a name for the Connection pool name.

Select "Proxy" for the Connection pool type.

Specify the Application Endpoint URL in the Address field. and choose

Ok

.

Note

The value of Address (Application Endpoint URL) should be of the format http://<Mobile BI

Server>/MobileBIService

Whitelisting the Application Endpoint URL for a REST (SMP BOE) connection

This section is applicable to you if you are using the SMP server version 2.2.

If your SMP server version is 2.2, you need to whitelist the application end point URL.

To whitelist a URL, perform the below procedure:

1. After creating the application connection template, in the "Mobility Server Cluster Management View", choose

Domains

>

Default

>

Connections

.

2. In the

Manage Connections

section that appears within the Connections tab on the right of the window, choose

New

.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

47

The

Add Connection Pool

window appears.

3. Perform the following sub-steps in the

Add Connection Pool

window:

Enter a name for the Connection pool name.

Select "Proxy" for the Connection pool type.

Specify the Application Endpoint URL in the Address field. and choose

Ok

.

Note

The value of Address (Application Endpoint URL) should be of the format http://<Mobile BI

Server>/MobileBIService

4. In the left panel, select

Security

in the default domain, and choose

Assign

.

The list of security configurations that are not yet assigned to the default domain appear on the

Assign

Security Configurations

screen.

5. Select the required security configuration, and choose

OK

.

5.7.3 Configuring Mobile Server to Connect to the SMP

Server

To configure the SAP BusinessObjects Mobile server for connecting to the Sybase Mobility Platform, perform the following steps:

1. Deploy MobileBIService.war file (version 4.0.3/ 4.0.2.13 or later) on your Web application server.

2. Locate the SUP.properties file.

Note

The file location of SUP.properties is the same as for the mobi.properties file. For information on the location of mobi.properties file based on your Mobile BI platform server version, see the related topic in this chapter.

3. Insert the following lines in the file:

MobiSec.cms=11.22.33.44

MobiSec.auth=secEnterprise

Note

○ You will notice that these lines have already been placed as comments in the SUP.properties file.

Change the lines from comments to code and update the values of the parameters.

○ Note that MobiSec is the name that you specified for the security configuration setting when you added it to the SMP server with the Sybase Control Center.

○ Possible values for authentication are:

<secEnterprise>

,

<secLDAP>

,

<secWinAD>

,

<secSAPR3>

.

Also, make sure that the specified IP address of the CMS is correct.

4. Save the SUP properties file and restart the Web Application server.

5. To verify that the settings on the Mobile server are correct, access this URL in your browser: http://<mobi-server>/MobileBIService/SUP/VerifyUser/MobISec

48

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

The browser displays an authentication dialog. If you enter a valid user name and password for the CMS specified in the configuration, you should see an empty page.

(MobiSec is the security configuration name in this particular example. Change it to the name you have used in your settings.)

Related Information

Mobile Server and Property File Locations Matrix [page 66]

5.7.4 Adding IMO- and REST-Based SMP Connections to the

Application On Device

To add an IMO-based SMP connection, access the application

Settings

, tap on

Create New Connection

and select

SMP BOE Connection (Legacy)

as the connection type. .

To add a REST-based SMP connection, access the application

Settings

, tap on

Create New Connection

and select

SMP BOE Connection

as the connection type as .

The "Create New Connection" screens for REST- and IMO-based connections that appear after you select the connection type are shown in the figure below. They have some common and some unique parameters.

● The

Security Configuration

name is based on the value you have specified when configuring the SMP server for Mobile server.

● See the table below for the server, port and farm ID values that you need to provide to users (depending on whether you are using a relay server):

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

49

Note

A "relay server" is a Web server set up as an intermediary between the client app and the SMP server. It enables secure load-balanced communication between mobile devices (client applications) and the SAP

Mobility Platform server.

SMP Connection Parameter

Server

Port

Farm ID

Value when Relay Server Not used Value when Relay Server Used

Address of SMP server (without port ) Address of relay server (without port)

5001 (default)

0

'80' for HTTP and '443' for HTTPS

Specific to SMP server (non-zero value)

Note

○ If the connection between the application and the SMP server/ relay server requires HTTPS:

Prefix the server name with "https://" in the

Server

field. For example, if the SMP server name is relayserver.acme.org, enter https://relayserver.acme.org in the

Server

field.

Ensure that the SMP server version is 2.1.3 or above.

●

User Name

and

Password

are the credentials for the CMS configured for the security configuration name in

Mobile server's SUP.properties file. You need to provide these credentials to the users.

Note

You can configure an SMP connection on your device and share the connection with users (for corporate connections). When you share a connection, users will receive an email containing the URL of the SMP connection and they can directly add the connection on their device, without having to configure it manually.

For example, when you share the above connection, the following URL is generated by the app in an email draft: sapbi://addconnection?

ConnectionType=SMPConnection&Application_ID=MobiApp&Sec_Config=MobiSec&server_url

=10.53.129.243&SMP_Port=5001&SMP_Farm_ID=0

●

Proxy

(for SMP REST connections) is the same as what you specify when white-listing the application endpoint URL.

●

Additional Back-End Credentials

(for SMP REST connections) are the credentials that you use for logging onto the BI platform (back end). In case of REST, the credentials that you use to register the application with the

SAP Mobility Platform can be different from the credentials that you use to log on to the back end. If both set of credentials are the same, you can keep this property disabled while creating the connection.

5.7.5 Removing an SMP Connection from the App

To remove an existing SMP connection from the app, follow the below procedure:

50

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

1.

Deregister

from SMP and delete the SMP connection using the

Settings

screen of the app.

2. In the SAP Control Center (SCC), verify that the

Applications Application Connections

tab does not display the user in the list. If the list displays the user, remove it.

5.7.6 Configuring Single Sign-On (SSO) in SMP Environment

Prerequisites

You have:

1. The SAP BusinessObjects BI platform configured for X509 SSO authentication.

2. The SAP Mobility Platform (version 2.2.4 and above) configured for X509 authentication.

Configuring the SMP Server for X509 Authentication-Based Single Sign-On

Configure the SMP server for use with the SAP BusinessObjects Mobile server as described in the related topic of this chapter, with only the following difference in step 7 of creating a security configuration:

● In the

Authentication Provider

drop-down, instead of selecting HttpAuthenticationLoginModule, select

CertificateAuthenticationLoginModuleand set the control flag as "Optional". Then add the following properties:

Trusted Certificate Store Type=JCEKS

Trusted Certificate Store Provider=SunJCE

Trusted Certificate Store Password=******

Validate Certificate Path=”True”

Trusted Certificate Store=DREVE:\Sybase\UnwiredPlatform\Servers\UnwiredServer

\Repository\Security

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

51

Configuring the Mobile Server (MobileBIService) for Single Sign-On Using

X509 Authentication

You need to modify the authscheme.properties and sso.properties files on the Mobile server.

Note

1. By default, these properties files are deployed at the following location on the server machine:

<WebAppsROOT>\webapps\MobileBIService\WEB-INF\config\default

Note

The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0

2. We recommended that you back up these properties files before modifying them. Save the files in a custom folder, and then modify them. For example, <WebAppsROOT>\webapps\MobileBIService\WEB-INF

\config\custom

Updating the authscheme.properties File

52

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Open the authscheme.properties file and un-comment the following line:

TRUST_X509=com.businessobjects.mobilebi.server.logon.impl.TrustedAuthX509

Updating the sso.properties File

Open the sso.properties file and define your CMS alias with the properties for your SAP BusinessObjects back end (for SSO via trusted authentication). For this, uncomment the lines and specify the required parameters as described in the following table:

File (sso.properties) Parameter default.cms.identifier

<id>.aliases

Purpose

Specifies the default CMS ID

Specifies the IP address/qualified name/alias for your CMS

Example default.cms.identifier = cms1 cms1.aliases = 10.X.X.X

Note

You can pass the FQN of the SAP

BusinessObjects back-end server as well.

<id>.authentication.scheme

<id>.trusted.auth.sharedsec

ret

<id>.trusted.auth.user.retr

ieval

<id>.product.locale

<id>.preferred.viewing.loca

le

<id>.authentication.type

Specifies the authentication scheme.

Specifies the secret key that is generated on the BI platform server for trusted authentication .

Specifies the mechanism of retrieving user ID.

Specifies the default product locale

Specifies the preferred viewing locale

Specifies the authentication type (such as 'secLDAP'/ 'secWinAD'/

'secEnterprise'/'secSAPR3')

<id>.authentication.scheme= cms1.authentication.scheme=

TRUST cms1.trusted.auth.sharedsec

ret=<Shared secret key configured with Business

Objects Backend> cms1.trusted.auth.user.retr

ieval=X509 cms1.product.locale=en cms1.preferred.viewing.loca

le=en cms1.authentication.type=se cEnterprise

Configuring the Client (Configuration Server) for Single Sign-On Using X509

Authentication

Users can add single sign-on (SSO) connections in the application only by importing connections from the configuration server. (Users cannot manually create them.) So that users can import SSO connections via X509 authentication in the application, you need to create the required connections on the mobile Configuration server.

Connections on the configuration server are created by updating the server.properties file file.

To create connections on the Configuration server, perform the following steps:

1. Access the server.properties file available at <WebAppsROOT>\webapps\MOBIServer\WEB-INF

\config\default

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

53

Note

○ Before modifying the properties file, it is recommended to take a back up of the existing file. Save the default file in a custom folder (<WebAppsROOT>\MobileBIService\WEB-INF\config\custom) and then do your modifications.

○ The <WebAppsROOT> is the folder on your specific application server, for example C:\Program

Files\Apache Software Foundation\Tomcat 6.0

2. Add (or modify the values of) the following lines in the server.properties file and save it:

SUPSMP_X509.DisplayName:SUP_SSO_REST_X509

SUPSMP_X509.BOBJ_MOBILE_CONNECTION_TYPE_STRING=BOESMP

SUPSMP_X509.BOBJ_MOBILE_SUP_SERVER = https://10.208.107.23:8002

SUPSMP_X509.BOBJ_MOBILE_SUP_PROXY_CONN =X509

SUPSMP_X509.BOBJ_MOBILE_SUP_SECURITY_CONFIG_NAME =X509

SUPSMP_X509.BOBJ_MOBILE_SSO_ENABLED=true

SUPSMP_X509.BOBJ_MOBILE_SSO_TYPE:X509Certificate

SUPSMP_X509.BOBJ_MOBILE_CERTIFICATE_REQUIRED_FOR_NETWORK:CertificateMandatory

Note

The following parameters are mandatory for specifying a single sign-on X509authentication-based connection:

○ BOBJ_MOBILE_SSO_ENABLED:true

○ BOBJ_MOBILE_SSO_TYPE:X509Certificate

Note

To access Design Studio content (Analysis applications) while using the SAP BI application in a REST-based

SMP environment, you need to have one of the following SMP server versions:

● SUP 2.2, Support Package 4, Patch 10391

● SUP 2.2, Support Package 5, Patch 10397

● SUP 2.3, Support Package 3, Patch 10398

Related Information

Configuring SMP for Use With the Mobile Server [page 42]

5.7.7 Restrictions of the SMP BOE-Legacy Environment

If you are using an IMO-based (SMP BOE [Legacy]) server connection in your mobile set up, the following BI documents based on HTML 5 rendering do not appear in the application:

● Analysis applications

● Interactive Crystal Reports

54

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

● Dashboard documents

(However, if the Dashboard documents being viewed on mobile are self-contained and do not have database connectivity, they work in the legacy environment without any issues.)

Note

1. Due to the above restrictions in the legacy SMP environment, we strongly recommend you use RESTbased (SMP BOE) connections in your setup. REST connections also support access to a greater number of BI content types compared to IMO.

2. You can use REST-based connections (connection type: "SMP BOE Connection") only if your SAP Mobility

Platform (SMP) version is :

○ SUP 2.2, Support Package 4, Patch 10391 or above

○ SUP 2.2, Support Package 5, Patch 10397 or above

○ SUP 2.3, Support Package 3, Patch 10398 or above

If you want to continue using the legacy environment, refer to the workarounds to overcome the restriction stated above.

Workaround for viewing all BI documents with the application in a Legacy SMP

BOE (IMO) environment

You can have a direct connection from the SAP BI application to the SAP BusinessObjects Mobile server

(MobileBIService). This can be established by opening the Web application server port on the external firewall and allowing direct access from the SAP BI app to the Mobile server, while retaining the SUP connection in parallel.

SMP would continue to offer authentication and authorization features, however for data access, the direct connection to the Mobile server would be used by the application.

Note

For Dashboards (with database connectivity) to work in the SUP environment, ensure that the following conditions are met:

● The SAP BI app has direct connectivity with the DSWSBOBJ Web services.

● DSWSBOBJ Web services and the MobileBIService.war are deployed on the same machine (server).

● The following URLs are whitelisted when configuring SUP in your setup:

○ http://<BOE address>/dswsbobje/services/Session

○ http://<BOE address>/dswsbobje/services/XcelsiusWebServices

For information on how to white-list URLs, refer to the related topic of this chapter.

Workaround for viewing Crystal Reports documents as PDFs in a Legacy SMP

BOE (IMO) environment

Consider the following scenarios:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

55

● You do not want to expose the Mobile server (of any version) in your setup directly to the Internet. SUP is a part of the environment between the client app and the Mobile server.

● You have upgraded your BI platform/ Mobile server to 4.0, Support Package 5 in the SUP environment, and so you cannot view Crystal Reports documents (the default behavior of Crystal Reports on the SP5 server is interactive, and interactive Crystal Reports are not rendered with SUP in the current app).

In both the above cases you can view the Crystal Reports documents in PDF format (as in prior versions of the app) in the SUP environment, with the help of the following configuration:

1. Access the following file on the Mobile server:

[Tomcat_InstallDir]\webapps\MobileBIService\WEB-INF\clientsettings.properties

2. Add the following parameter with the value 'true': feature.crystal.showAsPDF=true

3. Save the clientsettings.properties file and restart the Web app server.

Related Information

Configuring SMP for Use With the Mobile Server [page 42]

5.8 Using SAP BI URLs For Managing Connections

5.8.1 Creating an SAP BI URL To Add a Corporate

Connection

By creating an SAP BI URL and making it available to users of the SAP BusinessObjects Mobile for iOS application, you enable users to easily add connections from the Mobile client to the SAP BusinessObjects BI platform server.

Users access the SAP BI URL on their iOS device (iPhone or iPad) and launch the

Connection

details screen. This screen is pre-populated with the values for all required input parameters (set by you). The users then save the connection.

This avoids user errors made when a connection is created manually. This can occur when the user enters the input parameter values on the

Connection

details screen of the app, for example. Possible errors include an invalid

<Connection name>

, incorrect

<Server URL>

, invalid

<Server name>

.

To create the URL for a Corporate connection, you need to specify values for the required parameters using the following format: sapbi://addconnection?

ConnectionType=BOEConnection&name=ConnectionName&server_url=ServerName/

IP:Port&cms=ServerName/IP:Port&authType=AuthenticationType&default=yes/no where

<AuthenticationType>

can have one of the following values:

●

secEnterprise

for Enterprise

●

secLDAP

for LDAP

56

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

●

secWinAD

for Windows AD

●

secSAPR3

for SAP

For example, assume you are using the following parameters:

● Connection Name = Manufacturing

● Server URL = https://yoda.corp.com:8080

● CMS: Luke77

The corresponding URL for the above parameter values would be: sapbi://addconnection?name=Manufacturing&server_url=https://yoda.corp.com:

8080&cms=Luke77&authType=secEnterprise&default=no

Once the SAP BI URLis created, you can share it with users by e-mailing it to them.

Guidelines for URL Parameters

Connection Type

The connection type for a Corporate connection is a constant value: BOEConnection

Connection Name

You can use alphanumerics, hyphens, underscores, periods, and round brackets; the maximum number of characters allowed is 20.

Server URL

● You can use alphanumerics, hyphens ('-'), underscores ('_'), periods ('.'), colons (':'), and forward slashes ('/'); the maximum number of characters allowed is 281.

● If you want to connect to the mobile server in HTTPS mode, use HTTPS in the server URL. For example, https://<hostname>:<port> or https://<IP>:<port>.

● If you want to connect to the mobile server with reverse proxy, add the proxy context path after the port in the server URL. For example, http://<hostname>:<port>/<context path> or http://<IP>:<port>/<context path>.

5.8.2 Creating an SAP BI URL To Add an SUP Connection

Like Corporate connections, you can create a URL that allows users to create valid connections to the mobile server by using the Sybase Unwired Platform (SUP). This means, you prevent users from creating connections manually and thereby, from unintentionally creating invalid connections.

An SUP URL should have this format: sapbi://addconnection?

ConnectionType=SUPConnection&Application_ID=MobiApp&Sec_Config=MobiSec&server_url=10.5

3.129.243&SUP _Port=5001&SUP_Farm_ID=0

For an explanation of the parameter values in the above URL, refer to the following topic:

Adding IMO- and REST-Based SMP Connections to the Application On Device [page 49]

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

57

Related Information

Connecting to the SAP Mobility Platform (SMP) [page 41]

5.8.3 Using URLs To Delete Connections

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP Mobile for iOS app installed on their iPhone or iPad device.

Deleting all connections

To delete all active connections including Corporate, BIOD and SUP, use (or provide) the URL:

Sapbi://DeleteConnection?ConnectionType=ALL

Deleting specific Corporate connections

To remove a specific Corporate connection from the application, append the URL with the specific details of the connection as shown below: sapbi://DeleteConnection?

ConnectionType=BOEConnection&name=Tom&server_url=10.53.10.10:8080&cms=10.53.10.10&auth

Type=secEnterprise&default=no&user=UserName

Deleting a Sybase connection

To delete a Sybase connection, use the URL:

Sapbi://DeleteConnection?ConnectionType=SUPConnection

Deleting a BIOD connection

To delete a BIOD connection, use the URL:

58

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Sapbi://DeleteConnection?ConnectionType=BIOD

Note

Before you delete an SUP connection, ensure that you

Deregister

from SUP using the

Settings

screen of the app. Otherwise, problems may occur when creating connections in future.

5.8.4 Creating a URL to Modify a Connection

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP Mobile for iOS app installed on their iPhone or iPad device.

Modifying Corporate Connections

To modify an existing Corporate connection, create a URL with the following format: sapbi://ModifyConnection?ConnectionType=BOEConnection&ConnectionName_Prev=Conn1&

ConnectionName_New=Conn2&Server_Url_Prev=10.53.10.10:8080&Server_Url_New=10.10.10.10

:1010&

CMS_Prev=10.53.10.10&CMS_New=10.10.10.10&AuthType_Prev=secEnterprise&AuthType_New=se cLDAP

&default=yes&UserName_Prev=Administrator

For every parameter in the URL, you need to include

1. <Parameter_Name>_Prev

Previous (current) value of the parameter

2. <Parameter_Name>_New

New value for the parameter

Note

Previous values of connection parameters in the URL help identify the specific Corporate Connection to be modified on the device.

Tapping this URL on the device, overwrites the parameter values of the existing Corporate connection with new values and the connection is modified.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

59

Modifying SUP Connections

To modify an SUP connection, you need to pass the new parameter values in the SUP connection URL. Here is an example: sapbi://ModifyConnection?

ConnectionType=SUPConnection&Application_ID=MobiApp1&Sec_Config=MobiSec1&server_url=10

.10.10.10&SUP_Port=5001&SUP_Farm_ID=0

Tapping this URL on the device, overwrites the parameter values of the existing SUP connection with the new values passed in the URL and the connection is modified.

Note

Because only one SUP connection can exist for the SAP BI application on the device, the old values of the connection parameters do not need to be included in the URL. Passing the new values in the URL simply overwrites the old values with the new values.

To understand how an SUP Connection URL is generated, follow the link below.

Related Information

Adding IMO- and REST-Based SMP Connections to the Application On Device [page 49]

5.8.5 Creating SAP BI URLs to Add Single Sign On

Connections

This chapter explains the syntax for creating SAP BI URLs using which mobile users can directly add Single Sign

On (SSO) connections in the SAP BI application on their devices.

SAP BI URL Syntax (With example values) SSO

Connection

Type

X509 SSO

Mandatory

X509 SSO

Optional

SSO2Cookie

sapbi://addconnection/?cms=10.X.X.X&isSSO=YES&server_url=https://

ServerUrl:port&isCertificateRequired=CertificateMandatory&connection_name

=sso_X509Certificate_Mandatory&SSOType=X509Certificate&authType=secEnterp rise&ConnectionType=BOEConnection sapbi://addconnection/?cms=10.X.X.X&isSSO=YES&server_url=https://

ServerUrl:port&isCertificateRequired=CertificateOptional&connection_name= sso_X509Certificate_Optional&SSOType=X509Certificate&authType=secEnterpri se&ConnectionType=BOEConnection sapbi://addconnection/?

cms=10.X.X.X&isSSO=YES&server_url=ServerUrl:Port&connection_name=SSO2Cook ie&SSOType=SSO2Cookie&authType=secEnterprise&ConnectionType=BOEConnection

60

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

SSO

Connection

Type

SITE MINDER

SSO Basic

Auth

SUP SSO IMO

SSO2Cookie

SUP SSO

REST

SSO2Cookie

SAP BI URL Syntax (With example values) sapbi://addconnection/?

cms=10.X.X.X&isSSO=YES&server_url=ServerUrl:port&connection_name=sso_Site minder_Basic_Auth&SSOType=SITEMINDER_BASIC&authType=secLDAP&ConnectionTyp e=BOEConnection sapbi://addconnection/?

ConnectionType=BOESUPConnection&SUP_Farm_ID=0&Sec_Config=SecurityConfigNa me&server_url=SUPServer_Url&isSSO=YES&connection_name=SUP_SSO_IMO_SSO2Coo kie&SSOType=SSO2COOKIE&Application_ID=MobiApp&SUP_Port=5001 sapbi://addconnection/?

ConnectionType=BOESMPConnection&isSSO=YES&server_url=SUP_Server_URL&conne ction_name=SUP_SSO_REST_SSO2Cookie&proxyConnection=MobiApp&SSOType=SSO2CO

OKIE&Application_ID=MobiApp&Sec_Config=SecurityConfigName

SUP SSO X509

REST

sapbi://addconnection/?

ConnectionType=BOESMPConnection&isSSO=YES&server_url=Mutual_SSL_SUPServer

_Url&connection_name=SUP_SSO_REST_X509&proxyConnection=X509&SSOType=X509C ertificate&Application_ID=MobiApp&Sec_Config=SecurityConfigName

TRUSTED

AUTH Basic

USER_PRINCI

PAL

TRUSTED

AUTH Basic

REMOTE_USE

R

sapbi://addconnection/?

cms=10.X.X.X&isSSO=YES&server_url=Server_url&connection_name=SSO_Trusted_

Auth_Basic_UserPrincipal&SSOType=TRUSTED_AUTH_Basic&authType=secEnterpris e&ConnectionType=BOEConnection sapbi://addconnection/?

cms=10.X.X.X&isSSO=YES&server_url=Server_Url&connection_name=SSO_Trusted_

Auth_Form_RemoteUser&SSOType=TRUSTED_AUTH_FORM&authType=secEnterprise&Con nectionType=BOEConnection

SSO SAP

Custom App

FORM

sapbi://addconnection/?

cms=10.X.X.X&ssoCookieName=MYSAPSSO2&isSSO=YES&server_url=Server_url:Port

&connection_name=SSO_SAP_Custom_App_Form&SSOType=SSO_Form&authType=secEnt erprise&ConnectionType=BOEConnection

SSO SAP

Custom Query

String

sapbi://addconnection/?

cms=10.X.X.X&isSSO=YES&server_url=Server_Url:port&sso2CookieQueryURL=Quer yUrl:port/AuthService/SSO2Servlet?

j_username=EnterUserName&j_password=EnterPassword&connection_name=SSO_SAP

_Custom_App_QueryString&SSOType=SSO2COOKIE_QueryString&authType=secEnterp rise&ConnectionType=BOEConnection

Related Information

Single Sign On (SSO) Support on the Mobile BI Platform [page 31]

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

61

5.9 Configuring Application's Behavior by Specifying

Properties on the Server

Pre-requisites

1. You have the SAP BusinessObjects Mobile server and the SAP BusinessObjects BI platform server in your network.

2. You have the SAP BusinessObjects Mobile (SAP BI) application for iOS installed on your iPhone/ iPad device.

You can configure some chief behavioral aspects of the application by configuring the client settings on the SAP

BusinessObjects Mobile server.You configure client settings using the

clientsettings.properties

file on the Mobile server.

Note

● The location of clientsettings.properties file on the SAP BusinessObjects Mobile server is based on the server version you are using. To find the file-path for your specific server version, refer to the related topic of this chapter.

● If you are using the BI platform 4.1 and higher versions, you can also use the Central Management

Console (CMC) interface for configuring client settings. For information on how to configure client settings using the CMC, see the related topic of this chapter.

Following is a typical default configuration of the clientsettings.properties file: savePassword=false offlineStorage=false offlineStorage.ttl=365 offlineStorage.appPwd=true

Note

If you are using BI platform 4.1 or BI 4.1 SP1, the negative mobile application rights that are granted via the

CMC take precedence over the above client settings (properties). For example, if the right To save documents

to the local store of a device is not granted to the user in the CMC, users cannot download BI documents to their device even if the offlineStorage property is set to true in the client settings.

Also note that if the right to save documents is granted in the CMC, but offlineStorage=false in client settings, users cannot download BI documents to the mobile device. Only when the right is granted and offlineStorage=true that users can download/save BI documents to the device. For information on how to grant the application rights using the CMC, refer to the related topic of this chapter.

You can add the following features to the file, if you need to customize some of these based on your requirements:

● feature.email.enabled

● feature.collaboration.enabled

● feature.annotation.enabled

● feature.streamwork.enabled

62

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

● feature.jam.enabled

● feature.jam.url

● feature.jam.consumer.key

● feature.jam.consumer.secret

● feature.jam.callback.urlverb

● feature.help.enabled

● feature.help.url

● feature.help.video.enabled

● feature.help.video.playlistfeed

● feature.webi.refresh.enabled

● feature.webi.reportTitle.enabled

● feature.rel.legacy.mode

● feature.webi.default.palette.enabled

● feature.dashboard.sup.enabled

The above listed features are also configurable using the application SDK. For information on the significance and impact of above features on the application, see the Developer's Guide available at http://help.sap.com/ bomobileios .

Related Information

Using the CMC to Define Properties on BI Platform 4.1 [page 66]

Mobile Server and Property File Locations Matrix [page 66]

Granting Users the SAP BusinessObjects Mobile Application Rights on the BI Platform [page 64]

5.9.1 Using URLs To Delete Connections

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP Mobile for iOS app installed on their iPhone or iPad device.

Deleting all connections

To delete all active connections including Corporate, BIOD and SUP, use (or provide) the URL:

Sapbi://DeleteConnection?ConnectionType=ALL

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

63

Deleting specific Corporate connections

To remove a specific Corporate connection from the application, append the URL with the specific details of the connection as shown below: sapbi://DeleteConnection?

ConnectionType=BOEConnection&name=Tom&server_url=10.53.10.10:8080&cms=10.53.10.10&auth

Type=secEnterprise&default=no&user=UserName

Deleting a Sybase connection

To delete a Sybase connection, use the URL:

Sapbi://DeleteConnection?ConnectionType=SUPConnection

Deleting a BIOD connection

To delete a BIOD connection, use the URL:

Sapbi://DeleteConnection?ConnectionType=BIOD

Note

Before you delete an SUP connection, ensure that you

Deregister

from SUP using the

Settings

screen of the app. Otherwise, problems may occur when creating connections in future.

5.10 Granting Users the SAP BusinessObjects Mobile

Application Rights on the BI Platform

Once installed and configured, the users of an SAP BusinessObjects Mobile application can perform various actions in the app on device, including:

● Logging on to the application.

● Downloading BI documents.

● Sharing BI documents with other business users.

● Subscribing to document alerts.

Note

Alerts are notifications that appear in the application when Web Intelligence documents with conditional formatting are refreshed or updated on the server. Alerts appear only if the document is subscribed for alerts in the SAP BusinessObjects Mobile application.

64

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

However, to use the above features and interact with the application, users need to have the necessary

rights

on the BI platform.

As an administrator, you can grant these application rights to users through the Central Management Console

(CMC) by following the procedure below:

1. Access the CMC on the BI platform 4.0

For example: http://10.10.111.111:8080/BOE/CMC/

2. Choose

Applications

in the drop-down that appears on the CMC page.

3. Right click

SAP BusinessObjects Mobile

and choose

User Security

.

The

User Security

window appears.

4. In the table, select the particular user or user-group to which you want to grant SAP BusinessObjects Mobile rights. Choose

Assign Security

.

5. In the

Assign Security

window, choose the

Advanced

tab and choose

Add/Remove Rights

.

The

Add/ Remove Rights

window appears displaying the specific rights for SAP BusinessObjects Mobile :

6. Based on your security requirements, ensure that you have enabled the rights for various actions (such as subscribing to document alerts) by selecting the radio button in the first (tickmark) column.

7. Choose

Apply

, close the

User Security: SAP BusinessObjects Mobile

window and logout from the CMC.

Note

The rights for SAP BusinessObjects Mobile do not appear in the CMC on any release of the BusinessObjects

Enterprise XI 3.1

This feature is supported only on BI platform 4.0 and higher; BI platform 4.1 and higher release versions.

5.11 Customizing Application's Interface Features

You can customize the appearance and certain behavioural aspects of the application by performing the required configurations on the Mobile server. These include application's Home screen and tool-bar appearance, and also the time duration after which the application times out.

To quite an extent, the appearance of the

Home

screen on device is based on the organization of your documents and the specification of document properties defined in the BI LaunchPad (or your report designing client tool) on the BI platform. Other UI features are based on a metadata driven approach in which you update variables and their values in the .properties files on the Web application server, and restart the server for changes to take effect in the application on device.

The sub-sections of this chapter explain the configurations required to customize the application.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

65

Note

1. The server location of the .properties files depend on the Mobile BI platform server version you are using. See the related topic of this chapter for more information.

2. If you have deployed SAP BusinessObjects mobile server 4.1 or 4.1 SP1 in your set-up, you can use the

Central Management Console (CMC) to configure client settings and mobile properties. See the related topic of this chapter for more information.

Related Information

Mobile Server and Property File Locations Matrix [page 66]

Using the CMC to Define Properties on BI Platform 4.1 [page 66]

5.11.1 Mobile Server and Property File Locations Matrix

SAP BusinessObjects Mobile server version

XI 3.1 SP3, SP4, SP5, SP6

BI 4.0, SP5 and lower versions

BI 4.0, SP6

BI 4.1

File location of

clientsettings.properties

and

mobi.properties

<WebApp root>\webapps\MobileBIService\WEB-

INF\

<WebApp root>\webapps\MobileBIService\WEB-

INF\

<WebApp root>\webapps\MobileBIService\WEB-

INF\config\default

<WebApp root>\webapps\MobileBIService\WEB-

INF\config\default

Note

The <WebApp root> is the root folder location specific to your deployed application server, for example: C:

\Program Files (x86)\SAP BusinessObjects\Tomcat6

5.11.2 Using the CMC to Define Properties on BI Platform 4.1

If you have deployed SAP BusinessObjects mobile server 4.1 or 4.1 SP1 during your setup, you can use the Central

Management Console (CMC) to configure client settings and mobile properties. These parameters are otherwise configured through the clientsettings.properties and mobi.properties files on the Mobile server, respectively.

66

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

You need to explicitly define the following parameter in the MobileBIService\WebContent\WEB-INF

\web.xml file, so that the application can identify whether the Mobile configuration is defined on the CMC (BI platform) or in the properties files on the Mobile server:

<context-param>

<description>local-if configuration on server, boe-if configuration in CMC</ description>

<param-name>mobile.server.configuration.location</param-name>

<param-value>boe</param-value>

</context-param>

If you specify the context-param value as boe in the file above, your mobile server configuration on the CMC is considered.

To access mobile properties on the CMC, perform the following steps:

1. Open the

Central Management Console

on the BI platform server and access

Applications

.

You'll find the

SAP BusinessObjects Mobile

application listed on the page.

2. Right-click

SAP BusinessObjects Mobile

and choose

Properties

.

You'll see the following window:

3. Edit the category values in

Properties

as required.

Note

○ For information on the various categories, see the topic Configuring Categories on the Mobile Server of the Administrator and Report Designer's guide available at http://help.sap.com/bomobileios .

○ To understand the overall mobile properties and their impact on the application in general, refer to the

Mobile server Installation and Blackberry Configuration guide available at http://help.sap.com/ bomobile40

4. To edit client settings, choose

Client Settings

:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

67

5. Save your property settings and exit from the CMC.

Note

The negative mobile application rights that are granted via the CMC take precedence over the values specified for client settings via the CMC. For example, if the right To save documents to the local store of a device is not granted to the user in the CMC, users cannot download BI documents to their device, even if the offlineStorage property is set to true in the client settings.

Also note that if the right to save documents is granted in the CMC, but offlineStorage=false in client settings, users cannot download BI documents to the mobile device. Downloading/saving BI documents to the device is possible only if the right is granted and offlineStorage=true.

5.11.3 Configuring the Thumbnail Background Image of BI

Documents

Based on your requirements, you can customize the thumbnail image for BI documents that appear as tiles on the

Home

screen of the application.

If you do not configure a thumbnail image for BI documents on the server, the documents display a default image

(based on document type) on the Home screen. Once you open the document and return to the Home screen, the

68

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

default background image of the thumbnail is replaced by a snapshot of the first report of the document. The figure below illustrates this behavior for a Web Intelligence document:

However, once configured on the server (BI LaunchPad), the thumbnail background image remains constant on the Home screen. It does not change even after you open the BI document and return to the Home screen:

To configure the thumbnail background image for a BI document, perform the following steps:

1. Access the

Properties

of the document on the BI platform (BI LaunchPad/Web Intelligence Rich client).

2. Enter the URL of your image in the Keywords field and choose

Save

.

Note

1. The recommended thumbnail image size for best results on the device screen is 208 pixels * 208 pixels.

2. The background image size should not be greater than one hundred Kilobyte (100 KB).

3. Valid image formats include .jpeg, .jpg and .png.

4. If multiple image URLs are specified in the BI document's Keywords field on the BI platform, the application considers only the last valid image URL for the thumbnail background image.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

69

5. If there are multiple strings specified in the Keywords field, and if the image URL is not the last keyword string, a space is required between the URL and the comma (for example: keyword1, http:// www.xyz.com/myImage.png , keyword2, keyword3).

5.11.4 Configuring Document-Specific Help

For an open BI document on the device, when you tap

Help

in the secondary report toolbar, the Mobile knowledge center ( http://help.sap.com/bomobileios ) opens by default.

If you want to replace this Help URL with some other URL based on your specific requirements for the BI document, you can do so by performing the procedure below:

1. Access the

Properties

of the document on the Mobile BI platform (BI LaunchPad/ Web Intelligence Rich client).

2. Enter the URL of your custom Help in the Keywords field with the syntax below: docHelpURL=<new_URL> new_URL is your custom URL, for example, http://www.myHelpURL.com

3. Choose

Save

.

Note

In the current release of the application, you can use a BI document's Keywords field to customize either the document Help or the thumbnail image. However, you cannot implement both of these functionalities at the same time.

Related Information

Configuring the Thumbnail Background Image of BI Documents [page 68]

5.11.5 Configuring the Collaboration Options

In an open BI document on device, users choose

Collaborate

in the secondary report toolbar to share or discuss the report with business colleagues using SAP JAM. Based on requirements, you can do either of the following:

● Disable collaboration on the server, so that it does not appear as an option in the secondary report toolbar on device.

● Specify SAP JAM or SAP StreamWork as a collaboration options in the server configuration.

Note

○ By default the application supports SAP JAM as the Web based collaboration tool if no configuration is performed on the server.

○ Both collaboration tools cannot be simultaneously specified for use by the application. Only one can be used at a time.

70

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

To configure collaboration settings based on your specific requirements, perform the following procedure:

1. Access the clientsettings.properties file available at the following location on the Mobile server:

<Web_app_root>\webapps\MobileBIService\WEB-INF\config\default

Note

○ The <WebApp root> is the root folder location specific to your deployed application server, for example: C:\Program Files (x86)\SAP BusinessObjects\Tomcat6

○ The location of clientsettings.properties varies based on the Mobile server version you are using. See the related topic for more information.

2.

○ If you want to enable SAP Streamwork as the collaboration tool in the application, follow the below substeps and proceed with step 3.

1. Set the value of following property in the file as 'true' feature.streamwork.enabled=true

2. Ensure that the following property is disabled (set to 'false'): feature.jam.enabled=false

○ If you want to configure SAP JAM as the collaboration tool (default enabled) based on your specific requirements, follow the below substeps below:

1. Ensure that the following property is disabled (set to 'false') feature.streamwork.enabled=false

2. Specify values for the following properties based on their description:

Property feature.jam.enabled

feature.jam.url

feature.jam.consumer.key

feature.jam.consumer.secret

feature.jam.callback.urlverb

Description

○ If you set this property to

"false", SAP JAM is disabled for collaboration in the application.

○ If the value is "true" (default),

SAP JAM appears as the collaboration web site when users choose

Collaborate

in the secondary report toolbar in the application on device.

The JAM URL to which the application should redirect when users choose

Collaborate

in secondary toolbar of BI reports on device.

The consumer key that is issued when you register the application on JAM

The secret key that is issued when you register the application on

JAM.

The link that you specify as the redirection address while registering the application. For

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

71

Property Description example, sapbi://token

. This ensures that the application is launched when the user clicks this link (with the URI scheme defined by you).

Note

For SAP JAM to be enabled, it is mandatory that you specify a value for all the above listed parameters.

3. Save and close the clientsettings.properties file.

4. Restart the Web application server.

5. Launch the application on device, connect to the server, open the BI document and validate the result of your configuration by checking the

Collaborate

option in the secondary report toolbar.

Related Information

Mobile Server and Property File Locations Matrix [page 66]

5.11.6 Configuring the Visibility of BI Document Samples

This topic explains how you can enable or disable the offline BI document samples that appear in the application

(until you add a server connection).

1. Access client settings using the clientsettings.properties file on the Mobile server, or the Central Management

Console (CMC) interface (if you are using the BI platform 4.1).

2. To disable the BI document samples in the application, set the value of the following property to false:

feature.show.samples.enabled

Note

● See the related topics in this chapter for information on how to access client settings based on the server version that you are using.

● You can also generate custom BI report samples based on your specific requirements, and use them in the application. For more information, refer to the Developer's Guide published on http://help.sap.com/ bomobileios

Related Information

Using the CMC to Define Properties on BI Platform 4.1 [page 66]

72

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Mobile Server and Property File Locations Matrix [page 66]

5.11.7 Configuring QR Code Scanning

If you do not want users to usel the

Scan QR Code

option in the application, you can disable it using the client settings on the Mobile server. This topic explains how to disable QR code scanning in the application (by default it is enabled in the application).

1. Access client settings using the clientsettings.properties file on the Mobile server, or the Central Management

Console (CMC) interface (if you are using the BI platform 4.1).

2. To disable the QR code scanning in the application, set the value of the following property to false:

feature.qrcode.enabled

Note

See the related topics in this chapter for information on how to access client settings based on the server version that you are using.

Related Information

Using the CMC to Define Properties on BI Platform 4.1 [page 66]

Mobile Server and Property File Locations Matrix [page 66]

5.11.8 Configuring the Session Timeout Duration of the

Application

The number of concurrent sessions running on the SAP BusinessObjects Mobile server can impact its performance.

If you want a session of an SAP BI mobile application to be terminated after a defined period of inactivity, perform the following configuration on the Mobile server:

1. Open the web.xml file found at the following location:

<Webapp-server-root>\webapps\MobileBIService\WEB-INF

Note

The <WebApp-server- root> is the root folder location specific to your deployed application server, for example: C:\Program Files (x86)\SAP BusinessObjects\Tomcat6

2. Set the value of the session-timeout parameter found within the tags shown below:

<session-config>

<session-timeout>60</session-timeout>

</session-config>

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

73

Note

○ The session-timeout element defines the default session timeout interval for all sessions created in

MobileBIService (Mobile server).

○ The timeout duration begins when the device is locked or the application is sent to the background

(user switches to other applications on the device).

○ When a session times out, the user is logged off from the BI platform.

○ The specified timeout must be expressed as a whole number of minutes. In the example above, the timeout is 60 minutes.

If the timeout is zero ('0') or less, sessions never time out.

5.11.9 Configuring the Auto Update option for BI documents

You can configure the Auto Update option for BI documents in CMC. When you enable the Auto update option, if there are any updates to the downloaded BI documents on the server, the application automatically downloads the updated documents onto your device. In addition, if there are any BI documents available in BI Inbox, they get downloaded as well.

Context

To configure the Auto Update option for BI documents in CMC, perform the following steps:

Procedure

1. Log on to CMC and under the

Manage

section, choose

Applications

.

2. Double-click

SAP BusinessObjects Mobile.

3. Choose

Client Settings

.

4. Choose

+Add More...

.

5. Add the following keys and the corresponding values.

Table 1:

Key feature.autoupdate.enabled

Possible Values true, false feature.autoupdate.bi.inbox.enabled

true, false

Description

Set to true to enable the auto update option for BI documents.

Set to true to enable the auto update option for BI documents located in BI

Inbox.

74

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

6. Choose

Save & Close

.

Next Steps

Once you configure the Auto Update option in CMC, the user needs to enable this feature on the device to automatically download the updated documents from BI platform server onto the device.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

75

5.11.10 Configuring the Auto Refresh (polling) option for BI documents list

You can configure the Auto Refresh option also known as polling for BI documents list in CMC. As an administrator, you can either enable or disable this option by setting the auto-refresh duration on the server.

Context

To configure the Auto Refresh option for BI documents list, perform the following steps:

Procedure

1. Log on to CMC and under the

Manage

section, choose

Applications

.

2. Double-click

SAP BusinessObjects Mobile.

3. Choose

Client Settings

.

4. Choose

+Add More...

.

5. Add the following key and the corresponding value.

Table 2:

Key feature.notification.polling.interval

Possible values

Any positive integer value.

Description

By default, auto-refresh happens in ev­ ery 15 mins interval. You can change this interval by setting any positive in­ teger value for the polling interval. To disable the auto-refresh option, set the value to 0.

76

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

6. Choose

Save & Close

.

Results

The application Home screen is now auto-refreshed at the specified time interval. When an auto-refresh takes place, the BI documents are refreshed on the Home screen such that they are synchronized with the server.

5.11.10.1 Configuring auto refresh for application running in background

The auto-refresh duration setting is applicable only when you are running the mobile application in foreground.

Once you run the application in background, the iOS takes the control of the polling interval. However, the administrator can manage background polling in CMC.

Context

To manage background polling in CMC, perform the following steps:

Procedure

1. Log on to CMC and under

Manage

, choose

Applications

.

2. Double-click

SAP BusinessObjects Mobile

.

3. Choose

User Security

.

4. Choose the required user to whom you want to grant or deny rights.

5. Choose

Assign Security.

6. Choose

Advanced

.

7. Choose

Add/Remove Rights

.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

77

Results

The

Subscribe to document alerts

right controls background polling. By default, this right is granted to the user. If required, you can choose to deny this right for the user.

5.11.11 Configuring the display of nested categories on the

Home screen

You can configure the display of nested categories on the Home screen in CMC.

Procedure

1. Log on to CMC and under the

Manage

section, choose

Applications

.

2. Double-click

SAP BusinessObjects Mobile

.

3. Choose

Client Settings

.

4. Choose

+Add More...

5. Add the following key and the corresponding value.

Table 3:

Key Possible values feature.home.category.nested.enabled true, false

Description

Set to true to enable the display of nested/sub categories on the Home screen.

6. Choose

Save & Close

.

Results

After enabling the feature.home.category.nested.enabled key, when you tap on a category and if it has subcategories available within it, they appear on a new screen within the panel. Tapping on the sub-category again opens the lower sub-categories (if available).

5.12 Configuring Categories on the Mobile Server

A category is a logical classification of BI documents (objects). BI documents are assigned to categories on the BI platform. In the context of Mobile BI, categories help control various aspects of the BI documents accessed through the SAP BI applications on mobile devices.

78

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

These aspects include:

1. Controlling the user accessibility of BI documents:

Defining the specific devices on which a BI document can be accessed.

Preventing confidential documents from being saved in the device memory.

2. Customizing the display layout of BI documents on the mobile device screen. (Display layout of BI documents on device screen can be based on the Card Layout or Page Layout model).

3. Organizing BI content based on your custom requirements.

Category names are configured in the mobi.properties file on the Mobile server at the following location:

[<WebAppServer>_Home]\webapps\MobileBIService\WEB-INF\mobi.properties

There are three types of technical categories to which you can assign a BI document in the document designing tool on the BI platform:

1. Category to allow the BI document to be displayed and accessed on the mobile device.

(By default, this category is named "Mobile").

2. Category to ensure that the report layout on the device screen is the same as the "page layout" defined on the

BI platform.

(By default, this category is named "MobileDesigned").

3. Category to secure the document. Documents assigned to this category cannot be downloaded and saved in the device memory. They can only be accessed by users who are connected to the server.

(By default, this category is named "Confidential").

The extract below displays the default configuration of mobi.properties file on the mobile server:

#default

........

default.corporateCategory=Mobile default.personalCategory=Mobile default.category.mobileDesigned=MobileDesigned default.category.secure=Confidential default.docTypes=Webi,CrystalReport

..........

#ipad

......

ipad.corporateCategory=Mobile

.....

#iphone

......

iphone.corporateCategory=Mobile

...

#blackberry mobile

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

79

...

#android tablet

androidtablet.corporateCategory=Mobile

...

#android phone

androidphone.corporateCategory=Mobile

....

The mobi.properties file contains various sections based on request sources such as

<default>

,

<iphone,

><ipad>

,

<blackberry mobile>

,

<androidphone>

and

<androidtablet>

.

All the properties in the default request source govern various aspects of SAP BI applications on

all

mobile devices. If different parameter values are entered in a request source, that it the default request source is overidden.

You do not need to tweak the default settings in the properties file. However, if you have custom requirements for a specific device or platform, you can enter specific category names in the corresponding request source and the values will override the ones in the

<default>

request source.

In the mobi.properties file:

1. The lines:

<RequestSrc>.corporateCategory=Mobile

<RequestSrc>.personalCategory=Mobile indicate that BI documents assigned to the {Mobile} category can be accessed using the SAP BI (

SAP

BusinessObjects Mobile

) application on a mobile device.

2. The line:

<RequestSrc>.category.mobileDesigned=MobileDesigned indicates that BI documents assigned to the MobileDesigned category (on the BI platform) would appear on the mobile device screen according to the reports' page layout defined on the BI platform.

3. The line:

<RequestSrc>.category.secure=Confidential indicates that BI documents assigned to the Confidential category on the BI platform are secured. Documents assigned to this category cannot be saved in the device memory, and therefore, they cannot be accessed in disconnected (offline) mode.

Note

○ On the BI platform, you can change (customize) the category names that you see on the right side of the assignment operator (such as "Mobile", "MobileDesigned" and "Confidential") in the mobi.properties file . However, if you are changing a category name on the BI platform, you should update the corresponding line in the mobi.properties file.

○ Categories of type:mobileDesigned and secure cannot be personal categories. They have the

Corporate

type.

○ To make SAP BusinessObjects Dashboards accessible on mobile, they need not be assigned to a

Mobile category . This is an exceptional BI document type for which mobile access is enabled by the

Dashboard model designer using the SAP BusinessObjects Dashboards. See the related topic for more information.

80

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Example 1: Controlling visibility of BI documents

Suppose that you have 5 BI documents designed for the Mobile for iOS application, and you want 2 to appear on both (iPhone and iPad) devices; 2 documents to appear only on an iPad and 1 document to appear only on an iPhone.

You need to perform the following configuration:

1. In your report designing tool, assign the 2 documents you want to appear on both devices, to a category named

Mobile

. This is because the "Mobile" category name is present in the

<default>

request source of mobi.properties and is not specific to any device.

2. In your report designing tool, assign the 2 documents you only want to appear on iPad to a custom corporate category name (such as

iPad_specific

). Then, edit the following line in mobi.properties (replace old category name with the new name): ipad.corporateCategory=iPad_specific

Since the corporate category name in the ipad request source is different from the name in the default request source (Mobile), the iPad request source overrides the default request source. This ensures that the mobile server recognizes these BI documents for the iPad request source and they

only

appear in the SAP BI app installed on an iPad.

3. In your report designing tool, assign the document you want only to appear on iPhone, to a custom Corporate category name (such as

iPhone_specific

). Then, edit the following line in mobi.properties (replace old category name with the new name): iphone.corporateCategory=iPhone_specific

Now the iPhone request source overrides the default request source. This ensures that the mobile server recognizes these documents for the iphone request source and they

only

appear on the SAP BI app installed on an iPhone.

Example 2: Controlling display layout of BI documents on the mobile device screen

You have 4 Web Intelligence documents. 2 are designed for Android phones and 2 are designed for an iPad screen. To ensure that documents are displayed in the respective devices in the correct layout, perform the following steps:

1. Web Intelligence documents meant for iPad devices, perform the following steps:

In your report designing tool, assign the documents to a custom category name such as "iPad_designed".

Then, make this update in the mobi.properties file: ipad.corporateCategory=iPad_designed.

This ensures that the documents

only

appear on iPads and not on other devices.

Assign the documents to the "MobileDesigned" category on BI platform.This ensures that reports are displayed on the iPad screen according to their page layout defined on the BI platform.

2. Web Intelligence documents for the Android phone:

In your report designing tool, assign the documents to a custom category name such as

"Android_designed". Then, make this update in mobi.properties file: androidphone.corporateCategory=Android_designed. The Android phone request source overrides the default request source. This means that the documents

only

appear on Android phones and not on other devices.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

81

Assign the documents to the "MobileDesigned" category on BI platform.This ensures that the reports are displayed on the android device screen according to their "page layout" defined on the BI platform. If you give a custom name to this category on the BI platform (such as "Mydesign"), you should update mobi.properties file: androidphone.category.mobileDesigned=Mydesign accordingly.

Note

If you do not assign your BI documents to a mobileDesigned category on the BI platform, they appear on the mobile device screen according to the Card Layout model. For information on the two layout models

(Card layout and Page layout), see the Mobile BI Report Designer's Guide.

Example 3: Securing BI documents with confidential data

You have certain BI documents that contain sensitive business information. You do not want users to save these documents on their device or to have offline access. The device the user is using to access the document is irrelevant. You just need to assign the confidential BI documents to the "Confidential" category on the BI platform

(via the BI LaunchPad or otherwise).

This is because by default, the "Confidential" category is defined as a secured category in the mobi.properties file. If you choose a different name for this category on the BI platform (such as "Restricted"), update the properties file for the following line: default.category.secure=Restricted.

Note

Category names should not have a comma (',').

Related Information

Saving mobile dashboards to BI platform folders [page 112]

5.13 Generating SAP BI URLs for Opening BI Documents

An SAP BI document viewed in the application can have either of the following views on device:

● Default view (first report, first page)

● A report (page) view within the document

● A report part (zoomed) view

As an administrator, you can share a BI document (so that it opens in a particular view on the recipient's device) by generating and sending an SAP BI URL.

You can generate an SAP BI URL for a document in either of the following ways

a. Using the Email option in the report on app

82

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

When you choose

Email

in the secondary report tool-bar of an open report view on the device, the application generates an SAP BI URL with various parameters based on the view/ type of report.

b. Manually creating an SAP BI URL

You can create SAP BI URLs to allow users to directly open a BI document on their devices. The sub-sections of this topic explain how to create SAP BI URLs for various scenarios.

Note

Use SAP BI URLs to launch the SAP BI application from outside the app, that is from a third party iOS application. Once you are inside the application and you have to navigate between documents, use

OpenDocument instead of creating SAP BI URLs.

See the Mobile BI Report Designer's Guide for information on OpenDocument URLs.

5.13.1 Creating SAP BI URLs For Opening Specific BI

Documents or Reports

Pre-requisite

Recipients of the SAP BI URLs should have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP BusinessObjects Mobile application for iOS installed on their iPhone or iPad device.

1. Creating an SAP BI URL for opening a simple BI document (default view: first report, first page) in the app

To enable users to directly open a BI document with the tap of a URL on their iPad or iPhone devices, create an

SAP BI URL with the following format: sapbi://OpenDoc/?

ConnectionType=<conntype>&connection_name=<name>&server_url=<server_I.P address>&cms=<CMS_ipaddress>&Type=<Doctype>&iDocID=<ID>&reportPartKey=&reportPageNumbe r=0&reportIndex=&isInstance=N&prompt=

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI platform

(report designing client tool).

● For other parameters (reportPartKey, reportPageNumber, reportIndex, isInstance and prompt ), you do not need to assign any specific values. However, they should be retained in the URL syntax will null values assigned to them as shown in the above URL format.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

83

2. Creating an SAP BI URL for opening a specific report within a BI document in the app

To enable users to directly open a specific report within a BI document with the tap of a URL on their iPad or iPhone devices, create an SAP BI URL with the following format: sapbi://OpenDoc/?

ConnectionType=<Conn_type>&connection_name=<name>&server_url=<server_ipaddress_withPor t>&cms=<CMS_ipaddress>&Type=<docType>&iDocID=<idocID>&reportPartKey=&reportPageNumber=

&reportIndex=5&isInstance=N&prompt=

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI platform

(report designing client tool).

● reportIndex is the index number of the report. The number count starts from zero. To give access to nth report in the document, assign (n-1) as the value for this parameter.

For example, if you want users to get direct access to third report of the BI document, assign the value (3-1)=

2 to the reportIndex in the URL.

● For other parameters (reportPartKey, reportPageNumber, isInstance and prompt ), you don't need to assign any specific values. However, they should be retained in the URL syntax will null values assigned to them as shown in the above URL format.

Note

The SAP BI URL that the application generates dynamically (on sharing a report) may have values for all parameters including the reportPageNumber and reportPartKey.When creating the SAP BI URL manually, we do not recommend that you pass values for these parameters, as they are not guaranteed to work in the application.

5.13.2 Creating SAP BI URLs For Opening The Latest Instance of BI Documents

Pre-requisite

Recipients of the SAP BI URLs should have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP BusinessObjects Mobile app for iOS installed on an iPad or iPhone device.

To enable users to directly open the latest instance of a BI document (that is scheduled on the BI platform) with the tap of a URL on their devices, create an SAP BI URL with the following format: sapbi://OpenDoc/?

ConnectionType=<type>&connection_name=<conn_name>&server_url=<server_IPaddress>&cms=<C

84

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

MS_ipaddress>&Type=<doctype>&iDocID=<docID>&reportPartKey=&reportPageNumber=0&reportIn dex=&isInstance=Y&prompt=

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI platform

(report designing client tool).

● For other parameters (reportPartKey, reportPageNumber, reportIndex and prompt ), you do not need to assign any specific values. However, they should be retained in the URL syntax will null values assigned to them as shown in the above URL format.

5.13.3 Creating SAP BI URLs For Opening BI Documents With

Prompts

Pre-requisite

Recipients of the SAP BI URLs have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP BusinessObjects Mobile application for iOS installed on their iPhone or iPad device.

1. Creating an SAP BI URL for opening documents with prompts without refresh

To enable users to directly open a BI document with prompts using the SAP BI URL on their devices, create a URL with the following format: sapbi://OpenDoc/?

ConnectionType=<conn_type>&connection_name=<name>&server_url=<server_IPaddress>&cms=<C

MS_IPaddress>&Type=<docType>&iDocID=<ID>&reportPartKey=&reportPageNumber=0&reportIndex

=&isInstance=N&prompt=

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI platform

(report designing client tool).

● prompt defines the type of prompt (single or multiple).

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

85

2. Creating an SAP BI URL for opening documents with prompts (on refresh) with list of values (LOV)

To enable users to directly open a BI document with prompt (on refresh) with LOVs, take the following steps:

1. Create an SAP BI URL with prompt names and corresponding LOVs in the following format: sapbi://

OpenDoc/?

ConnectionType=BOEConnection&connection_name=243&server_url=10.10.10.243:8080&cms=1

0.10.10.243&Type=webi&iDocID=AemcMBDKWG1Bl0nBT0PDPTQ&reportPartKey=&reportPageNumbe r=0&reportIndex=&isInstance=Y&prompt=lsM[Enter value(s) for Year:]=[2005],[2006],

[2004],[2002]_lsM[Enter value(s) for City:]=[Los Angeles],[Washington],[San

Francisco],[New York],[Miami]

Note

Observe that multiple prompts (lsM) are separated by an underscore ('_').

2. Encode the

<prompt>

parameter section (prompt names and LOVs) of the URL.

For example, after encoding the prompt section of the above URL, it looks like: lsM%5BEnter%20value(s)%20for%20Year%3A%5D%3D%5B2005%5D%2C%5B2006%5D%2C%5B2004%5D%2C

%5B2002%5D_lsM%5BEnter%20value(s)%20for%20City%3A%5D%3D%5BLos%20Angeles%5D%2C

%5BWashington%5D%2C%5BSan%20Francisco%5D%2C%5BNew%20York%5D%2C%5BMiami%5D%0A%0A

3. Again encode the prompt section and join it with the remaining URL

After performing this step, the URL for the above example looks like this: sapbi://OpenDoc/?

ConnectionType=<connType>&connection_name=<name>&server_url=<server_IPaddress>&cms=

<CMS_IPaddress>&Type=<docType>&iDocID=<ID>&reportPartKey=&reportPageNumber=0&report

Index=&isInstance=N&prompt=lsM%5BEnter%2520value(s)%2520for%2520Year:%5D=

%5B2005%5D,%5B2006%5D,%5B2004%5D,%5B2002%5D_lsM%5BEnter%2520value(s)%2520for

%2520City:%5D=%5BLos%2520Angeles%5D,%5BWashington%5D,%5BSan%2520Francisco%5D,%5BNew

%2520York%5D,%5BMiami%5D

Note

For the parameters: reportPartKey, reportPageNumber, reportIndex and isInstance, you don't need to assign any specific values in the URL. However, they should be retained in the URL syntax will null values assigned to them as shown in the above URL format.

5.13.4 Creating SAP BI URLs for Opening Specific Sections of the BI Documents With Sections

Pre-requisite

Recipients of the SAP BI URLs (created using the format explained in this topic) have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

86

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

2. The SAP BusinessObjects Mobile application for iOS installed on their iPhone or iPad device.

To enable users to directly open a specific section of a BI document in the SAP BI app on their device, create an

SAP BI URL with the following format: sapbi://OpenDoc/?

ConnectionType=<conntype>&connection_name=<name>&server_url=<server_I.P address>&cms=<CMS_ipaddress>&Type=<Doctype>&iDocID=<ID>&reportPartKey=&reportPageNumbe r=0&reportIndex=&isInstance=N&prompt=&sectionPathByName=<section_name>

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI platform

(report designing client tool).

● reportIndex is the unique ID of the report, and enables the application to identify your specific report.

● The parameter

<sectionPathByName>

enables the application to retrieve the specific report section you want to open on the user's device. For this, pass the name of the section as specified on the server while creating the report-section.

Note

1. The parameters (reportPartKey, reportPageNumber, isInstance and prompt ) are optional.

However, if even you do not assign values to these parameters, you can retain them in the URL syntax will null values assigned to them as shown in the above URL format.

2. The parameter sectionPathByName cannot be used for specifying multiple sections in a report. At a time, you can open only a single report section using this parameter.

3. The parameter sectionPathByName cannot be used for multiple levels of section hierarchy if the reportsections are nested. Only a single level of hierarchy in report sections can be opened using this parameter.

5.13.5 Creating SAP BI URLs for Opening the Latest Available

Version of a BI document or Its Instance

Pre-requisite

Recipients of the SAP BI URLs have:

1. Access to the SAP BusinessObjects BI platform server/ SAP BusinessObjects Mobile server specified in the

URL.

2. The SAP BusinessObjects Mobile application for iOS installed on their iPhone or iPad device.

To enable users to open the latest available version of the BI document or its instance on their device, create an

SAP BI URL with the following format: sapbi://OpenDoc/?

ConnectionType=<conntype>&connection_name=<name>&server_url=<server_I.P address>&cms=<CMS_ipaddress>&Type=<Doctype>&iDocID=<ID>&reportPartKey=&reportPageNumbe r=0&reportIndex=&isInstance=N&prompt=&sectionPathByName=<section_name>&useInstance=<pa ram_value>

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

87

● ConnectionType, connection_name, server_url and cms are the regular SAP BI URL parameters that help the app (on user's device) identify the particular BI platform server with the relevant BI document.

● Type is the BI document type that has 2 valid values: 'webi', '<>'

● iDocID is the CUID of the document. Retrieve the CUID by accessing document

Properties

on the BI

LaunchPad.

Note

The parameters (reportPartKey, reportPageNumber, reportIndex, isInstance, prompt and sectionPathByName are optional. However, you can retain them in the URL syntax will null values assigned to them as shown in the above URL format.

● The useInstance parameter can have the value 'last' or null. Below is how this parameter works:

- If this parameter is assigned the value 'last', the BI document or its latest instance whichever is latest out of the two is opened from the server on the device.

- If this parameter is assigned the value 'last', and the user has already downloaded the BI document or its latest instance to the device, the document or the instance, whichever is latest out of the two is opened from the device memory. Note that if there is an update available on the server that the user has not retrieved for the downloaded document, the URL does not consider that update while opening the document.

- If no value is assigned to this parameter, always only the BI document is opened from the server. If the user has downloaded the BI document already to the

Home

screen (before tapping the SAP BI URL), the BI document is opened from the device memory. (Latest instance of the document even if available on the server or device memory is not opened when no value is assigned to this parameter.)

5.14 Understanding the Security Implementation in the App

5.14.1 Features of Application Password

The application password acts as a source of input for encryption of user data, where other users cannot decrypt the data without this input.

Here are some features of the SAP BusinessObjects Mobile application password:

● By default, the application password is not enabled in the application, until users add a connection to the BI platform server. When users add a BI platform server connection, the application forces them to create an application password (this is because user specific or personal information comes on the device only after a connection is created).

However, if users have not created a single connection, yet, they wish to enable the application password, they can do so using the

Settings

screen of the application. (Settings screen appears on tapping the

[Settings]

icon which is next to the current connection name in the left hand navigation panel.)

88

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Note

The above behavior applies if the user has performed a fresh installation of the application. If a user has upgraded the existing installation with a newer version of the application from the iTunes store, server connections would already exist in the application, and so the password would remain enabled.

● Password prerequisites:

Password length must be minimum eight characters.

For entering the password, the application allows a maximum of twenty attempts. If the attempts exceed this number, the application forces the user to reset the application.

Note

Resetting the application erases the application password and all the SAP BI content downloaded on the device.

● By choosing the

Clear Data Remove Application Data

option in the of the

Settings

screen, all BI data of the application is deleted from the local memory. However, this does not delete the application password.

● Users can change the password and set the "Application password timeout" parameter using the

Settings

screen.

Note

The

Application password timeout

parameter defines the duration of inactivity. Once this is exceeded, the application forces the user to enter the password to resume the application activity. This applies to the scenario when the user has switched over to other applications, and returns to the SAP BusinessObjects

Mobile application after some time.The default value of this parameter is 5 minutes.

● The following lines of code in the clientsettings.properties file on the Mobile server, help you customize the password settings in the application: savePassword=true offlineStorage=true offlineStorage.ttl=365 offlineStorage.appPwd=true

If you set savePassword=true, the

Save Password

option appears in the Connection settings screen of the application. Otherwise, it does not appear for the user.

If for a server, the administrator has set the value of offlinestorage.appPwd parameter to true, users cannot disable the application password (for the particular server connection) while using the application. If this parameter has the false (default) value, users can disable the application password using the

(

Settings

) screen of the application.

Other parameters associated with offline storage (such as "time to live") apply to the password as well.

Note

For information on the workflow of a particular action (such as disabling application password), use the embedded Help provided in the application.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

89

5.14.2 Support for Security Deployments On the Web

Application Server

Ensure that you have implemented either of the following scenarios on your Web application server (on which you have installed the SAP BusinessObjects Mobile server):

● Basic authentication (for example Siteminder)

● Form based authentication (for example Siteminder, Webseal)

● X509 certificate (two way client certificate)

When users add connections to the SAP Mobile server (with either of the above security deployments) using the

SAP BusinessObjects Mobile application on their devices, they see a security interface which asks for authentication. The following sections explain the three scenarios listed above.

a. Basic Authentication

1. Using the

Settings

screen of the application, users add a connection to the CMS with basic authentication deployed on it. (As an administrator, you provide the specific server details to the application users.)

2. On choosing the new connection in the

Settings

screen, the application displays the basic

Authentication

dialog box, asking the user to enter his/her credentials.

3. User is logged in to the connection, and can browse the BI documents available on the server.

b. Form Based Authentication

1. Using the

Settings

screen of the application, users add a connection to the CMS with form based authentication deployed on it. (As an administrator, you provide the specific server details to the application users.)

2. On choosing the new connection in the

Settings

screen, the application displays a form, asking the user to provide additional information.

Note

The form fields can be customized on the Web application server and UI features such as company logo can be included in the form. The form configured on the Web application server is displayed in the same way as in the application in a container on device.

3. User is logged in to the connection, and can browse the BI documents available on the server.

c. Certificate Based Authentication

1. Users first install the X509 certificate on the device. Information on how to install the certificate is provided in the sub-topic of this chapter.

90

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

2. Using the

Settings

screen of the application, users add a connection to the CMS with certificate based authentication deployed on it. (As an administrator, you provide the specific server details to the application users.)

3. When you choose the new connection in the

Settings

screen, the application displays a dialog box stating that the connection requires a certificate.

User chooses

Yes

to display the certificate.

4. Application displays the available certificates and asks for the right certificate.

5. User selects the certificate (installed in step 1) from the list.

6. User is logged in to the connection, and can browse the BI documents available on the server.

Note

1. Installed certificates can be removed from the application by choosing the

Clear Data Remove

Certificates

option in the

Settings

screen.

2. The application supports basic authentication and certificate based authentication for hyperlink objects as well.

5.14.2.1 Installing the x509 Certificate on Device

For adding or accessing a certificate based connection in the application, users need to first install the certificate on their device. SAP BusinessObjects Mobile applications support the set ups that are deployed based on the x

509 certificate.

x 509 certificate is usually of the format "<>.p12" or "<>.cert"

The procedures below are for users who install the certificate (received via email or accessed from a Web application server) on their device:

Installing the certificate received as an email attachment

1. On your desktop, download the certificate (*.p12) file.

2. Change the certificate file extension from ".p12" to ".mcert" and send it to the email account configured on your device.This ensures that the certificate file is in a recognizable format for the application.

3. On your device, double-click the certificate that you emailed to your account.

The application is launched.

● If the certificate is not password protected, a message appears on the screen saying that the certificate is installed successfully.

● If the certificate is password protected, a dialogue box appears on the screen asking you to enter the password. For the installation to complete successfully, enter the password and choose OK.

The message for successful certificate installation appears.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

91

Note

If the certificate you are installing already exists on your device, on performing step 3 in the above task, a dialogue box appears saying: "This certificate <ID> already exists". If you want to delete the existing certificate from the app, choose

Delete

in the dialogue box. Else, choose

Cancel

.

Installing the certificate hosted on a Web Application Server

1. On your device, access either of the following links emailed to you by the administrator:

SAPBI://action=downloadcert&certurl=<Download URL>

SAPBI://action=downloadcert&certurl=<Download URL>&Password=abc123

2. If you access the first link above:

The application is launched and the certificate file is downloaded from the URL location (certurl).

A dialogue box appears asking you to enter the password. Enter the password and choose OK.

The certificate is installed successfully on the device.

Note

If the certificate is not password protected, the application is installed directly on accessing the link.

3. If you access the second link above:

The application is launched and the certificate file is downloaded from the URL location (certurl).

The certificate is directly installed on the device.

Note

Since the password is already included in the URL, the application does not ask the user for the password.

In this case, if the certificate is not password protected, the parameter for password is ignored by the application.

An example of the parameter "Download URL" is http://10.208.107.248:8080/Resource/I087312.p12 ; where 10.208.107.248:8080 is the IP address and port of the Web application server machine and

I087312.p12 is the certificate file.

Note

If the certificate you are installing already exists on your device, on accessing any of the two links, a dialogue box appears saying: "This certificate <ID> already exists". If you want to delete the existing certificate from the application, choose

Delete

in the dialogue box. Else, choose

Cancel

.

92

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

5.14.3 User Data Protection and Privacy Parameters

User data is the data or information which is personal to an individual user. This includes the downloaded reports and application logon credentials of the user. To ensure the security of user data, the application implements certain security measures.

Some of these measures are as follows:

● Users have the option of saving their password for a connection in the application. However, in the default mobile server configuration, this option is disabled by default (savePassword=false). If a user enables the

Save Password option while configuring the connection on his or her device, the password is encrypted files using the FIPS compliant AES algorithm. On iPad/iPhone devices, files are stored with the iOS keychain.

● If users do not choose the option to save their password, they are prompted for the password whenever they access the application, whether they are in the online or offline mode of the device.

● In the default configuration of the application, the option to download and view documents locally on the device is disabled. (offlineStorage=false). Users can only access the documents available on the server in online mode.

Based on requirements, administrator can enable this option in the server configuration file.

● If offline storage of documents is enabled, there is a "Time to Live" parameter in the server configuration file, with a default value of 365 days (offlineStorage.ttl=365). This means that the downloaded documents expire after 365 days and are automatically removed from the local memory of device.

● For Web Intelligence or Crystal Reports documents with private or confidential data, you can secure the documents by assigning them to a "Confidential" category in document designing tool. A secure document can only be accessed by users while they are connected to the Mobile server. Once users log off from the server, the secure document is deleted from the device memory.

The parameters (savePassword, offlineStorage and offlineStorage.ttl) explained above can be found in the following file on the Mobile server:

[<Web app server>_Home]\webapps\MobileBIService\WEB-INF\ClientSettings.properties

Based on your specific security requirements, you can change the values of the above parameters in the

ClientSettings.properties file.

Note

1. The location of clientsettings.properties file on the SAP BusinessObjects Mobile server is based on the server version you are using. To find the file-path for your specific server version, refer to the related topic of this chapter.

2. If you are using the BI platform 4.1 and higher versions, you can also use the Central Management

Console (CMC) interface for configuring client settings. For information on how to configure client settings using the CMC, see the related topic of this chapter.

3. For your configuration changes to take effect in the app, ensure that you restart the Web application server after making updates to the ClientSettings.properties file.

4. For more information on the security measures implemented in the application and in the mobile system landscape, refer to the Security Guide available at http://help.sap.com/bomobileios

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

93

Related Information

Configuring Categories on the Mobile Server [page 78]

Features of Application Password [page 88]

Configuring Application's Behavior by Specifying Properties on the Server [page 62]

Using the CMC to Define Properties on BI Platform 4.1 [page 66]

Mobile Server and Property File Locations Matrix [page 66]

5.15 MDM Configuration Support for iOS 7 Devices

For devices with iOS 7 or higher, Apple provides the "Managed App Configuration" functionality. This functionality allows a Mobile Device Management (MDM) server to push down a configuration dictionary into the managed app's NSUserDefaults for the purpose of remotely configuring settings.

For further information on MDM configuration support, see https://developer.apple.com/library/ios/ samplecode/sc2279/Introduction/Intro.html

SAP BusinessObjects Mobile (SAP BI) Application Configuration Properties that can be Managed by the MDM Server

Predefined Connections List

You can configure a single predefined connection or multiple predefined connections in the application by specifying values for the conn.list.(n) property on the MDM server, where 'n' is the array index starting with a value of 1. Each array item is of the type "String", and the value of each item corresponds to a connection URL.

For example, you can specify a predefined connection URL for a BOE server connection with the syntax shown below: conn.list.1=sapbi:// addconnection? ConnectionType=BOEConnection&con nection_name=SAP

%20Analytics %20Gallery&server_url=&cms=

Note

For more information on specifying valid URL values for a predefined connections list, refer to chapter 5.1

Customizing the Onboarding Features of the Developer's Guide posted on http://help.sap.com/bomobileios .

94

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Default Application Behavior Properties (Other than the predefined connections list)

All the key properties defined in the defaultsettings.plist file of the application SDK that are described in the chapter 5 of the Developer's Guide ("Customizing the Default Behavior of the Application"), can be managed by the MDM using the corresponding key-value pairs.

For example, you want the MDM to remotely manage the email feature of the application functionality. The feature.email.enabled.default property in defaultsettings.plist has a default value of 'true'. To manage this feature remotely, you can define the corresponding key as email.enabled in the configuration dictionary of the MDM server and specify its value as 'true'/'false', based on your requirements. Similarly, you can manage other application features such as annotation, collaboration, Help, and default Home view.

For each property (formatted as

feature.<xyz>.default

) in defaultsettings.plist of the app, you can define the corresponding property on the MDM server in the format

<xyz>

.

For a description of all such properties that define the default behavior of the application, refer to the subchapters of chapter 5 in the Developer's Guide posted on http://help.sap.com/bomobileios .

Note

The only property in defaultSettings.plist that does not follow the above rule is the predefined connections list (feature.predefinedconnections.list.default) that defines an array of predefined connection URLs.

5.16 Working With Notifications

When you refresh the Home screen (using the pull-down gesture) or when it is auto-refreshed, the

(

Notifications

) icon appears in the tool-bar if server updates are available for your downloaded BI documents. You can view and fetch document updates using the panel that appears on tapping the

Notifications

icon. The notifications displayed in the panel include:

● Notifications for downloaded documents that are updated on the server.

● Notifications for downloaded documents that are removed from the server or are no longer assigned to the

Mobile category.

● Notifications for mobile-enabled documents that are added new on the server, and are thus available on the

Home screen of the application.

Example 1: Notifications when documents are updated on the server

To understand this scenario, perform the following steps:

1. Download a BI document from the

Home

screen of the application to your device.

2. Log on to BI Launch Pad and do either of the following:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

95

Access the BI document and choose

Schedule

from the context menu. On the

Scheduling

page, set any values for the scheduling options; preferably run an instance by choosing the

<Recurrence>

value as

Now; or

Open the BI document, choose the

Modify

menu option, edit and save document.

3. Refresh the application's

Home

screen. Tap (Notifications) on the

Home

screen toolbar.

The application opens the

Notifications

panel, and you find the BI document displayed on the panel.

4. Tap the document to retrieve the update and to view the updated document or tap the (

Update

) icon, which is located beside the document title, to update the document.

Example 2: Notifications when BI documents are removed from the server

To understand this scenario, perform the following steps:

1. Download a BI document from the

Home

screen of the application to your device.

2. Log on to BI Launch Pad and do either of the following:

Search and navigate to the BI document, choose

Categories

and deselect the

Mobile

category assigned to the document; or

If you have the rights, delete the BI document from the server.

3. Refresh the application's

Home

screen. Tap (Notifications) on the

Home

screen toolbar.

The application takes you to the

Notifications

panel, and you find the BI document listed in the panel.

Example 3: Notifications when Web Intelligence documents with conditional formatting are refreshed on the server

To understand this scenario, perform the following steps:

1. Identify a document with conditional formatting.

Users can identify conditional formatting by observing the formatting of table cells in the reports of the document. They may have a different colored text and background-image or hyperlinks.

2. Download a BI document from the

Home

screen of the application to your device.

3. Open the document, and tap (

Settings

) in the tool-bar to open the secondary report tool-bar, and choose

'i' (

Info

) to go to the

Information

screen of the document in the app, and ensure that it is

subscribed for alerts

.

4. Log on to the BI platform server (BI Launch Pad), search and open the Web Intelligence document, and choose (Refresh).

(This refreshes the data-providers of the document.)

5. Refresh the application's

Home

screen. Tap (Notifications) on the

Home

screen toolbar.

The application takes you to the

Notifications

panel, and you find the BI document displayed in the panel.

6. Tap the document to retrieve the update and to view the updated document or tap the (

Update

) icon, which is located beside the document title, to update the document.

96

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Example 4: Notifications when BI documents are added to the Mobile category on the server

To understand this scenario, perform the following steps:

1. Log on to BI launch pad and add a BI document to the Mobile category.

2. Refresh the application's

Home

screen. Tap (Notifications) on the

Home

screen toolbar.

The application takes you to the

Notifications

panel, and you find the BI document displayed within the

Added

Documents

section on the

Notifications

panel.

3. Tap the document to view the newly added document.

Notifications During Auto Refresh of Home Screen and Auto-Update of BI

Documents

The application Home screen is auto-refreshed every 15 minutes. When an auto-refresh takes place, the BI documents are re-listed on the Home screen such that they are synchronized with the server.

When the screen is auto-refreshed, the (

Notifications

) icon appears in the tool-bar if server updates are available for your downloaded BI documents.

The application provides you with an

Auto Update

option that you can enable using the application Settings. With each refresh of the Home screen, if you want the documents with available updates to be re-downloaded from the server, without explicitly fetching the updates from the Notifications panel, set

Auto Update

to ON.

The figure below displays how the "Notifications" panel appears when auto update is OFF and when it is ON:

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

97

Notifications on the Application Icon

Whenever there are refresh updates available for your downloaded BI documents, the application icon on the device screen displays a notification badge as shown in the below image:

The number that appears over the badge is a summation of notifications from all server connections that you have added in the application. For example, if you have added 3 server connections, and there is 1 update available on first server, 1 update available on the second server and 2 updates available on the third server, the Notifications badge displays the sum of all notifications, which is 4.

This number changes dynamically and is always in synchronization with the (

Notifications

) icon that appears in the tool-bar of the application.

98

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

Related Information

What's New in 6.1? [page 11]

Administrator's Guide

Administering SAP BusinessObjects Mobile for iOS

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

99

6 Creating Personal Views of Web

Intelligence Reports

Personal Views is a capability to save personalized views of a Web Intelligence report.

Understanding the Significance of Personal Views

For some business requirements, you may want a particular view of a Web Intelligence report to be opened every day and refreshed. For example, consider the following use case:

For customer A, a sales representative filters data with certain input control values and drills down two levels in the report tables. The representative then saves a personal view of the report and names it Daily Sales - Customer

A. Now the representative can open this personal view every day and quickly refresh (or update) the report with latest data from the server, without performing the same actions for customer A again. This way, having performed different server actions (for different customers), the representative can save multiple personal views of the same report (but with different results) for offline or personalized viewing (such as Daily Sales - Customer A,

Daily Sales - Customer B and Daily Sales - Customer C).

Creating and Accessing Personal Views in the Application

To create a personal view of a Web Intelligence report, perform the following steps:

1. Open the report, and perform the required server actions so that the report arrives at your desired view. (Your actions may include drilling, filtering using input controls, displaying information in sections, and other actions based on server interaction.)

2. Tap (

Report Settings

) to open the secondary toolbar, then tap

Save View

.

The "Save View" dialog opens.

3. Specify a

Personal View Name

and optionally a description of the view. Then tap

Done

.

The personal view is created and you can access it using the

Personal Views

tab in the

Browse

panel. You can also refresh the data in your personal view anytime by tapping the [Refresh] option in the view toolbar.

Characteristics of Personal Views

1. You can create multiple personal views of the same base (source) document, and each view is independent of each other.

2. If you want a saved personal view to display the latest information from the server (in online mode), you need to explicitly

Refresh

the personal view after opening it. You can update the personal view with the latest data from the server in two ways:

100

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Creating Personal Views of Web Intelligence Reports

○ By tapping the

Refresh

icon in the toolbar of the opened personal view.

○ By tapping the

Update

option that appears in the Information (

>

) screen of the personal view tile.

Note

If you want to disable the refresh or update of personal views in the application, you can set the value of the following client setting to 'false' feature.webi.personal.view.update.enabled

To access client settings based on the server version that you are using, see the related topics of this chapter.

3. When you refresh a personal view, the application refreshes the source BI report (from which you created the view) and applies all the history actions on the report to bring it to the view state.

4. You can save personal views of Web Intelligence documents only. Other BI document types do not support this feature.

5. Personal views are supported on both Web Intelligence documents and their instances.

Note

If the Web Intelligence document is scheduled on the BI platform server, and there is an instance of the same available on the server, when users tap

Update

or

Refresh

, the server returns either the refreshed document or its latest instance, depending what is more recent.

6. When you save a personal view, the application does the following:

○ Saves the state of a Web Intelligence report. (In whatever state you left the report before saving the view, the same state is maintained when you access the personal view.)

○ Saves the history of server actions that you performed on the report before saving the personal view.

On a personal view, you can perform all server actions that you performed before saving the view. For example, if you drilled down in the report's charts or tables and applied filters, you can perform the same actions after opening the personal view (even in offline mode).

Note

If the report has REL (report element linking), the application also records the sequence in which you filtered data in the linked report parts. You can only use REL in the same sequence of linking.

7. Irrespective of whether you are in offline or online working mode, you can perform only those actions on a saved personal view that you performed before saving it.

For example, if you drilled down in report parts, but did not drill up, you cannot drill up in the personal view.

If the report has hierarchical tables, but you did not perform an expand or collapse action on the nodes, you cannot expand or collapse nodes in the personal view.

Note

For a personal view, the application does not record the actions that are independent of server interaction

(such as sort, re-order, or freeze in tables). Users can perform these actions in personal views anytime and in any order.

8. Apart from Refresh and Update, no other action (request) on a personal view goes to the mobile BI server.

Administrator's Guide

Creating Personal Views of Web Intelligence Reports

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

101

(Before saving the view, when you perform server actions such as drill and filter, the application fetches the required data and stores it in local memory of the device. When you perform the same actions on the saved personal view, the required data is fetched from device memory, and there is no server interaction.)

9. If the personal view has an OpenDocument URL that targets a BI document that is not Web Intelligence, the target document does not open when you tap the URL in the personal view (even if you tapped the URL before saving the view of report).

10. If the BI report has drill-enabled tables, the personal view displays the drill pop-up options on only those cells on which you have drilled information before saving the view. Other cells do not display the drill pop-up.

11. Using input controls, if you have filtered data in the BI report before saving the personal view, when you open the personal view and tap (

Filter

), the pop-up displays only the combination of values that you chose while filtering data. The following figure displays the view that appears:

102

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Creating Personal Views of Web Intelligence Reports

When you tap on any value combination, the pop-up displays all the individual values the same way as they appeared in the original BI report, as shown below:

You can select any value and tap

Apply

to apply value selections.

12. You cannot create a personal view from an existing personal view.

13. The maximum number of personal views that you can save on-device depends on the value of the

Personal

View Storage

setting that you specify in

Application Settings

->

Additional Settings

.

Note

If you specify 'None' as the personal view storage limit, you can save an unlimited number of personal views on your device.

14. You can delete personal views from the device in one of the following ways:

○ By tapping the

Delete Personal View

option that appears on the Information(>) pop-up of the personal view tile.

○ By erasing application data using

(Settings)Application SettingsAdditional SettingsClear Data

Remove Application Data

○ By removing the server connection that has the BI report from which the personal views are created.

Administrator's Guide

Creating Personal Views of Web Intelligence Reports

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

103

15. In the following scenarios, you cannot save personal views for a Web Intelligence report:

○ The parent document is configured to "Refresh on Open".

○ The parent document is set to Confidential on the server.

○ The parent document is a "View as PDF".

○ The

<offline storage>

property on the Mobile server is set to 'False'.

16. In the following scenarios, saved personal views are automatically removed from the device memory:

○ The parent (source) document of the personal view has expired (based on the TTL server parameter).

○ The administrator has either removed the parent document from the server or unassigned it from the

Mobile category.

○ The administrator set the parent document to Confidential on the server.

○ The

<offline storage>

property on the Mobile server is set to 'False'.

17. The secondary toolbar of a personal view does not have the

Collaborate

option, as personal views are not designed for discussing.

Few Limitations of Personal Views

1. If you use hierarchical input controls or hierarchical sections in a Web Intelligence report, the application does not permit you to save a personal view of the report.

2. When you email a personal view, the email body contains the view snapshot only. It does not contain any SAP

BI URL for OpenDocument.

3. You cannot save a personal view of the Web Intelligence report that is invoked by a source report using the

OpenDocument function. The application prompts you to return to the source document for saving a personal view.

4. Personal views are supported only on the following BI Platform server versions:

○ SAP BusinessObjects BI platform 4.0, Support Package 8 and above

○ SAP BusinessObjects BI platform 4.1, Support Package 2 and above

5. If your personal view has an OpenDocument URL that targets the same BI document as the source (parent document from which you created the view), the URL does not work as expected in the personal view.

104

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Creating Personal Views of Web Intelligence Reports

7 Managing the Mobile support for

Dashboards

SAP BusinessObjects Dashboards allows dashboard consumers to view models on mobile devices such as the iPad. Certain components and dashboard features are unavailable or behave differently on mobile devices. You can use the

Mobile Compatibility

panel to ensure that your model will run correctly on mobile devices.

Add-on components created using the Dashboards Component SDK can be made mobile-compatible. For more information, refer to the Dashboards Component SDK documentation, available on the SAP Help Portal ( http:// help.sap.com/bodash41 ).

Note

Mobile support requires SAP BusinessObject Business Intelligence platform 4.0 Support Package 5 or later.

7.1 Using the Mobile Compatibility panel

Context

The

Mobile Compatibility

panel helps ensure that your model will run correctly on mobile devices. The panel displays a warning icon for each component or feature in your model that is unsupported on mobile devices.

Selecting a component in the

Mobile Compatibility

panel selects it on the canvas and opens its property sheet.

To view all incompatible components or features in the model, in the

Mobile Compatibility

panel, click

Refresh

( ). Incompatible items are categorized as follows:

●

General

- Miscellaneous warnings and suggestions, such as an oversized canvas or an unsupported theme.

●

Component

- Unsupported components. Component warnings are split into the following subcategories:

○ Unsupported components. These components are not displayed in the model when the model is viewed on mobile. Components in this category are denoted by a red warning icon.

○ Supported components with unsupported properties. These components are displayed when the model is viewed on mobile but may behave differently or have certain properties disabled. Components in this category are denoted by a yellow warning icon.

○ Visual variant components. These components are replaced by their fallback component when the model is viewed on mobile with all settings preserved. For example,

Gauge2

or

Gauge3

would be replaced by

Gauge

on mobile. Components in this category are denoted by a yellow warning icon.

Note

Background2

,

Background4

, and

Background5

are supported.

●

Connectivity

- Unsupported external connections. This includes all connections added through the

Data

Manager

.

Administrator's Guide

Managing the Mobile support for Dashboards

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

105

7.2 Supported components in mobile dashboards

The following is a summary of all components supported on mobile devices, along with any of their unsupported properties or features.

Note

All components have

Entry Effect

and

Insert On

:

Mouse Over

disabled on mobile.

Chart components

Component

Bar Chart

Column Chart

Bubble Plot

Combination Chart

Line Chart

Pie Chart

Stacked Bar Chart

Stacked Column Chart

106

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Unsupported properties

● All

Enable Run-Time Tools

,

Plot Area

,

Title Area

, and

Range Label

options.

●

Allow Zoom Out Only

,

Logarithmic

, and

Fixed Label Size

scale options.

●

Show Fill

,

Show Border

,

Border Thickness

, and

Check

Box

legend options.

● All underline font styles.

●

Alerts

.

● All

Enable Run-Time Tools

options.

●

Allow Zoom Out Only

,

Logarithmic

, and

Fixed Label Size

scale options.

●

Show Fill

,

Show Border

,

Border Thickness

, and

Check

Box

legend options.

● All underline font styles.

●

Alerts

.

● All

Enable Run-Time Tools

,

Plot Area

,

Title Area

,

Legend

Area

, and

Range Label

options.

●

Allow Zoom Out Only

,

Logarithmic

, and

Fixed Label Size

scale options.

●

Show Fill

,

Show Border

,

Border Thickness

, and

Check

Box

legend options.

● All underline font styles.

●

Alerts

.

● All

Plot Area

,

Title Area

, and

Legend Area

options.

● All underline font styles.

● All

Enable Run-Time Tools

,

Plot Area

,

Title Area

,

Legend

Area

, and

Range Label

options.

●

Allow Zoom Out Only

,

Logarithmic

, and

Fixed Label Size

scale options.

●

Show Fill

,

Show Border

,

Border Thickness

, and

Check

Box

legend options.

Administrator's Guide

Managing the Mobile support for Dashboards

Component

Waterfall Chart

Container components

Component

Canvas Container

Tab Set

Selector components

Component

Check Box

Icon

Push Button

Radio Button

Toggle Button

Combo Box

Label Based Menu

List Box

List View

Administrator's Guide

Managing the Mobile support for Dashboards

Unsupported properties

● The

Marker Overlap

appearance option.

● All underline font styles.

●

Alerts

.

● All

Enable Run-Time Tools

options.

●

Allow Zoom Out Only

,

Logarithmic

,

Fixed Label Size

, and

Minor Divisions

scale options.

●

Show Fill

,

Show Border

,

Border Thickness

, and

Check

Box

legend options.

● All underline font styles.

Unsupported properties

All

Scroll Bar

color options.

Unsupported properties

All properties are supported.

● All

Scroll Bar

color options.

●

Drop-Down Animation

.

●

Alerts

.

● All

Interaction

options except

Always Expanded

and

Expand On Mouse Click

.

● All

Title

options.

●

Alerts

.

● All

Scroll Bar

color options.

●

Alerts

.

● All

Scroll Bar

color options.

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

107

Component

Scorecard

Unsupported properties

● Change

Column Width

at runtime and

Column Width

by percentage.

Single Value components

Component

Gauge

Gauge7

Gauge8

Horizontal Progress Bar

Vertical Progress Bar

Horizontal Slider

Vertical Slider

Text components

Component

Input Text

Input Text Area

Label

Unsupported properties

●

Object Elasticity

,

Adjustable

and

Open Limits

,

Mouse

Sensitivity

, and

Vertical Mouse Tracking

behavior options.

●

Play Button

and

Limit Background Color

appearance options.

●

Adjustable

and

Open Limits

behavior options.

●

Play Button

and

Limit Background Color

appearance options.

Unsupported properties

All properties are supported.

Enable HTML Formatting

.

● All

Scroll Bar

color options.

●

Enable HTML Formatting

.

Art and background components

Component

Background

Background2

Background4

Background5

Ellipse

Unsupported properties

All properties are supported.

108

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile support for Dashboards

Component

Horizontal Line

Rectangle

Vertical Line

Image

Unsupported properties

●

Import

SWF files.

●

Hide SWF Background Color

.

Web Connectivity

Component

URL Button

Unsupported properties

All properties are supported.

Note

Linking a

URL button

to unsupported data sources will not work. For example, an OpenDocument URL will not pass

FlashVars to the model since FlashVars are not supported.

For more information about unsupported data sources, see

Unsupported features in mobile dashboards [page

111]

.

Note

On an iPad, external URLs (such as http://help.sap.com) are opened in Safari.

Universe Connectivity

Component

Query Refresh Button

Unsupported properties

All properties are supported.

7.2.1 Using components in mobile dashboards

Mobile dashboard users interact with components using the device's touch screen. The user can interact with components and items by tapping, touching, or dragging them. The user can also pinch to zoom chart component scales or models with a canvas size larger than the mobile device's resolution.

Component interaction that involves clicking or dragging is unchanged on mobile. Component interaction that involves mousing over is unsupported, with the following exceptions:

Administrator's Guide

Managing the Mobile support for Dashboards

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

109

Pie Chart

When viewing a model on a computer, the user can mouse over a slice of a

Pie Chart

to show detailed values. On mobile devices, the user must tap the slice. The values are displayed in the center of the chart, as shown below:

Column Chart and Line Chart

When viewing a model on a computer, the user can mouse over a column on a

Column Chart

or a point on a

Line

Chart

to show detailed values. On mobile devices, the user must briefly touch the column or point. The values are displayed on the column or point, as shown below:

110

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile support for Dashboards

Pinch to zoom

The user must pinch to zoom chart component scales. Pinching to zoom a chart's scale is shown below:

7.3 Unsupported features in mobile dashboards

The following is a summary of unsupported or partially supported features when viewing a model on mobile devices.

Fonts

For a list of fonts supported on mobile, see http://iosfonts.com/ . All listed fonts that are installed on your local machine will be added to Dashboards' font list with

(iOS 5+)

appended.

Note

If a font is not supported, it defaults to Verdana.

Themes

Only the

Nova

theme is supported.

Note

If another theme is used, it defaults to

Nova

. The color scheme remains the same.

Administrator's Guide

Managing the Mobile support for Dashboards

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

111

Canvas size

If the canvas is larger than the mobile device's native resolution, scroll bars will be used if the dashboard is viewed in

Original Size Mode

. The native resolution of the iPad is 1024x768, so it is recommended you set the canvas to this size when designing your model.

Model connectivity

If the model is running in offline mode, or if the mobile device has no network connection, all connections in the model will be disabled and will use cached data.

Note

Only connections added from the

Query Browser

are supported. Connections added through the

Data Manager

are supported if denoted by an asterisk.

7.4 Saving mobile dashboards to BI platform folders

Context

When you create a new model and save it to the platform, it is saved as a Dashboards object that includes both the design file (XLF) and the runtime file (SWF).

Note

For general information about creating, modifying, and saving models, see the Dashboards and Presentation

Design User Guide, available on the SAP Help Portal ( http://help.sap.com

) under

Analytics All Products

.

Procedure

1. After creating or modifying a model, click

File

and select one of the following options:

Option

Save to Platform

Mobile Only

Description

Use this option if you have created a new model, or have opened and modified an existing

Dashboards model. Features unsupported on mobile devices are omitted.

112

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile support for Dashboards

Option Description

Note

For more information about unsupported features, see

Using the Mobile Compatibility panel

[page 105]

.

Save to Platform

Desktop and Mobile

Use this option if you have created a new model, or have opened and modified an existing

Dashboards model. In the mobile file, features unsupported on mobile devices are omitted.

Note

For more information about unsupported features, see

Using the Mobile Compatibility panel

[page 105]

.

Save to Platform As

Dashboards Object for Mobile Only

Use this option if you have opened and modified an existing Dashboards model, or have opened an Xcelsius object and want to save it as a new Dashboards object, but do not want to overwrite the existing object. Features unsupported on mobile devices are omitted.

Note

For more information about unsupported features, see

Using the Mobile Compatibility panel

[page 105]

.

Save to Platform As

Dashboards Object for Desktop and

Mobile

Use this option if you have opened and modified an existing Dashboards model, or have opened an Xcelsius object and want to save it as a new Dashboards object, but do not want to overwrite the existing object. In the mobile file, features unsupported on mobile devices are omitted.

Note

For more information about unsupported features, see

Using the Mobile Compatibility panel

[page 105]

.

2. In the

Log On to SAP BusinessObjects Business Intelligence platform

dialog box, enter the following information:

Option

System

Description

Type the name of the Central Management console (CMC) where you want to save the file.

The CMC stores information about the objects saved to the BI platform system. For more information about the CMC, refer to the BI platform documentation available on the SAP Help Portal ( http:// help.sap.com

).

User name

Password

Type your logon name.

Type you password.

Authentication Click the appropriate authentication type.

3. Click

OK

.

4. If you are not replacing an existing file, select the folder where you want to save the Dashboards object, enter a file name, and click

Save

.

Administrator's Guide

Managing the Mobile support for Dashboards

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

113

8 Managing the Mobile support for

Information Spaces and Information Views

SAP BusinessObjects Explorer is a data discovery application that allows you navigate through datasets known as

Information Spaces and Exploration Views. These datasets are created in the web version of SAP BusinessObjects

Explorer as part SAP BusinessObjects Business Platform.

When you open an Information Space on an iPhone or iPad, you can explore your corporate data, search, apply filters and dimensions and retrieve answers to your business questions.

In order to access your corporate data on your iPhone or iPad, you need to ensure that your data administrator makes the appropriate connections available to your user profile.

For information on how to create information spaces using the SAP BusinessObjects Explorer and other related information, refer to the SAP BusinessObjects Explorer for iPhone/iPad User Guide available at http:// help.sap.com/businessobject/product_guides/boexpl41/en/41_expl_user_en.pdf

8.1 Valid Data Format for Augmented Views

When the data is correctly formatted, Information Spaces and Exploration Views show the information augmented, so that you can view the information in terms of your points of interest (POIs).

For the augmented view of a document to load, it is essential that one of the columns of the data set uploaded to the Explorer server is formatted as a point of interest (POI).

A POI is a structure containing the following information:

● POI name (mandatory)

● POI location (mandatory)

● POI image

● POI associated link

The POI column in the data set should be formatted as follows:

NAME|| LATITUDE;LONGITUDE|| IMAGE_URL|| LINK_URL

Example: myStore||45.5;-1.2||http://mydomain/myimage||http://mydomain

This order and format is mandatory. POI information must be separated by the string “||”.

The following is an example of a data set which is valid for getting an augmented view:

Store

Store 1||

46.43431150;1.16331900||

Year

2010

Quarter

Q1

Revenue

7703

114

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile support for Information Spaces and Information Views

Store http://sapweb20.com/blog/ augreality/icon21.png

Store 1||

46.43431150;1.16331900|| http://sapweb20.com/blog/ augreality/icon21.png

Store 1||

46.43431150;1.16331900|| http://sapweb20.com/blog/ augreality/icon21.png

Store 1||

46.43431150;1.16331900|| http://sapweb20.com/blog/ augreality/icon21.png

Store 2||

50.47431150;2.55331900|| http://sapweb20.com/blog/ augreality/icon13.png|| http://sapweb20.com/blog/ augreality/icon13.png

Store 2||

50.47431150;2.55331900|| http://sapweb20.com/blog/ augreality/icon13.png|| http://sapweb20.com/blog/ augreality/icon13.png

Store 2||

50.47431150;2.55331900|| http://sapweb20.com/blog/ augreality/icon13.png|| http://sapweb20.com/blog/ augreality/icon13.png

Store 2||

50.47431150;2.55331900|| http://sapweb20.com/blog/ augreality/icon13.png|| http://sapweb20.com/blog/ augreality/icon13.png

Year

2010

2010

2010

2010

2010

2010

2010

Quarter

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Revenue

3918

5602

3100

1025

680

1100

6709

The data set can have any number of dimensions, but one of the columns should be formatted as POI. If this condition is fulfilled, then when tapping the document, the augmented view will load and the augmented views icon will be available. Otherwise, the normal exploration view opens up.

Administrator's Guide

Managing the Mobile support for Information Spaces and Information Views

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

115

9 Managing the Mobile Support for Analysis

Applications

Analysis applications are Web applications that allow users to analyze data from SAP NetWeaver BW and SAP

HANA. Integration with SAP BusinessObjects Mobile means that users can access analysis applications on mobile devices, such as the iPad or the iPhone.

Application designers create analysis applications with SAP BusinessObjects Design Studio. For using analysis applications on mobile devices and integrating them with SAP BusinessObjects Mobile they need to create the analysis applications in the

SAP BusinessObjects BI Platform

mode of Design Studio.

This section provides administrators with an overview of the tasks required to integrate analysis applications with

SAP BusinessObjects Mobile.

9.1 Installation

Make sure that you have installed the full installation of the Analysis Application Service for SAP BusinessObjects

Design Studio on the BI platform, including:

Analysis Application Web Components

,

Analysis Application Service

and

Analysis Application support for Mobile Devices

.

The installation feature

Analysis Application support for Mobile Devices

adds mobile support to analysis applications, thereby integrating analysis applications with SAP BusinessObjects Mobile. It allows application users to access analysis applications on mobile devices, such as the iPad or the iPhone.

Note

The setup feature

Analysis Application support for Mobile Services

requires Mobile Services to be installed.

For more information, see the Administrator Guide: SAP BusinessObjects Design Studio based on SAP

BusinessObjects BI Platform on the SAP Help Portal at http://help.sap.com/boad .

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

Note

The 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

116

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile Support for Analysis Applications

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

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

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

.

Administrator's Guide

Managing the Mobile Support for Analysis Applications

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

117

The

Categories

dialog box appears.

3. Choose the mobile category.

4. Click

OK

.

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

,

androidphone

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

118

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile Support for Analysis Applications

9.3 Creating Analysis Applications in SAP BusinessObjects

Mobile for Mobile Devices

When creating mobile analysis applications with SAP BusinessObjects Mobile for mobile devices, note the following SAP recommendations:

● Keep the applications simple and do not use too many components.

● Do not use crosstab components for mobile applications.

● Only design mobile applications in portrait format. Landscape orientation is not supported when running the application in the SAP BusinessObjects Mobile application.

Note

○ When using an iPhone, only create applications based on the predefined templates for iPhones (do not use the blank template for iPhones).

In the

New Application

dialog box, select

iPhone

as the target device. In the next step, select a predefined iPhone template (for example,

iPhone Template 1

).

○ When using an Android phone or tablet, there are no predefined templates. In the

New Application

dialog box, leave the default value as the target device. Within the

Display

properties of the application, select one of the following mobile themes listed:

○ mobile black

○ blue crystal

○ mobile

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

9.4 Further information

For more information about creating analysis applications with SAP BusinessObjects Design Studio, see the

Application Designer Guide: Designing Analysis Applications on the SAP Help Portal at http://help.sap.com/boad .

For more information about installing, configuring and managing SAP BusinessObjects Design Studio, see the

Administrator Guide: SAP BusinessObjects Design Studio based on SAP BusinessObjects BI Platform on the SAP

Help Portal at http://help.sap.com/boad .

Administrator's Guide

Managing the Mobile Support for Analysis Applications

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

119

10 Managing the Mobile Support for SAP

Lumira Server or SAP Lumira Cloud

SAP Lumira server and SAP Lumira cloud are visual data analysis tools. Integration with SAP BusinessObjects

Mobile means that users can access datasets and visualizations on the iPad. Users can also create visualizations on the iPad and save them to the SAP Lumira server or the SAP Lumira Cloud. This section provides administrators with an overview of the tasks required to connect SAP Lumira server or SAP Lumira Cloud with

SAP BusinessObjects Mobile.

10.1 Configuring the Connection to SAP Lumira server or SAP

Lumira Cloud

1. In the SAP BusinessObjects Mobile application, open the

Application Settings

.

2. Tap

Create new connection

, and then tap

Connection type

.

3. Choose

SAP Lumira Cloud

or

SAP Lumira server

.

4. Enter a

Connection Name

.

5. Enter the

Server URL

.

6. Enter a

User Name

.

7. Optional: Enter a

Password

then toggle

Save Password to ON

. If you do not enter a password, you will be prompted to enter a password when you attempt to connect to the SAP Lumira Server or SAP Lumira Cloud.

8. Tap

Done

.

The connection you created will appear in the connections list in the Application Settings. Tap the connection name to connect to SAP Lumira Server or SAP Lumira Cloud.

10.2 Further Information

For more information about creating visualizations with SAP Lumira Server, see the SAP Lumira Server User

Guide on the SAP Help Portal at http://help.sap.com/lumira

For more information about creating visualizations with SAP Lumira Cloud, see the SAP Lumira Cloud User Guide on the SAP Help Portal at http://help.sap.com/lumira .

120

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Managing the Mobile Support for SAP Lumira Server or SAP Lumira Cloud

11 Troubleshooting Errors

11.1 Troubleshooting the Mobile Server Error Messages

In this section, you find a description of the error messages that are generated on server side of the SAP

BusinessObjects Mobile on iOS application. This information may help you in troubleshooting these errors when the app users face them.

Note

● Errors explained in this section are generated on the server side of the Mobile solution, yet they are encountered while working with the app.

● Most errors occuring on the server are caused by HTTP errors such as HTTP 503, HTTP 400, HTTP 404,

HTTP 500 and others.

With effect from the 4.0.3 release of the application, whenever the application (client) receives an HTTP error code from the server, the code is included in the error message displayed by the app. This helps the administrator identify the server error and take the required action to fix it.

For example, consider the following error:

"Connection to the server could not be established; try again or contact your administrator (MOB06005)"

If during the occurence of this error, the application recieves HTTP 503 error from the server, the error message is displayed as:

"Connection to the server could not be established; try again or contact your administrator (MOB06005)

(HTTP 503)"

Sometimes, instead of the HTTP code, the server may return a zero error code ('0'). In this case, the application does not append anything to the error message.

11.1.1 An internal server error occurred while processing the client request (MOB00022)

Cause

This error occurs when the user is connected to 4.0 Fix Pack 2.13 release of the BI platform server and does content

Search on server

using the SAP BI application on iPad. It is a limitation of server configuration.

Action

To resolve this issue, take the following steps:

1. Stop the Web application server on which the MobileBIService.war is installed.

2. Locate MobiService.jar file in the following directory:

<WEB_APP_ROOT>\MobileBIService\WEB-INF\lib

Administrator's Guide

Troubleshooting Errors

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

121

3. Open MobiService.jar as a zip file (using Winrar or Winzip).

4. Extract command_factories.properties file from the MobiService.jar

5. Open command_factories.properties using a text editor and add the following lines at the end of file: com.businessobjects.mobilebi.server.messages.AdvancedSearchRequest=com.businessob

jects.mobilebi.server.commands.impl.AdvancedSearchFactory

com.businessobjects.mobilebi.server.messages.AdvancedSearchDataRequest=com.busine

ssobjects.mobilebi.server.commands.impl.AdvancedSearchDataFactory

Save the file.

6. Update MobiService.jar with the updated command_factories.properties file.

7. Restart the Web application server.

11.1.2 Connection to the server could not be established; contact your administrator if the problem persists

(MOB06004)

Cause

The proxy information configured on the device might be incorrect or the application server might be down.

Action

1. Verify that the proxy server settings are configured correctly on your device.

2. Verify the connectivity to the application servers on which the Mobile WebApp and the BusinessObjects

Enterprise (BI platform) is deployed. You should also make sure that these servers are up and running.

11.1.3 Connection to the server could not be established; try again or contact your administrator (MOB06005)

Cause

This error occurs when there is a problem in redirecting the request to the Web proxy server. The server is unable to handle the request temporarily, due to an overload of the request. This error arises due to HTTP 503 response from the server.

Action

Trying again after sometime resolves the issue.

11.1.4 The request has timed out; try again or contact your system administrator (MOB06006)

Cause

122

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Troubleshooting Errors

This error occurs when user's HTTP request to the server has timed out. This can be due to slow speed of the network or because of connectivity problems between the client and server.

Action

Verify the connectivity of user's mobile device to the mobile server.

11.1.5 You are not authorized for this request (MOB06008)

Cause

The file for which the user has requested the server requires access rights and permissions.

Action

Check if the user is authorized to view or access the requested document on the BI platform.

11.1.6 Your request is invalid; verify the connection details or contact your administrator (MOB06009)

Cause

The request which the user has made to the server is incorrect. This message may also be displayed due to an

HTTP 404 error.

Action

Ask the user to try again after some time. If user's request invokes a document from the server, verify if the requested document is accessible on the BI platform server.

11.1.7 Internal server error occurred while processing your request; try again or contact your system administrator

(MOB06010)

Cause

This error indicates that the Web application server has encountered some unexpected condition. This can also arise due to improperly configured proxy servers.

Action

Verify that the proxy server settings are configured correctly on user's device.

If this does not resolve the problem, try restarting the Web application server.

Administrator's Guide

Troubleshooting Errors

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

123

11.1.8 Missing prompt value; select at least one value for the prompt (MOB06011)

Cause

This error appears when the user has not entered any values in the prompt which appears while refreshing a Web

Intelligence document using the app.

Action

Ask the user to ensure that he/she has selected at least one value for each prompt that appears on refreshing a document.

11.1.9 Verify network connectivity (MOB06021)

Cause

This error is encountered when the openDocument link of a webintelligence document is not able to fetch or retrieve the target document.

Action

Verify that the network connectivity is fine. You can do so by trying to access the internet from the browser on user's device.

11.1.10 Connection to the server could not be established; try again or contact your administrator (MOB06031)

Cause

This error occurs when the network within which users are working does not have connectivity with the SAP

BusinessObjects Mobile server.

Action

Verify the server connection details in the app on user's device, such as the IP address or syntax of the connection

URL.

11.1.11 Server returned an error while downloading the document (MOB06060)

Cause

This error may appear when the user is trying to download a document. It occurs due to following reasons:

124

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Troubleshooting Errors

● There are connectivity issues between the Mobile server and the CMS (BI platform server).

● The document which the user is trying to download is corrupt.

Action

Ask the user to try downloading the document again. If the problem persists, check if the document is opening and behaving as expected on the BI platform.

11.1.12 This action cannot be performed; verify network connectivity (MOB08002)

Cause

This error occurs due to one of the following reasons:

● Connection to the BI platform server is lost.

● The device has lost its connectivity to the Wifi network.

Action

Verify the following:

1. Application's connectivity to the BI platform.

2. Device connectivity to the Wifi network.

11.1.13 An internal server error occurred while processing your request on hierarchical data; the document will be closed; contact your administrator for more information (MOB09001)

Cause

This error is encountered when users are working with reports based on hierarchical report parts or hierarchical prompts. It occurs because the Web Intelligence server is unable to fetch data from a hierarchical data source

(such as OLAP and BW).

Administrator's Guide

Troubleshooting Errors

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

125

Action

None. This is a known limitation of the app.

11.1.14 There was a problem in opening the document; download the document again or contact your administrator (MOB06061)

Cause

This error appears when users are trying to open a document that is either corrupt or is not downloaded completely.

Action

Ask the user to download the document again and to download it completely. Also, check if the document is opening and behaving as expected on the BI platform.

11.1.15 Maximum character file size limit exceeded. The document is too large to be processed by the server.

Contact your BusinessObjects administrator (WIS

30272)

Cause

When users view a Web Intelligence document in HTML format, the Web Intelligence server generates character based output, which is then interpreted by the Web browser. This errors occurs, if the size of the character output is greater than the maximum size specified by you on the Web Intelligence server.

Action

As the app administrator, you can change the value for Maximum Character Stream Size (MB) in the Web

Intelligence Processing server properties via the CMC (Central Management Console). However, increasing the maximum binary output (Binary Stream Maximum Size (MB)) can affect the performance.

126

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Troubleshooting Errors

11.2 Troubleshooting the Mobile Client Error Messages

In this section, you find a description of the error messages which are generated on client side of the SAP

BusinessObjects Mobile on iOS application. These error messages may be encountered while working with the app as well.

11.2.1 Email is not configured on this device (MOB07001)

Cause

This error occurs when the user does not have email configured on your device.

Action

Configure a valid email account on user's device.

11.2.2 Internal server error occurred while processing your request; contact your administrator (MOB07002)

Cause

This error arises due to partially downloaded documents. When the document is not downloaded completely, it's

XML is not well-formed and so the client side software is unable to parse it.

Action

Delete the document from user's device memory (downloaded list of BI documents) and download it again.

11.2.3 Server error prevented the document from refreshing; try again (MOB07003)

Cause

The document does not refresh due to a server error. The Universe may not have been found at the back-end.

Action

Check if the Web Intelligence server is running fine.

Administrator's Guide

Troubleshooting Errors

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

127

11.3 Configuring Trace Logs for Monitoring on the BI Platform

Tracing allows you (system administrator) and support personnel to report on the performance of BI platform components (servers and Web applications) and the activities that occur within the monitored components.

System-level messages generated by BI platform servers are traced and written to log files. You can use these log files to monitor performance or for debugging purposes.

Traces are recordings of events that occur during the operation of a monitored component. The traced events range from severe exception errors on one end to simple status messages at another.

For complete information on managing, configuring and using logs, refer to the Business Intelligence Platform

Administrator Guide available at http://help.sap.com/businessobject/product_guides/boexir4/en/ xi4_bip_admin_en.pdf

128

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

Administrator's Guide

Troubleshooting Errors

Important Disclaimers and Legal Information

Coding Samples

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

Accessibility

The 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 in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of wilful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.

Gender-Neutral Language

As 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 Hyperlinks

The 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. All links are categorized for transparency

(see: http://help.sap.com/disclaimer ).

Administrator's Guide

Important Disclaimers and Legal Information

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

129

www.sap.com/contactsap

© 2015 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.