xi3 mobile admin en

8/14/2019 Xi3 Mobile Admin En

http://slidepdf.com/reader/full/xi3-mobile-admin-en 1/56

Installing and Deploying

BusinessObjects Mobile

BusinessObjects Mobile

Windows



© 2008 Business Objects. All rights reserved. Business Objectsowns the following

U.S. patents, which may cover products that are offered and licensed by Business

Copyright

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 OnDemand, 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.

Business Objects products in this release may contain redistributions of software

licensed from third-party contributors. Some of these individual components may

Third-party

Contributorsalso 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



ContentsAbout the BusinessObjects Mobile Installation and Deployment

Guide 5

Chapter 1

The information in the BusinessObjects Mobile installation guide...............6

Target audience for the BusinessObjects Mobile installation guide.............6

Introducing BusinessObjects Mobile 9Chapter 2

BusinessObjects Mobile overview.............................................................10

BusinessObjects Mobile business intelligence features.......................11

BusinessObjects Mobile deployment and administration features.......13

How BusinessObjects Mobile works..........................................................14

Supported Platforms.............................................................................16

Server requirements.............................................................................17

Device prerequisites and device type support.....................................17

What's new in this release.........................................................................17

Installing and Configuring BusinessObjects Mobile 19Chapter 3

BusinessObjects Mobile deployment checklist..........................................20

Recommended deployment architecture...................................................21

Deploying Mobile server components..................................................22

Deploying the client OTA web application components ......................23

Installation package contents....................................................................23

Installed file description and location...................................................25

Server-side installation..............................................................................27

Installing BusinessObjects Mobile on Windows...................................27

Installing alert and status icons for Web Intelligence documents.........28

Installing background images as templates for device screens...........29

Installing and Deploying BusinessObjects Mobile 3



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..................38Client installation........................................................................................39

Automated deployment to mobile devices...........................................39

Setting up administration and security rights 41Chapter 4

Managing security rights for mobile users and documents.......................42

Tracking user activity.................................................................................42

Troubleshooting Information 43Chapter 5

Logging and tracking errors on the Mobile server.....................................44

To reload log levels...............................................................................44

To trigger the log dump remotely..........................................................45

Tracking device errors...............................................................................45

Standard troubleshooting tips....................................................................45

Network unavailable errors........................................................................46

Get More Help 49Appendix A

Index 53

4 Installing and Deploying BusinessObjects Mobile

Contents



About the BusinessObjectsMobile Installation and

Deployment Guide

1



The information in the BusinessObjects

Mobile installation guideThis guide provides information about BusinessObjects Mobile features and

technology, and gives instructions on how to deploy the application as part

of a BusinessObjects Enterprise deployment. It includes:

• descriptions of the deployment scenarios supported by Business Objects

for BusinessObjects Mobile.

• information on how to provide a secure wireless network to transfer

business intelligence data to mobile device users.

• step-by-step instructions on how to install and deploy the BusinessObjects

Mobile server components on top of BusinessObjects Enterprise for each

supported platform.

• step-by-step instructions on how to deploy the client application for

BusinessObjects Mobile to supported mobile devices via a corporate web

site.

• information on how to set up and manage user rights.

• information on key administration tasks, such as pushing documents to

mobile users, subscribing users to alerts, tracking server and device

activity, and troubleshooting your BusinessObjects Mobile system.

Note: Instructions on how to download the BusinessObjects Mobile client

application to a mobile device from a corporate web site page are provided

in the Using BusinessObjects Mobile guide.

Related Topics

• Recommended deployment architecture on page 21

Target audience for the BusinessObjectsMobile installation guide

This guide is designed to help the following administrators set up and manage

a Business Objects business intelligence deployment that caters to users of

mobile devices:

• IT administrators, who install and configure the Mobile server and the

Mobile server database.


About the BusinessObjects Mobile Installation and Deployment Guide

1 The information in the BusinessObjects Mobile installation guide



• Business intelligence administrators, who deploy BusinessObjects

Enterprise XI 3.0, to plan and manage how business intelligence data

and applications are deployed and managed enterprise wide, and who

manage BI documents, folders and alerts for Mobile users.

• IT security managers, who guarantee that business intelligence datacommunicated via the internet and wireless networks remains secure, to

manage Mobile client access to the server, and to manage the security

policy of the Mobile server.

• Email/mobile administrators, who configure the BlackBerry Enterprise

server and Mobile proxy server.

Related Topics

• BusinessObjects Mobile overview on page 10


1About the BusinessObjects Mobile Installation and Deployment Guide

Target audience for the BusinessObjects Mobile installation guide



Introducing BusinessObjectsMobile

2



BusinessObjects Mobile overview

BusinessObjectsMobile consists of a client-side application formobile devicesand a Mobile server component that communicates with the BusinessObjects

Enterprise server, so that professionals on the move can access business

intelligence information from a mobile device, such as a smartphone or PDA.

The application is designed specifically to meet the screen size and

interactivity constraints of mobile devices. Business intelligence documents,

reports and analytics are displayed on supported mobile devices with native

rendering, single-click access and device-appropriate user interactivity.

BusinessObjects Mobile is a java application of approximately 1 mb that you

download to your mobile device. This application exists in different versions

for the following device types:

• BlackBerry

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


