SAP BusinessObjects Mobile (for Android) Document Version: Administrator and Report Designer's Guide

(1)

SAP BusinessObjects Mobile (for Android)

Document Version: 5.0.0 - 2013-06-20

(2)

1 Preface

This document describes how to install and configure the SAP BusinessObjects Mobile solution to access and analyze Business Intelligence documents on Android devices.

1.1 Audience

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 solution including the application on the user's device, the SAP BusinessObjects Mobile server and the SAP BI platform server. This group of people is also responsible for application customizations and troubleshooting.

● Business Intelligence administrators and document designers who:

○ Design Web Intelligence for viewing on the device.

○ Manage Web Intelligence documents.

1.2 Product Overview

SAP BusinessObjects Mobile application (for Android) enables Android smartphone and tablet users to access, view, and analyze their enterprise specific Business Intelligence information on the move.

Using this application, mobile users can:

● Create connections to the SAP BusinessObjects BI platform server and access Web Intelligence documents and Dashboards.

● Search, view and download documents on their device (downloaded documents are displayed in the application's "Home" screen).

● Use the various options in the application to interact and analyze the report.

1.3

2 What's new in the Application?

The SAP BusinessObjects Mobile (for Android) application provides the following enhancements in the current release:

● Languages supported:

This application is now also supported in Czech. Other supported languages are:

○ Simplified Chinese

○ Japanese ○ Russian ○ Polish ○ French ○ German ○ Portuguese ○ Spanish

● Support for new content type: Starting with this release, the application also provides support for SAP BusinessObjects Dashboards content type. SAP BusinessObjects Dashboards (created with a Dashboard Designer) are corporate dashboards with analytics based on Universe queries, BW (BEx queries) and HANA (Universe). They are rich in look and feel, and provide support for various mobile features.

● Web Intelligence enhancements:

○ Support for new chart type:

○ Combination chart: The combination chart is a visualization that combines the features of the Bar chart, Line chart and Surface chart. The combination chart displays the data using a number of bars and/or lines, each of which represents a particular measures.

○ Waterfall chart: Waterfall charts (also known as Bridge charts) display vertical bars. Each one of these bars starts at the level where the preceding bar ends, making the bars look as if they were floating.

○ Hierarchical display of charts, and hierarchical list of values defined in Web Intelligence reports and the Universe.

○ Support for BW data sources:

○ Via BICS and Unx (for multisource) Connectivity

○ Support for BW Variables

○ Support for Webi Prompts on BW

○ Support for Other Multidimensional Data Sources:

○ Via Unx Connectivity

○ Support for MSAS and Essbase

○ Support for Hierarchies

● Layout enhancements:

The application now supports displaying the Web intelligence reports designed in page layout model on android devices with screen size 7 inch and higher.

● Support for connection authentication:

This release provides support for 2 factor authentication and complex deployment scenarios with authentication. This guarantees the user secure and trusted access to the enterprise information.

(8)

3 Administering SAP BusinessObjects

Mobile for Android

3.1 Solution Overview

The SAP BusinessObjects Mobile solution allows end users to access SAP BusinessObjects Web intelligence documents through their Android smartphones and tablets. It is suited for 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 (along with a relay server)

(9)

3.1.1 SAP BusinessObjects Mobile Client

Using the SAP BusinessObjects Mobile (for Android) application, business professionals can access Business Intelligence content from their mobile devices. The SAP BusinessObjects Mobile solution runs multiple client applications, each supported on different platforms.

The SAP BusinessObjects Mobile (for android) application enables Android smartphone and tablet users to access to access following types of BI content:

● SAP BusinessObjects Web Intelligence documents

● SAP BusinessObjects Dashboards

The application provides users with document rendering, refreshing, document sharing, navigation and

collaboration options. The application also facilitates analysis by providing options such as drilling data, filtering data and viewing report data in sections for better analysis of Web Intelligence documents.

It supports device appropriate features such as native rendering, single-tap access, and user interactivity. Related Links

Installing SAP BusinessObjects Mobile Client

3.1.2 SAP BusinessObjects Mobile Server

The SAP BusinessObjects Mobile server is a Web application that:

● Receives requests sent by the SAP BusinessObjects Mobile client and passes them to the SAP BusinessObjects Enterprise (BI platform) server.

● Receives responses (such as, Web intelligence or CR documents, report data or parameter values) from the SAP BusinessObjects BI platform and sends them to the SAP BusinessObjects Mobile client.

● Optimizes responses from the Business Intelligence (BI) platform, thus making them suitable for the Mobile client to consume.

● Provides flexibility and customizing options for client applications such as the types of BI documents to be displayed on the device.

● Provides additional security options such as restricting users from downloading confidential documents by assigning the documents to a confidential category.

3.1.3 SAP BusinessObjects Business Intelligence (BI)

Platform Server

The SAP BusinessObjects BI platform server renders corporate data captured from corporate databases and data warehouses through business intelligence documents. It handles the whole document lifecycle including creation, catalog, refresh, content delivery, and report interactivity.

(10)

The SAP BusinessObjects BI platform server processes requests sent by the SAP BusinessObjects Mobile client through the SAP BusinessObjects Mobile server, and returns responses (for example, Web intelligence

documents).

Supported Versions of Business Intelligence Platform and the Mobile Server

The SAP BusinessObjects Mobile for Android application is supported on the following versions of the Business Intelligence (BI) platform and BI Mobile server

● SAP BusinessObjects BI platform Server 4.0, Fix Pack 2.14 and above

● SAP BusinessObjects BI platform Server 4.0. Fix Pack 3.2 and above

● SAP BusinessObjects Mobile Server 4.0 SP05

● SAP BusinessObjects Mobile Server 4.0 SP06

● SAP BusinessObjects Mobile Server 4.1

● SAP BusinessObjects Edge BI 4.1

Note

The SAP BusinessObjects Mobile server should be the same release version as the BI platform server. Related Links

Installing SAP BusinessObjects Enterprise Server

3.2 Installing the Required Components

3.2.1 Installing the Application (Mobile Client)

You can download the SAP BusinessObjects Mobile application to your device from Google Play Store. Once downloaded, the SAP BI Mobile icon appears in the application menu on your mobile device.

3.2.2 Installing the SAP BusinessObjects Mobile Server

Ensure sure that your Web Application server has the same version as the SAP BusinessObjects BI platform server.

To install Mobile server on the Web application server for Android devices, perform the following steps: 1. Stop the Web Application server.

(11)

3. Restart the Web Application server.

The SAP BusinessObjects Mobile server can be installed on the same Web application server where other SAP BusinessObjects BI platform Web applications are deployed.

If you have any of the following server versions installed in your enterprise environment, see the corresponding guide for installing the Mobile server:

● For Mobile Server 4.0 SP05, see: http://service.sap.com/~sapidb/011000358700001280592012E/ xi4sp5_mob_inst_deploy_en.pdf

● For Mobile Server 4.1, see http://service.sap.com/~sapidb/011000358700000508552013E/ sbo41_mob_inst_deploy_en.pdf

3.2.3 Installing the SAP BusinessObjects BI Platform Server

For information about installing the SAP BusinessObjects BI platform server, see SAP BusinessObjects Enterprise Administrator Guide (Release 3.1 or 4.0) on SAP Help Portal at http://help.sap.com.

Note

The SAP Business Objects Business Intelligence (BI) platform was previously known as SAP BusinessObjects Enterprise (BOE).

3.2.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 premises.

Ensure that your Web application server has the same version as the SAP BusinessObjects BI platform server. To install a configuration server, perform the following steps:

1. Stop the Web application server.

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

[<Web_app_server> Home directory]\webapps folder on your server:

[Installation Directory]\SAP BusinessObjects\Mobile 14\server

3. Restart the Web application server.

If you have any of the following server versions installed in your enterprise environment, see the corresponding guides for configuring your Mobile server:

(12)

● For Edge BI 4.1, see http://help.sap.com/boall_en/

3.3 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 to control various aspects of the BI documents accessed via the SAP BI applications on mobile devices.

These aspects include:

● 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 to the user's device memory.

● Customizing the display layout of BI documents on the mobile device screen. (The display layout of BI documents on the device screen can be based on the Card Layout or Page Layout model).

● Organizing BI content based on your specific 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 that you can assign a BI document to 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. (In the default setting, this category is called "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.

(In the default setting, this category is called "MobileDesigned").

3. Category to secure the document. Documents assigned to this category cannot be downloaded and saved to the user's device memory. They can be only be accessed while being connected to the server.

(In the default setting, this category is called "Confidential").

The snippet 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 ...

(13)

ipad.corporateCategory=Mobile ...

#iphone

...

iphone.corporateCategory=Mobile ...

#blackberry mobile

...

#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. Only when different parameter values are entered in a device based request source, the new values OVERRIDES the default request source.

For your day-to-day work, you do not need to change the default settings in the properties file. However, if you have specific requirements for a particular device or platform, you can enter specific category names in the corresponding request source. These values will override those in the <default> request source.

In the mobi.properties file: 1. The lines:

<RequestSrc>.corporateCategory=Mobile <RequestSrc>.personalCategory=Mobile

imply that BI documents assigned to the {Mobile} category can be accessed via the SAP BI (SAP BusinessObjects Mobile) application on a mobile device.

2. The line:

<RequestSrc>.category.mobileDesigned=MobileDesigned

implies that BI documents assigned to the MobileDesigned category (on the BI platform) would appear on the mobile device screen in accordance with the report's page layout defined on the BI platform.

3. The line:

<RequestSrc>.category.secure=Confidential

implies that BI documents assigned to the Confidential category on the BI platform are secured. Documents assigned to this category cannot be saved to the user's device memory, and therefore cannot be accessed in disconnected (offline) mode.

(14)

○ On the BI platform, you can change (customize) the category names that you see to the right of the assignment operator (such as "Mobile", "MobileDesigned" and "Confidential") in the

mobi.properties file . However, if you change a category name on the BI platform, you should update the corresponding line in the mobi.properties file accordingly.

○ The categories of the type:mobileDesigned and secure, cannot be Personal categories. They are of

Corporate type.

Example 1: Controlling visibility of BI documents

Of five BI documents designed for the SAP BusinessObjects Mobile (for Android) application, suppose you want two to appear on all Android devices; two documents to appear on the Android tablets only and one document to appear on an Android smartphone only.

To do this, you need to perform the following configuration:

1. In the BI LaunchPad, assign the two 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 the BI LauchPad, assign the 2 documents you only want to appear on the Android tablet to a custom Corporate category name (such as tablet_specific). Then, edit the following line in mobi.properties

(replace the old category name with the new one):

androidtablet.corporateCategory=tablet_specific

Since the corporate category name in the android tablet request source is different to that in the default request source (Mobile), the Android tablet request source overrides the default request source. This ensures that the mobile server recognizes these BI documents for the Android tablet, and that the BI documents (assigned to the tablet_specific category in BI LaunchPad) appear only in the SAP BI app installed on an Android tablet.

3. In the BI LaunchPad, assign the document that only you want to appear on iPhone, to a custom Corporate category name (such as smartPhone_specific). Then, edit the following line in mobi.properties (replace old category name with the new one):

androidphone.corporateCategory=smartPhone_specific

The android phone request source now overrides the default request source. This ensures that the mobile server recognizes these documents for the Android phone request source and they appear only on the SAP BI app installed on an Android phone.

Example 2: Controlling the display layout of BI documents on the mobile device

screen

(15)

In the BI LaunchPad, assign the documents to a custom category name such as "iPad_designed". Then, perform this update in the mobi.properties file: ipad.corporateCategory=iPad_designed. This ensures that the documents appear only on iPads and not on any other devices.

Assign the documents to the "MobileDesigned" category on BI platform.This ensures that reports are displayed on the iPad screen in accordance with the page layout defined on the BI platform.

2. For documents meant for the Android phone, perform the following steps:

In the BI LaunchPad, assign the documents to a custom category name such as "Android_designed". Then, perform this update in the mobi.properties file:

androidphone.corporateCategory=Android_designed. The Android phone request source now overrides the default request source. This means that the documents appear only on Android phones and not on any other devices.

Assign the documents to the "MobileDesigned" category on BI platform.This ensures that the reports are displayed on the Android device screen in accordance to the "page layout" defined on the BI platform. (If you give this category a custom name on the BI platform (such as "Mydesign"), you should update

mobi.properties file: androidphone.category.mobileDesigned=Mydesign accordingly)

Example 3: Securing BI documents containing confidential data

You have certain BI documents that contain sensitive business information. You do not want users to save these documents to their devices or to have offline access to them. Since this is irrespective of the device the user is using to access the document, you just need to assign the confidential BI documents to the "Confidential" category on the BI platform (InfoView or other report designing tools).

This is because, the "Confidential" category is defined as a secured category by default in the mobi.properties

file. If you choose a different name for this category on the BI platform (such as "Restricted"), you need to perform this update in properties file: default.category.secure=Restricted.

If you have any of the following server versions installed in your enterprise environment, see the corresponding guides for configuring categories on the Mobile server:

3.4 Configuring Connections for Importing to the Mobile

Application

Pre-requisite

(16)

Configuring connections for importing

To configure connections (for importing to the application), you need to update the following file on the Configuration server:

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

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

● DisplayName (mandatory)

● BOBJ_MOBILE_URL

● BOBJ_MOBILE_CMS

● BOBJ_MOBILE_USER_NAME

● BOBJ_MOBILE_USER_PASSWORD

● BOBJ_MOBILE_AUTH_METHOD

● BOBJ_MOBILE_CONNECTION_TYPE

● BOBJ_MOBILE_SAVE_PWD

where,

<AuthenticationType> can have one of the following values:

● secEnterprise for Enterprise

● secLDAP for LDAP

● secWinAD for Windows AD

● secSAPR/3 for SAP

<Connection Types> can be set to one of the following values:

● Set 1 for Enterprise

● Set 2 for XXX

● Set 3 for YYY

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_USER_NAME: john

connection1.BOBJ_MOBILE_USER_PASSWORD:******** connection1.BOBJ_MOBILE_AUTH_METHOD: secEnterprise connection1.BOBJ_MOBILE_CONNECTION_TYPE:1

connection1.BOBJ_MOBILE_SAVE_PWD: True

Note

Several users of the SAP BusinessObjects BI platform might have common user names. When configuring

(17)

3.5 Using SAP BI URL for Managing Connections

3.5.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 Android) 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 Android device (smartphone or tablet) 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 if the user enters the input parameter values on the application's "Connection" details screen, 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

● secSAPR/3 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 parameter values shown above would be: sapbi://addconnection? name=Manufacturing&server_url=https://yoda.corp.com:

8080&cms=Luke77&authType=secEnterprise&default=no&save_password=yes Once the SAP BI URL has been created, you can share it with users by e-mail.

Guidelines for URL Parameters

● Connection Type: The connection type for a corporate connection is a constant value: “BOEConnection”

● Connection Name: You can use alphanumeric characters, hyphens, underscores, periods, and round brackets; the maximum number of characters allowed is 20.

● Server URL:

○ You can use alphanumeric characters, 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>.

(18)

● CMS Server: For the CMS name,

○ You can use alphanumeric characters, hyphens, underscores, periods, and colons; the maximum number of characters allowed is 261.

○ The maximum number of characters allowed for the user name is 100.

○ For the username and password, characters such as ampersand ('&'), question mark ('?'), and equals ('=') are not supported; providing a password is optional.

3.5.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 that you prevent users from creating connections manually and thereby, from unintentionally creating invalid connections.

An SUP URL should have the following 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

3.5.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 Android) application installed on their smartphone or tablet 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&authType=sec Enterprise&default=no&user=UserNam

