Child pages
  • Emory Internal Mobile Application Distribution
Skip to end of metadata
Go to start of metadata

Background

Emory OIT makes enterprise mobile applications available for download to authorized Emory people. Enterprise mobile applications are mobile applications intended only for internal use by Emory people or preliminary internal use by Emory people prior to general public release in an application marketplace like the Apple AppStore or Google Play. This internal distribution method is in a proof-of-concept stage and is presently intended only to support internal development and testing processes. In 2013 Emory will either formalize this approach into a production service or implement some other internal mobile application distribution approach as a production service.

iOS Process

iOS applications intended for internal distribution must be signed with a valid distribution certificate from a legitimate Emory University Apple iOS Developer Enterprise Account. Emory OIT has such Developer Enterprise Accounts and can sign apps on behalf of other Emory developers and distribute them internally. Alternately Emory units with their own valid Apple Enterprise Developer Accounts may sign their application archives and use Emory OIT's distribution site to distribute the application to a specific target audience. It is possible for Emory to have multiple iOS Developer Enterprise Accounts. It is not possible for Emory to have more than one legitimate iOS Developer Account for publishing applications externally to the Apple AppStore (contact Daniel Palmer in UTS for information about distributing an Emory application through Apple's AppStore).

To distribute an application internally, you will need:

  1. an Apple Developer Enterprise Account registered to "Emory University" or "Emory Healthcare" (or access to someone in control of one of these accounts to sign your application archive for you).
  2. access to Emory OIT Subversion. If you are in OIT and already have access to Subversion, you should not need to request additional access. Mobile application distributions are performed from /emoryoit/distributions/mobile/[application-name] where the application name is like [organization]-[appname]-platform, for example emory-webease-ios is the package name for the Emory WebEase Mobile Application for iOS. Another example would be actsi-mppi-android for the ACTSI Master Patient Participant Index Service Lookup App for Andriod. If you are not in an OIT unit and do not already have access to Subversion, you may make a request to deploy your application via ServiceNow and UTS will create your deployment area in Subversion and grant you access to that specific location.

Steps to distribute your applications:

  1. Create your application archive in Xcode for "Release."
  2. Sign the archive with an enterprise distribution profile.
  3. Export the archive and check the option "for enterprise deployment."
  4. Provide the following values to the enterprise deployment wizard:
    1. URL to the application archive (.ipa) file: https://dev.app.emory.edu/mobile/[your-app-identifier]/YourAppName.ipa
    2. URL to the manifest file: https://dev.app.emory.edu/mobile/[your-app-identifier]/YourAppName.plist
    3. URL to the small image: https://dev.app.emory.edu/mobile/[your-app-identifier]/YourAppsSmallImage.png
    4. URL to the large image: https://dem.app.emory.edu/mobile/[your-app-identifier]/YourAppsLargeImage.png
  5. Commit all of these artifacts to your application distribution directory in Subversion (for example, /emoryoit/distributions/mobile/[your-app-name])
  6. This distribution directory will already contain access control artifacts if it was created for you or you can copy access control artifacts from another deployment. The authorized-downloaders file contains a list of specific Emory people (by NetID) allowed to download your application. If you provide no list of people in the authorized-downloaders file, nobody will be able to download your application. If you would like all Emory people to be able to access your application, edit the .htaccess file in your directory and remove the "Require authorized-downloaders" line. It is not possible to use this distribution method to distribute application to non-Emory people unless those people have Emory sponsored accounts. You may request sponsored accounts for non-Emory people on you teams. If there are a significant number of non-Emory beta testers or users of applications there are other deployment options not described here. Contact Emory OIT Architecture for details.

Android Process

Android applications for internal distribution must be signed for distribution with a valid key that you can generate yourself. For details on the process of exporting an Android application signed properly for distribution, see Signing Your Applications on the Android Developer site.

Steps to distribute your applications:

  1. From the Eclipse IDE, export your application for release.
  2. Sign the archive with your release key (Note: steps one and two can be completed at once with the Android application export wizard in Eclipse)
  3. Commit the exported apk file to your application distribution directory in Subversion (for example,  /emoryoit/distributions/mobile/[your-app-name])
  4. This distribution directory will already contain access control artifacts if it was created for you or you can copy access control artifacts from another deployment. The authorized-downloaders file contains a list of specific Emory people (by NetID) allowed to download your application. If you provide no list of people in the authorized-downloaders file, nobody will be able to download your application. If you would like all Emory people to be able to access your application, edit the .htaccess file in your directory and remove the "Require authorized-downloaders" line. It is not possible to use this distribution method to distribute application to non-Emory people unless those people have Emory sponsored accounts. You may request sponsored accounts for non-Emory people on you teams. If there are a significant number of non-Emory beta testers or users of applications there are other deployment options not described here. Contact Emory OIT Architecture for details.

Mobile Distribution Index Link

The mobile application distribution index is available at <https://dev.app.emory.edu/mobile>. The recommended approach is to bookmark this page in your mobile device to return to this page easily for new apps and updates.

Applications

  • No labels