Configuring and Deploying
BusinessObjects Mobile Interactive
Viewing
Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Copyright
©
2007 Business Objects. All rights reserved. Business Objects owns the following
U.S. patents, which may cover products that are offered and licensed by Business
Objects: 5,555,403; 6,247,008; 6,289,352; 6,490,593; 6,578,027; 6,768,986;
6,772,409; 6,831,668; 6,882,998 and 7,139,766. Business Objects and the Business
Objects logo, BusinessObjects, Crystal Reports, Crystal Xcelsius, Crystal Decisions,
Intelligent Question, Desktop Intelligence, Crystal Enterprise, Crystal Analysis,
Web Intelligence, RapidMarts, and BusinessQuery are trademarks or registered
trademarks of Business Objects in the United States and/or other countries. All
other names mentioned herein may be trademarks of their respective owners.
Third-party
Contributors
Business Objects products in this release may contain redistributions of software
licensed from third-party contributors. Some of these individual components may
also be available under alternative licenses. A partial listing of third-party
contributors that have requested or permitted acknowledgments, as well as required
notices, can be found at: http://www.businessobjects.com/thirdparty
Contents
About BusinessObjects Mobile Interactive Viewing 5Chapter 1
What is BusinessObjects Mobile Interactive Viewing?................................6
About this guide.........................................................................................11
BusinessObjects Mobile Interactive Viewing Features..............................12
About report creation.................................................................................12
How BusinessObjects Mobile Interactive Viewing works..........................13
Device Prerequisites and Device Type Support........................................15
Functional limitations.................................................................................16
Server-side prerequisites and configuration 17Chapter 2
Server requirements..................................................................................18
Network Access.........................................................................................18
Package contents......................................................................................25
Server-side installation and configuration..................................................28
Pre-configuring the client application for OTA delivery to J2ME devices...34
Configuring the IT Policy on the BlackBerry Enterprise Server.................35
How can BusinessObjects Mobile Interactive Viewing help with Business
Intelligence solutions?............................................................................7
The BusinessObjects Mobile Interactive Viewing package..................11
Using a secured connection.................................................................19
The BusinessObjects Mobile Interactive Viewing certificate................20
Configuring SSL on the device.............................................................23
Instructions for configuring SSL on users' devices.........................24
Apache Tomcat MIME types.................................................................30
IIS MIME types.....................................................................................31
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 3
Contents
Chapter 3
BusinessObjects Mobile Interactive Viewing Report Authoring
Guidelines 39
How documents are displayed on mobile devices.....................................40
About actions.............................................................................................41
Authoring actions..................................................................................42
Syntax for actions.................................................................................44
Creating document links for improved navigation......................................45
Authoring Recommendations for Mobile Content......................................47
Using alert and status icons in Web Intelligence documents...............52
Creating performance management gauges for viewing on devices....56
4 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
1
About BusinessObjects Mobile Interactive Viewing
1
What is BusinessObjects Mobile Interactive Viewing?
What is BusinessObjects Mobile
Interactive Viewing?
BusinessObjects Mobile Interactive Viewing is a client-side application
enabling mobile devices to access business intelligence content via the
Services Oriented Architecture of a Business Objects Enterprise XIR2 SP2
server. BusinessObjects Mobile Interactive Viewing is a small (approximately
400 KB) J2ME application designed specifically to meet the constrained
screen size and simple interactivity requirements of mobile devices. BI content
can be accessed virtually anytime with one click and users can easily and
intuitively interact with BI content from the mobile device.
BusinessObjects Mobile Interactive Viewing allows mobile device users to
access and refresh documents, view certain static analytics, link between
documents, drill into charts, and take actions based on data in documents
(including making phone calls and sending sms messages). These features
are exposed to device users through Web Intelligence and BusinessObjects
documents and performance management analytics published on the
BusinessObjects Enterprise XIR2 SP2 server.
6 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
What is BusinessObjects Mobile Interactive Viewing?
How can BusinessObjects Mobile Interactive Viewing help with Business Intelligence solutions?
BusinessObjects Mobile Interactive Viewing deploys business intelligence
to mobile devices in a user friendly manner. In BusinessObjects Mobile
Interactive Viewing, reports, documents and analytics are displayed on
various mobile devices with native rendering, single-click access and
device-appropriate user interactivity to enable mobile viewing of various BI
content:
•
Alerts
1
• Charts
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 7
About BusinessObjects Mobile Interactive Viewing
1
What is BusinessObjects Mobile Interactive Viewing?
• Graphs
8 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
What is BusinessObjects Mobile Interactive Viewing?
1
• Analytics
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 9
About BusinessObjects Mobile Interactive Viewing
1
What is BusinessObjects Mobile Interactive Viewing?
The BusinessObjects Mobile Interactive Viewing package enables the
Business Objects administrator to set up mobile client access to a Business
Objects Enterprise XIR2 server to allow device users to:
•
Download and install BusinessObjects Mobile Interactive Viewing
over-the-air (OTA) from a server designated by the administrator.
•
Set up auto login for a Business Objects Enterprise XIR2 server.
•
Set up a default document and report that will open automatically upon
login.
•
View, navigate, fit to screen, zoom in, zoom out, fence headers, show/hide
cell information display, and navigate business intelligence content coming
with fully native graphics rendering on the device.
10 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
About this guide
•
Drill down and drill up on business intelligence content.
•
Refresh business intelligence content.
•
Change multiple prompts on business intelligence content.
The BusinessObjects Mobile Interactive Viewing package
Using the components in the BusinessObjects Mobile Interactive Viewing
package you can:
•
Configure the Business Objects Enterprise XIR2 server to deliver content
to mobile devices.
1
•
Set up a group of users with BI content for mobile access on a Business
Objects Enterprise XIR2 server.
•
Design content specifically for the targeted mobile devices.
•
Deploy the XIR2 server-side technical prerequisites to enable mobile
device access.
• Pre-configure the client application and push it to users over the air or
over the wire.
About this guide
The documentation covers the essential details of how to design reports for
mobile use, how to install and deploy a BusinessObjects Mobile Interactive
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 11
About BusinessObjects Mobile Interactive Viewing
1
BusinessObjects Mobile Interactive Viewing Features
Viewing solution for a Business Objects Enterprise XIR2 server and how to
make it easy for end users to get their BI content on the move.
This document explains how to:
• deploy the BusinessObjects Mobile Interactive Viewing server components
and push the application to client devices
• develop documents and analytics appropriate to mobile device limitations
• enable access via the mobile network
Refer to Using the BusinessObjects Mobile Interactive Viewing for information
on installing the client application and using it to access BI content from a
mobile device.
BusinessObjects Mobile Interactive
Viewing Features
Lightweight mobile devices accompany users in their everyday business and
private lives and enable immediate access to information from virtually
anywhere. The trade off for this ubiquity is that mobile devices have limited
memory, variable network bandwidth, small screen size, and limited input
capabilities due to the absence of a real keyboard and mouse. For
professionals on the move, an enterprise mobile BI application needs to fit
into these constraints in the way that it combines enterprise data access,
mobile communications and software ease of use.
About report creation
Although BusinessObjects Mobile Interactive Viewing will display any report,
the user experience is best when reports are written specifically for easy
reading and navigation on a small screen.
Related Topics:
• Authoring Recommendations for Mobile Content on page 47
12 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
How BusinessObjects Mobile Interactive Viewing works
How BusinessObjects Mobile Interactive
Viewing works
A BusinessObjects Mobile Interactive Viewing solution includes two
components:
• A J2ME Java client application running on a mobile device with which
business users access, view and interact with content on XIR2.
• A BusinessObjects Enterprise XIR2 SP2 server with deployed Web
Services and some additional report content design practices targeted at
simplifying the mobile BI end user experience.
1
The Business Objects server is a BusinessObjects Enterprise XIR2 SP2
server. Its role is to expose corporate key data captured from corporate
database and data warehouses through BI documents and handle the BI
document lifecycle (Creation, Catalog, refresh, content delivery, report
interactivity. Users access data through the server portal.
The Java Client Application is a J2ME Midlet which has to be downloaded
and installed on the mobile device. Its role is to enable BI content access,
rendering and navigation from a mobile device. It is also able to trigger
selected server actions on documents such as refresh or drill. Although
BusinessObjects Mobile Interactive Viewing can read any Web Intelligence
or BusinessObjects document and most performance management gauge
analytics, it is best to design documents to fit the constraints of mobile device
displays.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 13
About BusinessObjects Mobile Interactive Viewing
1
How BusinessObjects Mobile Interactive Viewing works
The communication between the Java Client Application and the BI Server
is via industry-standard Web Services. The transport between the mobile
and the server is via standard HTTP or HTTPS protocol over the mobile
operator network and internet. To enable this communication the BI Server
Web Services must be made available to the Mobile Operator Network.
BusinessObjects Mobile Interactive Viewing uses the Web Services standards
defined by the key W3C specifications (SOAP, WSDL and XML). In particular,
BusinessObjects Mobile Interactive Viewing uses Business Objects Enterprise
XIR2 web services, including:
• Session Web Service
Authenticates the user and creates a session security token used in every
other Web service call
• BI Catalog Web Service
Provides folder and document access, including the various instances of
a document.
• Report Engine Web Service
Provides Open, Refresh, Navigate and Drill functions for document
content.
• Performance Management analytic Web Service
Exposes gauge analytics for viewing on devices.
• Remote Action Web Service
Exposes remote action functionality to allow device end users to interact
with enterprise software.
Business Objects provides a wide range of Web Services for developers that
you can find in http://www.businessobjects.com/products/dev_zone/.
Developers use these Web Services in IDEs with languages such as C# and
Java.
14 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
About BusinessObjects Mobile Interactive Viewing
Device Prerequisites and Device Type Support
Device Prerequisites and Device Type
Support
BusinessObjects Mobile Interactive Viewing requires a J2ME-capable mobile
device or smartphone with support for MIDP 2.0 and CLDC 1.1. Although
BusinessObjects Mobile Interactive Viewing can work on data infrastructures
like GPRS, users will experience best performance on 3G or EDGE networks.
BusinessObjects Mobile Interactive Viewing has been tested on the following
platforms and devices:
• Symbian S60 Platform
• Nokia N70 (N70 or later, N72 or later)
• Nokia e70 (e70 or later , e60 or later , e80 or later)
• Nokia e61 (e61 or later, e62 or later)
• Symbian P990 Platform
• Sony Ericsson M600i (M600i or later, M600x or later)
1
• BlackBerry Platform (OS version 4.1 or later)
• BlackBerry 8700 and 8707 (8700 series)
• BlackBerry Pearl 8100 (8100 series)
• BlackBerry 7290 (7200 series)
• BlackBerry 7100 (7100 series)
• Windows Mobile 5 Platform
• Palm Treo 750
• Orange SPV M3100 (Orange SPV series, HTC TyTN/ HTC Hermes/
QTek 9600 / iMate JASJAM / DOPOD CHT9000 / MDA Vario 2 / O2
XDA Trion)
• Samsung SGH-i320
• HP iPAQ hw6915
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 15
About BusinessObjects Mobile Interactive Viewing
1
Functional limitations
Functional limitations
• There is a wide range of mobile device platforms in the marketplace so
there is no guarantee that the BusinessObjects Mobile Interactive Viewing
J2ME midlet will work on all Java-capable devices.
• BusinessObjects Mobile Interactive Viewing does not offer push updates
within the application although regular alerts on the mobile device may
be used for that purpose.
• BusinessObjects Mobile Interactive Viewing supports Web Intelligence
and Desktop Intelligence documents and certain performance
management analytics.
• BusinessObjects Mobile Interactive Viewing does not support cascading
prompts.
• The BusinessObjects Mobile Interactive Viewing midlet is a 400K
download, but report data sets can be quite large and can theoretically
saturate available device memory. Large data sets on the server can be
mitigated by designing smaller report views.
• While BusinessObjects Mobile Interactive Viewing report size is limited
only by available device memory, in practice there are real limits to the
size and complexity of reports that you can display on a small mobile
device while maintaining acceptable usability. BI graphics and data should
not exceed 2X the physical screen width of the target devices for optimal
display.
16 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
2
Server-side prerequisites and configuration
2
Server requirements
Server requirements
BusinessObjects Mobile Interactive Viewing is a simple client-side addition
to an existing XIR2 deployment. Deploying BusinessObjects Mobile Interactive
Viewing does not require additional hardware since it fully leverages the
BusinessObjects Enterprise XIR2 Server and with deployed BI Web Services.
BusinessObjects Mobile Interactive Viewing is packaged with updated
versions of the prerequisite web services that must be deployed on top of
BusinessObjects Enterprise XIR2 SP2 to expose BI functionality to mobile
users.
Network Access
In order for BusinessObjects Mobile Interactive Viewing to access a BO XIR2
server, XIR2's standard web services interfaces must be accessible via the
mobile operator network for mobile device connection. There are a variety
ways to do this, both secured and not secured. Here is an example of a
BusinessObjects Mobile Interactive Viewing implementation:
Note: BlackBerry devices implemented on a BlackBerry Enterprise server
have their own solution for secure data transport. Refer to BlackBerry for
details.
There are several different network configurations that will achieve secure
information access: it is an IT choice to select a deployment scenario that
will best fit a specific solution's access and security requirements.
18 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
The following are example configurations that enable mobile client
applications to access XIR2 standard web services via the Mobile Operator
Network:
• Deploy a specific bridge to the Mobile Operator Network, such as the
BlackBerry Mobile Data System from RIM Corporation (this is shown in
the drawing above
• Deploy a dedicated BI server in a company's DMZ to make it directly
visible from the Internet
• Deploy a Reverse Proxy to expose the XIR2's Web Services from the
internal corporate Network
Using a secured connection
A secured connection ensures the identity of server and the confidentiality
of data exchanged between server and clients, making sure that clients
communicates with the real server, and that all data exchanged between the
clients and the server will be encrypted so that no password or confidential
data can be read by a third party listening on the communication line.
Server-side prerequisites and configuration
Network Access
2
There are two ways to set up security:
•
Some mobile vendors offer proprietary security mechanisms. In the case
of RIM, BlackBerrys can be secured using the BlackBerry Enterprise
Server/ Mobile Data System which enables BlackBerrys to securely access
e-mail and enterprise web/data servers using a VPN like solution.
•
Web Servers and Application Servers can be secured using HTTPS/SSL
standard web protocols.
BusinessObjects Mobile Interactive Viewing supports both
•
Unsecured HTTP connection to the server
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 19
Server-side prerequisites and configuration
2
Network Access
•
Secured HTTPS connection to the server
BusinessObjects Mobile Interactive Viewing also supports BlackBerry
Enterprise server in both HTTP and HTTPS mode.
The BusinessObjects Mobile Interactive Viewing certificate
BusinessObjects Mobile Interactive Viewing is signed to ensure secure
communication between the device on which it is installed and the
BusinessObjects Enterprise server to which it connects.
How SSL Secured Connections work
SSL (Secure Sockets Layer) and (TLS) Transport Layer Security (its
successor), are cryptographic protocols that provide secure communications
on the Internet. They provide endpoint authentication and communications
privacy over the Internet using cryptography. They authenticate the server
(ensure its identity) and allow client/server applications to communicate in
a secured way preventing eavesdropping, tampering, and message forgery.
SSL is based on usage of Public Key cryptography and signature algorithm.
These algorithms associate to each entity a private key and public key which
are mathematically related so that data enciphered using the private key can
be deciphered using the public key, and vice versa.
SSL certificates are signed files attached to an entity. They contain both a
description of the entity identity and the entity-related public key. A certificate
is signed by an authority, and is valid for a specific time period.
SSL requires a certification authority, trusted by both server and clients, to
be able to validate server and client certificates.
20 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Network Access
2
The certification authority public key is installed on the client through a
certification authority issued certificate, which is stored on the device in a
protected area called a key store.
Certificates related to the most common certification authority used on the
internet are pre-configured inside the device by the device manufacturer; it
is also possible to add a certificate authority, by importing its certificate inside
the key store through a configuration operation.
A public key, private key pair is generated for the server using standard PKI
mechanism.
The server public key and identity are included inside a server certificate
which is then signed by the certification authority.
The server private key and certificate are stored on the server.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 21
Server-side prerequisites and configuration
2
Network Access
When communication is established between the client and the server, a
very complex handshake occurs with several exchanges between the client
and the server to enable the establishment of secure communication between
the client and the server.
Among these exchanges, one important step is the server authentication by
the client. The server communicates its certificate to the client which validates
both the certificate validity and the server identity by challenging the certificate
signature through the list of trusted certification authority installed certificates.
When the certificate has been validated a session is established between
the client and the server using a temporary encryption key which will only
be valid for the duration of the session.
A variant of SSL enables both server and client authentication. In this case
a certificate private key pair is generated for each client by the certification
authority and exchanged with the server during the establishment of a secured
session.
22 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Configuring SSL on the device
SSL requires a Server certificate, which can be either:
•
A certificate issued by a recognized Certification Authority (Verisign,
Thawte, Entrust), this certificate needs to be bought from the certification
authority.
•
A certificate issued by a user private certification authority, this certificate
has been signed by an authority which is not in the list of recognized
certification authority on the device.
•
Or a self signed test certificate, which is a test certificate which is a
certificate signed using itself as a root certification authority.
Server-side prerequisites and configuration
Network Access
2
The list of trusted certification authority can be obtained from the configuration
menu of mobile devices.
If you buy a certificate for your server issued by any of these certification
authorities there should be no problem using this certificate on the mobile,
assuming that you followed all the required step described by the certificate
provider to obtain the certificate and that you properly identify your server.
The field cn: (common name) of the certificate should contains the full DNS
name under which the server will be made visible to the device.
Example if your site will be accessible under the following URL:
https://uws.businessobjects.com/wsmobi
Then the DNS name for your server to be used in thee certificate should be
uws.businessobjects.com
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 23
Server-side prerequisites and configuration
2
Network Access
And when generating your certificate signing request you should answer to
the following question
What is your first and last name?
[Unknown]: uws.businessobjects.com
By entering this DNS adress
If you use a self generated certificate or a certificate generated by your own
certification authority you will need to do a few more configuration steps on
the mobile among which importing the certification authority root certificate
into the mobile and on some device like Blackberry configuring the device
to use the use its own list of certificate (configure TLS to Handheld instead
of Proxy on BlackBerry).
Note: For the device to check the validity of the security certificate, the device
system date must be correctly configured. Since security certificates are
validated based on the server identity and the validity period of the certificate,
if the device system date is incorrectly configured, the device cannot validate
the certificate and the secure connection cannot be made to the server.
Instructions for configuring SSL on users' devices
By default, mobile devices are configured to accept only certificates coming
from a recognized certification authority, so a configuration operation is
required to change the default to work with other certificates.
To configure the security certificate on your device:
1. Navigate to the Security Settings menu of your device.
2. Chose the security protocol TLS.
3. Select Change Option in order to change the TLS method (the TLS default
is set to proxy).
4. Select Handheld to change the TLS method to Handheld.
24 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Package contents
5. Check that Prompt for Server Trust is set to Yes and validate your
operation by selecting Ok.
6. Download a certificate from the BI Server by clicking on the browser
application in the application menu and entering the BusinessObjects
Mobile Interactive Viewing Loader URL of the BusinessObjects Mobile
Interactive Viewing download page on the XIR2 server.
7. Select the CA Root certificate DER format on the XIR2 server.
8. When clicking on the certificate the device will install the certificate inside
the list of recognized certification authorities.
9. When clicking on the certificate the device will install the certificate inside
the list of recognized certification authorities.
10. To test that the certificate works, connect to a SSL site with an authorized
certificate. First, access the web browser on your device and open the
URL of the XIR2 server.
11. Select Security Options.
12. Under Certificates, select the Business Objects certificate.
13. Trust the Web Server. Enter the URL of the BusinessObjects Mobile
Interactive Viewing web site using HTTPS.
14. Add the server as a trusted server.
2
Package contents
The complete BusinessObjects Mobile Interactive Viewing zip file contains
the following files:
• Web services package (dswsbobje-mobile.war file)
This package includes all the BusinessObjects Enterprise XIR2 web
services plus two web services that are customized to support
BusinessObjects Mobile Interactive Viewing features:
• dsws-epmengine-ws
• dsws-remoteaction-ws
The web services delivered with the BusinessObjects Mobile Interactive
Viewing package must be deployed on the XIR2 SP2 server. They contain
additional functionality to support features made available by
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 25
Server-side prerequisites and configuration
2
Package contents
BusinessObjects Mobile Interactive Viewing. If you already have an
existing deployment of the BusinessObjects Enterprise XIR2 web services,
deploy these separately for use with BusinessObjects Mobile Interactive
Viewing.
• BlackBerry client package (.war file) that contains:
• the signed client applet (Mobi.jad)
• the applet download page
The OTALoader folder contains the client executables with a simple
download Web page which enables end users to download and install
the client into a Mobile device Over-The-Air (OTA). These pages
should be made available to your mobile users from a publicly
accessible web server.
• Mobi.cod: archives containing the code
• J2ME client package (.war file) that contains:
• the signed client applet (Mobi.jad)
• an unsigned version of the J2ME client (MobiUnsigned.jad)
The package includes an unsigned version for use on devices that do
not have the appropriate security certificate because they are blocked
by the carrier. Using the signed version is the recommended scenario.
• the applet download page
The OTALoader folder contains the client executables with a simple
download Web page which enables end users to download and install
the client into a Mobile device Over-The-Air (OTA). These pages
should be made available to your mobile users from a publicly
accessible web server.
• Mobi.jar: java archive containing the code
• Documentation files:
• readme.txt
• xir2_mobi_user_en.pdf
• xir2_mobi_admin_en.pdf
• ReportSamples folder: Sample database and reports for testing
26 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Package contents
• ReportSamples/README_ReportSamples.txt: About this test database
and reports
• ReportSamples/MOBI_Test_Universe.unv: Sample Universe for
MoBI_Test_DB
• ReportSamples/MOBI_Test_Report Samples.biar: Sample Reports
for MoBI_Test_DB
• ReportSamples/MOBI_Test_DB: Sample Microsoft Access database
• Images folder: Mobile device visuals for report authors
The Images folder contains a folder with two images of a Nokia or a
Blackberry screen that authors can use as a design backdrop in Web
Intelligence as well as a folder of alert icons authors can use in their
reports.
• Images/README_Images.txt: About images for report design
2
• Images/skin_Blackberry.gif: Blackberry report authoring skin
• Images/skin_Nokia.gif: Nokia report authoring skin
• Images/SymbolFail: Fail report alerts icon
• Images/SymbolPass: Pass report alerts icon
• Images/SymbolWarning: Warning report alerts icon
• Images/TrendGreenUp: TrendGreenUp report alerts icon
• Images/TrendRedDown: TrendRedDown report alerts icon
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 27
Server-side prerequisites and configuration
2
Server-side installation and configuration
• Images/TrendYellowDown: TrendYellowDown report alerts icon
• Images/TrendYellowFlat: TrendYellowFlat report alerts icon
• Images/TrendYellowUp: TrendYellowUp report alerts icon
• (There are a variety of 3D versions of these same images also included
in the zip file)
Server-side installation and configuration
Installing BO XIR2 SP2
You must install BusinessObjects Mobile Interactive Viewing on top of
BusinessObjects Enterprise XIR2 Service Pack 2.
Installing the required Web Services
The web services required to deploy BusinessObjects Mobile Interactive
Viewing are packaged with the application in the dswsbobje-mobile.war file.
Deploy the web services in this file to your web app server as you would any
other war file.
These web services deliver additional functionality and support for
BusinessObjects Mobile Interactive Viewing and must be therefore be
deployed instead of the standard BusinessObjects Enterprise XIR2 SP2 web
services.
Note: To use the AD authentication method, you must perform some
additional configuration to the web services. More information is provided
28 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Server-side installation and configuration
on this topic, and on configuring the XIR2 web services, refer to http://devli
brary.businessobjects.com.
Pre-configuring the client application
The client application (both the BlackBerry and J2ME versions) are packaged
pre-configured to access demo data on a public demo server made available
by Business Objects. You can pre-configure the client application that users
install on their device with the link to your BusinessObjects Enterprise server.
Refer to Pre-configuring the client application for OTA delivery to J2ME
devices on page 34for instructions for configuring the J2ME client or
Configuring the IT Policy on the BlackBerry Enterprise Server on page 35for
instructions on configuring the IT policy for the BlackBerry client.
Installing the Client download page
The client download page files allow you to configure a web page that mobile
users will access from their devices to download the client application. The
package includes three versions of the client download page:
• OTALoader\J2ME\index.html (the root level page that includes links to
the BlackBerry and J2ME versions of the download page)
• OTALoader\J2ME\index.html (specifically for the J2ME client download)
• OTALoader\BlackBerry\index.html (specifically for the BlackBerry client
download)
2
To install the BusinessObjects Mobile Interactive Viewing client download
files, copy the files in the folder OTALoader into a Web Server folder. Once
you have created the web site, you can instruct mobile users to enter its URL
on their devices to downolad the client application.
To enable the files to be recognized by mobile devices for download, you
must configure the required MIME types on the Web Server.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 29
Server-side prerequisites and configuration
2
Server-side installation and configuration
Apache Tomcat MIME types
In the case of Tomcat, these MIME type configurations are done by manually
editing
$TOMCAT_HOME/conf/web.xml
and adding the following three MIME type declarations:
Mime typeExtension
text/vnd.sun.j2me.app-descriptorJad
application/java-archiveJar
application/vnd.rim.codCod
In Tomcat these MIME type declarations are added by manually adding the
following lines at the end of <mime-mapping> list of the
$TOMCAT_HOME/conf/web.xml file:
<!-- MH Extensions for Mobile Application download -->
<mime-mapping>
<mime-mapping>
<extension>jad</extension>
<mime-type>text/vnd.sun.j2me.app-descriptor</mime-type>
</mime-mapping>
<mime-mapping>
30 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
<extension>jar</extension>
<mime-type>application/java-archive</mime-type>
</mime-mapping>
<mime-mapping>
<extension>cod</extension>
<mime-type>application/vnd.rim.cod</mime-type>
</mime-mapping>
IIS MIME types
Server-side prerequisites and configuration
Server-side installation and configuration
2
In the case of Microsoft IIS, these MIME type declarations are added by
editing the IIS server properties to add the three MIME type declarations:
Mime typeExtension
text/vnd.sun.j2me.app-descriptorJad
application/java-archiveJar
application/vnd.rim.codCod
These three MIME type declarations are made through the following series
of steps:
1.
In the IIS configuration panel, select the web site you are configuring and
right-click on Properties.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 31
Server-side prerequisites and configuration
2
Server-side installation and configuration
2.
In the properties pane, select the HTTP Header tab and click on File
Types at the bottom of this pane.
3.
In the File Types dialog box click New Type and add the three new file
types to this server's configuration. To do this, from the File types dialog
32 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Server-side installation and configuration
box select New Type and then enter the extension and mime type strings
of the each of the three new file types one by one from the table above.
For example, for the cod file type MIME entry (item three in the table
above), the IIS File Type entry pane looks like this:
2
When you have correctly added all three file types to the server configuration,
these three configuration additions should appear as follows within Registered
File Type within the IIS Registered MIME Types dialog.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 33
Server-side prerequisites and configuration
2
Pre-configuring the client application for OTA delivery to J2ME devices
Pre-configuring the client application for
OTA delivery to J2ME devices
This section explains how to pre-configure the client .jad file for J2ME devices.
For instructions on configuring the BlackBerry server for OTA push to client
devices, refer to the BlackBerry Server documentation.
To edit the J2ME version of the application:
1. Open the Mobi.jad (or MobiUnsigned.jad) file in the java folder for edit.
2. Edit the BOBJ_WS_URL field with the web service URL to which mobile
device users will connect.
3. Edit the BOBJ_CMS field with the name of the CMS repository that
contains the documents that mobile users will request.
4. Edit the BOBJ_UPDATE_URL field with the URL from which device will
download the configured .jad file.
5. Edit the MOBI_USERNAME field with the pre-configured user name to
connect to the CMS.
6. Edit the MOBI_PASSWORD field with user's password.
If you configure the user name and password, they will be available in
the login screen when the user launches the application. The user can
34 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Configuring the IT Policy on the BlackBerry Enterprise Server
overwrite the pre-configured values with another user name and password
before logging in.
7. Save your changes and close the Mobi.jad (or MobiUnsigned.jad) file.
8. Send the Mobi.jad (or MobiUnsigned.jad) file to your mobile users, or
upload it to a website from which they can download it.
Note: You can modify the properties listed above even though the application
is signed. Modifying any of the other properties in the .jad will break the
security signature.
Configuring the IT Policy on the
BlackBerry Enterprise Server
BusinessObjects Mobile Interactive Viewing supports a sever-side push of
connection and configuration information from the BlackBerry (BES) to the
BlackBerry device.
To configure the connection to the CMS and web services on the BES and
to push it to device users:
2
1.
Open the BlackBerry Manager.
2.
Select the BlackBerry Domain in the left pane.
3.
Select the Global tab.
4.
Click Edit Properties.
5.
Click IT Policy from the left pane of the Global Properties popup.
6.
Click the '…' button beside the IT Policies list box entry.
7.
In the IT policies dialog box, select the IT Policy you want to modify and
click Properties, or click New to create a new policy.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 35
Server-side prerequisites and configuration
2
Configuring the IT Policy on the BlackBerry Enterprise Server
8.
Select User Defined Items from the bottom of the left pane.
9.
Select IT Policy Template under Policy Item Customization and click the
'…' button.
10.
Click New in the IT Policy Template window.
11.
Select IT Policy Template Item from the left pane of the IT Policy Item
dialog.
12.
Replace the text New Policy Template with 'BOBJ_CMS'
13.
Change the Type to String
14.
Click OK.
The IT Policy Template window will now list an entry called BOBJ_CMS.
1. Click NEW
2. Highlight IT Policy Template Item on the left pane of the IT Policy Item
dialog.
3.
Replace the text New Policy Template with BOBJ_WSUR.
4.
Change the Type to String.
5.
The IT Policy Template window will now list both BOBJ_CMS and
BOBJ_WSURL.
6.
Click OK to close the IT Policy Template window You should now see 2
entries on the top right, listing BOBJ_CMS and BOBJ_WSURL under
Policy Item Settings.
7.
Click in the box to the right of BOBJ_CMS and enter the name of your
Business Objects CMS.
36 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Server-side prerequisites and configuration
Configuring the IT Policy on the BlackBerry Enterprise Server
8.
Click in the box to the right of BOBJ_WSURL and enter the URL of your
Business Objects Web Services (for example
http://BOBJSERVER:8080/dswsbobje/services
9.
Click OK to close all open dialogs except the Global Properties dialog.
To assign this policy to individual users:
1.
Click IT Policy to User Mapping
2.
Click the '…' button beside the IT Policy to User Mapping text
3.
Ensure all the users that are to have BusinessObjects Mobile Interactive
Viewing deployed have the policy you just modified checked. In the
example above, you should see the Default policy listed with a checkmark
beside it for each user.
2
To assign this policy to a group:
1.
Click IT Policy to User Mapping
2.
Select the User Groups List
3.
Select the group you want to modify
4.
Click the IT Admin task on the lower right of the screen
5.
Click Assign IT Policy
6.
Select the IT Policy you want to assign to the group.
7.
Click Done.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 37
Server-side prerequisites and configuration
2
Configuring the IT Policy on the BlackBerry Enterprise Server
The configuration settings will be pushed wirelessly to your selected users.
38 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
How documents are displayed on mobile devices
How documents are displayed on mobile
devices
For best results, reports should be specifically designed to accommodate
the small screen size and limited memory and interaction capabilities of
mobile devices.
BusinessObjects Mobile Interactive Viewing makes viewing and interacting
with BI content as intuitive as possible on mobile devices. In BusinessObjects
Mobile Interactive Viewing, documents are natively rendered on mobile
devices to take full advantage of the available display real estate.
The major presentation differences from the typical Infoview user experience
are:
• the specialized user interface for mobile content navigation
• the ability to set up single click document access
• conversion of report tabs to list view selections on the device
For details on these features, refer to Using BusinessObjects Mobile
Interactive Viewer.
About the cache
Caching occurs at both the server and device levels. The limit of the device
cache is the available memory, whereas the BusinessObjects Enterprise
cache is handled per session. A mobile user session cache is emptied at
the end of the session.
The size of the server cache can be configured. The default number of views
that the server caches is 10. As a user opens additional views (for example
by navigating through multiple pages in a report) older views are deleted
from the cache. The server cache may therefore contain fewer viewers than
the device limit could potentially hold.
If a user navigates through more pages than can be cached on the server,
then tries to return to views that have already been flushed from the server
40 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
cache, an error message is displayed on the device indicating that the
requested data is no longer available in the server cache:
The users can repopulate the cache with the requested view by selecting
OK.
About actions
BusinessObjects Mobile Interactive Viewing supports user actions from a BI
context. Actions enable business users to leverage BI context and data to
make better and timelier business decisions. BusinessObjects Mobile
Interactive Viewing Actions are triggered through a URL within a Web
Intelligence document cell and are able to leverage any BI content that exists
within a Web Intelligence report.
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
About actions
3
BusinessObjects Mobile Interactive Viewing supports:
•
local actions
•
remote actions
Local actions
By setting up action scripts on documents destined for viewing via
BusinessObjects Mobile Interactive Viewing; document authors can enable
mobile users to perform predefined actions from documents to obtain
additional data from other sources.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 41
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
About actions
Local actions leverage device functionality to enable users to obtain additional
data:
•
phoneto automatically dials a predefined phone number
•
smsto enables the user to send a text message to a predefined recipient
•
lookup enables the user to retrieve a phone number from the device's
address book
Remote actions
Remote actions work like local phone API actions, except that they leverage
functionality made available by a server-side Web Service to enable users
to interact with enterprise software. Remote actions require customizing the
appropriate web services to accept user input from the device and to pass
it to the appropriate application.
For more information on implementing remote actions, contact your Business
Objects Global Services representative.
Authoring actions
As a simple example, let's imagine a sales manager checks a particular sales
representatives' pipeline report from his mobile and decides he wants to call
the representative to discuss details about a particular deal. The report author
who wants to enable this workflow adds a URL cell to the Web Intelligence
document that contains the following syntax:
<a href='action_url'
desc='action_description'>[Cell value]</a>
Here is how this syntax is rendered by the Web Intelligence client:
42 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
About actions
3
A cell containing a valid action will be displayed as a hyperlink (underlined
by a blue line). The BusinessObjects Mobile Interactive Viewing client can
read this URL and change the displayed menu items and the Info Display
cell based on what is encoded there by the report author.
The new item in the menu will be accessible from a cell containing the action,
enabling the user to trigger the action within this context. To invoke the
actions the user browses to the cell and uses the menu or the enter key to
execute the action.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 43
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
About actions
Syntax for actions
The syntax for local actions is:
• laction://phoneto?num='0123456789'
• laction://smsto?num='0123456789'
• laction://lookup?name='jane doe'
Parameters take the following syntax:
@paramName='Label|type|defaultValue'$
where:
• @ indicates to the device that the user will enter data
• label is the string that will be displayed on the device before the field in
which the user will input data
• type (optional) is the data type that the user will enter (the supported types
are numeric, decimal, password, string, url)
• defaultValue (optional) is the value that is entered in the field by default
(if you enter a default value, you must indicate the data type that the
device should expect to receive as input)
• $ is a separator that allows you to concatenate two parameters
As an example of how this works, here is the exact URL from the Web
Intelligence report shown above that uses the report variable
'[SalesREPName] ' to invoke the local device PIM for making a phone call:
="<a
href=\'laction://phoneto?num=laction://lookup?name='"+[SalesREPName]+"'$$\'
desc=\'Call '+[SalesREPName]+'\'>[SalesREPName]</a>"
The formula terms above have the following meanings:
44 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Creating document links for improved navigation
• desc= What is displayed in the Cell of the Web Intelligence report (e.g.
'Call Jane Doe')
• name= The name that will be submitted to the device PIM for lookup
('Jane Doe' which is the current report value of [SalesREPName]). The
function uses the first and last name as separate search parameters, so
in the example above, the function would search for 'jane' and 'doe' in
the directory.
• phoneto= The phone call action that is invoked using the resulting phone
number that the PIM look up delivers from the phone's local phone
directory. Note that this feature can only be used if the device has a PIM
package that supports it. The phone directory must have this name in it
for the call to be successfully invoked.
Lookup action
The lookup action passes a value (phone number) to one of the other two
options. This feature can only be used if the device has a PIM package that
supports it.
The lookup action can also take the @num parameter, as follows:
3
<a href="laction://phoneto?@num='Enter number|numeric'$"
The @ argument indicates to the device that the user will enter the phone
number manually. When the user accesses the report containing this action,
the device displays the message 'enter number' and expects the user to
enter a numeric value (a phone number).
Creating document links for improved
navigation
Document links are specific actions that enable navigation from one document
to another. In Web Intelligence, OpenDocument links are created through
URL syntax in a cell that looks like this:
=<a href=\"action_url\" desc=\"action_description\">"+[Cell value]+"</a>"
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 45
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Creating document links for improved navigation
Specifically, the Business Objects Open Document syntax is as follows:
action_url=\' http://<server>:<port>/businessobjects/enter
prise115/desktoplaunch/opendoc/openDocument.jsp?sDocName=<doc
name>\'
The complete Web Intelligence OpenDocument syntax is documented at:
http://devlibrary.businessobjects.com/BusinessObject
sXIR2/en/en/BOE_SDK/boesdk_dotNet_doc/doc/boesdk_net_doc/html/Re
port_Linking13.html .
When an OpenDocument link is placed inside a Web Intelligence document,
the field containing an open document link appears underlined as if it were
a hyperlink. End users can move from the source document to the target
document simply by browsing to a cell that contains a document link, and
then by pressing OK or selecting Open from the menu.
Supported paramaters for document linking
BusinessObjects Mobile Interactive Viewing only supports a subset of the
full-fledged Web Intelligence OpenDocument syntax. Specifically,
BusinessObjects Mobile Interactive Viewing supports the following parameters
(note that BusinessObjects Mobile Interactive Viewing is case sensitive, so
the syntax must be respected exactly as specified):
• sPath: relative paths to the folder containing the current document, using
the following syntax:
[My+folder],[My+subfolder],
If this parameter is omitted, the function calls the document using the
iDocId (see below)
• sDocName: this parameter can be used without the iDocId if the document
name is unique in the CMS. If two documents in the CMS have the same
name, this parameter must be used in conjunction with the sPath and/or
the iDocID. If a unique identifier is not specified and two documents exist
in the CMS under the same name, BusinessObjects Mobile Interactive
Viewing displays the first document it retrieves when it searches the CMS.
• iDocID: this is the document's unique CUID in the CMS.
• sReportName
46 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
• sRefresh
• lsS[NAME]
• lsM[NAME]
Authoring Recommendations for Mobile
Content
Design for the device screen size
Since documents are rendered by BusinessObjects Mobile Interactive Viewing
using pixel to pixel mapping of your report layout, for greatest control authors
should design reports to the pixel. There are real limits to the size and
complexity of reports that you can display on a small mobile device while
maintaining any semblance of acceptable usability. For optimal display on
devices, graphics and data should not exceed 2X the physical screen width
of the target devices. This reality will force the creation of BI content
specifically for mobile devices.
3
Use the Java Editor
For greatest presentation accuracy and control use the Web Intelligence
Java editor.
Use a mobile device emulator
Use a mobile device emulator when authoring BI content to simulate the
mobile user experience. Install a device emulator on your workstation and
download BusinessObjects Mobile Interactive Viewing on the emulator to
test each report being displayed inside the emulator and ensure that there
are no surprises. The experience in the emulator and on the mobile device
will be slightly different both in display and edit controls.
Publish documents in a mobile folder
At log in, BusinessObjects Mobile Interactive Viewing will present the list of
documents and folders contained inside the user start folder to simplify the
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 47
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Authoring Recommendations for Mobile Content
user experience and reduce the number of clicks required to access content.
If no start folder is specified, BusinessObjects Mobile Interactive Viewing will
show folders and documents located either in the Mobile folder under Public
folders or the root folder, depending on whether or not a dedicated Mobile
folder exists. End users can select any folder in the repository as their default
folder.
Leverage XIR2 security
Normal XIR2 security applies to all document access made from the Mobile
folder. Use security rules to control which users have access to which mobile
documents.
Keep reports short
Short reports usually work better in mobile situations because mobile devices
are usually bandwidth and memory limited and it is difficult to navigate large
reports with a small screen.
Create and Use Design Templates
Embed an image of the target device in the report background as a model
of the screen size to help authors design the report to fit the device
constraints. Use image backgrounds as the report design template for target
mobile devices. Manipulate positioning and set column widths to make things
fit to the device screen. As a convenience we provide two backgrounds for
this purpose in the BusinessObjects Mobile Interactive Viewing download,
but you can create your own backgrounds and do the same.
Make these backgrounds available within XIR2 reports by copying the
background images into the Images folder of the Business Objects Enterprise
XIR2 program folder on the server at the following path:
C:\Program Files\Business Objects\BusinessObjects Enterprise 11.5\Images
This is the same file path as where the alert icons are copied.
48 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
Here is how a Nokia skin appears as a background in a Web Intelligence
document:
3
To set the background image go to the Background Image item in the
Properties tab of Web Intelligence java editor and then select the Custom
radio button and enter the file name of the image (the file must be local to
the web server in the images folder or available as a web URL).
Use shortest significant names for headers and names
•
Use codes instead of names for countries and cities.
•
Use short name (made of first name initials + last name) instead of full
name for persons.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 49
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Authoring Recommendations for Mobile Content
•
Use short labels for dates: FY04 instead of Year 2004, Q104 instead of
1st Quarter 2004.
Create short data display formats
Divide numbers by 1,000 or by 1,000,000 and express the numbers in K or
in M using Custom format to reduce the number of digits displayed (to reduce
column width). You may also put k or m in the column title to make columns
as small as feasible. Change universe definitions of dimensions and
measures, to enable drills on shortened text labels. For example, in the test
reports we converted the date dimension into two strings: a Text column
Year string (4 characters) and a Quarter (2 character) string. Then we built
an expression for YearAndQuarter made of the Quarter string concatenated
with the 2 last characters of Year.
To display charts with short numeric format display, first convert the chart to
a cross tab, shorten the number digits as necessary (e.g. divide by 1,000 or
by 1,000,000), and then convert the tab back to a chart.
Use Position controls to maximize screen real estate
Place your elements as close as possible to the left corner of the report (e.g.
Charts, Grids or Tables):
• Place first report element, label or grid (at position (0, 0)) so that no blank
will be displayed on the mobile screen.
• Remove the border of the page (Left Margin, Top Margin) = (0 px, 0 px)
• Remove the headers of the page (Top Header, Bottom Header) = (0 px,
0 px)
Limit font sizes to small-medium-large
Use Fonts 9, 12 and 15: Report display is limited to three available font sizes:
Small, Medium and Large. This ensures greatest compatibility across the
variety of device types available in the marketplace. Font mapping on
BusinessObjects Mobile Interactive Viewing uses the following fonts. Design
BI reports with these font sizes to achieve optimal rendering accuracy and
consistency between the server and client behavior:
50 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
• Arial 9 to map Small font of the mobile
• Arial 12 to map Medium font of the mobile
• Arial 15 to map Large font of the mobile
Use small fonts for tables. Do not use bold styles for table content (use bold
only for labels).
Plan for drillable headers
Leave blank cell space for drill icons that BusinessObjects Mobile Interactive
Viewing will place on drillable headers.
Design content to fit within available column space
All numbers should display entirely within available cell space. Strings should
display entirely, or at least the most significant part of each string should be
visible.
Make tables and graphs fit in the smallest device screen size
3
When this is not possible:
• Design columns and labels to fit the screen of the target mobile device(s).
• In no event design reports larger than two screen widths of the device
screen.
• In reports that exceed a single screen width, make sure that at least two
columns (and better three or four columns) fit entirely in the physical
screen width.
• Try to adjust the columns sizing so that the grid exactly fits the width of
the mobile screen (or such that at least a fixed number of columns exactly
fits the screen width).
Use short meaningful names for document and report tabs
In BusinessObjects Mobile Interactive Viewing, Report Tabs are converted
into a user selection list and also are displayed in the report context labels.
Choose Report Tab names that are short and meaningful to the end user as
they become navigation aids. These name strings should be at most 20
characters wide to be reliably visible on mobile devices.
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 51
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Authoring Recommendations for Mobile Content
Using alert and status icons in Web Intelligence documents
Use alert indicator icons to add graphics to report content for easier mobile
device end user consumption. The BusinessObjects Mobile Interactive
Viewing download includes 8 alerting icons that can be added to conditional
report alerts for greater visual impact.
• Trend Icons
• Status Icons
Using these icons requires two steps:
1. Make these icons available within XIR2 reports by copying the icon images
into the Images folder of the Business Objects Enterprise XIR2 program
folder on the server at the following path:
C:\Program Files\Business Objects\BusinessObjects Enterprise
11.5\Images
2. To add icons to a conditional alert within a report, select the column for
the alert and open the alerts button:
52 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
3
3. Select or create the alert you need for the data in question:
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 53
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Authoring Recommendations for Mobile Content
4. Set the appropriate icon on each condition of the alert by selecting the
Format button on the alert condition:
54 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
3
5. In the Background part of the alert format dialog (bottom of the window)
type in the specific icon file name in the URL entry field. The server will
add boimg// as a prefix to your file name which tells the server to look in
the local images directory for this icon:
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 55
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
3
Authoring Recommendations for Mobile Content
Creating performance management gauges for viewing on devices
BusinessObjects Mobile Interactive Viewing enables users to access and
display gauge analytics (speedometer, barometer, thermometer) on mobile
devices.
Users can display static gauge analytics published as InfoObjects in the
BusinessObjects Enterprise CMS. Mobile device users can access gauge
analytics stored in the Mobile folder, public and personal folders, the favorites
folder or the inbox.
Users cannot refresh analytics from the device or open gauges set to Refresh
on Open. To ensure that users view up-to-date data in analytics, you may
create a schedule in the CMC to refresh the analytic on an appropriate basis.
56 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
The following types of gauges are supported:
• static analytics without prompts
• basic gauges saved as SVG
• gauges based on goals
•
sliced gauges (note that only the slice used to save the analytic will be
usable)
The following gauge features are not supported:
• traffic lights
• navigation (linking) options from the gauge (you can display gauges that
contain links on the device but the link will not be active)
• gauges with a previous time period configured (a second needle)
• tooltips
• metric tree options
• gauges saved as refresh on open
• gauges based on prompts
• gauges that contain javascript
• gauges saved as HTML or Flash
• gauges that have no data during the selected period
3
Configuring and Deploying BusinessObjects Mobile Interactive Viewing 57
BusinessObjects Mobile Interactive Viewing Report Authoring Guidelines
Authoring Recommendations for Mobile Content
3
58 Configuring and Deploying BusinessObjects Mobile Interactive Viewing
Loading...