Introducing BusinessObjects Mobile

2 BusinessObjects Mobile overview



BusinessObjects Mobile business intelligencefeatures

Using BusinessObjects Mobile, professionals on the move can analyze,

interact, and be alerted about changes to critical data related to their business

interest easily at any time.

Related Topics

• Supported documents on page 11

• Supported business intelligence functionality on page 11

Supported documents

BusinessObjectsMobile provides users of a mobile devicewith remoteaccess

to the following types of business intelligence document:

• Web Intelligence documents

• Crystal Reports documents

• Some gauge analytics (including speedometers, barometers, and

thermometers)

Note: For details on which document versions that BusinessObjects Mobile

supports, go to http://support.businessobjects.com/documentation/support ed_platforms/default.asp.

Depending on the document type, you can view, analyze and interact with

the data it contains in a variety of ways.

Related Topics

• Supported business intelligence functionality on page 11

Supported business intelligence functionality

Using BusinessObjects Mobile, you can leverage a wide range of features

and functionality to manage your Business Intelligence documents and data.

Key features include the ability to:

• Set up a default document or folder that opens automatically whenever

you log into the application.


2Introducing BusinessObjects Mobile


http://support.businessobjects.com/documentation/supported_platforms/default.asp






• Refresh reports to retrieve the most up-to-date data.

• View results using zoom and navigational shortcuts.

• Drill on results to analyze detailed or summary data.

• Navigate to related documents via hyperlinks on reports.• Change how results are filtered by modifying prompt values.

• Receive alerts when a specific document is modified, a condition is met,

or a schedule is run.

• Take follow-up actions by clicking on report cells to launch an SMS, phone

call or email.

• Save and consult documents offline to mitigate network interruptions and

minimize communication costs.

Functional limitations

BusinessObjects Mobile presents some functional limitations, due to thetechnical 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 beleveraged 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


• Supported documents on page 11

Report creation recommendations

Although BusinessObjectsMobile can display any Web Intelligencedocument

or Crystal report, user experience is best when reports are written specifically

for easy reading and navigation on a small screen. You can find best practice

information on how to design reports targeted at mobile end users in the



2 BusinessObjects Mobile overview







Using BusinessObjects Mobile guide: Best practices for mobile document

design section.

BusinessObjects Mobile deployment andadministration features

The BusinessObjects Mobile package includes components designed to

facilitate the deployment and administration tasks that IT and business

intelligence Administrators need to perform when catering to mobile users.

Ease of deployment

IT Administrators responsible for installing and deploying the application canleverage 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:

• Set up a group of mobile users with secured access to business

intelligence content on a Business Objects Enterprise server.

• Track user activity, for example the devices used and user login

information, to provide statistical information about how BusinessObjects

Mobile is being used.

• Design content specifically for the targeted mobile devices.

Note: Power users with experience in designing Web Intelligence

documents and Crystal Reports can also design mobile content. For full

information on designing these documents and reports for mobile

consumers, see the Using BusinessObjects Mobile guide:Best practices

for mobile document design section.






Related Topics

• Automated deployment to mobile devices on page 39

• Tracking user activity on page 42

How BusinessObjects Mobile works

The BusinessObjects Mobile solution includes server components that need

to be installed next to BusinessObjects Enterprise XI 3.0, plus a client

application formobile devices.A BusinessObjects Mobiledeployment consists

of the following client and server components:

• BusinessObjects Enterprise XI 3.0 server

• BusinessObjects Mobile server, including the BusinessObjects Mobile

server database• BusinessObjects Mobile client application on mobile devices

In addition, if you are deploying BusinessObjects Mobile to BlackBerry

devices, Business Objects recommends that you also deploy the BlackBerry

Enterprise Server (BES).

BusinessObjects Enterprise XI 3.0

The standard BusinessObjects Enterprise XI 3.0 server is packaged with

two BusinessObjects SDKs (the Report Engine SDK and the Crystal

Enterprise SDK). The BusinessObjects Enterprise server exposes corporatedata captured from corporate databases and data warehouses through

business intelligence documents, and handles the document lifecycle

(creation, catalog, refresh, content delivery and report interactivity). Users

access data through the server portal.

BusinessObjects Mobile relies on the BusinessObjects Enterprise SDKs to:

• authenticate the user

• provide folder and document access

• provide open, refresh, navigate, and drill functionality

• expose gauges

• expose remote action functionality

The BusinessObjects Mobile package includes some report design best

practice documentation, to help document creators design business

intelligence content that displays correctly on supported mobile devices.



2 How BusinessObjects Mobile works



BusinessObjects Mobile server

The Mobile server is installed on the corporate intranet and passes requests

and answers between the BusinessObjects Enterprise server and Mobile

clients. The BusinessObjects Mobile server comprises two servers:• Mobile authentication server -- manages user access and security policy,

and records user logs.

This information can be used as source data for reports on your mobile

user activity.

• Mobile job server -- stores details about each synchronization operation

performed by a device with business intelligence content published to the

BusinessObjects Enterprise server.

Data from both servers is stored in the Mobile server database.

BusinessObjects Mobile server database

The BusinessObjects Mobile server database stores data on user activity

and the status on synchronization between the BusinessObjects Enterprise

server, the Mobile server, and the devices. It contains one row for every

