OX6:OX Mobile Web Interface: Difference between revisions

From Open-Xchange
No edit summary
 
(67 intermediate revisions by 5 users not shown)
Line 1: Line 1:
= Information and Installation of Open-Xchange Mobile Web App =
= Information and Installation of Open-Xchange Mobile Web Interface (Only for OX 6) =
 
== Notice ==
This description is updated for version 1.1 of the Mobile Web App (Mobile Web Interface). If you are looking for the manual of version 1.0, visit this site
[Old manual [http://oxpedia.org/wiki/index.php?title=OX_Mobile_Web_App&oldid=10092]]


== Description ==
== Description ==
The Open-Xchange Mobile Web App provides you access to your data from the Open-Xchange Server 6 via your smartphone. The Open-Xchange Mobile Web App offers online and offline access to appointments, contacts and mails on the road using your smartphone's browser. Optimized for low bandwiths the Open-Xchange Mobile Web App offers instant and fast over the air access to your data, which are at the same time safely stored on Open-Xchange Server. The following modules are supported:
The Open-Xchange Mobile Web Interface provides you access to your data from the Open-Xchange Server 6 via your smartphone. The Open-Xchange Mobile Web Interface offers online and offline access to appointments, contacts and mails on the road using your smartphone's browser. Optimized for low bandwiths the Open-Xchange Mobile Web Interface offers instant and fast over the air access to your data, which are at the same time safely stored on Open-Xchange Server. The following modules are supported:


*E-Mail
*E-Mail
Line 12: Line 8:
*Contacts
*Contacts


Moreover the app offers seamless integration to use your phones basic functions like phone calls. You can easily start calls from your Open-Xchange contacts on your smartphone or directly send E-Mails.
Moreover the web interface offers seamless integration to use your phones basic functions like phone calls. You can easily start calls from your Open-Xchange contacts on your smartphone or directly send E-Mails.
 
== Features and Functions ==
 
=== Mail Module ===
*Access to all Open-Xchange private mail folders
*Creation of new e-mails
*Answer, forward and delete e-mails
*Move mails (since 1.1)
*Mail attachments (Attachment handling/support is defined by mobile device)
 
=== Contact Module ===
*Access to all Open-Xchange contact folders and contacts with details
*Creation of e-mails directly from contact module
*Start calls directly from contact module
* Google Maps ® v. 3 integration for addresses (since 1.1)
 
=== Calendar Module ===
* Access to all Open-Xchange calendar folders and appointments with details
* Accept/Decline appointments
* View participants, resources and notes each appointment
 
=== Persistence of the Mobile Web App ===
*Offline capability
*All contacts are available offline
*All appointments are available offline
*All mail header are available offline
*All mails which are opened once are available offline


===Configuration===
*Timeframe which will be checked for appointments (1 Week, 2 Weeks, 1 Month, 2 Months)
*Subscription of contact folders
*Subscription of mail folders


===Themeability, branding and i18n ===
===Themeability, branding and i18n ===


* i18n for DE, EN, ES, FR, NL and PL, other languages can be added.
* i18n for DE, EN, ES, FR, NL, PL and JP. Other languages can be added.
* Themeability by CSS
* Themeability by CSS
* JavaScript plugins for branding
* JavaScript plugins for branding and custom functions.
 


== Supported devices ==
== Supported devices ==


The OX Mobile Web App runs on devices with a Webkit-based browser. These are mainly devices running iOS, Android and newest generation of BlackBerrys. For devices running Symbian we recommend using Opera Mobile Browser.
The Open-Xchange Mobile Web Interface is designed to run on modern devices running Android or iOS. It can also used with modern desktop browsers.


{|border="2" rules="all" align="left">
{|border="2" rules="all" align="left">
Line 62: Line 28:
   | 
   | 
|-
|-
   |Apple iPhone
   |Apple iOS
   |yes (iPhone running iOS 2.0, 2.1, 3.0, 4.0, 4.2.1, 4.3)
   |iOS 3 - 5.1
   |Official Supported by OX: 2G, 3G, 3GS, 4, 4s and iPod-Touch 3.1.3
   |
  |-
  |-
   |Android
   |Android
   |yes
   |yes, Android 2.2 - 4.0
   |Official Supported by OX: Google Nexus One (Android 2.3.3), Samsung Galaxy Nexus (Android 4.0.3). The app is optimized for a display size of 320 x 480 pixels  
   |Official Supported by OX: Google Nexus One (Android 2.3.3), Samsung Galaxy Nexus (Android 4.0.3). The web interface is optimized for a display size of 320 x 480 pixels. Smaller resolutions may result displaying issues of some UI elements
|-
  |Other devices
  |via Opera Mobile 11.x
  |Opera Mobile also works with the Mobile Web App. The app is optimized for a display size of 320 x 480 pixels
|-
  |Windows Mobile 6.5 running Internet Explorer
  |no, not planed
  |
|-
|Windows Phone 7
|not yet, scheduled for version 1.2
|
|-
|-
|}
|}


== Technical overview ==
== Technical overview ==
* Based on HTML5, CSS, Javascript (Framework jQuery Mobile)
* Based on HTML5, CSS, Javascript (jQuery Mobile)
* Optimized for Webkit browsers like Mobile Safari and Chrome. Will also work with restrictions on Firefox and Opera Mobile
* Optimized for Webkit browsers like Mobile Safari and Chrome. Will also work with restrictions on Firefox and Opera Mobile
* Complete offline capability
* Complete offline capability
'''Updates with version 1.1.0 rev 8'''
* True fixed toolbars:
Version 1.1.0 rev 6 of the Mobile Web Interface used dynamic recalcualtion to re-position footer and header bars on the fly after scrolling the document. The new version of jQuery Mobile (1.1) now uses CSS based positioning which is truly native on supported platforms.
Some platforms like iOS 4 will now fall back to static positioning where the toolbars simply scroll with the page.
Platforms which support fixed toolbars:
* iOS5 – iPhone and iPad
* Android 2.2 and 2.3
* Android 3.x tablets (Honeycomb)
* Android 4.x (ICS)
* Chrome for Android (beta)
* BB Playbook 1-2
* All modern desktop browsers (IE, Firefox, Safari, Chrome, etc.)


===Offline Mode details===
===Offline Mode details===


The OX Mobile Web App uses HTML5 to provide an offline mode for the user. To do this, there are two different kinds of storage mechanisms.
The Open-Xchange Mobile Web Interface uses HTML5 to provide an offline mode for the user. To do this, there are two different kinds of storage mechanisms.


* The whole application will be cached using the "HTML5 application cache". This will be done on the first visit/start of the app. After this initial download, all graphics, language files, js-files and everything else which is needed to run the app is stored locally on your phone in a storage managed by the browser.
* The whole web interface uses caching by incorporating the "HTML5 application cache". This will be done on the first visit/start of the web interface. After this initial download, all graphics, language files, js-files and everything else which is needed to run the web interface is stored locally on your phone in a storage managed by the browser.


* The data from the OX server will be stored using the HTML5 storage mechanism which will be supportet by the users device. These can be a HTML5 local storage, session storage or an SQLite database. For the user there's no difference between these different storage modes.
* The data from the OX server will be stored using the HTML5 storage mechanism which will be supportet by the users device. These can be a HTML5 local storage, session storage or an SQLite database. For the user there's no difference between these different storage modes.


Note: In case your device has no storage support (like the Nokia N97), a log message will inform you about this. The log can be found under the settings page.


== Requirements ==
== Requirements ==
Line 103: Line 75:
* Open-Xchange Server >= v.6.20 rev 21
* Open-Xchange Server >= v.6.20 rev 21


{{InstallPlugin|pluginname=open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default open-xchange-gui-mobile-v2|sopath=OXtender-stable/MobileApp|ldbaccount=LDBACCOUNT:LDBPASSWD|reponame=mobilewebapp}}
== Installation on Open-Xchange v6.22.x ==
 
=== Debian GNU/Linux 6.0 ===
 
Add the following entry to /etc/apt/sources.list if not already present:
 
deb http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/DebianSqueeze/ /
 
and run
 
$ apt-get update
$ apt-get install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config
 
=== SUSE Linux Enterprise Server 11===
 
Add the package repository using zypper if not already present:
 
$ zypper ar http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/SLES11 MobileWebInterface
 
and run
 
$ zypper ref
$ zypper in open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config
 
=== RedHat Enterprise Linux 6 ===
 
Start a console and create a software repository file if not already present:
 
$ vim /etc/yum.repos.d/MobileWebInterface.repo
 
[MobileWebInterface]
name=Open-Xchange
baseurl=http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
and run
 
$ yum update
$ yum install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config
 
=== CentOS 6===
 
Start a console and create a software repository file if not already present:
 
$ vim /etc/yum.repos.d/MobileWebInterface.repo
 
[MobileWebInterface]
name=Open-Xchange
baseurl=http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m
 
and run
 
$ yum update
$ yum install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config
 
== Optional link to Mobile Web Interface in OX6 login mask (since 6.20.3) ==
There is an optional plugin available which adds a link to the Mobile Web Interface to the common OX6 login screen.
 
=== Debian ===
$ apt-get install open-xchange-gui-mobile-redirect-plugin
 
 
=== SUSE Linux Enterprise Server ===
$ zypper install open-xchange-gui-mobile-redirect-plugin
 
 
=== RedHat Enterprise Linux ===
$ yum install open-xchange-gui-mobile-redirect-plugin
 
 
The plugin needs to be configured in ${DOCROOT}/ox6/plugins/com.openexchange.mobile.redirect/config/config.js
 
data = {
    url: "https://m.example.com//",
    isEnabled: function() {
        return true;
        //----- example to add a device check instead of always returning true -----//
        // return (/iphone|ipod|android|/i.test(navigator.userAgent.toLowerCase()));
    },
    getText: function() {
        return _("Switch to mobile version");
    }
};
 
 
 
 
 
== Upgrading from previous versions ==
If you have the previous version of the Mobile Web Interface installed (1.0), you can not upgrade to version 1.1 or later directly. Due to a package rename you have to remove the old packages before installing the new ones. The packages for version 1.0 are prefixed with "open-xchange-gui-mobile-v2", the new ones are prefixed with "open-xchange-mobile*".
 
 
=== Debian ===
$ apt-get purge open-xchange-gui-mobile-v2
$ apt-get purge open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default
 
 
=== SUSE Linux Enterprise Server ===
$ zypper remove open-xchange-gui-mobile-v2
$ zypper remove open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default
 
 
=== RedHat Enterprise Linux ===
$ yum remove open-xchange-gui-mobile-v2
$ yum remove open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default
 
Please note, the package open-xchange-gui-mobile-v2 is located on your ox backend system, open-xchange-gui-mobile-v2-gui and open-xchange-gui-mobile-v2-theme-default are installed on your webserver machine. If both systems are the same you have to remove all packes on the same system.
 
After removing the old packages proceed with the installation of the new version 1.1 or later


{{UpdatePackage}}
== Installation on OX App Suite ==
The download and installation information for Open-Xchange App Suite product family (Open-Xchange Server Edition and Hosting Edition) is available at: http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mobile_Web_Interface


== Configuration ==
NOTE: This paragraph describes installation for version 1.0


Installation on the Apache or another webserver:
= Configuration =
* After installation locate the installed files in your webroot directory, i.e. <code>/var/www/ox6-mobile-v2/</code> on Debian
Installation on the Apache 2 webserver:
* Edit the file <code>"ox-access.conf"</code> in directory ox6-mobile-v2
 
* Change localhost to the address the mobile app will be reachable followed by "/ajax", i.e. "<code>https://m.example.com/ajax</code>". '''Note''': We strongly recommend the usage of https, otherwise data will be transmitted unencrypted via client and server
'''Important note for upgraders:'''
* The Mobile App acts like a second UI next to the normal web frontend.
In previous versions (lower 1.1) a server address had to be entered in the cache.manifest file to grant access to the OX6 backend. This not needed anymore. The new version of the mobile web grants per default access to all uncached ressources. Don't edit the cache.manifest manually.
* run the command (adopt webserver path on SLES/RHEL).
 
$ /opt/open-xchange/sbin/update-cache.manifest /var/www/ox6-mobile-v2/cache.manifest.in /var/www/ox6-mobile-v2/cache.manifest /var/www/ox6-mobile-v2/ox-access.conf
* You need to add a new mimetype to your webserver configuration to make sure the caching (offline mode) works.  
* You also need to add a new mimetype to your webserver configuration to make sure the caching (offline mode) works.  
** On Apache servers you can add the mimetype either global or via "<code>.htaccess</code>" file.
** On Apache servers you can add the mimetype either global or via "<code>.htaccess</code>" file.
** For global configuration edit the file <code>mime.conf</code> under  <code>/etc/apache2/mods-enabled/</code>
** For global configuration edit the file <code>mime.conf</code> under  <code>/etc/apache2/mods-enabled/</code>
Line 126: Line 211:


  <VirtualHost *:80>
  <VirtualHost *:80>
   ServerAdmin webmaster@localhost
    ServerAdmin webmaster@localhost
   ServerName mobile.YOUR_DOMAINAME.TLD
    ServerName mobile.YOUR_DOMAINAME.TLD
   ServerAlias m.YOUR_DOMAINAME.TLD
    ServerAlias m.YOUR_DOMAINAME.TLD
   DocumentRoot /var/www/ox6-mobile-v2
    DocumentRoot /var/www/mobile
   <Directory />
    <Directory />
       Options FollowSymLinks
        Options FollowSymLinks
       AllowOverride None
        AllowOverride None
   </Directory>
    </Directory>
   <Directory /var/www/ox6-mobile-v2>
    <Directory /var/www/mobile>
       Options Indexes FollowSymLinks MultiViews
        Options Indexes FollowSymLinks MultiViews
       AllowOverride None
        AllowOverride None
       Order allow,deny
        Order allow,deny
       allow from all
        allow from all
   </Directory>
    </Directory>
   ErrorLog /var/log/apache2/error.log
    ErrorLog /var/log/apache2/error.log
   # Possible values include: debug, info, notice, warn, error, crit,
    # Possible values include: debug, info, notice, warn, error, crit,
   # alert, emerg.
    # alert, emerg.
   LogLevel warn
    LogLevel warn
   CustomLog /var/log/apache2/access.log combined
    CustomLog /var/log/apache2/access.log combined
  </VirtualHost>
  </VirtualHost>


* For more details and README see the systems documentation directory (/usr/share/doc).
* For more details and README see the systems documentation directory (/usr/share/doc).


==Running the OX Mobile Web App on your smartphone==


After installation of the App on your webserver, a client can easily access the app via his phone's browser. We recommend to add a new subdomain to your web address to make access for clients easy. A short subdomain like <code>https://m.example.com</code> which points to your installation will save users from entering a long URL on their devices.
=Running the Open-Xchange Mobile Web Interface on your smartphone=


Like mentioned before, the OX Mobile Web App is a pure web application. Due to this fact there is no installation or download needed to use this app on a smartphone. Just add a bookmark in your browser to access the app again later.  
After installation of the web interface on your webserver, a client can easily access the web interface via his phone's browser. We recommend to add a new subdomain to your web address to make access for clients easy. A short subdomain like <code>https://m.example.com</code> which points to your installation will save users from entering a long URL on their devices.


Especially on iOS devices there's a seamless integration within the native apps installed via the AppStore®. Just add a new bookmark to the OX Mobile Web App and choose "Add to homescreen". After this, the OX Mobile Web App will place a new app icon on the homescreen.
Like mentioned before, the Open-Xchange Mobile Web Interface is a pure web application. Due to this fact there is no installation or download needed to use this web interface on a smartphone. Just add a bookmark in your browser to access the web interface again later.  


===Common mistakes===
Especially on iOS devices there's a seamless integration within the native apps installed via the AppStore®. Just add a new bookmark to the Open-Xchange Mobile Web Interface and choose "Add to homescreen". After this, the Open-Xchange Mobile Web Interface will place a new app icon on the homescreen.
Most problems can be solved by clearing the browser cache and reload the app. Try this before you request a bug or change the server settings.


Problem: After login a page is shown showing "Connection problem. Received response code 0".


Resolution: Your ox-access.conf is not configured correctlly. You must enter the full web app server address followed by the /ajax path. Server address means the full url a user will type in his browser to access the app. I.e. "https://m.example.com/". If everything on the backend is configured correctly, try to reload the app.
==Using the offline mode==


Problem: Using the browser's back button brings me back to the login page. After this the app does not work correctly.
During the first run, the web interface is stored localy on your smartphone. These caching mechanism makes a later access to the web interface very fast and gives you the possibility to run the web interface even if there's no internet connection available.  


Resolution: Only use the navigation of the app. On each subpage a back button is located at the upper left corner which brings you back to the previous page.
The Open-Xchange Mobile Web Interface detects on startup whether there's an internet connection available or not. If not, the web interface will start in offline mode. In this case most features which need a internet connection are disabled. In offline mode you can access all your subscribed contacts and all of your appointments. Also all your mail headlines are available. Furthermore each email which was opened earlier is available in offline mode.


===Using the offline mode===


During the first run, the app is stored localy on your smartphone. These caching mechanism makes a later access to the app very fast and gives you the possibility to run the app even if there's no internet connection available.
=Known Issues=


The OX Mobile Web App detects on startup whether there's an internet connection available or not. If not, the App will start in offline mode. In this case a plane icon is shown in the upper left corner of the main menu. In offline mode you can access all your subscribed contacts and all of your appointments. Also all your mail headlines are available. Furthermore each email which was opened earlier is available in offline mode.


'''Note:''' The Mobile Web App will detect the state of your internet connection live. Open the log under the settings page for informations
==Client==


==Known Issues==
* The Open-Xchange Mobile Web Interface uses a custom, built-in navigation and history. To navigate back you will have to use the "back" buttons located on the top-left of the page. Using the browser's back button will sometimes not bring you back to the right page.
 
===Client===
 
* The OX Mobile Web App uses a custom, built-in navigation and history. To navigate back you will have to use the "back" buttons located on the top-left of the page. Do not use browser's back button. This causes the app to jump to the login screen and you will have to reload the app.
 
* If you want to use the App in airplane mode or no network connection is availabe, the android browser will show up a message like "page could not be loaded due to missing network connection". Just ignore this alert and press "OK". The app will work in offline mode even android shows up this message.  


* If you clean the browser cache on your device or reset it to defaults, all local stored data will be flushed.
* If you clean the browser cache on your device or reset it to defaults, all local stored data will be flushed.


===Server===
* The OX backend uses a security mechanism called "IP check". This feature is enabled by default for a OX Server. This feature will have an impact on the usage of the OX Mobile App, especially the option "Stay logged in". This feature will only work if your IP address does not change between the restarts of the app. If you are changing your network connection often when you travel around (different GSM spots, WIFI connections), your phone will get new IP addresses to access the internet. This will cause the OX backend to refuse your auto-login attempt (which is performed on every start of the App) because your IP address has changed.


To avoid this you can either turn off the IP check feature on the OX backend or set up a second server with weaker security settings only for mobile clients.
==Server==
* The Open-Xchange backend uses a security mechanism called "IP check". This feature is enabled by default for a OX Server. This feature will have an impact on the usage of the Open-Xchange Mobile Web Interface, especially the option "Stay logged in". This feature will only work if your IP address does not change between the restarts of the web interface. If you are changing your network connection often when you travel around (different GSM spots, WIFI connections), your phone will get new IP addresses to access the internet. This will cause the OX backend to refuse your auto-login attempt (which is performed on every start of the web interface) because your IP address has changed. To avoid this you can either turn off the IP check feature on the OX backend or add the Open-Xchange Mobile Web Interface to the client whitelist table for IP-check. This will disable the IP check just for the web interface.


== Deployment as native app ==


The OX Mobile Web App can also be deployed as a native smartphone app. This option is available for Android Systems and later for iOS, too. As Android allows installation of apps from every location you can place an *.apk file on a webserver or in your own Android App-Store. The OX Mobile Web App will act like any other app on the device and offers the same functionality as the web hosted variant.
= Theming =


Deploying a native iOS App can only be done via the Apple AppStore®. To do so you need to submit your special branded version of the app to Apple. Only Apple decides if the app will be listed in the AppStore or not.
The Open-Xchange Mobile Web Interface is themed via CSS and HTML. To create your own theme you will have to create new graphics and edit the css file in the theme path. To do so follow the steps below:


For more information on native app deployment please contact us directly.
# Locate the theme path under "path to your webroot/mobile/theme"
# To create your own theme make a copy of this folder and backup the original one
# The folder contains a css file which holds all editable values for the web interface. To change values edit the original file or create a new one which overwrites some of the old styles. Use Firebug or the Chrome/Safari developer tools to locate css classes and styles you want to edit.
# The folders "img" holds all graphics which are used in the web interface.
# Always remember: Your are designing for mobile. This means: Keep fonts clear and easy to read. Keep file sizes small due to small bandwiths. Keep buttons big enought the user can touch them easily.


== Branding options ==
=== Application name===
The OX Mobile Web App comes with the standard name set "OX Mobile Web App". This title is saved in a png file under "/lib/jqtouch/themes/default/external/i18n_img/brand_[locale].png". To brand the app with your custom title just replace the files for each language to your needs. The i18n tool will show the graphic for each language. To configure the page title (in html title tag) please use the customisation plugin located at custom/custom.js


* open the file custom.js in folder "custom" located at your install dir
=Reporting Bugs=
* open the file custom.js.sample located in the same folder
* use the sample file as template for your customisations. Change the values of APP_TITLE and ABOUT_PAGE_TEXT to your needs.
* copy and overwrite your custom.js.sample to the file custom.js
 
== Theming ==
 
The OX Mobile Web App is themed via CSS and HTML. To create your own theme you will have to create new graphics and edit the css files in the theme path. To do so follow the steps below:
 
# Locate the theme path under "path to your webroot/ox6-mobile-v2/lib/jqtouch/themes"
# The default theme is named "default". To create your own theme make a copy of this folder and backup the original one
# The folder contains a css file which holds all editable values for the app. To change values edit the original file or create a new one which overwrites some of the old styles. Use Firebug or the Chrome/Safari developer tools to locate css classes and styles you want to edit. Then create a new css file and place it next to mox.min.css. Edit this file to your needs and add a new "style" tag to the index.html just AFTER the mox.min.css style tag. This will ensure that your styles overwrite the original ones.
# The folders "img" and "external" hold all graphics which are used in the app. To change them, just edit and save them under the same name. Don't change filenames or the theme will be broken. Also keep all file dimensions and file types (*.png, *.jpg). Changing files dimensions will corrupt the theme and layout will be broken.
# Always remember: Your are designing for mobile. This means: Keep fonts clear and easy to read. Keep file sizes small due to small bandwiths. Keep buttons big enought the user can touch them easily.
 
==Reporting Bugs==


Open-Xchange is interested in learning about bugs, specifically in your runtime environment. If you experience any misbehaviors, please report bugs via our public bugzilla:
Open-Xchange is interested in learning about bugs, specifically in your runtime environment. If you experience any misbehaviors, please report bugs via our public bugzilla:
[https://bugzilla.open-xchange.com/enter_bug.cgi?product=OX%20Mobile%20Web%20App Open-Xchange Bugzilla]<br>
[https://bugs.open-xchange.com/ Open-Xchange Bugzilla]<br>
Product: OX Mobile Web App
Product: Mobile Web Interface
 
The OX Mobile Web App logs all errors to a logfile which can be found under settings -> log.
 
== Please note ==


There may be some issues with checkboxes on Android devices. Sometimes checkboxes and listboxes do not respond to tap actions. If so, please rotate your phone to landscape mode and back. Then, the checkboxes should response again
The Open-Xchange Mobile Web Interface logs all errors to a logfile which can be found under Settings -> System Messages


Please read the SDB article to inform you about the reasons and solution.


[[Category: OX6]]
[[Category: OX6]]

Latest revision as of 09:44, 6 April 2017

Information and Installation of Open-Xchange Mobile Web Interface (Only for OX 6)

Description

The Open-Xchange Mobile Web Interface provides you access to your data from the Open-Xchange Server 6 via your smartphone. The Open-Xchange Mobile Web Interface offers online and offline access to appointments, contacts and mails on the road using your smartphone's browser. Optimized for low bandwiths the Open-Xchange Mobile Web Interface offers instant and fast over the air access to your data, which are at the same time safely stored on Open-Xchange Server. The following modules are supported:

  • E-Mail
  • Calendar
  • Contacts

Moreover the web interface offers seamless integration to use your phones basic functions like phone calls. You can easily start calls from your Open-Xchange contacts on your smartphone or directly send E-Mails.


Themeability, branding and i18n

  • i18n for DE, EN, ES, FR, NL, PL and JP. Other languages can be added.
  • Themeability by CSS
  • JavaScript plugins for branding and custom functions.


Supported devices

The Open-Xchange Mobile Web Interface is designed to run on modern devices running Android or iOS. It can also used with modern desktop browsers.

Device Support    
Apple iOS iOS 3 - 5.1
Android yes, Android 2.2 - 4.0 Official Supported by OX: Google Nexus One (Android 2.3.3), Samsung Galaxy Nexus (Android 4.0.3). The web interface is optimized for a display size of 320 x 480 pixels. Smaller resolutions may result displaying issues of some UI elements

Technical overview

  • Based on HTML5, CSS, Javascript (jQuery Mobile)
  • Optimized for Webkit browsers like Mobile Safari and Chrome. Will also work with restrictions on Firefox and Opera Mobile
  • Complete offline capability


Updates with version 1.1.0 rev 8

  • True fixed toolbars:

Version 1.1.0 rev 6 of the Mobile Web Interface used dynamic recalcualtion to re-position footer and header bars on the fly after scrolling the document. The new version of jQuery Mobile (1.1) now uses CSS based positioning which is truly native on supported platforms.

Some platforms like iOS 4 will now fall back to static positioning where the toolbars simply scroll with the page.

Platforms which support fixed toolbars:

  • iOS5 – iPhone and iPad
  • Android 2.2 and 2.3
  • Android 3.x tablets (Honeycomb)
  • Android 4.x (ICS)
  • Chrome for Android (beta)
  • BB Playbook 1-2
  • All modern desktop browsers (IE, Firefox, Safari, Chrome, etc.)


Offline Mode details

The Open-Xchange Mobile Web Interface uses HTML5 to provide an offline mode for the user. To do this, there are two different kinds of storage mechanisms.

  • The whole web interface uses caching by incorporating the "HTML5 application cache". This will be done on the first visit/start of the web interface. After this initial download, all graphics, language files, js-files and everything else which is needed to run the web interface is stored locally on your phone in a storage managed by the browser.
  • The data from the OX server will be stored using the HTML5 storage mechanism which will be supportet by the users device. These can be a HTML5 local storage, session storage or an SQLite database. For the user there's no difference between these different storage modes.


Requirements

  • Open-Xchange Server >= v.6.20 rev 21

Installation on Open-Xchange v6.22.x

Debian GNU/Linux 6.0

Add the following entry to /etc/apt/sources.list if not already present:

deb http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/DebianSqueeze/ /

and run

$ apt-get update
$ apt-get install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config

SUSE Linux Enterprise Server 11

Add the package repository using zypper if not already present:

$ zypper ar http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/SLES11 MobileWebInterface

and run

$ zypper ref
$ zypper in open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config

RedHat Enterprise Linux 6

Start a console and create a software repository file if not already present:

$ vim /etc/yum.repos.d/MobileWebInterface.repo
[MobileWebInterface]
name=Open-Xchange
baseurl=http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update
$ yum install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config

CentOS 6

Start a console and create a software repository file if not already present:

$ vim /etc/yum.repos.d/MobileWebInterface.repo
[MobileWebInterface]
name=Open-Xchange
baseurl=http://LDBACCOUNT:LDBPASSWD@software.open-xchange.com/OX6/6.22/OXtender-stable/MobileWebInterface/RHEL6/
gpgkey=http://software.open-xchange.com/oxbuildkey.pub
enabled=1
gpgcheck=1
metadata_expire=0m

and run

$ yum update
$ yum install open-xchange-mobile open-xchange-mobile-theme-default open-xchange-mobile-config

Optional link to Mobile Web Interface in OX6 login mask (since 6.20.3)

There is an optional plugin available which adds a link to the Mobile Web Interface to the common OX6 login screen.

Debian

$ apt-get install open-xchange-gui-mobile-redirect-plugin


SUSE Linux Enterprise Server

$ zypper install open-xchange-gui-mobile-redirect-plugin


RedHat Enterprise Linux

$ yum install open-xchange-gui-mobile-redirect-plugin


The plugin needs to be configured in ${DOCROOT}/ox6/plugins/com.openexchange.mobile.redirect/config/config.js

data = {
    url: "https://m.example.com//",
    isEnabled: function() {
        return true;
        //----- example to add a device check instead of always returning true -----//
        // return (/iphone|ipod|android|/i.test(navigator.userAgent.toLowerCase()));
    },
    getText: function() {
        return _("Switch to mobile version");
    }
};



Upgrading from previous versions

If you have the previous version of the Mobile Web Interface installed (1.0), you can not upgrade to version 1.1 or later directly. Due to a package rename you have to remove the old packages before installing the new ones. The packages for version 1.0 are prefixed with "open-xchange-gui-mobile-v2", the new ones are prefixed with "open-xchange-mobile*".


Debian

$ apt-get purge open-xchange-gui-mobile-v2
$ apt-get purge open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default


SUSE Linux Enterprise Server

$ zypper remove open-xchange-gui-mobile-v2
$ zypper remove open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default


RedHat Enterprise Linux

$ yum remove open-xchange-gui-mobile-v2
$ yum remove open-xchange-gui-mobile-v2-gui open-xchange-gui-mobile-v2-theme-default

Please note, the package open-xchange-gui-mobile-v2 is located on your ox backend system, open-xchange-gui-mobile-v2-gui and open-xchange-gui-mobile-v2-theme-default are installed on your webserver machine. If both systems are the same you have to remove all packes on the same system.

After removing the old packages proceed with the installation of the new version 1.1 or later

Installation on OX App Suite

The download and installation information for Open-Xchange App Suite product family (Open-Xchange Server Edition and Hosting Edition) is available at: http://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mobile_Web_Interface


Configuration

Installation on the Apache 2 webserver:

Important note for upgraders: In previous versions (lower 1.1) a server address had to be entered in the cache.manifest file to grant access to the OX6 backend. This not needed anymore. The new version of the mobile web grants per default access to all uncached ressources. Don't edit the cache.manifest manually.

  • You need to add a new mimetype to your webserver configuration to make sure the caching (offline mode) works.
    • On Apache servers you can add the mimetype either global or via ".htaccess" file.
    • For global configuration edit the file mime.conf under /etc/apache2/mods-enabled/
    • Add the line "AddType text/cache-manifest .manifest" to the file, save and restart apache
    • For configuration via .htaccess file just add a .htaccess file to the install directory. This should include the line "AddType text/cache-manifest .manifest'". Note: Either the global configuration or the .htaccess file should be used. (.htaccess files will only work if your Apache settings contain AllowOverride. For further information on mime types, please refer to your webservers user manual)
  • To direct to the correct host another site in apache is needed. Create a file named "mobile" in /etc/apache2/sites-available (and enable it by linking to it from sites-enabled, of course):
<VirtualHost *:80>
   ServerAdmin webmaster@localhost
   ServerName mobile.YOUR_DOMAINAME.TLD
   ServerAlias m.YOUR_DOMAINAME.TLD
   DocumentRoot /var/www/mobile
   <Directory />
       Options FollowSymLinks
       AllowOverride None
   </Directory>
   <Directory /var/www/mobile>
       Options Indexes FollowSymLinks MultiViews
       AllowOverride None
       Order allow,deny
       allow from all
   </Directory>
   ErrorLog /var/log/apache2/error.log
   # Possible values include: debug, info, notice, warn, error, crit,
   # alert, emerg.
   LogLevel warn
   CustomLog /var/log/apache2/access.log combined
</VirtualHost>
  • For more details and README see the systems documentation directory (/usr/share/doc).


Running the Open-Xchange Mobile Web Interface on your smartphone

After installation of the web interface on your webserver, a client can easily access the web interface via his phone's browser. We recommend to add a new subdomain to your web address to make access for clients easy. A short subdomain like https://m.example.com which points to your installation will save users from entering a long URL on their devices.

Like mentioned before, the Open-Xchange Mobile Web Interface is a pure web application. Due to this fact there is no installation or download needed to use this web interface on a smartphone. Just add a bookmark in your browser to access the web interface again later.

Especially on iOS devices there's a seamless integration within the native apps installed via the AppStore®. Just add a new bookmark to the Open-Xchange Mobile Web Interface and choose "Add to homescreen". After this, the Open-Xchange Mobile Web Interface will place a new app icon on the homescreen.


Using the offline mode

During the first run, the web interface is stored localy on your smartphone. These caching mechanism makes a later access to the web interface very fast and gives you the possibility to run the web interface even if there's no internet connection available.

The Open-Xchange Mobile Web Interface detects on startup whether there's an internet connection available or not. If not, the web interface will start in offline mode. In this case most features which need a internet connection are disabled. In offline mode you can access all your subscribed contacts and all of your appointments. Also all your mail headlines are available. Furthermore each email which was opened earlier is available in offline mode.


Known Issues

Client

  • The Open-Xchange Mobile Web Interface uses a custom, built-in navigation and history. To navigate back you will have to use the "back" buttons located on the top-left of the page. Using the browser's back button will sometimes not bring you back to the right page.
  • If you clean the browser cache on your device or reset it to defaults, all local stored data will be flushed.


Server

  • The Open-Xchange backend uses a security mechanism called "IP check". This feature is enabled by default for a OX Server. This feature will have an impact on the usage of the Open-Xchange Mobile Web Interface, especially the option "Stay logged in". This feature will only work if your IP address does not change between the restarts of the web interface. If you are changing your network connection often when you travel around (different GSM spots, WIFI connections), your phone will get new IP addresses to access the internet. This will cause the OX backend to refuse your auto-login attempt (which is performed on every start of the web interface) because your IP address has changed. To avoid this you can either turn off the IP check feature on the OX backend or add the Open-Xchange Mobile Web Interface to the client whitelist table for IP-check. This will disable the IP check just for the web interface.


Theming

The Open-Xchange Mobile Web Interface is themed via CSS and HTML. To create your own theme you will have to create new graphics and edit the css file in the theme path. To do so follow the steps below:

  1. Locate the theme path under "path to your webroot/mobile/theme"
  2. To create your own theme make a copy of this folder and backup the original one
  3. The folder contains a css file which holds all editable values for the web interface. To change values edit the original file or create a new one which overwrites some of the old styles. Use Firebug or the Chrome/Safari developer tools to locate css classes and styles you want to edit.
  4. The folders "img" holds all graphics which are used in the web interface.
  5. Always remember: Your are designing for mobile. This means: Keep fonts clear and easy to read. Keep file sizes small due to small bandwiths. Keep buttons big enought the user can touch them easily.


Reporting Bugs

Open-Xchange is interested in learning about bugs, specifically in your runtime environment. If you experience any misbehaviors, please report bugs via our public bugzilla: Open-Xchange Bugzilla
Product: Mobile Web Interface

The Open-Xchange Mobile Web Interface logs all errors to a logfile which can be found under Settings -> System Messages