Page tree
Skip to end of metadata
Go to start of metadata

This BOpedia page is provided by the RIG team. Don't hesitate to put comments.
Contributor : Gregory Botticchio, RIG specialist, gregory.botticchio@sap.com

Product versions:
BOE XI3.1 and next (SP3 for instance)
BOBJ MOBILE XI3.1 and next (SP3 for instance)


Contents

Overview.


The aim of this article is to provide a test case explaining from end to end how to install, configure, and deploy the MOBILE 3.1 server/client with a BlackBerry emulator (BB server and device).
You will find in this article all the related information and materials needed to achieve this.
In this example, the BOBJ MOBILE XI3.x is deployed on the same server than the BOE XI3.x one (on Windows). Another server is hosting the Blackberry emulator.
You will also fond some general information on the MOBILE 3.1 installation and deployment.

What do we support?


For the official "SAP BOBJ MOBILE Supported Platforms" pdfs, follow this link: https://websmp201.sap-ag.de/support
Then: "Help and Support" >> "SAP BusinessObjects Support" >> "Documentation" >> "Supported Platforms/PARS" >> "SAP BusinessObjects Mobile".

  1. BOE XI3.1 and BOBJ Mobile XI3.1 are tightly linked together. It is highly recommended to always install the latest MOBILE XI3.1 release corresponding to any Enterprise XI3.1 service or fix pack.
  2. The BOBJ MOBILE XI3.x doesn't need necessary to be be on the same platform than the BOE XI3.x . It is recommended to have a dedicated platform for the MOBILE servers.
  3. The BOE XI3.x, required for the BOBJ MOBILE 3.x servers to work, can be on WINDOWS, or on UNIX: in this case, we support heterogeneous platforms.
  4. Platforms supported for the BOBJ MOBILE 3.1 Servers:
    1. Windows Server 2003 SP1 and SP2 (32 and 64 bits OS editions);
    2. Windows Server 2003 R2 (32 and 64 bits OS editions);
    3. Windows Server 2008 (32 and 64 bits OS editions);
  5. Devices supported for the BOBJ MOBILE 3.1 Client:
    1. Blackberry OS v4.1, v4.2, v4.3, v4.5 and v4.6 and from FP 2.5 onwards, also v5 (see SAP Note 1505169);
    2. NOKIA Symbian Series-60 3rd Edition;
    3. Windows Mobile v5.0 with .Net Compact Framework v2.0 or above;
    4. Windows Mobile v6.0 and v6.1

Pre-requisites and Softwares localization.


Prior to the Mobile installation:

  1. BOE XI3.0 or XI3.1 must be installed and configured;
  2. SAP Integration Kit for BOE XI3.0 or XI3.1, if it is required, must also be installed and configured;
  3. BlackBerry Email and MDS Services Emulator must be installed;
  4. Blackberry Devives Emulator must also be installed;
    You can substitute the BB emulators (3.+4.) by a Symbian one.
  5. Sun_Java Wireless ToolKit 2.5.2 must be installed.

The above BOBJ softwares required for the BOBJ Mobile installation can all be found at the following links: https://websmp205.sap-ag.de/support , then, "Downloads" >> "SAP BusinessObjects downloads"
Use the above link as the root one to find the following products.

  1. For "BOE XI3.0" or "BOE XI3.1":
    1. Go Into: https://websmp205.sap-ag.de/installations/
    2. Then: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP ENTERPRISE" >> "BOBJ ENTERPRISE XI 3.0" >> "Installation".
    3. Or: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP ENTERPRISE" >> "BOBJ ENTERPRISE XI 3.1" >> "Installation".
    4. Select your version.
  2. For "SAP JavaConnector 2.1.8":
    1. Go into: http://service.sap.com/connectors/
    2. Then: "SAP Java Connector" >> "Tools and Services" >> "Download SAP JCo Release 2.1.8"
  3. For "SAP IntegrationKit for BOE XI3.0 or XI3.1":
    1. Go Into: https://websmp205.sap-ag.de/installations/
    2. Then: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP INTGR. FOR SAP" >> "BOBJ INTGR. FOR SAP XI 3.O" >> "Installation".
    3. Or: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP INTGR. FOR SAP" >> "BOBJ INTGR. FOR SAP XI 3.1" >> "Installation".
    4. Select your version.
  4. For "BOBJ Mobile XI3.0 or XI3.1":
    1. Go Into: https://websmp205.sap-ag.de/installations/
    2. Then: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP MOBILE" >> "BOBJ MOBILE XI 3.0" >> "Installation".
    3. Or: "Installations and Upgrades - Entry by Application Group" >> "SAP BusinessObjects packages and products" >> "SBOP MOBILE" >> "BOBJ MOBILE XI 3.1" >> "Installation".
    4. Select your version.

For the BlackBerry Simulator part:

  1. For "BlackBerry Email and MDS Services Simulator Package":
    1. Go into: http://www.blackberry.com/developers/downloads/simulators/
    2. Then: click on "Download the BlackBerry email and MDS Services simulator package";
    3. Select in the drop-down list "BlackBerry Email and MDS Services Simulator Package" then NEXT;
    4. Download the "BlackBerry® Email and MDS Services Simulator Package v4.1.2 (Bundle 17)".
  2. For "BlackBerry Device Simulators":
    1. Go into: http://www.blackberry.com/developers/downloads/simulators/
    2. Then: click on "Download a device simulator";
    3. Select in the drop-down list "BlackBerry Device Simulators V5.0.0" then NEXT;
    4. Download for instance the "BlackBerry® Device Simulators v5.0.0.337 (8530)" package.

