Business Objects Mobile – Architecture and Deployment

Hello All,
As a continuation of my previous blog, we are going to see more in detail about BO Mobile Architecture, Deployment scenarios, Server side and client side requirements in this blog.

The diagram below shows Mobile Installation on top of Business Objects Enterprise Framework

And the Business Objects Mobile Architecture will be like

Three deployment scenarios are supported for SAP Business Objects Mobile. You can choose to deploy based on your User community.

• BlackBerry devices registered on a corporate BlackBerry Enterprise Server (BES)
• Non-BlackBerry devices and/or BlackBerry devices not registered on a corporate BES. This requires a proxy server or firewall to ensure security.
• User population that includes BlackBerry devices registered on the BES and other devices. This requires a BES and a proxy server or firewall.

Based on the above deployment scenarios the common architecture of BO Mobile would be like

Server side requirements

The following components need to be deployed on top of SAP Business Objects Enterprise Installation.

• The Mobile server composed of an authentication server (VAS) and a processing server (VMS).
• A mobile database that logs the user activity and provides information on synchronization of data between the SAP Business Objects Enterprise server and the mobile devices.
• A BlackBerry Enterprise Server (BES), if you are deploying the application to BlackBerry device users (Deployment type 1).
• A proxy server, if your deployment to BlackBerry devices does not include a BES server or if your deployment includes non-BlackBerry devices (Deployment type 2 and 3).
• To deploy client application to devices through OTA provisioning, you need to install and deploy the OTA web application, delivered with SAP Business Objects mobile, on a web application server.

Client side requirements

Based on deployment scenario, SAP Business Objects mobile application can be delivered to users via

• Over-The-Air to BlackBerry devices using the push capability in the BlackBerry Enterprise Server.
• Over-The-Air (OTA) via a secured web site page. This requires you to deploy the OTA web application delivered with SAP Business Objects Mobile to a secured web application server.
• Manually on each device using the client desktop application supplied by device manufacturer.

I Hope this blog gives a good understanding on Business Objects Mobile architecture and deployment.
In our next blog we will see configuration of BO Mobile using Blackberry simulators.

Keep reading!