record on the device for each user, so there are a lot of rows, but little data

in each row.

BusinessObjects Mobile supports a subset of the database platforms and

versions supported by BusinessObjects Enterprise XI 3.0. A pre-configured

Apache Derby database is delivered with BusinessObjects Mobile.

Note: It is recommended you plan for 2 KB of memory per user that connects

to the mobile server.

BusinessObjects Mobile client

The Mobile client is a J2ME application that must be download to each mobile

device. The Mobile client application enables business intelligence content

access, rendering, and navigation from a mobile device. It is also triggers

selected server actions on documents such as refresh or drill.BusinessObjects Mobile can read any Web Intelligence document or Crystal

report and most Dashboard and Analytics gauge analytics. However, it is

best to design documents to fit the constraints of mobile device displays.



How BusinessObjects Mobile works



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 Mobile client application also allows you to subscribe to alerts ondocuments that have been modified on the server or have alerters configured.

Supported alerts include alerts on the device when:

• the server document is modified

• a data condition is met when the server document is modified

• the schedule of a document is executed

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.

The communication between the Client Application and the BusinessObjects

Enterprise Server is through a secured proprietary transport protocol.

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


• Setting up the Mobile Administration database on page 32• Deploying with a BlackBerry Enterprise Server (BES) on page 33

Supported Platforms

The BusinessObjects Mobile application is delivered as a plug-in to

BusinessObjects Enterprise XI 3.0. The application includes server

components designed to work on the following platforms:

• Microsoft Windows

For detailed information about platform requirements for each of the

BusinessObjects Mobile supported platforms, see: http://support.businessob

jects.com/documentation/supported_platforms/default.asp.



2 How BusinessObjects Mobile works











Related Topics

• Server requirements on page 17

• Server-side installation on page 27

Server requirements

BusinessObjects Mobile is delivered as an add-on to an existing

BusinessObjects Enterprise XI 3.0 deployment. To leverage functionality

designed specifically for mobile users, it is necessary to deploy the following

server components on top of BusinessObjects Enterprise XI 3.0:

• Mobile server (composed of an authentication server and a job server)

• Database server that logs user activity and provides information on the

synchronization of data between the BusinessObjects Enterprise server and devices

• If you are deploying the application to BlackBerry devices users, Business

Objects recommends that you include the BlackBerry Enterprise Server

(BES) in your deployment. If you are not, you can deploy a proxy server

to handle communication between the BusinessObjects Enterprise server

and client devices

Related Topics

• How BusinessObjects Mobile works on page 14

• Recommended deployment architecture on page 21

Device prerequisites and device type support

For the list of supported platforms and devices see: http://support.busines

sobjects.com/documentation/supported_platforms/default.asp.

Although BusinessObjectsMobile canwork on data infrastructures like GPRS,

the best performance is experienced on 3G, 3G+ or EDGE networks.

What's new in this release

This release of BusinessObjects Mobile introduces powerful new features

to improve your business intelligence deployment for mobile users.



What's new in this release







New server features

• Uses Business Objects SDKs (Web Intelligence report Engine SDK and

Crystal Enterprise SDK) instead of Web Services.

• Works as an add-on to BusinessObjects Enterprise XI 3.0.• Delivers new integrated server components for: security, alerting, and

synchronization with the BusinessObjects Enterprise server.

New client features

• Provides the ability for users of mobile devices to work offline, on

documents stored locally on the device, without being connected to the

server.

• Allows users to subscribe to alerts that notify the device of specific

modifications to documents and document alerters.• Supports interaction with Crystal reports.

• Allows mobile users to leverage the new tracking feature in Web

Intelligence documents, where changes compared to a previous version

of the document are highlighted.

New administration features

• The server database tracks user and device activity.

Comparing versions 1 and 2

Mobile version 2Mobile version 1

Based on XI 3.0Based on XI Release 2

Uses SDKUses Web Services

Works only with BlackBerry devicesWorks with any J2ME MIDP/CLDC de-

vices

Related Topics• BusinessObjects Mobile overview on page 10



2 What's new in this release



Installing and ConfiguringBusinessObjects Mobile

3



BusinessObjects Mobile deployment

checklistThis checklist provides an overview of the steps you need to accomplish to

complete a successful installationand deployment of BusinessObjectsMobile.

It is recommended you read this checklist before beginning the installation

procedure.

1. Visit the Business Objects Supported Platforms web site at: http://sup

port.businessobjects.com/documentation/supported_platforms/default.asp .

2. Install and configure BusinessObjects Enterprise XI 3.0.

Refer to the BusinessObjects Enterprise XI 3.0 Installation and

Configuration Guide for more information.

3. Install the BusinessObjects Mobile server components on:

• a dedicated server

• the BusinessObjects Enterprise XI 3.0 server

4. Configure the Mobile server (both the authentication and job servers).

5. Set up the Mobile server database and configure the connection.

6. Optional: enter the configuration for the BlackBerry Enterprise Server

(BES) if you are including a BES in your deployment.

7. Optional: if your deployment includes a BlackBerry Enterprise Server (BES) then you need to set up the BES connection and activate the BES

push listener and configure the BES IT policy.

8. Optional: if you are deploying a proxy server to enable communication

between the mobile server and devices, configure and deploy the proxy