For the Symbian (NOKIA) Emulator part:

  1. For "sun_java_wireless_toolkit-2.5.2_01-win.exe":
    1. Go into: http://java.sun.com/products/sjwtoolkit/download.html
    2. Then: click on "Download";
    3. Select in the drop-down list your OS version, then CONTINUE;
    4. Click on the link "sun_java_wireless_toolkit-2.5.2_01-win.exe" to start the download.
  2. Ypou will need a JDK 1.5.0 (minimum) version to execute the Symbian emulator:
    1. Go into: http://java.sun.com/javase/downloads/index.html
    2. Find a JDK 1.5.0 minimum version.

Architecture.


Package content and Components role.

The MOBILE installation package is containing two main parts:

  1. First part: The Server components.
    Based on the architecture you want to deploy, the Mobile Server components can be installed on the BOE XI3.1 platform OR, on a dedicated server. The server components are indenpendant of the BOE XI3.1 server; and it includes:
    1. the Mobile Server : the Mobile server is installed on the corporate intranet and passes requests and answers between the BOE XI3.1 server and Mobile clients. The Mobile server contains three things :
      1. Mobile Authentication server (VAS): it manages user access and records user logs. This information can be used as source data for reports on your mobile user activity;
      2. Mobile Job server (VMS): it manages synchronization operations performed by a device with BI content published to the BOE XI3.1 server.
        Data from both servers is stored in the Mobile administration database via Java Database Connectivity (JDBC).
      3. the Mobile administration database: The Mobile Server part includes a pre-configured APACHE DERBY database you can use with the Mobile server, plus configuration files (SQL scripts) to execute for other supported DBs type. The Mobile administration database stores data on user activity and the status on synchronization between the BusinessObjects Enterprise server, the Mobile server, and the mobile devices. It contains two databases:
        • the Authentication database, which stores data from the VAS about: mobile users (ID, name, email) + the definition of mobile user groups + mobile devices information (ID, type, IP ...);
        • the Synchronization database, which stores data from the VMS about user synchronizations to the BOE server, including document versioning information for documents stored locally on the device.
    2. The Report Samples: It has to be installed or copied on the BOE XI3.1 platform itself. This part contains a BIAR file (containing some samples reports) to deploy with the "Import/Wizard" tool, the Universe for the samples reports, and the corresponding MS Access DB for the Universe.
    3. The Mobile documentation: It contains the online documentation and the pdf files for End and Administrator user.
  2. Second part: The Client components.
    When selecting this option, the setup will install the Mobile client executables (per device platform) and the OTA (OverTheAir) client download web page.
    The Client components can be installed on the same server than the Mobile server one or, on the BOE XI3.1 server or, diectly on the Web Application server.
    1. the client executables is composed of:
      • ".cod" files: containing the client application for BlackBerry devices;
      • ".sis" files: containing the client application for Symbian devices;
      • ".cab" files: containing the client application for Windows Mobile devices.
    2. the OTA client dowload web page is composed of:
      • the "MobileOTA.war" web archive file, to deploy on the Web/Application server of your choice (default one being TOMCAT). It contains a simple download web page that enables end users to download and install the Mobile client into a Mobile device via Over-The-Air (OTA) provisioning. The MobileOTA.war can be deployed into the WebApplication of your choice by using the "wdeploy" tool provided with the BOE XI3.1 server.

Before to start, things to take into consideration.

INFO: the following diagrams provide you some insight and example of what can be a Mobile deployment in true condition. But, if you intend to deploy Mobile in a Production environment, you have to consider several important things. Installing Mobile in production is not only installing a new set of BOBJ servers on a PC. It requires the coordination of different part of you BI environment :

  • BOE XI3.1 server: it must already exist and must also be accessible from the Mobile servers. You have to decide if you want to install the Server Components and/or the Client components on it or not.
  • BOBJ Mobile server: you have to decide if you're going to use a dedicated server that will host the Mobile components (recommanded) or use the BOE XI3.1 server to host those components.
  • Web Application: you may consider to use it for installing the Mobile Client components on it. This will allow you to deploy the "MobileOTA.war" file, and so to enable the "Over The Air" (OTA) capabilities. If a Web Application is already used, you may want to deploy this ".war" file on it. Or simply use the Tomcat webapp one.
  • BES/MDS server: if you plan to deploy Mobile for BlackBerry, the BES must be be reachable from the Mobile servers. You will also need the BES port number, used by the BES server for the Mobile VAS server configuration file, from the BB administrators. You may also consider the best way for your company to deploy the Mobile client on the devices: you can use the OTA capabilities, or, the native push mechanism from the BES server.
  • DataBase: You have to decide which DB to use to store the Mobile Administration DB. By default, Mobile server is working with the Apache Derby one. This one is installed and configured automatically with the Mobile Server components. But you may want to change for your corporte DB. In this case, you will need an acount from your DB administrators.
  • Proxy server and FireWall: if your deployment includes a Proxy server, you will have to define the redirection rule define on it. Mobile Server can work with a Proxy server , but not with a REVERSE PROXY SERVER.
    For the FireWall: if your deployment includes a FireWall, you have to open the ports for the VMS server, VAS server, and the WebApplication.
    The two above points are important if you intend to deloy Mobile Client on non-BlackBerry devices, or, BB devices not registered on a BES server.
    In both case, you will need help from your NetWork administrators.




Mobile deployement scenarii.