Deleting a Sybase connection

(19)

Note

Once you (or users) have deleted an SUP connection, ensure that you (or they) Deregister from SUP using the application's "Settings" screen. Otherwise, problems can occur when creating connections in future.

3.5.4 Creating a URL to Modify a Connection

Pre-requisite

2. The SAP Mobile (for Android) application is installed on their smartphone or tablet 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&ServerUrl_Pr ev=10.53.10.10:8080&ServerUrl_New=10.10.10.10:1010&CMS_Prev=10.53.10.10&CMS_New=10.10.10.10&AuthT ype_Prev=secEnterprise&AuthType_New=secLDAP&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.

Modifying SUP Connections

To modify an SUP connection, you need to include 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 that you have included in the URL and the connection is modified.

Note

As 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. Including the new values in the URL simply overwrites the old values with the new values.

(20)

3.6 Configuring the Mobile Server for the Sybase Unwired

Platform (SUP)

To enable users of the Mobile client applications to connect to the SAP BusinessObjects Mobile server using the Sybase Unwired Platform (SUP), you need to perform certain configuration steps. These includes:

1. Install SUP on a machine on your premises.

For detailed information about installing the Sybase Unwired Platform, go to

http://infocenter.sybase.com/help/index.jsp and navigate to Sybase Unwired Platform 2.1 ESD #1 Installation Guide for Runtime 2.1

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