server.

9. Optional: if your deployment includes a BlackBerry Enterprise Server

(BES), start the MDS.

10. Start the Mobile authentication server (VAS).

11. Start the Mobile job server (VMS).

12. Optional: install and configure the OTA download page on a corporate

web server, so that device users can download the Mobile client

application Over-The-Air:

a. Deploy the web application (war file).

b. Add the required MIME types to the application server.


Installing and Configuring BusinessObjects Mobile

3 BusinessObjects Mobile deployment checklist







Related Topics


• Installed file description and location on page 25

• Server-side configuration on page 30

• Deploying the client OTA download web application on page 36

Recommended deployment architecture

Note: Before planning your deployment architecture for BusinessObjects

Mobile, we recommend that you read the documentation on BusinessObjects

Mobile overview and How BusinessObjects Mobile works.

Several deployment scenarios are supported for BusinessObjects Mobile:

• Deploy BusinessObjects Mobile server components and client OTAdelivery web application together on the BusinessObjects XI 3.0 server.

• Deploy BusinessObjects Mobile server components and client OTA

delivery web application together on a dedicated server.

• Deploy BusinessObjects Mobile server components and client OTA

delivery web application on separate servers.

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


3Installing and Configuring BusinessObjects Mobile

Recommended deployment architecture



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 Mobile server components

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.



3 Recommended deployment architecture



Related Topics


• Deploying the client OTA web application components on page 23

Deploying the client OTA web applicationcomponents

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.

To deploy the client OTA web application, do so in either a distributed or

combined installation. In a combined installation, you install theBusinessObjects Mobile server components and the client OTA web

application on the same server. To configure this deployment, run the

BusinessObjects Mobile setup on the desired server and select all

components for install.

In a distributed installation, you install the BusinessObjects Mobile server

components and the client OTA web application on separate servers. To

configure this deployment, run the BusinessObjects Mobile setup on the

server that you use to host the mobile server components, and select only

the Mobile server components for install.

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


Installation package contentsThe BusinessObjects Mobile setup is approximately 300 MB in size. It

includes the following packages, which are installed by default:

• the Mobile server package, which includes:

• jar files: java archives containing the code



Installation package contents



• cod files: archives containing the code

• the Mobile server database

• the Mobile server

• the signed client applet (MobiBB.jad)

• Documentation files:

• the administrator guide: xi3_mobile_admin_xx.pdf

• the device user guide: xi3_mobi_admin_xx.pdf

• ReportSamples folder: Sample database and reports for testing

• ReportSamples/README_ReportSamples.pdf: About this test

database and reports

• ReportSamples/MOBI_Test_Universe.unv: Sample Universe for

MoBI_Test_DB

• ReportSamples/MOBI_Test_Report Samples.biar: Sample Reportsfor 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• 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

• 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)



3 Installation package contents



Note: These image files for alerts icons and report skins are delivered

to assist document creators to design reports optimized for display on

mobile devices.

• the Mobile client OTA download web archive (.war) which includes:• 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 via a web server.

• the device user online help

The mobile_user.zip file contains an HTML version of the

BusinessObjects Mobile User Guide that you can deploy on the OTA

site for device user access.

• a java servlet that enables the web page to detect the OS version of the device connecting to the web page.

Related Topics


• Installing alert and status icons for Web Intelligence documents on

page 28

• Installing background images as templates for device screens on page 29

Installed file description and location

After a successful installation of BusinessObjects Mobile server components,

the following files are installed on the BusinessObjects Mobile server:

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



Installation package contents



• authentication key pair

• Server\VMS contains:

• VMSServer (job server) log files

• VMSServer (job server) configuration files• VMS binaries (JAR files)

• Server\Preinstall contains database configuration scripts for supported

databases.

• Server\Tools contains the Password Scrambler tool to encrypt the Mobile

server database administrator password.

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




3 Installation package contents



Server-side installation

Installing BusinessObjects XI 3.0

You need to install BusinessObjects Mobile on top of BusinessObjects

Enterprise XI 3.0. For the list of supported platforms and devices, see:

http://support.businessobjects.com/documentation/supported_platforms/de

fault.asp.

Installing the Client application download page

The client application download page files allow you to configure a web page

that mobile users can access from their devices to download the client

application. The war package delivered with the installation setup includes:• mobile_user.zip: the device user online help in HTML format

• a java servlet that enables device OS detection by the web site (to

download automatically the correct version of the client application)

Related Topics

• Deploying the war file on page 37

Installing BusinessObjects Mobile on Windows

Verify that BusinessObjects Mobile supports your server platform and

operating system. Refer to the Business Objects Supported Platforms web

site at http://support.businessobjects.com/documentation/supported_plat

forms/default.asp.

To install the BusinessObjects Mobile server-side components and client

OTA web application on a Windows server:

1. Extract the BusinessObjects Mobile .zip file to the Mobile server host

machine and launch the BusinessObjects Mobile installer (setup.exe).