In the following diagram, the OTA client download web page is installed on the BusinessObjects Enterprise web application server. For the purposes of this diagram, the BusinessObjects Enterprise CMS and web application servers are illustrated as being on the same physical machine.

  1. BB deployment.

    This deployment scenario is recommended, if you are deploying BOBJ Mobile to BlackBerry devices registered on a corporate BlackBerry Enterprise Server (BES).
    Including a BES on your Mobile deployment provides you with close integration between BOBJ Mobile and your corporate email and address books. In addition, the push mechanism of the BES Mobile Data Service (MDS) lets you push data and IT policies to the BlackBerry devices automatically. In such a deployment, the DMZ and proxy server are not mandatory.
    Using the BES MDS push mechanism, Administrators can preconfigure the Mobile client application with the connection settings for the BusinessObjects Enterprise server (CMS) and Mobile server and then download the client application to mobile devices remotely, so that mobile users don't need to set their connection settings manually. You can include one or more BES/MDS servers on your Mobile deployment.
    After installing the BOBJ Mobile package, you have to:
    • configure the connection between the BES/MDS and the BusinessObjects Mobile servers.
  2. Non-BB deployment.

    This deployment scenario is recommended if you are not using a BlackBerry Enterprise Server (BES) as part of your BusinessObjects Mobile deployment.
    In this case, BusinessObjects recommends you to include a firewall and/or proxy server to ensure secured communication between devices and the BusinessObjects Enterprise server.
    The Mobile server is located behind the firewall or proxy server on your corporate intranet.
    After installing BOBJ Mobile, you have to configure the connection between the proxy server and the BOBJ Mobile servers. You need to open three ports for the firewall:
    • a port for the Authentication server (VAS);
    • a port for the Job server (VMS);
    • a port for the OTA web application page;
  3. Mixed deployment.

    This deployment scenario is recommended if you are deploying BOBJ Mobile to a mixed user population that includes BlackBerry devices registered on a corporate BlackBerry Enterprise Server (BES) and other devices.
    These "other devices" could be external users whose BlackBerry devices are not registered on your corporate BES and/or users using the Mobile client application on non-BlackBerry devices, such as Symbian or Windows Mobile.
    In this configuration a BES and a firewall or proxy server are necessary. The Mobile server and the BES are located behind the firewall or proxy server on your corporate intranet.
    After installing BOBJ Mobile, you need to configure the connection between the proxy server and the BusinessObjects Mobile server. You need to open three ports for the firewall:
    • a port for the Authentication server (VAS);
    • a port for the Job server (VMS);
    • a port for the OTA web application page;
    • You also need to configure the connection between the BES/MDS and the BOBJ Mobile servers.
  4. Mobile servers deployment inside the DMZ.

    This deployment scenario is recommended if you want to over secured the Mobile severs inside a DMZ, whatever the type of devices you would like to use. I t can be performed in attition of one of the three previous deployment types described above.
    In this configuration, the VAS and VMS servers are between two firewalls. You might also want to encrypt the communications between the BOBJ Mobile servers and the BOE XI3.1 platforms. By default, the communication betwen the BOBJ Mobile servers and the Mobile clients are encrypted. To do so:
    1. We need to configure the "-port" AND "-requestPort" parameters for the following servers into the BOE Central Management Console (CMC):
      • CMS (for authentication, querying info store, and browsing the repository);
      • RAS (for Crystal reports);
      • WebIReportServer;
    2. Configure the SDK listening port on the mobile server through the "-Dooc.iiop.port=xxxx" java application property ('xxxx' being between 6400 and 6420);
    3. Configure, if required, the CORBA SSL on the BOE severs and also on the BOBJ Mobile servers;
    4. Set up any DNS resolutions (if needed) on the Mobile server for the machine names stated in the "-port" parameters.
      After installing and configuring BOBJ Mobile server, you need also to configure the connection between the proxy server and/or BES, if there is one, and the BusinessObjects Mobile server. You need to open three ports on the firewall 1:
  1. #* a port for the Authentication server (VAS);
    • a port for the Job server (VMS);
    • a port for the OTA web application page.
      You need to open five ports on the firewall 2:
    • a fix port for the BOE CMS server (CMS "-requestport" value);
    • a fix port for the BOE WIreport server (WebiReportserver "-requestport" value);
    • a fix port for the BOE RAS server (RAS "-requestport" value);
    • a fix port for the SDK listener ("-Dooc.iiop.port" value);
    • a port for the OTA web application page;

Mobile/Client architecture.

The Mobile/Client architecture can be detailled as follows:

  1. Mobile "client code" details:
    1. It runs only on client;
    2. It handles user interactions by providing the UI;
    3. It renders BI content on the mobile devices;
    4. It communicates with the servers via the TRANSPORT layer;
    5. It is written in J2ME code with MIDP 2.0/CLDC 1.1;
  2. Mobile "server code" details:
    1. It runs only on server;
    2. It interfaces with BOE XI3.1 deployment, using BOBJ SDK. It communicates with CMS (for authentication, querying info store, and browsing the repository), WIReportServer (webi reports) and RAS (CR reports) via CORBA.
    3. It communicates with the client via the TRANSPORT layer;
    4. The ports used by TRANSPORT layer can be customized through the VAS/VMS "server.config" files and the "BINDTO_PORT" and "MANAGEMENT_PORT" parameters in it;
    5. It is written in standard Java 5 code;
  3. Mobile "Transport" details:
    1. It manages communication between the Mobile server and the Mobile client;
    2. It is a proprietary (no http) protocol with ENCRYPTION and DATA COMPRESSION;
    3. It manages the storage of local data on the client;
    4. Licensed from Vaultus, which provides a common interface for Blackberry, Symbian and Windows Mobile devices;
    5. This is a mixed bag of Java and platform specific native code;
  4. Mobile "Common code" details:
    1. It is shared between client and server;
    2. Document object model;
    3. Client/server message definitions;
    4. It is written in J2ME to be compatible with both client and server.

Performance, Sizing and Tuning guidelines.


