Professional Documents
Culture Documents
BusinessObjects Mobile
BusinessObjects Mobile
Windows
Copyright © 2008 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; 5,857,205; 6,289,352; 6,247,008; 6,490,593; 6,578,027;
6,831,668; 6,768,986; 6,772,409; 6,882,998; 7,139,766; 7,299,419; 7,194,465;
7,222,130; 7,181,440 and 7,181,435. Business Objects and the Business Objects
logo, BusinessObjects, Business Objects Crystal Vision, Business Process On
Demand, BusinessQuery, Crystal Analysis, Crystal Applications, Crystal Decisions,
Crystal Enterprise, Crystal Insider, Crystal Reports, Desktop Intelligence, Inxight,
the Inxight Logo, LinguistX, Star Tree, Table Lens, ThingFinder, Timewall, Let
there be light, Metify, NSite, Rapid Marts, RapidMarts, the Spectrum Design, Web
Intelligence, Workmail and Xcelsius are trademarks or registered trademarks in
the United States and/or other countries of Business Objects and/or affiliated
companies. All other names mentioned herein may be trademarks of their respective
owners.
Third-party Business Objects products in this release may contain redistributions of software
Contributors 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
2008-02-08
Contents
Chapter 1 About the BusinessObjects Mobile Installation and Deployment
Guide 5
The information in the BusinessObjects Mobile installation guide...............6
Target audience for the BusinessObjects Mobile installation guide.............6
Server-side configuration...........................................................................30
To configure the Mobile server.............................................................30
Setting up the Mobile Administration database....................................32
Deploying with a BlackBerry Enterprise Server (BES).........................33
Standard deployment with a proxy server............................................34
To start the Mobile servers manually....................................................35
To use a device simulator for testing....................................................35
To migrate BusinessObjects Mobile version 1 to version 2..................36
Deploying the client OTA download web application.................................36
Deploying the war file...........................................................................37
Setting the required MIME types on the application server..................38
Client installation........................................................................................39
Automated deployment to mobile devices...........................................39
Index 53
1
1 About the BusinessObjects Mobile Installation and Deployment Guide
The information in the BusinessObjects Mobile installation guide
Related Topics
• Recommended deployment architecture on page 21
Related Topics
• BusinessObjects Mobile overview on page 10
2
2 Introducing BusinessObjects Mobile
BusinessObjects Mobile overview
Although BusinessObjects Mobile can work on data networks like GSM and
GPRS; EDGE, 3G or 3G+ networks offer the best performance.
Related Topics
• BusinessObjects Mobile business intelligence features on page 11
• Device prerequisites and device type support on page 17
Related Topics
• Supported documents on page 11
• Supported business intelligence functionality on page 11
Supported documents
Related Topics
• Supported business intelligence functionality on page 11
Functional limitations
BusinessObjects Mobile presents some functional limitations, due to the
technical and design constraints of mobile devices:
• BusinessObjects Mobile is not guaranteed to work on all mobile devices
and operating systems. For the list of supported devices and operating
systems, see: http://support.businessobjects.com/documentation/support
ed_platforms/default.asp.
• Report data sets can be large and can theoretically saturate available
device memory. The unsatisfactory display of large data sets can be
mitigated by designing smaller report views.
Detailed information on the supported document features that can be
leveraged using BusinessObjects Mobile is provided in the Using
BusinessObjects Mobile guide: Best practices for mobile document design
section. BusinessObjects Mobile supports Web Intelligence documents,
Crystal reports and some analytics, with some functional limitations.
Related Topics
• Device prerequisites and device type support on page 17
• Supported documents on page 11
Ease of deployment
IT Administrators responsible for installing and deploying the application can
leverage the following deployment features:
• Deploy a secure web site so that users can download and install the
BusinessObjects Mobile client application Over-The-Air (OTA).
• Deploy the Mobile server and a proxy server or BlackBerry Enterprise
Server.
Ease of administration
Business intelligence administrators responsible for managing business
intelligence applications and content can leverage the following administration
features:
Related Topics
• Automated deployment to mobile devices on page 39
• Tracking user activity on page 42
Note: It is recommended you plan for 2 KB of memory per user that connects
to the mobile server.
The Mobile client also supports secured local storage for downloading and
storing local copies of Web Intelligence documents, Crystal Reports and
supported analytics on the mobile device.
The alert mechanism allows the display of an alert description and a link to
the related document on the device. Depending on the device, an alert can
trigger a sound, vibration or flashing light on the screen. Alerts also enable
users to store the document related to the alert on the device.
For the latest list of supported platforms and devices, see: http://support.busi
nessobjects.com/documentation/supported_platforms/default.asp.
Related Topics
• BusinessObjects Mobile deployment checklist on page 20
• Device prerequisites and device type support on page 17
• Setting up the Mobile Administration database on page 32
• Deploying with a BlackBerry Enterprise Server (BES) on page 33
Supported Platforms
Server requirements
Related Topics
• How BusinessObjects Mobile works on page 14
• Recommended deployment architecture on page 21
Related Topics
• BusinessObjects Mobile overview on page 10
3
3 Installing and Configuring BusinessObjects Mobile
BusinessObjects Mobile deployment checklist
You can choose to enable communication between mobile devices and the
BusinessObjects XI 3.0 server via a third-party proxy server inside your
corporate DMZ or a BlackBerry Enterprise Server (BES).
Related Topics
• Deploying with a BlackBerry Enterprise Server (BES) on page 33
• How BusinessObjects Mobile works on page 14
• Deploying Mobile server components on page 22
• Deploying the client OTA web application components on page 23
Deploying the client OTA web application is optional. To prevent having the
client application available to device users in this way, do not install the war
file containing the OTA delivery web application.
If you do want to install the client OTA delivery web application, do so on the
same server as the mobile server or on a separate server. Business Objects
recommends that you install the Mobile server components on a dedicated
server for performance and stability reasons.
Deploying the client OTA web application is optional. To prevent making the
client application available to device users,do not install the war file containing
the OTA delivery web application.
Then run the setup again on the server on which you are deploying the client
OTA web application. BusinessObjects recommends that you deploy the
client OTA web application on the BusinessObjects Enterprise XI 3.0 server
to leverage the wdeploy tool to deploy automatically the client OTA web
application.
Related Topics
• Deploying the client OTA download web application on page 36
Related Topics
• Deploying the client OTA download web application on page 36
• Installing alert and status icons for Web Intelligence documents on
page 28
• Installing background images as templates for device screens on page 29
In server:
• Server\common contains:
• Root key
• Signed authentication key
• Common configuration files keys
• Common binaries (JAR files)
• Server\VAS contains:
• VAS (authentication server) configuration files
• VAS (authentication server) binaries (JAR files)
• authentication server data and logs
The selected components are now installed on the server. If you installed
the Mobile server components, the following options are now available from
the Windows Start menu under BusinessObjects XI 3.0 > BusinessObjects
Mobile:
• Launch Mobile Authentication server (VAS)
• Launch Mobile Job server (VMS)
• Install Mobile Authentication server (VAS) as a service
• Uninstall Mobile Authentication server (VAS) as a service
• Install Mobile Job server (VMS) as a service
• Uninstall Mobile Job server (VMS) as a service
• Launch Password Scrambler
The images and icons packaged with the setup are installed in the
BusinessObjects Enterprise 12.0\images directory. If you run the setup
on the same server that is running BusinessObjects XI 3.0, the image files
are added to the existing directory. If you run the setup on a different server,
the setup creates the BusinessObjects Enterprise 12.0\images directory.
If you chose to install the client OTA web application, the setup installs the
MobileOTA.war at BusinessObjects Enterprise 12.0\Java\application
by default.
Related Topics
• BusinessObjects Mobile deployment checklist on page 20
Related Topics
• Deploying the war file on page 37
5. Enter user and organization information and select one of the availability
options then click Next to proceed.
6. Select one of the following installation options:
• Typical
• Complete
• Custom -- if you want to select individual components for installation
Note: Use this option if you want to conduct a distributed installation
(installing the server components and the client OTA web application
on separate servers).
Related Topics
• BusinessObjects Mobile deployment checklist on page 20
• Server-side installation on page 27
• Server-side configuration on page 30
Related Topics
• Installing background images as templates for device screens on page 29
Server-side configuration
Depending on the deployment scenario you have adopted for
BusinessObjects Mobile, you need to configure one or more of the following
server connections after installation:
• If your deployment does not includes a BES, you can install and configure
a third-party proxy server to enable communication between the
BusinessObjects Enterprise server on the intranet and mobile devices.
• If you have a BES server, you need to configure the connection between
the BES server and the Mobile server.
Related Topics
• To configure the Mobile server on page 30
• Deploying with a BlackBerry Enterprise Server (BES) on page 33
• Setting up the Mobile Administration database on page 32
• Deploying the client OTA download web application on page 36
You can install the mobile server on the BusinessObjects XI 3.0 server or
on a dedicated server.
1. Open the Business Objects\Mobile
12\server\VMSServer\config\server.config and the Business
Objects\Mobile 12\server\VAS\config\server.config files for edit.
Related Topics
• Deploying with a BlackBerry Enterprise Server (BES) on page 33
• BusinessObjects Mobile deployment checklist on page 20
By default, the ports through which the Mobile server communications are
11011 for the authentication server (VAS) and 11711 for the job server (VMS).
You can change the default ports by instructing the server to accept incoming
traffic from a different port.
All incoming traffic is via the port you specify. If you are deploying a proxy
server (not a BES), configure it to redirect communication to the port that
you selected.
The mobile server database does not store user credentials, but information
about user connections and synchronizations to the mobile server. The
BusinessObjects Mobile setup includes a pre-configured Apache Derby
database that you can use with the mobile server, plus configuration files for
other standard supported databases. To configure a database other than
Apache Derby:
1. Create a database and a database admin user.
This database houses the mobile authentication database and the mobile
job server database.
2. Run the appropriate SQL configuration scripts in the database of your
choice. The configuration scripts delivered with the mobile setup are
located at:
Business Objects\Mobile 12\preinstall\VAS and Business
Objects\Mobile 12\preinstall\VMSServer
Note: You must run two separate configuration scripts: one for the
authentication server (VAS) and one for the job server (VMSServer).
Configuration scripts are available for:
• SQL Server
Related Topics
• How BusinessObjects Mobile works on page 14
(BES). You need to configure the connection between the BES server and
the BusinessObjects Mobile server. You then need to activate the BES push
listener, which reconnects the BlackBerry server automatically if it cuts out
while data is being processed.
Related Topics
• To configure the Mobile server on page 30
This deployment scenario is recommended if you are not using the BlackBerry
Enterprise server (BES) as part of of the Mobile deployment.
The Mobile server can communicate with multiple CMS. The Mobile server
is located on the intranet and can be deployed in a firewalled configuration.
The Mobile server cannot be configured in a reverse proxy conguration
however, because communication between the Mobile server and client is
via proprietary communication protocols, not HTTP.
Related Topics
• To configure the Mobile server on page 30
You can start the mobile servers (the Authentication and job servers) by
launching them from the Start menu under: \BusinessObjects Enterprise
XI 3.0\BusinessObjects Mobile. Always start the Authentication server
(VAS) first. You can also configure the servers as Windows services.
Related Topics
• Logging and tracking errors on the Mobile server on page 44
• Installed file description and location on page 25
You can use device simulators to test your deployment and connections,
and to view documents before deploying them to real devices.
Note: To use a device simulator for testing, you have to update the
VAS/cluster.config file to enable the simulator to access the server via the
BlackBerry MDS server.
You can download simulators and instructions for deploying and configuring
them from the device vendors who create them.
Related Topics
• BusinessObjects Mobile deployment checklist on page 20
Related Topics
• Setting the required MIME types on the application server on page 38
• Installation package contents on page 23
• Deploying the client OTA download web application on page 36
• Deploying the war file on page 37
The OTA web pages are packaged in a Web Archive (war) file. Detailed
instructions on deploying web applications in war files are located in:
• for manual deployments: BusinessObjects Enterprise XI 3.0 Installation
and Configuration Guide
• for automatic deployment using the wdeploy tool delivered with
BusinessObjects Enterprise XI 3.0:BusinessObjects Enterprise XI 3.0
Installation and Configuration Guide
Overview of wdeploy
wdeploy is a command-line tool for JSP environments that you can use to
deploy BusinessObjects web applications.
To deploy the OTA web archive and support download of the Mobile client
application to device users, add the following MIME types to the application
server:
Jad text/vnd.sun.j2me.app-descriptor
Cod application/vnd.rim.cod
<mime-mapping>
<extension>jad</extension>
<mime-type>text/vnd.sun.j2me.app-descriptor</mime-type>
</mime-mapping>
<mime-mapping>
<extension>cod</extension>
<mime-type>application/vnd.rim.cod</mime-type>
</mime-mapping>
Client installation
The BusinessObjects Mobile client is a small application that needs to be
downloaded to each device. There are three ways to install the client on the
mobile device:
• from a secured web site using Over-The-Air (OTA) provisioning.
• Over-The-Air via the BlackBerry Enterprise Server (BES) to push the
download to devices.
• manually on each device via the client desktop (using, for example, USB,
Bluetooth, Infrared).
Related Topics
• Automated deployment to mobile devices on page 39
• Deploying the client OTA download web application on page 36
Related Topics
• Deploying the client OTA download web application on page 36
• Deploying with a BlackBerry Enterprise Server (BES) on page 33
4
4 Setting up administration and security rights
Managing security rights for mobile users and documents
Administrators can then easily set up security rights for mobile users, groups,
and documents using the standard BusinessObjects Enterprise security
rules.
To manage mobile user and document security rights, you use the standard
BusinessObjects Enterprise Central Management Console (CMC).
The data on device profiles and user activity can be used to provide statistical
reports to fine-tune and evolve your mobile deployment.
This information is stored in the mobile server database that you created to
log user activity and errors.
5
5 Troubleshooting Information
Logging and tracking errors on the Mobile server
To control the server level of logging, edit the values in the server\com
mon\config\shared.config.
You can change the server logs level without stopping the servers.
2. You can also trigger this dump by issuing the following command: vtXXXd
dump.
Related Topics
• To trigger the log dump remotely on page 45
Related Topics
• To reload log levels on page 44
• an installation/deployment issue?
• a login issue?
• an execution issue?
For detailed errors in the VAS and VMS logs, check that:
• the VAS can communicate with the BlackBerry server (if you are deploying
a BES)
• the VMS has registered to the VAS
• the client has registered to the VAS
• the VMS can communicate with the BusinessObjects Enterprise server
If TCP and APN settings are not correctly configured on the device, the user
can receive "open-tunnel failure" or "Network unavailable" errors.
Configure the device for internet access to resolve these errors, which can
also be caused by:
Cause Resolution
Incorrect Network con- • Check the data subscription
figuration of the device • Check the carrier settings (TCP)
• Check the IT policy
• Check the application rights (can use HTTP and
socket connection)
A
A Get More Help
http://support.businessobjects.com/documentation/product_guides/
http://www.businessobjects.com/support/
For more information, contact your local sales office, or contact us at:
http://www.businessobjects.com/services/consulting/
http://www.businessobjects.com/services/training
mailto:documentation@businessobjects.com
Note: If your issue concerns a Business Objects product and not the
documentation, please contact our Customer Support experts. For information
about Customer Support visit: http://www.businessobjects.com/support/.
A C
actions 11 Central Management Console 42
email 11 checklist
SMS 11 installation 20
administration console 13 CLDC 10
administration Console 10 client
Administration Console 17, 42 application 39
administration database 10 client application 14
administration tasks 6 downloading 6
alerters installing 6
download icons 28 CMC 42
alerts 11, 17 connection information
subscribing groups 13 preconfigure 13, 20
analytics 11 Crystal Reports 11, 17
Apache
configuring 38 D
application
client-side 14, 39 database
authentication server 14, 17, 30 mobile administration 14, 20, 32
repository 20
default document 11
B default folder 11
barometers 11 demos 23
BES 14, 20, 21, 30, 39 deployment 34
Blackberry architecture 21
devices 39 automating 13, 39
BlackBerry distributed 20, 30
client application 27 scenarios 21
Enterprise Server 14, 17, 20, 21, 30, 39 standalone 20
deployment (continued) I
with BES 33
device errors icons
tracking 45 for reports 23, 28
device tracking 17, 42 images
devices report templates 29
BlackBerry 39 installation 27
DMZ 20, 21, 30 background images 29
configuring 30 checklist 20
document security 42 client application via OTA 13, 36, 39
documents client application via wire 13, 39
default 11 client device application 6
local 11 files installed 25
offline 11 graphics files 23
Web Intelligence 11 icons 28
drill 11 server-side 32
validating 25
web download page 23
E intranet environment 21
EDGE 10
EDGE networks 17 J
email 11
errors J2ME 10, 23, 39
open-tunnel failure 46 client application 27
tracking 45 J2ME client application 14
job server 14, 17, 20, 30
F
L
features
limitations 12 limitations
folders features 12
default 11 Linux 16
load balancing 30
local
G documents 11
GPRS 10 login
GSM 10 preconfigure 13, 20
logon
preconfigure 39
logs
log dump 45
reload 44
M platforms (continued)
Windows 16
midlet 39 ports
MIDlet 14 for proxy server 30
download 27 proxy server 14, 30, 33, 34
MIDP 10 configuring 30
MIME types 38
configure 27
mobile server
R
errors 44 readme 23
logs 44 report design
Mobile server 17 download icons 28
mobile servers reports
starting 35 Crystal Reports 11
display recommendations 12
N refresh 11
repository 14, 17, 32
network unavailable 46
networks
3G+ 17
S
EDGE 17 samples 23
supported 17 SDK
Crystal Enterprise 14, 17
O Report Engine 14, 17
security 21
offline server
documents 11 BlackBerry 39
open-tunnel failure servers
troubleshooting 46 authentication 14, 17, 21, 30
OTA 23, 27, 39 BlackBerry 14
web download page 36 database 17
OTA delivery job 14, 17, 30
for installation 13, 39 Mobile 17
OTA web pages 37 proxy 14, 30, 33
OTALoader file 23, 27 supported platforms 16
skins 29
smartphone 10
P SMS 11
platforms 27 speedometers 11
Linux 16 Symbian series-60 10
UNIX 16 Symbian UIQ 10
T W
templates war file
background images 29 deploying 37
thermometers 11 Web Intelligence
Tomcat alerter icons 28
configuring 38 documents 11
tracking devices 42 tracking changes 17
troubleshooting 44, 45, 46 Windows 16
server installation 27
Windows CE 10
U Windows Mobile 10
UNIX 16 wire delivery
user rights 42 for installation 13, 39
user tracking 17, 42