2. Select the installation language (the default is Optionally, check the Create

log file during installation checkbox to activate logs during the setup

process. Click OK to proceed.

3. Click Next to display the License Agreement.

4. Accept the license agreement and click Next to proceed.














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

7. Select a destination location (default location is c:\BusinessObjects

XI 3.0\BusinessObjects Mobile) and click Next to proceed.

The application files are installed on the server.

8. Click Finish to complete the installation process.

You are ready to perform the server-side configuration steps appropriate to

your chosen deployment scenario.

Related Topics



• Server-side configuration on page 30

Installing alert and status icons for Web Intelligencedocuments

The BusinessObjects Mobile download package includes eight trend and

status alerting icons that can be added to Web Intelligence conditional report

alerters for greater visual impact when viewed on mobile devices.

Using these icons requires two steps:

1. Make these icons available to Web Intelligence document creators bycopying the icon images into the images folder of the BusinessObjects

Enterprise XI program folder on the server at the following path:

C:\Program Files\Business Objects\BusinessObjects Enterprise

12\images



3 Server-side installation



Note: The BusinessObjects Mobile setup installs the icon files in this

directory by default. If you did not install the Mobile server components

on the BusinessObjects Enterprise server, you need to move the icons

from the Mobile server to the BusinessObjects Enterprise server so that

they are available to document creators.

2. To add icons to a conditional alerter within a report:

a. Select the column for the alert and open the alerts button.

b. Select or create the alert you need for the data in question.

c. Set the appropriate icon on each condition of the alert by selecting

the Format button on the alert condition.

d. In the Background part of the Alert Format dialog type in the specific

icon file name in the URL entry field.

The server adds boimg:// as a prefix to your file name, directing the

server to the local images directory for this image file.

Related Topics

• Installing background images as templates for device screens on page 29

Installing background images as templates for devicescreens

It is highly recommended that document creators, catering to mobile users,

use image backgrounds for target mobile devices as report design templates.

Embedding an image of the target device in the report background provides

a model of the screen size that helps design the report to fit the device

constraints. This makes it easy to position blocks and set column widths so

that the report elements fit to the device screen.

Note: Business Objects provides two backgrounds for this purpose in the

BusinessObjects Mobile download package. You can also create your own

backgrounds for specific mobile devices.

1. Install these graphics files on the BusinessObjects Enterprise server at

the following location: C:\Program Files\Business Objects\Busines

sObjects Enterprise 12\images

Note: The BusinessObjects Mobile setup installs the background image

files in this directory by default. If you did not install the Mobile server

components on the BusinessObjects Enterprise server, you need to move






the images from the Mobile server to the BusinessObjects Enterprise

server so that they are available to document creators.

2. To set the background image in a Web Intelligence document, go to the

Background Image item in the Properties tab of Web Intelligence JavaReport Panel, and then select the Custom radio button and enter the file

name of the image.

The server adds boimg:// as a prefix to your file name, which tells the

server to look in the local images directory for this image file.

Server-side configuration

Depending on the deployment scenario you have adopted for

BusinessObjects Mobile, you need to configure one or more of the followingserver 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


To configure the Mobile server

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.

2. Set the EXTERNAL_HOSTNAME parameter to the name of the machine

that hosts so that devices can resolve the machine name to locate the

mobile server.



3 Server-side configuration



For example: EXTERNAL_HOSTNAME=mobile_server.do

main_name.com

3. Open the Business Objects\Mobile

12\server\VAS\config\cluster.config and the BusinessObjects\Mobile 12\server\VMSServer\config\cluster.config files

for edit.

4. Set the HOST_PORT parameter to the name of the machine that hosts

your BES/MDS so that devices can locate the server.

For example: HOST_PORT=MDS_server.domain_name.com

The Mobile server can communicate with multiple CMS. The Mobile server

is located on the intranet and can therefore be deployed in a firewalled

configuration.

Note: The Mobile server cannot be configured in a reverse proxyconfiguration however, because communication between the Mobile

server and client is via proprietary communication protocols, not HTTP.

Related Topics



To change the default communication ports on the Mobile server

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.

To change the ports through which the Mobile server communicates:

1. Open the config\server.config files in the VAS and VMSServer

directories.

2. Set the BINDTO_PORT parameter to the port you want to use for traffic

incoming to the Mobile server.

3. Save and close both config files.






4. Restart the Mobile server.

Setting up the Mobile Administration database

Verify that your database platform and version is supported for

BusinessObjects Mobile. Refer to: http://support.businessobjects.com/docu

mentation/supported_platforms/default.asp. Verify that your database has

at least 2 KB of memory per user in your mobile deployment.

The mobile administration database is made up of two major databases:

• the authentication database, which stores information about:

• mobile users (ID, name, email)

• definition of mobile user groups• mobile devices (ID, type, IP, login time, user ID, device ID)

• the push/sync database, which stores information about user

synchronizations to the server, including document versioning information

for documents in the local store.

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










• Apache Derby

• DB2

• Oracle

• MySQL3. Fromthe Start menu, launch BusinessObjects XI 3.0 > BusinessObjects

Mobile > Launch Password Scrambler .

4. Type the database administrator password in the Password Scrambler

tool, and click OK to run the tool.

The Password Scrambler Tool generates an encrypted password to

protect the password in the Mobile server configuration files.

5. Copy the encrypted password.

6. Update the mobile server configuration files to point to the mobile server

database. Open and edit the cluster.config files in both the server\VASand server\VMSServer folders and change the following parameters:

a. URL: URL of the JDBC connection. The default value of the JDBC

connection is: derby:../derby_db.

b. DB_DRIVER: the database driver name The default value is

org.apache.derby.jdbc.EmbeddedDriver .

c. Type the database admin user name in the LOGIN field.

d. Paste the encrypted database admin password in the PASSWORD

field.

7. Optionally, update the other configurable database parameters:

• Maximum number of simultaneous connections (Default = 30)

• Initial capacity (Default = 5)

8. Save and close the configuration files.

Related Topics

• How BusinessObjects Mobile works on page 14

Deploying with a BlackBerry Enterprise Server (BES)

This deployment scenario is recommended if you are deploying

BusinessObjects Mobile to BlackBerry users.

If you are deploying BusinessObjects Mobile to BlackBerry users, Business

Obejcts recommends that you deploy via a BlackBerry Enterprise Server






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

To configure the BES, refer to BlackBerry documentation.

Related Topics


Standard deployment with a proxy server

This deployment scenario is recommended if you are not using the BlackBerry

Enterprise server (BES) as part of of the Mobile deployment.

You can configure a proxy server to enable communication between client

devices and the BusinessObjects XI server.

If you do not plan to include a BlackBerry Enterprise server in your

deployment, you can configure a proxy server to enable communication

between client devices and the BusinessObjects XI server.

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 congurationhowever, because communication between the Mobile server and client is

via proprietary communication protocols, not HTTP.

To configure a proxy server to allow devices to communicate with the Mobile

server, open ports 11011 and 11711. These are the default ports that are

opened for incoming and outgoing communication with the proxy server. If

you change these default values, update the proxy with the customized

values you selected.

Related Topics







To start the Mobile servers manually

If your deployment includes a BlackBerry Enterprise Server (BES), start theMDS server before launching the Mobile servers.

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.

If you want to start the servers manually:

1. Start the VAS first with the vtauthd.bat in the server\VAS\bin file. Use

the command start2 to launch the bat.

A DOS window launches and displays the progression of the VAS startup.

2. Once the VAS is ready, start the VMS first with the vtvmsd.bat in the

server\VMSServer\bin file. Use the command start2 to launch the

bat.

A DOS window launches and displays a server initialization complete

message when the VMS is ready.

Related Topics

• Logging and tracking errors on the Mobile server on page 44

• Installed file description and location on page 25

To use a device simulator for testing

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.






To migrate BusinessObjects Mobile version 1 toversion 2

You must first install BusinessObjects XI 3.0.

If you have already deployed BusinessObjects Mobile version 1 on top of

BusinessObjects XI Release 2, migrate your mobile device users to

BusinessObjects Mobile version 2:

1. Install BusinessObjects XI 3.0.

2. Disable access to the web services.

3. Install and configure the new Mobile version 2 server components.

4. Remove the version 1 application from client devices. If you deployedversion 1 via the BES, you can replace the version 1 client application

with the version 2 application by using the BES server to force removal

of the version 1 client and to push the version 2 client to devices.

If you are maintaining both BusinessObjects Enterprise XI R2 and XI 3.0

servers at the same time, you can maintain a side-by-side install of

BusinessObjects Mobile versions 1 and 2.

Related Topics


Deploying the client OTA download webapplication

To enable device users to download to the BusinessObjects Mobile client

application to their devices, you can configure an OTA download web site.

The client package and download page is delivered in a standard SUN war

file in the BusinessObjects Mobile setup. The MobileOTA.war file includes:

• a web application• a java servlet to enable device detection on the web page

• the device user HTML online help files (which can be deployed on the

web page)

• the client application

To configure the OTA web application:



3 Deploying the client OTA download web application



• ensure that your application server is Java-compliant and supported by

BusinessObjects Enterprise XI 3.0.

• use the wdeploy tool to deploy the MobileOTA.war file (only available if

you installed the mobile server package on the BusinessObjects XI 3.0

server and in the BusinessObjects Enterprise installation directory).

• manually deploy the war file (required if you installed the mobile server

package on a dedicated server).

• configure the required MIME types on the application server.

Related Topics

• Setting the required MIME types on the application server on page 38

• Installation package contents on page 23


• Deploying the war file on page 37

Deploying the war file

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 can do any or all of the following:

• list all the available, installed applications listed in your BusinessObjects

Enterprise $INSTALLDIR\deployment\apps directory

• deploy all the available BusinessObjects web applications that you haveinstalled and BusinessObjects customized web applications developed

with Developer Suite.

• build the available web applications you have installed

• create the resources and configuration files required for a specified

application and then deploy the application



Deploying the client OTA download web application



• deploy an application whose resources and configuration files have been

prepared for deployment

• list all the applications that have been previously deployed in an application

server • undeploy applications that have been previously deployed in an application

server, in a web server or both

Note: In line with BusinessObjects Enterprise version XI Release 2

terminology, this documentation uses the term web application server instead

of the term application server used through version 6.x.

See the README file for specific information or known issues.

wdeploy is a command-line tool for JSP environments that you can use to

deploy BusinessObjects web applications.

wdeploy is ANT-based with some Javascript helpers.

Setting the required MIME types on the applicationserver

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:

Mime typeExtension

text/vnd.sun.j2me.app-descriptor Jad

application/vnd.rim.codCod

Example: Setting the required MIME types in Tomcat

In Tomcat, MIME type declarations are added at the end of <mime-map

ping> list of the $TOMCAT_HOME/conf/web.xml file as follows:

1. Open $TOMCAT_HOME/conf/web.xml for edit.



3 Deploying the client OTA download web application

2. Add the following text:



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

3. Save and close the web.xml file.

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


Automated deployment to mobile devices

Dependingon your deployment scenario, youcandeliver theBusinessObjects

Mobile client application to users:

• Over-The-Air (using OTA delivery) via an internal web site page

• Over-The-Air to BlackBerry devices using the push capability in the

BlackBerry Enterprise Server (BES)



Client installation



Related Topics





3 Client installation



Setting up administrationand security rights

4



Managing security rights for mobile users

and documentsBusiness intelligence administrators and document creators designing

documents for mobile users, are advised to publish those documents to a

folder dedicated to mobile documents. Typically, this folder is named Mobile.

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

To access documents viaBusinessObjects Mobile, device users need access

rights for documents via InfoView.

Note: For full details on setting up security rights, refer to the

BusinessObjects Enterprise Administrator's Guide.

Tracking user activity

Administrators can track and store data on mobile users and devices acrossthe BusinessObjects Mobile deployment, including:

• device names

• IP addresses

• device serial numbers

• user names

• user logins

• time/date of connection

• device types

The data on device profiles and user activity can be used to provide statisticalreports 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.


Setting up administration and security rights

4 Managing security rights for mobile users and documents



Troubleshooting Information

5



Logging and tracking errors on the

Mobile serverThe main types of server errors you need to capture in your deployment are:

• BusinessObjects Enterprise errors directly reported to the Mobile client.

Refer to the BusinessObjects Enterprise Error Message Guide for details.

• Mobile server errors:

• Generic errors

• Authentication errors: invalid credentials, session errors

• Networking Errors: Remote site unreachable, Cannot resolve address,

Local database access errors, Connection to application server lost

To control the server level of logging, edit the values in the server\com

mon\config\shared.config.

To reload log levels

You can change the server logs level without stopping the servers.

To reload the log levels while the server is running:

1. Open the server config files and issue the following command: vtXXXd

reload_cfg.

The log is reloaded and the server dumps a state snapshot to the

VMP_DUMP channel when it encounters a suspicious condition.

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



5 Logging and tracking errors on the Mobile server



To trigger the log dump remotely

The MANAGEMENT_PORT can be used to trigger a server dump or tomonitor server status. Do not proxy it or make it externally accessible. To

generate a server dump remotely:

1. Open the config\server.config files in both the VAS and VMSServer

directories.

2. Set the MANAGEMENT_PORT to the ports you want to open to receive

commands via TCP. By default, these ports are 11012 and 11712.

The management ports are enabled to receive and process commands

via TCP.

3. Send the following command to the server via the TCP connection: dump

The server writes a state dump to the logs.

Related Topics

• To reload log levels on page 44

Tracking device errors

In addition to BusinessObjects Enterprise errors and Mobile server errors

that can be displayed on the device, the device also displays and logs mobileclient errors:

• Connectivity errors: Network not available, Cannot find server

• Local Store Errors: Cannot access local store, Cannot open document

from local store, Out of memory

You can check the logs on BlackBerry devices by pressing and maintaining

the Alt key while typing lglg on the device.

Standard troubleshooting tipsThe following questions can help you resolve errors captured in your server

and device logs.

Is this error caused by:

• a server- or client- specific issue?


5Troubleshooting Information

Tracking device errors



• an installation/deployment issue?

• a login issue?

• an execution issue?

Some areas to check when troubleshooting:

• Is the device supported/compatible?

• Can the device browser access the internet?

• Can the device access BES/MDS or the proxy server?

• Are the server OS/JDK version/database supported/compatible?

• Did you start the servers in the right order (BES, then VAS, then VMS)?

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

Network unavailable errors

Mobile devices that connect to BusinessObjects Mobile need to be configured

to access the internet. Ensure that all devices in your deployment can connect

to the internet so they can access the Mobile 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:

ResolutionCause

• Check the data subscription

• Check the carrier settings (TCP)

• Check the IT policy• Check the application rights (can use HTTP and

socket connection)

Incorrect Network con-

figuration of the device



5 Network unavailable errors



ResolutionCause

• Mobile server name

• Mobile port number

• CMS name

Incorrect connection

settings

• Device cannot connect to the BES

• BES cannot connect to the Mobile Server

• Mobile Server cannot connect to the BusinessOb-

jects XI 3.0 Server

• Device cannot connect to the internet or to the

proxy server (if your deployment includes a proxy

server)

• The proxy server (if your deployment includes a

proxy server) cannot connect to the Mobile Server • The Mobile Server cannot connect to the Busines-

sObjects XI 3.0 Server

Device cannot connect

to the Mobile server


5Troubleshooting Information

Network unavailable errors





5 Network unavailable errors



Get More Help

A



Online documentation library

Business Objects offers a full documentation set covering all products and

their deployment. The online documentation library has the most up-to-dateversion of the Business Objects product documentation. You can browse

the library contents, do full-text searches, read guides on line, and download

PDF versions. The library is updated regularly with new content as it becomes

available.

http://support.businessobjects.com/documentation/product_guides/

Additional developer resources

http://devlibrary.businessobjects.com

Online customer support

The Business Objects Customer Support web site contains information about

Customer Support programs and services. It also has links to a wide range

of technical information including knowledgebase articles, downloads, and

support forums.

http://www.businessobjects.com/support/

Looking for the best deployment solution for your company?

Business Objects consultants can accompany you from the initial analysis

stage to the delivery of your deployment project. Expertise is available in

relational and multidimensional databases, in connectivities, database design

tools, customized embedding technology, and more.

For more information, contact your local sales office, or contact us at:

http://www.businessobjects.com/services/consulting/

Looking for training options?

From traditional classroom learning to targeted e-learning seminars, we can

offer a training package to suit your learning needs and preferred learning

style. Find more information on the Business Objects Education web site:

http://www.businessobjects.com/services/training


Get More Help

A


http://devlibrary.businessobjects.com/







http://devlibrary.businessobjects.com/




Send us your feedback

Do you have a suggestion on how we can improve our documentation? Is

there something you particularly like or have found useful? Drop us a line,

and we will do our best to ensure that your suggestion is included in the nextrelease of our documentation:

mailto:[email protected]

Note: If your issue concerns a Business Objects product and not the

documentation,pleasecontact ourCustomer Support experts. For information

about Customer Support visit: http://www.businessobjects.com/support/ .

Business Objects product information

For information about the full range of Business Objects products, visit:http://www.businessobjects.com.


AGet More Help



http://www.businessobjects.com/

http://www.businessobjects.com/






Get More Help

A



Index.NET client application 14

3G 10

3G+ 10, 17

A

actions 11email 11

SMS 11

administration console 13

administration Console 10

Administration Console 17, 42

administration database 10

administration tasks 6

alerters

download icons 28

alerts 11, 17

subscribing groups 13

analytics 11Apache

configuring 38

application

client-side 14, 39

authentication server 14, 17, 30

B

barometers 11

BES 14, 20, 21, 30, 39

Blackberrydevices 39

BlackBerry

client application 27

Enterprise Server 14, 17, 20, 21, 30, 39

BlackBerry (continued)

installation package 23

server 39

BlackBerry device 10

C

Central Management Console 42

checklist

installation 20

CLDC 10

client

application 39


downloading 6

installing 6

CMC 42

connection information

preconfigure 13, 20

Crystal Reports 11, 17

D

database

mobile administration 14, 20, 32

repository 20

default document 11

default folder 11

demos 23

deployment 34

architecture 21

automating 13, 39

distributed 20, 30

scenarios 21

standalone 20




deployment (continued)

with BES 33

device errors

tracking 45

device tracking 17, 42

devices

BlackBerry 39

DMZ 20, 21, 30

configuring 30

document security 42

documents

default 11

local 11

offline 11

Web Intelligence 11drill 11

E

EDGE 10

EDGE networks 17

email 11

errors

open-tunnel failure 46

tracking 45

F

features

limitations 12

folders

default 11

G

GPRS 10

GSM 10

I

icons

for reports 23, 28

images

report templates 29

installation 27

background images 29

checklist 20

client application via OTA 13, 36, 39

client application via wire 13, 39

client device application 6

files installed 25

graphics files 23

icons 28server-side 32

validating 25

web download page 23

intranet environment 21

J

J2ME 10, 23, 39


J2ME client application 14

job server 14, 17, 20, 30

L

limitations

features 12

Linux 16

load balancing 30

local

documents 11

login

preconfigure 13, 20

logonpreconfigure 39

logs

log dump 45

reload 44


Index



M

midlet 39

MIDlet 14

download 27

MIDP 10

MIME types 38

configure 27

mobile server

errors 44

logs 44

Mobile server 17

mobile servers

starting 35

N

network unavailable 46

networks

3G+ 17

EDGE 17

supported 17

O

offlinedocuments 11

open-tunnel failure

troubleshooting 46

OTA 23, 27, 39

web download page 36

OTA delivery

for installation 13, 39

OTA web pages 37

OTALoader file 23, 27

Pplatforms 27

Linux 16

UNIX 16

platforms (continued)

Windows 16

ports

for proxy server 30

proxy server 14, 30, 33, 34

configuring 30

R

readme 23

report design

download icons 28

reports

Crystal Reports 11

display recommendations 12refresh 11

repository 14, 17, 32

S

samples 23

SDK

Crystal Enterprise 14, 17

Report Engine 14, 17

security 21

server BlackBerry 39

servers

authentication 14, 17, 21, 30

BlackBerry 14

database 17

job 14, 17, 30

Mobile 17

proxy 14, 30, 33

supported platforms 16

skins 29

smartphone 10

SMS 11speedometers 11

Symbian series-60 10

Symbian UIQ 10


Index



T

templates

background images 29

thermometers 11

Tomcat

configuring 38

tracking devices 42

troubleshooting 44, 45, 46

U

UNIX 16

user rights 42

user tracking 17, 42

W

war file

deploying 37

Web Intelligence

alerter icons 28

documents 11

tracking changes 17

Windows 16

server installation 27

Windows CE 10

Windows Mobile 10

wire delivery

for installation 13, 39

Index

xi3 mobile admin en

Documents