The official "Performance, Sizing and Tuning" guidelines for BOBJ Mobile XI3.1 can de reached at the following link.

BOBJ Mobile server side installation.



INFO: This part supposes that you have already installed the BUSINESS OBJECTS XI3.x server. It describes what the different options proposed to you when installing the MOBILE package are. In this example, all the Mobile components (server+client) are installed on the same server: This server can be a dedicated Mobile server (it is recommanded) or the BOE XI3.1 server. In this example, we are installing all the Mobile components on the BOE XI3.1 server.



  1. Launch the Mobile v2 "Setup.exe" file.
  2. Choose your setup language: "English".
  3. Click on NEXT.
  4. Select "Accept ..." and NEXT:
  5. Fill in the requested information and NEXT:
  6. Choose the "Custom" installation type and NEXT:
    We are selecting the "Custom" option in order to check the different Mobile components that will be installed on this server. As stated before, we will install all the Mobile components on the BOE XI3.1 server. So, the "Complete" installation would have achieved the same.
  7. Select the features to install and click NEXT:
    Once again, the "Custom" installation give you access to the Mobile components list. It is usefull if you want to install the Mobile server on a dedicated server, and e-launch the installation in order to install the Mobile client (i.e. the "MobileOTA.war") on the WebApplication server.
    For a detailled list of the Mobile Components list and function, please, check the above part "Architecture" >> "Package content and Components role".
  8. Click NEXT:
  9. Installation is on its way.
  10. Click on FINISH:
  11. Click YES:

"MobileOTA.war" file deployment.



INFO: The following steps describe how to deploy the war files, installed with the Mobile package from the previous part, on the TOMCAT application server. As shown by the snapshots, the TOMCAT webapp and BOE XI3.x server are running on the same server. If you are using another web application type, you can use the "wdeploy" tool installed on the BOE XI3.x server.
By deploying the "MobileOTA.war", you will allow owner of devices to access a web page from where they will download the Mobile client through OTA provisionning. But it isn't mandatory. Moreover, not deploying the "MobileOTA.war" file won't prevent the Mobile Servers and Clients to work properly. The Mobile Client executables will be installed into the Mobile folder tree: you can choose to push them to the devices.



  1. Go into the folder: "<BusinessObjects XI folder>\BusinessObjects Enterprise 12.0\java\applications"
  2. Copy the file "MobileOTA.war" into the folder "webapps" of the TOMCAT installation: "<BusinessObjects XI folder>\Tomcat55\webapps"
  3. Wait, or re-start the TOMCAT webapp: the "MobileOTA.war" file will be deployed automatically.
  4. Verify that in the folder "<BusinessObjects XI folder>\Tomcat55\webapps" the "MobileOTA.war" file is deployed.
    One new folder should appear: "MobileOTA"
  5. Verify that the following MIME types exist into the file "web.xml" in the folder: "<BusinessObjects XI folder>\Tomcat55\conf\"
    Else, add them!
       <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>
    
       <mime-mapping>
            <extension>sis</extension>
            <mime-type>application/vnd.symbian.install</mime-type>
       </mime-mapping>
       <mime-mapping>
            <extension>sisx</extension>
            <mime-type>application/vnd.symbian.install</mime-type>
       </mime-mapping>
    
       <mime-mapping>
            <extension>cab</extension>
            <mime-type>application/vnd.ms-cab-compressed</mime-type>
       </mime-mapping>
    
  6. Verify you can access the MobileOTA URL through the web application server.
    You should see the web page to download the "MOBILE.jad" file for the Blackberry device.
    For this, use the following URL: "http://<serverName>:<port>/MobileOTA/"

BOBJ Mobile samples reports deployment.


  1. Go in to the folder: "<BusinessObjects XI folder>\Mobile 12\ReportSamples"
  2. Launch the BOBJ XI3.x Import Wizard tool.
    Select the "MOBI_Test_Report_Samples.biar" and deploy it into our BusinessObjects XI3.0 server.
  3. Launch DESIGNER XI3.x and import the universe "MOBI_Test_Universe.unv":
    1. verify that the connection "MobiTestDB" is working.
      Otherwise:
    2. launch "DATA SOURCES (ODBC)" and create into "System DSN" a new connection "MobiTestDB" pointing to the access database "<BusinessObjects XI folder>\Mobile 12\ReportSamples\MOBI_Test_DB.mdb"
    3. save and re-export the universe.

BOBJ Mobile servers configuration.


