Chapter 19 n Deploying Applications Over the Air 5 Figure 19-1: Your in-house app catalog can either be a mobile website that can be deployed as a Web Clip or a native iOS app, shown here. This itms-services:// URL can be sent in an e-mail or a text message, or simply linked to from a website or from within a native application. Here is an example of how the URL can be embedded in an HTML link: Install App The manifest fi le must be an XML fi le that follows Apple’s PropertyList (PLIST) syntax in order to describe the various properties, attributes, and metadata of the application that is to be deployed over the air. This information is used to provide the device with all the information necessary to facilitate the installation of the application, as well as the appropriate metadata that is displayed to users as part of a prompt to request permission. This XML fi le can be a static fi le that resides on a web server, or it can be dynamically generated with PHP, Java, ASP.NET, or any other web server language or technology. Here is an example manifest fi le: items Copyrighted Material. Not for Redistibution. Copyright © 2011, John Wiley and Sons.  | iPad in the Enterprise - Developing and Deploying Business Applications Page 6 | Apperian
Chapter 19 n Deploying Applications Over the Air 5 Figure 19-1: Your in-house app catalog can either be a mobile website that can be deployed as a Web Clip or a native iOS app, shown here. This itms-services:// URL can be sent in an e-mail or a text message, or simply linked to from a website or from within a native application. Here is an example of how the URL can be embedded in an HTML link: Install App The manifest fi le must be an XML fi le that follows Apple’s PropertyList (PLIST) syntax in order to describe the various properties, attributes, and metadata of the application that is to be deployed over the air. This information is used to provide the device with all the information necessary to facilitate the installation of the application, as well as the appropriate metadata that is displayed to users as part of a prompt to request permission. This XML fi le can be a static fi le that resides on a web server, or it can be dynamically generated with PHP, Java, ASP.NET, or any other web server language or technology. Here is an example manifest fi le: items Copyrighted Material. Not for Redistibution. Copyright © 2011, John Wiley and Sons.