For detailed information about configuring the SUP for use with the SAP BusinessObjects Mobile server, see

Configuring SUP for use with the Mobile Server.

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

For detailed information about configuring the SAP BusinessObjects Mobile server to connect to the SUP server, see Configuring Mobile Server to connect to the SUP server.

3.6.1 Configuring Mobile Server to Connect to the SUP

Server

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

1. Deploy the MobileBIService.war file (version 4.0.3/ 4.0.2.13 or later) on your Web application server. 2. Locate the WEB_INF\sup.properties file.

Note

The file location of sup.properties is the same as for mobi.properties. 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. You can change the lines from comments to code and update the values of the parameters.

○ You can connect to multiple CMS by providing the CMS address along with the security configuration in the sup.properties.

For Example:

MobiSec_another.cms=11.42.44.55 MobiSec_another.auth=secEnterprise

(21)

○ Note that MobiSec is the name that you specified for the security configuration setting when you added it to the SUP 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 BI Mobile server are correct, access this URL in your browser:

http://<mobi-server>/MobileBIService/SUP/VerifyUser/MobiSec

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

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

3.6.2 Configuring SUP 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 SUP server machine, launch the Unwired Server Cluster Management View (Sybase Control Center).

2. In the Unwired Platform Cluster panel that appears on the left, select Security. 3. Choose New in the General tab in the panel on the right.

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 in the Security folder in the panel on the left.