Modify the server.config file and add new parameters.

  1. Modify the "server.config" files on your Mobile server: it is necessary, even if you are upgrading from BOBJ Mobile XI3.0 to BOBJ Mobile XI3.1 or latest FixPack or ServicePack.
    • Verify the Mobile servers are stopped:
      If you launched them with the DOS command, you simply have to quit those DOS command.
      If they have been defined as "Services", you will have to stop them with the Windows Services dialog box.
    • Open the "<BusinessObjects XI3.1 folder>\Mobile12\server\VAS\config\server.config" file and the "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\config\server.config" file for edit.
    • Remove the following string from both files:
       EXTERNAL_HOSTNAME=MyServer
      
    • Replace manually the content of the "VAS/server.config" and "VMS/server.config" files, so that they look like the following:

      VAS/server.config

      VMS/server.config


      VERSION = 6.0
      
      [server]
      SERVER_ID=AUTH_SERVER
      
      [comm]
      BINDTO_PORT=VAS_OR_VMS_PORT_TO_CONNECT_TO
      MANAGEMENT_PORT=VAS_OR_VMS_MANAGEMENT_PORT
      
      [comm $ external]
      ENABLED=default mds
      
      [comm $ external $ default]
      EXTERNAL_HOSTNAME=My_Mobile_Server_External_Name
      EXTERNAL_PORT=My_Server_Port
      CLIENT_TYPE=any
      CLIENT_HOSTNAME=0.0.0.0
      
      [comm $ external $ mds]
      CLIENT_TYPE=mds
      EXTERNAL_HOSTNAME=My_Mobile_Server_External_Name
      
      # common across all auth servers
      INCLUDE_CONFIG_FILe = config/cluster.config
      


      VERSION = 6.0
      
      [server]
      SERVER_ID=AUTH_SERVER
      
      [comm]
      BINDTO_PORT=VAS_OR_VMS_PORT_TO_CONNECT_TO
      MANAGEMENT_PORT=VAS_OR_VMS_MANAGEMENT_PORT
      
      [comm $ external]
      ENABLED=default mds
      
      [comm $ external $ default]
      EXTERNAL_HOSTNAME=My_Mobile_Server_External_Name
      EXTERNAL_PORT=My_Server_Port
      CLIENT_TYPE=any
      CLIENT_HOSTNAME=0.0.0.0
      
      [comm $ external $ mds]
      CLIENT_TYPE=mds
      EXTERNAL_HOSTNAME=My_Mobile_Server_External_Name
      
      # common across all auth servers
      INCLUDE_CONFIG_FILe = config/cluster.config
      
    • Save and close both "server.config" files.
  2. Definition of the added parameters:
    • BINDTO_PORT: it is the port on which the service runs (true for both VAS and VMS). The port to use can be define here: by default, the VAS is running on port 11011, the VMS on 17011. But, once again, you can define here which port the VAS/VMS must be running on.
      It is sufficient to specify only the auth service (VAS) in the Mobile Client configuration settings. Once successfully authenticated, the application communicates to the VMS automatically.
    • MANAGEMENT_PORT: it is the management port use by administrators. The port to use is defined here. By default, management port for VAS is 11012, and VMS one is 17012.
      Administrators can log in and do certain operations such as restarting services, initiate logging, see users connected etc, but not very efficiently usable as of now.
    • ENABLED: this parameter decides the deployment type you are using. Based on this parameter values, the system will look for details under respective section of the configuration file as explained in below 3 rows:
      • "ENABLED=default" will pick the configurations under the section [comm $ external $ default]
      • "ENABLED=mds" will pick the configurations under the section [comm $ external $ mds]
      • "ENABLED=default mds" will pick the configurations under the sections [comm $ external $ default] AND [comm $ external $ mds]:
    • EXTERNAL_HOSTNAME: when you have firewall implementation -> This should be the firewall address or the Proxy server one (based on your deployment). Else, it would be the Mobile servers address ().
    • EXTERNAL_PORT: When you have firewall implementation, this will be corresponding to the firewall port or the Proxy server one before the redirection (based on your deployment). Else, it would be VAS and/or VMS port on Mobile servers (ie. 11011 and 17011).
    • CLIENT_TYPE: Value of this parameter would be always:
      • "any" : under the section [comm $ external $ default]
      • "mds" : under the section [comm $ external $ mds]
    • CLIENT_HOSTNAME: can be ignored.

      NOTE: from now, this article assumes that the correctly structured configuration files exist on your Mobile server. You can now proceed to enter the correct parameter values as specified in this documentation. in the following part, the values used for the true deployment are based on the deployment scenari from previous part.

Configuration for a BlackBerry deployment.

  1. Configure the VAS "server.config" file.
    Edit the "<BusinessObjects XI3.1 folder>\Mobile12\server\VAS\config\server.config" file and modify accordingly:

    for a Corporate BES

    for a BES emulator


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=mds
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-Server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=mds
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-Server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  2. Configure the VMS "server.config" file.
    "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\config\server.config" file and modify accordingly:

    for a Corporate BES

    for a BES emulator


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=mds
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-Server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=mds
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-Server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  3. Modify the VAS "cluster.config file.
    Edit the "<BusinessObjects XI3.1 folder>\Mobile 12\server\VAS\config\cluster.config" in order to set the connection between the Mobile server and the BES as follows:
    • For a deployment with a single BES/MDS:
      [comm]
      
      [comm $ mds]
      HOST_PORT=MyCorporateBES:BES_Port_Number
           (For example: HOST_PORT=corporate-bes:8080 OR HOST_PORT=emulator-bes:8080)
      
    • For a deployment with multiple BES/MDS (use a space as the separator):
      [comm]
      
      [comm $ mds]
      HOST_PORT=<BEShostname1>:<BES_port1> <BEShostname2>:<BES_port2> <BEShostname3>:<BES_port3>
           (For example: HOST_PORT=corporate-bes1:8080 corporatebes2:8081 corporate-bes3:8082)
      
  4. Save and close the above three modified files.
  5. Re-start the Mobile server (start the Authentication server (VAS) first, and then start the Job server (VMS)).

Pre-configuration for a BlackBerry deployment with connection settings details.

