System Requirements for Client

TMVMI client supports both phone and tablet running on iOS, Android, or Windows. Below are the compatible OS versions:

• iOS 7.0 and above
• Android 4.0 and above
• Windows 8.1
• Windows Phone 8.1
• Windows 10 Mobile

System Requirements for TMVMI Server

TMVMI Server is delivered as a Linux-based appliance and is packaged as an ISO file. Below are the requirements:

• Processor: 64-bit x86 four core
• Memory: 4 GB
• Hard disk: 30 GB available for installation
• Network Cards (NIC): One 1 GB NICs

System Requirements for TMVMI Secure Access

Secure Access is delivered as a Linux-based appliance and is packaged as an ISO file. Below are the requirements:

• Processor: 64-bit x86 four core
• Memory: 4 GB
• Hard disk: 30 GB available for installation
• Network Cards (NIC): One 1 GB NICs

System Requirements for Bare Metal machines

TMVMI Server can be installed on bare metal machines or virtual machines. The following machines are supported:

• Dell R510
• Dell R520
• Dell R710
• Dell R720
• Dell R810
• IBM X3550
• HP DL380G6

TMVMI Server can be installed on the following virtual machine versions:

• VMWare ESX 4.1
• VMWare ESXi 4.1, 5.1, or 5.5
• VMWare Workstation 9 or 10
• VMWare Fusion 5 or 6
• Windows 2012 HyperV
• Citrix XenServer 6

It supports the following CPU type:

• Intel processors support SSSE3

We provide local application solution to support offline mode.

Virtual Mobile Infrastructure enables you to deploy Android and iOS apps on user mobile devices outside user workspace, so that users may use these apps even when the network is not available.

It also lets you modify the functionality of local applications that you deploy to help align them with the organization's security policies. You can also configure the security policy to protect the local application data on the mobile device. For example, you can restrict copy and paste operations within a managed local application, or forbid to share file in local applications. You can also remove or disable a local application from administration web console. The option to remove or disable application cannot be run on mobile devices.

Note that you can only upgrade from TMVMI 5.0 to TMVMI 5.1. For more information, refer to this article: Upgrading Virtual Mobile Infrastructure (TMVMI) and Secure Access to version 5.1.

To upgrade:

1. Download the upgrade package, and rename it to "upgrade.tar.bz2".
2. Copy the file to the server path /gluster/upload.
3. Open the command line and login with admin account.
4. Type "enable", then type "upgrade".
5. Manually restart the machine. The server will be upgraded after the restart.

TMVMI server generated a private HTTPs certificate during installation. If you want to download iOS local app from server, you need to install the certificate first, and then install iOS local app from TMVMI server.

• Single or multiple TMVMI server(s) without SA and HA

  Click iOS local app in launcher to download and install the iOS local app directly.

• Single or multiple TMVMI server(s) + SA (1 network card)

  Configure the SA IP address or domain name in Administration > Mobile client > Secure Access settings. After saving the settings, click iOS local app in launcher to download and install the iOS local app.

• Single or multiple TMVMI server(s) + SA (2 network cards)

  Configure the SA server IP address or domain name that mobile devices can connect from the Internet. The settings can be set in Administration > Mobile client > Secure Access. After saving the settings, click iOS local app in launcher to download and install iOS local app.

• NAT server + Single or multiple TMVMI server(s) + SA (1 or 2 network cards)

  Configure the NAT server IP address or domain name in Administration > Mobile client > Secure Access settings. The IP address of download URL is a NAT server IP address that mobile device can connect from Internet. Replace the certificate in SA to NAT server certificate. After saving the settings, click iOS local app in launcher to download and install iOS local app.

• Multiple servers + HA + SA (1 network card)

  Configure SA IP address or domain name in Administration > Mobile client > Secure Access settings. After saving the settings, click iOS local app in launcher to download and install iOS local app.

• Multiple servers + HA + SA (2 network cards)

  Configure SA server IP address or domain name that mobile devices can connect from the Internet. This can be set in Administration > Mobile client > Secure Access settings. After saving the settings, click iOS local app in launcher to download and install iOS local app.

• Multiple servers + HA without SA

  It is strongly recommend to deploy SA if you enable HA mode.

Some application developers encounter issues in running their apps in TMVMI. VMI is incompatible with certain settings in APK. An app may fail to work in VMI if it has the following settings:

• The application requires hardware support (e.g. bluetooth or NFC).
  • For bluetooth, APK's AndroidManifest.xml contains the following string:

    uses-permissionandroid:name="android.permission.BLUETOOTH"

  • For NFC, APK's AndroidManifest.xml contains the following string:

    uses-permission android:name="android.permission.NFC"

• The application needs OpenGL ES 2.0 or 3.0 support. APK's AndroidManifest.xml contains the following strings:

  uses-feature android:glEsVersion="0x20000" android:required="true"
  uses-feature android:glEsVersion="0x30000" android:required="true"

• The application needs Google Framework. APK's AndroidManifest.xml contains the string below:

  meta-data android:name="com.google.android.gms.version" android:value="@integer/google_play_services_version"

• The application must be run in SDK which version is greater than 22. APK's AndroidManifest.xml contains the following string wherein "minSdkVersion" is higher than 22:

  uses-sdk android:minSdkVersion="integer" android:targetSdkVersion="integer" android:maxSdkVersion="integer"

   

  In order for an app to work with VMI, the "minSdkVersion" value should be less than or equal to 22.
• An application contains mismatched ARM and x86 lib. VMI supports APK with x86 since we are running on x86 server. Also, VMI supports APK with ARM lib because it has abox. However, APKs that put ARM (or other non-x86 processors) lib in x86 directory are not supported. APKs with mismatched x86 libs and ARM libs are unsupported too. Below are some examples of unsupported settings:
  • An APK has "armeabi" and "x86" directories. There are a.so, b.so, and c.so in "armeabi", and another a.so, b.so and c.so in "x86". However, b.so is in ARM format, which means there is an ARM lib in x86 dir.
  • An APK has "armeabi" and "x86" directory. There are a.so, b.so, and c.so in "armeabi", but only a.so and b.so in "x86".