Note

Make a note of the Security Configuration name. You need this name to configure the SUP connection on the client application.

(22)

5. Select the new security configuration in the Unwired Platform Cluster panel. 6. Select the Authentication tab in the panel on the right 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 drop-down, enter a URL with the following 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.

(23)

11. Go to the General tab and choose Validate. This allows you to validate the changes to the security configuration before applying them to the SUP server. Then choose Apply.

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

Note

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

● Creating an Application

1. On the SUP server machine, launch the Unwired Server Cluster Management View. 2. In the Unwired Platform Cluster panel on the left, select Applications.

3. Choose New in the Applications tab in the panel on the right. 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.

(24)

You can either create a (new) application connection template or 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 Unwired Platform Cluster panel on the left, choose Applications. 2. Choose Application Connection Template.

3. Choose New.

The Template popup appears.

4. In the Template name field, enter the name for the template. 5. In the Base template field, choose Default.

(25)

a. In the Application Identifier field, choose MobiApp as the value. b. In the Domain field, choose Default as the value.

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

(26)

8. Choose Ok.

3.7 Generating SAP BI URLs for Opening BI Documents

3.7.1 Overview

An SAP BI document viewed in the Android client 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 (single report part per page) view

As an administrator, you can share a BI document (so that it opens directly in a particular view on the recipient's device) by generating it and sending an SAP BI URL.

You can generate an SAP BI URL for a document in either of the following ways:

(27)

When you choose (email) for a document while working in the application, the application generates a SAP BI URL with various parameters based on the view/type of report. You can send this SAP BI URL to users via email.

b. Manually creating a 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.

3.7.1.1 Manually Creating SAP BI URLs for Opening specific

BI Documents or Reports

Pre-requisite

2. The SAP Mobile for Android application installed on their Android device.

1. Creating a SAP BI URL for opening a simple BI document (default view: first

report, first page) in the application

To provide users with access to a simple BI document on their mobile devices, create an SAP BI URL with the following format:

sapbi://OpenDoc/?

ConnectionType=BOEConnection&connection_name=123&server_url=10.10.10.10:8080&cms=10.10 .

10.10&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=0&repor tIndex=&isInstance=N&prompt=

● <ConnectionType>, <connection_name>, <server_url> and <cms> are the regular SAP BI URL parameters that help the application (on the user's device) to identify the particular BI platform server containing the BI document to be opened.

● <Type> is the BI document type. There are 2 valid values for this: 'webi', '<>'

● <iDocID> is the CUID of the document. You should retrieve the CUID by accessing the document Properties

on the BI platform (report designing client tool).

● For other parameters (<reportPartKey>, <reportPageNumber>, <reportIndex>, <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.

(28)

2. Creating a SAP BI URL for opening a specific report within a BI document

To give users access to a specific report within a BI document on their device, create an SAP BI URL with the following format:

sapbi://OpenDoc/?

ConnectionType=BOEConnection&connection_name=243&server_url=10.53.129.243:8080&cms=10. 53.129.243&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=&r eportIndex=5&isInstance=N&prompt=

● <ConnectionType>, <connection_name>, <server_url> and <cms> are the regular SAP BI URL

parameters that help the application (on user's device) identify the particular BI platform server having the BI document intended to be opened.

● <Type> is the BI document type that has 2 valid values: 'webi', '<>'

● <iDocID> is the CUID of the document. You should 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 (–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 do not need to assign any specific values. However, they should be retained in the URL syntax with null values assigned to them as shown in the URL format above.

Note

The SAP BI URL generated dynamically by the application (on using the Email option) may have values for all parameters including the <reportPageNumber> and <reportPartKey>.

While creating the SAP BI URL manually, we do not recommend you to pass values for these parameters, as they are not guaranteed to work in the application.

3.7.1.2 Manually Creating SAP BI URLs For Opening Latest

Instance of BI Documents

Pre-requisite

2. The SAP Mobile for Android application installed on the Android device.

To provide application users with access to the latest instance of a BI document (that is scheduled on the BI platform), create an SAP BI URL with the following format:

(29)

.

10.10&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=0&repor tIndex=&isInstance=Y&prompt=

● <ConnectionType>, <connection_name>, <server_url> and <cms> are the regular SAP BI URL parameters that help the application (on the user's device) to identify the particular BI platform server containing the BI document to be opened.

● <Type> is the BI document type. There are 2 valid values fro this: 'webi', '<>'

● <iDocID> is the CUID of the document. You should retrieve the CUID by accessing the document Properties

on the BI platform (report designing client tool).

● <isInstance> is a flag parameter with two valid values {'Y', 'N'}. If you set this parameter value to 'Y', the latest instance of scheduled BI document opens when the recipient taps the SAP BI URL on his/her device.

● For other parameters (<reportPartKey>, <reportPageNumber>, <reportIndex> and <prompt> ), you don't need to assign any specific values. However, they should be retained in the URL syntax with null values assigned to them as shown in the URL format above.

3.7.1.3 Manually Creating SAP BI URLs for Opening BI

Documents with Prompts

Pre-requisite

2. The SAP BusinessObjects Mobile (for Android) application installed on their Android device.

1. Manually creating an SAP BI URL for opening documents containing prompts

without refresh

To provide application users with access to a BI document containing prompts (without refresh) defined on the BI platform, create an SAP BI URL with the following format:

sapbi://OpenDoc/?

ConnectionType=BOEConnection&connection_name=123&server_url=10.10.10.10:8080&cms=10.10 .

10.10&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=0&repor tIndex=&isInstance=N&prompt=

● <ConnectionType>, <connection_name>, <server_url> and <cms> are the regular SAP BI URL

parameters that help the application (on the user's device) to identify the particular BI platform server having the BI document to be opened.

● <Type> is the BI document type. There are two valid values for this: 'webi', '<>'

● <iDocID> is the CUID of the document. You should retrieve the CUID by accessing document Properties on the BI platform (report designing client tool).

(30)

● <prompt> defines the type of prompt (single or multiple).

● For other parameters (<reportPartKey>, <reportPageNumber>, <reportIndex> and <isInstance>), you don't need to assign any specific values. However, they should be retained in the URL syntax with null values assigned to them as shown in the URL format above.

2. Manually creating an SAP BI URL for opening documents having prompts (on

refresh) with list of values (LOV)

To provide application users with access to a BI document containing prompts (on refresh) with LOV defined on the BI platform, perform 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

Multiple prompts (lsM) are separated by underscores ('_').

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 this:

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. Encode the prompt section again and join it with the remaining URL After performing this step, the URL for the above example looks like this:

sapbi://OpenDoc/?

ConnectionType=BOEConnection&connection_name=123&server_url=10.10.10.10:8080&cms=10 .

10.10.10&Type=webi&iDocID=AXtcyDP4u09Jn1_P9BSR9H0&reportPartKey=&reportPageNumber=0 &reportIndex=&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 do not 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 URL format above.

(31)

3.8 Defining the Log Level in the Application

You define the log level to record information returned by the server while working with the application. This log information helps you to identify issues if the application fails or encounters a problem.

To set the log level, perform the following steps: 1. Log on to the mobile application on mobile device. 2. Under Settings, choose Logs.

3. You find the following parameters:

○ Enable Logs: This allows you to generate application log files. You should only toggle this button to Yes if requested to by your system administrator's, as this can effect the performance of your application.

○ Send log file: This allows you to send the log file saved locally to your device, using the e-mail option.

○ Clear log: This allows you to clear the log files saved locally to the device. You can view the log file by performing the following steps:

1. On your device home screen, select the File Manager application.

Note

On some devices, the File Manager is located under Applications. 2. Open the mobilogger.log file.

A maximum of two mobilogger.log files can be created. The size of each log file is 512 Kilo Bytes. Once the second file is full, the first one is overwritten.

3.9 Configuring Trace-Logs for Monitoring on the BI Platform

Tracing allows you ( as the system administrator) and support personnel to report on the performance of BI platform components (servers and web applications) and activities in the monitored components.

System-level messages generated by BI platform servers are traced and written to log files. You can use these 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 to simple status messages.

For more thorough information about managing, configuring and using logs, see the Business Intelligence Platform Administrator Guide at http://help.sap.com/businessobject/product_guides/boexir4/en/ xi4_bip_admin_en.pdf

(32)

3.10 Understanding the Security Implementation in the

Application

3.10.1 Features of the 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 Mobile for Android application password:

● The application password is not enabled in the application, until users add a connection to the BI platform server that is application password enabled by the administrator. When users attempt to log on to this connection, the application forces them to enter an application password (as user specific or personal information is not displayed on the device until a connection has been created).

If users have not created a single connection, but want to enable the application password, they can do this by using the application's Settings screen.

Note

The behavior described above 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 Play store, server connections will already exist in the application, and so the application password will remain enabled.

● The following lines of code in the clientsettings.properties file on the Mobile server help you to 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 application's Connection settings screen. Otherwise, it does not appear for the user.

offlinestorage.appPwd=true indicates that application password is stored in the local memory of the device (in the same way as BI documents) once it has been set and is removed only when the user chooses to reset the application data or has permission to disable the Use Application password option from the client application.

3.10.2 Support for 2 Factor Authentication

Ensure that you have implemented one of the following scenarios on your Web application server (Where you have installed the SAP BusinessObjects Mobile server):

(33)

When users add connections to the SAP Mobile server (with one of the above mentioned security deployments) using the SAP BusinessObjects Mobile (for Android) application on their devices, they see a security interface requiring authentication. The following sections explain the three scenarios listed above.

a. Basic Authentication

1. On the application's "Settings" screen, users add a connection to the CMS with basic authentication deployed on it. (As an administrator, you provide the application users with specific server details.)

2. When the new connection in the "Connections" screen is chosen, the application displays the "Authentication" dialog box, prompting the user to enter his/her credentials.

3. The user is logged on to the connection and can browse the BI documents available on the server.

b. Form-Based Authentication

1. On the application's "Settings" screen, users add a connection to the CMS with form-based authentication deployed on it. (As an administrator, you provide the application users with the specific server details.) 2. When new connection is chosen in the "Connections" screen, the application displays a form, prompting 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 on the device.

3. The user is logged in to the connection, and can browse the BI documents available on the server.

c. Certificate-Based Authentication

Pre-requisite: Ensure that the *.p12 extension certificate is installed on the user's device.

1. On the application's "Settings" screen, users add a connection to the CMS having certificate- based

authentication deployed on it. (As an administrator, you provide the application users with the specific server details.)

2. When you choose the new connection in the "Connections" screen, the application displays a dialog box stating that the connection requires a certificate.

(34)

○ If no certificates are installed: select Install and choose a certificate. The selected certificate is installed:

(35)

○ If you want to install a new certificate and use it for authentication: Select Install and choose a certificate. The selected certificate is installed. The user selects this new installed certificate from the list:

4. The user is logged on to the connection, and can browse the BI documents on the server.

Note

1. Installed certificates can be removed from the application by choosing Clear Data > Remove Certificates on the device's"Settings" screen.

2. The application also supports basic authentication and certificate based authentication for hyperlink objects.

(36)

3.10.3 Understanding the User Data Protection and Privacy

Parameters

User data is data or information that is specific to an individual user. This includes downloaded reports and the user's application logon credentials. To guarantee the security of user data, SAP BusinessObjects Mobile implements certain security measures.

These include the following:

● Users have the option of saving their password for a connection in the application. In the default

configuration, this option is disabled (savePassword=false). However, if a user enables the Save Password

option while configuring the connection on his or her device, the password is encrypted using the FIPS compliant AES algorithm.

● If users do not choose to save their password, they are prompted for it whenever they access the application, regardless of whether they are in online or offline mode.

● In the default configuration for 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.

Depending on the prevailing requirements, the 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 device's local memory.

● For Web Intelligence documents containing private or confidential data, you can secure the documents by assigning them to a "Confidential" category in the document designing tool. A secure document can be accessed by users only while 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 directory]\webapps\MobileBIService\WEB-INF \ClientSettings.properties

Depending on your specific security requirements, you can change the values of these parameters in the

ClientSettings.properties file.

Note

For more information about the security measures implemented in the application and in the mobile system landscape, see the SAP BusinessObjects Mobile System Security Guide available at at the SAP Help portal:

(37)

4 Designing Web Intelligence Reports

Optimized for Android Devices

4.1 Predicting the Layout of Report Parts On the Device

The layout prediction model implemented in the SAP BusinessObjects Mobile software ensures that the report parts of a Web Intelligence report are displayed in a non-disruptive, optimized and predictable layout on the device screen.

As a report designer, you should note the information provided in this topic when designing Web Intelligence documents to be viewed on the mobile device.

The table below provides information about the supported layout prediction models based on the device platform: When designing the Web Intelligence documents, you should assign them to the appropriate category (in the Web Intelligence report designing tool on the BI platform).

● To view the Web Intelligence documents in page layout on an Android tablet, assign the documents to the

Mobileand MobileDesigned categories.

● To view the Web Intelligence in the Single report part per screen model on the Android smartphones and seven inch tablets, assign the Web Intelligence documents to the Mobile category (the default setting). You can customize the category names above which can be found in the Categories view of your Web Intelligence documents (in the client tool). If you change a category name or add sub-categories to a category, you need to update the following lines in the Mobile server configuration file (mobi.properties) with the new values:

#default default.corporateCategory=Mobile default.personalCategory=Mobile default.category.mobileDesigned=MobileDesigned ... #Androidphone

androidphone.corporateCategory=Mobile,Category 1,Category 2... androidphone.personalCategory=Mobile,Category 1,Category 2... androidphone.category.mobileDesigned=MobileDesigned

androidphone.category.secure=Confidential androidphone.category.doctypes=Webi ...

#Androidtablet

androidtablet.corporateCategory=Mobile,Category 1,Category 2... androidtablet.personalCategory=Mobile,Category 1,Category 2... androidtablet.category.mobileDesigned=MobileDesigned

androidtablet.category.secure=Confidential androidtablet.category.doctypes=Webi ...

4.1.1 Page Layout Model

The page layout model supports displaying multiple report parts on the device screen. The characteristics of the page layout prediction model are as follows:

(38)

1. All report parts (charts, graphs, tables, free cells) from one page of a Web Intelligence report (in portrait mode) are displayed on a single device screen, without any significant disruption to their layout. The software scales the size of the report part for an optimal fit on the device screen.

2. Report parts in subsequent pages of the Web Intelligence report are displayed in further screens on the device (indicated by pagination dots). If a report part spans multiple pages in the Web Intelligence document, this part belongs to the page from where it originates.

Suppose for example that, there is a long vertical table in the first page of a document which spans to five pages in Web Intelligence. In the application (SAP BI), the table is displayed only on the first page and can be vertically scrolled to see further data.

3. In Web Intelligence, report pagination happens based on a page size of 630 pixels (width) and 860 pixels (height). This is achieved using the standard margin size of 0.79 inches in page mode in the Web Intelligence report.

4. If the height or width of a table on a single page of the Web intelligence report does not fit the device screen, the table appears on the screen with a vertical or horizontal scroll. The records of the table are not truncated.

4.1.2 The "Single Report Part per Screen" Model

The Single report part per screen layout model supports displaying a single report part per page on the Android smartphones. The model has following features:

1. A single report part (such as a chart, graph, table or blank cell) of a Web Intelligence report (in portrait mode) is displayed on the screen, without any significant disruption to it's layout. The software scales the size of the report part for an optimal fit on the smartphone screen.

2. Report parts in subsequent pages of the Web Intelligence report are displayed in further pages on the smartphone (indicated by page number at the bottom of the screen). If a report part spans multiple pages in the Web Intelligence document, the part belongs to the page that it originates from.

As an example let us assume that there is a vertical table in the first report of a document which spans to five pages in Web Intelligence. In the client application, the table is displayed only on the first page and can be scrolled vertically to see further data.

3. In Web Intelligence, report pagination is performed based on a page size of 630 pixels (width) and 860 pixels (height). This is achieved by using the standard margin size of 0.79 inches in the page mode of the Web Intelligence report.

4. If the height or width of a table on a single page of the Web intelligence report does not fit the screen, the table appears on the screen with a vertical or horizontal scroll. The records of the table are not truncated.

4.2 Configuring the Blank Cells of a Report for Viewing on

the Device

If you have used any of the prediction layout model types to design a Web Intelligence (or Interactive Analysis) report, the blank cells of the report need to be formatted in a specific way so that they can be viewed on the

SAP BusinessObjects Mobile (for Android) Document Version: Administrator and Report Designer's Guide