You can configure the mobile client application with connection settings details before deploying the client on the device.
This is supported only for BlackBerry devices with OS >= 4.3.0, and for SYMBIAN S60 operating system. And it works starting BOBJ MOBILE XI3.1 SP3.
To pre-configure your mobile client application with connection settings details, perform the following steps:

  1. Deploy the “MobileOTA.war” file on the web application server, if it is not already done (i.e: if it is already done, you will find a folder "MobileOTA" in the tomcat's "webapp" directory);
  2. Locate the “blackberry/MobileXI3BB.jad” (or "symbian/MobileBISymbianS60.jad") file where “MobileOTA.war” is deployed (i.e: in the Tomcat's "webapp" directory);
  3. Open the “MobileXI3BB.jad” (or "MobileBISymbianS60.jad") file with the text editor, append the following lines by replacing <...> with correct values, and save it. You can exclude the values that are not required:
    BOBJ_MOBILE_AUTH_SERVER:<mobile server>
    BOBJ_MOBILE_AUTH_PORT:<Port of VAS Service, for example, 11011>
    BOBJ_MOBILE_CMS:<cms address, for example CMSCOLPAL:6400>
    BOBJ_MOBILE_AUTH_METHOD:<authentication type> where <authentication type> could be any one of these values based on your requirements: secEnterprise, secWinAD, secLDAP, secSAPR3.
    Note: Ensure that you delete the web application server cache to remove the instance of MobileXI3BB.jad cached by the server if you previously accessed the "MobileOTA" web page. To do so: you can delete the entire "MobileOTA" folder in the Tomcat's "working" directory.
  4. Re-start the web application server (not mandatory);
  5. Download the mobile client onto your mobile device: You will notice that the connection settings details such as Mobile server, VAS port number, CMS name, and the Authentication type are populated;
  6. Enter your “UserName/Password” and check one of following option:
    1. “Save password” : You are logged into BusinesssObjects Mobile automatically. This saves you time when you want to consult data quickly without spending time on the login procedure. Your connection to your live data on the server is automatic which can pose a security threat if your device is lost or stolen.
    2. “Auto-Connect” : If you want to start BusinessObjects Mobile automatically each time you switch on the device. If you select this option, the “Save password” option is automatically selected and the “Work offline” option is disabled. Both options are hidden until you deselect Auto-connect.
  7. You have also the possibility to push for a default UserName and Password, in the same way than with the above connections settings.
    To do this, Open the “MobileXI3BB.jad” (or "MobileBISymbianS60.jad") file with the text editor, append the following lines by replacing <...> with correct values, and save it:
    BOBJ_MOBILE_USER_NAME:<UserName>
    BOBJ_MOBILE_USER_PASSWORD:<Password>
    Note: the <Password> is not encrypted into the "*.jad" file.

Configuration for a Non-BlackBerry deployment.

  1. Configure the VAS "server.config" file.
    Edit the "<BusinessObjects XI3.1 folder>\Mobile12\server\VAS\config\server.config" file and modify accordingly:

    for a Corporate deployment

    for a deployment with Symbian emulator
    without Proxy/Firewall


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=default
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile.corporate.com
    EXTERNAL_PORT=11000
    CLIENT_TYPE=any
    CLIENT_HOSTNAME=0.0.0.0
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=default
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile-Server
    #EXTERNAL_PORT=My_VAS_External_Port
    CLIENT_TYPE=any
    #CLIENT_HOSTNAME=0.0.0.0
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  2. Configure the VMS "server.config" file.
    "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\config\server.config" file and modify accordingly:

    for a Corporate deployment

    for a deployment with Symbian emulator
    without Proxy/Firewall


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=default
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile.corporate.com
    EXTERNAL_PORT=11700
    CLIENT_TYPE=any
    CLIENT_HOSTNAME=0.0.0.0
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=default
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile-server
    #EXTERNAL_PORT=My_VMS_External_Port
    CLIENT_TYPE=any
    #CLIENT_HOSTNAME=0.0.0.0
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  3. Save and close the above two modified files.
  4. Re-start the Mobile server (start the Authentication server (VAS) first, and then start the Job server (VMS)).

Configuration for a Mixed deployment.

  1. Configure the VAS "server.config" file.
    Edit the "<BusinessObjects XI3.1 folder>\Mobile12\server\VAS\config\server.config" file and modify accordingly:

    for a Corporate deployment

    for a deployment with Symbian and BES emulator
    without Proxy/Firewall


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=default mds
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile.corporate.com
    EXTERNAL_PORT=11000
    CLIENT_TYPE=any
    CLIENT_HOSTNAME=0.0.0.0
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=11011
    MANAGEMENT_PORT=11012
    
    [comm $ external]
    ENABLED=default mds
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile-server
    #EXTERNAL_PORT=My_Server_Port
    CLIENT_TYPE=any
    #CLIENT_HOSTNAME=0.0.0.0
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  2. Configure the VMS "server.config" file.
    "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\config\server.config" file and modify accordingly:

    for a Corporate deployment

    for a deployment with Symbian and BES emulator
    without Proxy/Firewall


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=default mds
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile.corporate.com
    EXTERNAL_PORT=11700
    CLIENT_TYPE=any
    CLIENT_HOSTNAME=0.0.0.0
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    


    VERSION = 6.0
    
    [server]
    SERVER_ID=AUTH_SERVER
    
    [comm]
    BINDTO_PORT=17011
    MANAGEMENT_PORT=17012
    
    [comm $ external]
    ENABLED=default mds
    
    [comm $ external $ default]
    EXTERNAL_HOSTNAME=Mobile-server
    #EXTERNAL_PORT=My_Server_Port
    CLIENT_TYPE=any
    #CLIENT_HOSTNAME=0.0.0.0
    
    [comm $ external $ mds]
    CLIENT_TYPE=mds
    EXTERNAL_HOSTNAME=Mobile-server
    
    # common across all auth servers
    INCLUDE_CONFIG_FILe = config/cluster.config
    
  3. Modify the VAS "cluster.config file.
    Edit the "<BusinessObjects XI3.1 folder>\Mobile 12\server\VAS\config\cluster.config" in order to set the connection between the Mobile server and the BES as follows:
    • For a deployment with a single BES/MDS:
      [comm]
      
      [comm $ mds]
      HOST_PORT=MyCorporateBES:BES_Port_Number
           (For example: HOST_PORT=corporate-bes:8080 OR HOST_PORT=emulator-bes:8080)
      
    • For a deployment with multiple BES/MDS (use a space as the separator):
      [comm]
      
      [comm $ mds]
      HOST_PORT=<BEShostname1>:<BES_port1> <BEShostname2>:<BES_port2> <BEShostname3>:<BES_port3>
           (For example: HOST_PORT=corporate-bes1:8080 corporatebes2:8081 corporate-bes3:8082)
      
  4. Save and close the above three modified files.
  5. Re-start the Mobile server (start the Authentication server (VAS) first, and then start the Job server (VMS)).

Configuration for a deployment inside a DMZ.

  1. Configure the "-requestPort" and "-port" parameters for the following servers into the Central Management Console (CMC):
    • CMS (for authentication, querying info store, and browsing the repository);
    • RAS (for Crystal reports);
    • WebIReportServer.
      For a detailled explanation on how to perform this, please, check the pages 166, 310 from the "BOE XI3.1 Administration Guide" here.
  2. Configure the SDK listening port on the mobile server through the "-Dooc.iiop.port=xxxx" java application property:
    The "-Dooc.iiop.port=xxxx" parameter needs to be added to the end of "VT_JVM_ARGS" line of the two following script files. It the VAS and VMS start scripts:
    • "<BusinessObjects XI3.1 folder>\Mobile 12\server\VAS\bin\vtauthd.bat"
    • "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\bin\vtvmsd.bat"
      The value of xxxx could be any value (within 6400 to 6420) as long as there is no listening port by that number on that machine (no conflicts with existing ports).
      This port should also be opened up on the firewall.
  3. Open these ports on the firewall that separates the Mobile server and the BOE server.
  4. Set up any DNS resolutions (if needed) on the Mobile server for the machine names stated in the "-port" parameters in #1.

Configuration for a CORBA SLL enabled CMS.

  1. Enable the CORBA SSL on the BOE XI3.1 server:
    To do so, check the pages 206 to 211 of the "BOE XI3.1 Administration Guide" here.
    We don't need to enable SSL on the WebApplication server.
  2. Enable CORBA SSL for the VAS and VMS servers.
    Make the following entry into the two following start scripts:
    • "<BusinessObjects XI3.1 folder>\Mobile 12\server\VAS\bin\vtauthd.bat"
    • "<BusinessObjects XI3.1 folder>\Mobile 12\server\VMSServer\bin\vtvmsd.bat"
      set VT_JVM_ARGS=%VT_JVM_ARGS%
      -Dbusinessobjects.orb.oci.protocol=ssl
      -DcertDir=[directory where SSL certificates are located]
      -DtrustedCert=cacert.der
      -DsslCert=servercert.der
      -DsslKey=server.key
      -Dpassphrase=[the pass phrase used for certificate generation]
      

BOBJ Mobile Administration Database setup.


  1. By default, MOBILE V2 is installed with a pre-configured database: APACHE DERBY.
    This DB is up and running once the installation is done: no configuration to perform. You can use it directly with your MOBILE server.
  2. You can change the default DB.
    For this, you will have to:
    1. create a DB and a DB admin user.
    2. use the appropriate SQL configuration scripts in the database of your choice. The configuration scripts delivered with the mobile setup are located at:"<BusinessObjects XI folder>\Mobile 12\preinstall\vmsserver"
    3. from the START menu, launch the "PASSWORD SCRAMBLER" from the BusinessObjects folders
      1. type the db admin user and password
      2. click OK
    4. this generate an encrypted password to use into the MOBILE VAS and VMS configuration files.
    5. copy this encrypted password.
    6. open and edit the "cluster.config" for the VAS and VMS servers in the folders:
      1. "<BusinessObjects XI3.x folder>\Mobile 12\server\VAS\config"
      2. "<BusinessObjects XI3.x folder>\Mobile 12\server\VMSServer\config"
    7. update the following parameters: URL; DB_DRIVER; LOGIN (db admin user); PASSWORD (encrypted password).

Start the BOBJ Mobile servers.


INFO: This part supposed that you have already installed the MDS and Blackberry device emulator, or the Symbien emulator, on a second server, different than the current server where is installed BOBJ XI3.x and MOBILE V2.

  1. Before to start the VAS and VMS servers, make sure the MDS emulator is running on the second server.
    In the case you're using a Symbian emulator, ignore this point.
    You can launch the VAS and VMS servers from "Start >> All Programs >> BusinessObjects XI 3.1 >> BusinessObjects Mobile": "Launch Mobile VAS/VMS".
    Or perform the following:
  2. Launch a DOS command session and go into the folder: "<BusinessObjects XI3.x folder>\Mobile 12\server\VAS\bin"
  3. Start the VAS server with the following command: "vtauthd.bat start2"

    Wait the VAS server to be up and running.
  4. Launch a DOS command session and go into the folder: "<BusinessObjects XI folder>\Mobile 12\server\VMSServer\bin"
  5. Start the VMS server with the following command: "vtvmsd.bat start2""

    Wait the VMS server to be up and running.

    THE MOBILE V2 SERVER IS UP and RUNNING NOW !

BOBJ Mobile client installation and configuration with the BlackBerry emulator.


INFO: All the following actions are done on a second server where is installed the MDS and Blackberry device simulator.

  1. Launch a BB device simulator.
  2. Select the BB browser and launch it.
  3. Use the following URL which points to the "MOBILE OTA Loader" web page: "http://<serverName>:<port>/MobileOTA/"
  4. Get the MOBILE OTA Loader web page and select "Mobile for Blackberry": Get the link !
  5. Download the BUSINESS OBJECTS MOBILE v12.0.0.
  6. Click on YES to validate the download and installation.
  7. Select OK to finish the installation.
    Leave the BB browser.
  8. Select the "BusnessObjects Mobile" on the BB desktop and launch it.

  9. Get the login page. Edit the "Connection Settings"
  10. Fill in the requested information:
    1. Mobile server;
    2. Mobile server PORT number;
    3. CMS Name and CMS PORT number (i.e.: CMSNAME:CMSPORT);
    4. And SAVE those settings.
  11. Enter your credentials and login.
  12. You get the folders. Success!!!

BOBJ Mobile client installation and configuration with the Symbian emulator.


INFO: All the following actions are done on a second server where is installed the Symbian emulator.

  1. Once the WTK Emulator is installed, copy the ".jad" + ".jar" files into the same folder;
  2. Execute "Run MiDP Application" from the "Sun Java (TM) Wireless Toolkit 2.5.2_01" menu;
    A dialog box will pop up.
  3. Select the "MobileBISymbianS60.jad" file and click on OK: By default, a Symbian device will appear.
  4. Launch the Mobile installation by selecting "Launch":

  5. Select the "Menu" item and then "Connections Settings":
  6. Enter the CMS credentials and properties for the BOBJ Mobile, and then "Save"
  7. Enter your BOBJ credentials:
  8. Select the "Menu" item and then "Login":
  9. Get "is it ok to use the network?", select "Yes":
  10. Get your default folders:

Report creation for Mobile client, tips and tricks.


INFO: this part will give some general guidance on how to create reports that fit for the Mobile client on devices.

There are real limits to the size and complexity of reports that you can display on a small mobile device, due to the small screen size, limited memory, and interaction capabilities of mobile devices. Documents intended for mobile consumption must be designed according to best practice design guidelines for mobile devices.
On overview of the result tis available here.
You can also use the report samples added on the Mobile Demo website here.

  1. Do not use existing report, create reports adapted to the device screen.
  2. Use the Java Report Panel (JRP) for maximum formatting accuracy and control.
  3. Create and use mobile device design templates:
    They are provided with the installer package. You can import them into the JavaReport panel when creating a report in order that, what you design into the JRP is what you gt onto the device.
  4. Create small report:
    Short reports usually work better in mobile situations, because mobile devices are limited in bandwidth and memory, and large reports are difficult to navigate in a small screen.
    Limit the size of the report to 300 to 500 ko: It is a good average.
  5. Use a mobile device simulator to test your documents.
  6. Publish documents in a "Mobile" folder to ease the access to content being dedicated for the Mobile client.
  7. Make Tables and Graphs fit into the smallest device screen size.
    When you cannot reduce the size of tables and graphs:
    • Design columns and labels to fit the screen of the target mobile devices;
    • Make the Tables of the report scrollable only on one axis at a time ((xx'): horizontal scrolling. Or (yy'): vertical scrolling)
    • Do not design reports larger than two or three screen widths of the device screen;
    • Do not design reports larger than two or three screen heights of the device screen;
    • For 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/height of the mobile screen (or such that at least a fixed number of columns/rows exactly fit the screen width/height).
  8. Use shortest significant names for headers and names.
    • Use codes instead of names for countries and cities;
    • Use the short name for people (made up of their first name initials + their last name) instead of full names;
    • Use short labels for dates: 'FY04' instead of 'Year 2004', 'Q104' instead of 'first Quarter 2004';
  9. 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 WebIntelligence Custom format to reduce the number of digits displayed; this is to reduce column size.
  10. 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.
    Font mapping on BusinessObjects Mobile uses the following fonts:
    • 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;
  11. Plan for drillable headers.
    Leave blank cell space for drill icons that BusinessObjects Mobile places on drillable headers.
  12. Use 'OpenDocument()' API to link reports.
    BOBJ Mobile Client supports OpenDocument links in WebIntelligence reports, but not in Crystal reports.
    Moreover, BOBJ Mobile Client supports a subset of the WebIntelligence 'OpenDocument()' syntax: sPath, iDocId, sDocName, sReportName, sRefresh, lsS, lsM.
    Please, check the following 'OpenDocument() Devlibrary Guide' Here for details regarding the creation of OpenDocument syntax.

Troubleshooting information.


INFO: this part will only describe how to activate the BOBJ Mobile servers traces. Very usefull in order to track activities between the VAS, VMS and client.

  1. VAS and VMS trace: the VAS and VMS traces are activating from a common . It is the "share.config" file under the folder "<BusinessObjects XI3.1 folder>\Mobile 12\server\common\config\".
    You have to set all the "LEVEL =" entries with "ERROR": i.e. "LEVEL = ERROR".
    All the errors will then be added into respective VMS and VAS log files under "<BusinessObjects XI folder>\Mobile 12\server\VMSServer\logs\" and "<BusinessObjects XI folder>\Mobile 12\server\VAS\logs\".
  2. Tracking device errors.
    In addition to BusinessObjects Enterprise errors and Mobile server errors that can be displayed on the device, the device displays and logs the following Mobile client 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 ALT+L ALT+G ALT+L ALT+G from the home screen to see the BB device logs.
  3. Mobile client trace:
    There is no trace available for the Mobile client. But, to help to troubleshoot the behavior, you can indicate us any Warning or Error message get on the Mobile client on the devices, when running a Mobile client workflow.

Upgrade procedure.


  1. From Mobile XI3.0 to Mobile XI3.1.
  2. From Mobile XI3.1 to Mobile XI3.1 FP 1.x.
  3. From Mobile XI3.1 to Mobile XI3.1 SP2.
  4. From Mobile XI3.1 SP2 to Mobile XI3.1 SP2 FP2.x.

References and links


https://cw.sdn.sap.com/cw/docs/DOC-123008}SBO Mobile XI - Basics and Best Practices