Product Documentation

Preparing Mobile Apps with the MDX Toolkit

Oct 20, 2015

Citrix provides the MDX Toolkit so that you can wrap a mobile app for iOS or Android with Citrix logic and policies. The tool can securely wrap an app that was created within your organization or a mobile app made outside the company. The Worx App SDK libraries install in the Citrix/MDXToolkit/data/MDXSDK and MDXSDK_Android folders. The MDXSDK folder is required for the integration of wrapped iOS mobile apps with Citrix Worx. When you wrap iOS apps that include the Worx SDK libraries, you can publish the apps in the Apple App Store and the Citrix Worx Store. After the app is wrapped, you can upload then the app to App Controller. For more information about the Worx App SDK, such as an overview for ISVs, and to download the SDK, see Worx App SDK on the Citrix web site.


The MDX Toolkit requires the Java Development Kit (JDK) 1.7. You can download the JDK 1.7 from Java SE Development Kit Downloads on the Oracle web site. The instructions for installing the JDK on Mac OS X are on the Computech Tips web site.

Before you wrap an iOS app, download and install the iOS Distribution Provisioning Profile and Distribution Certificate to your computer. The provisioning profile signs the app for distribution.

Wrapping Android Mobile Apps

For Android apps, you need to follow these basic steps:

  • Specify an Android mobile app APK file. When you click Next , the MDX Toolkit validates the Android SDK path. If the tool cannot validate the path, you can browse to the SDK on your computer.
  • Choose the JDK on your computer for wrapping Android mobile apps. If the JDK is not installed on your computer, the tool prompts you to install the tool. When you click Install, the tool locates the tool on the Web and then installs the JDK on your computer. Make sure you install version 1.7.
  • Choose the Android Software Development Kit (SDK) on your computer for wrapping Android mobile apps and choose the Android APK tool.
  • Choose the keystore for signing Android mobile apps. When you wrap the app, you must provide the keystore that was created when the app was developed. The Android operating system requires that all installed mobile apps be digitally signed with a certificate with a private key that is held by the developer. The certificate does not need to be signed by a Certificate Authority. Android mobile apps can use self-signed certificates. For more information about signing Android mobile apps, see the Android developers web site.

When you wrap the mobile app with the MDX Toolkit, you can select the option Use debug keystore. This option allows you to sign the mobile app if the release keystore is not available during development. To create an Android app that users install on their devices, you must create a retail build of the app and disable Use debug keystore so you can sign the package with a real key. A keystore can contain multiple private keys, in most cases it will be only one key. If the keystore contains multiple private keys, when you wrap the app, you can select the key alias. When the MDX Toolkit finishes wrapping the app, the app file name includes _andr. The file type is .mdx.

Wrapping iOS Mobile Apps

For iOS apps, you need to following these basic steps:

  • Specify an iOS mobile app IPA file.
  • In the MDX Toolkit wizard, choose the option to deploy the app from XenMobile or to deploy the app from the Apple App Store.
  • Choose the iOS Distribution Provisioning Profile and Distribution Certificate to sign the app for distribution.

When the MDX Toolkit finishes wrapping the app, the app file name includes _iOS. The file type is .mdx.

When you run the MDX Toolkit, the app determines the application type and version. You can select the minimum and maximum operating system versions.

Uploading the Wrapped App and Configuring Policies

After you complete wrapping the app, you then upload the MDX file to App Controller. You use the App Controller management console to configure specific app details and policy settings that the Worx Store enforces. When users log on, the app appears in the store. Users can then subscribe, download, and install the app on their device. For more information about configuring the app details and policy settings in App Controller, see Adding Apps.