Generating packages for managed applications

• US 10,223,526 B2
• Filed: 05/21/2015
• Issued: 03/05/2019
• Est. Priority Date: 05/21/2015
• Status: Active Grant

• Current Assignee: Omnissa, LLC
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Xuan, Chaoting, Stuntebeck, Erich
• Primary Examiner(s): Abedin, Shanto
• Application Number:
  US14/718,694
• Publication Number:
  US 20160342788A1
• Time in Patent Office: 1,384 Days
• Field of Search: 726 1, 726 22, 726 26
• CPC Class Codes: G06F 21/54 by adding security routines or objects to programs
• CPC Class Codes: G06F 2221/2111 Location-sensitive, e.g. geographical location, GPS

Abstract

Embodiments relate to a managed application package generator that creates an executables file, a resource file, and a manifest file for a managed application. The executables file comprises an executable for a loader that loads a target application into memory. The resource file comprises a public resource for the target application. The manifest file comprises manifest data for the target application.

Claims

1. A method, for generating a managed application package for distribution to a plurality of devices, the managed application package being based on a target application package, comprising:

generating an executables file for the managed application package, wherein the executables file comprises a first executable for a loader that loads a target application into memory, wherein the executables file further comprises a second executable for a compliance rule enforcer for the target application;

generating a resource file for the managed application package, wherein the resource file comprises a public resource for the target application;

generating a manifest file for the managed application package, wherein the manifest file comprises manifest data for the target application;

bundling the executables file, the resource file, and the manifest file into the managed application package; and

distributing the managed application package to the plurality of devices for installation, wherein the managed application package is installed on the plurality of devices; and

distributing the target application package to the plurality of devices, wherein the target application package is stored in a local storage area, and the loader intercepts a request from the target application for access to resources referenced by the resource file, the request being redirected to the local storage area of the target application package, wherein the loader and the target application are executed by at least one of the plurality of devices.

2. The method of claim 1, wherein the executables file for the managed application package comprises bytecode configured to be executed by a virtual machine.

3. The method of claim 1, wherein the executables file for the managed application package comprises native code.

4. The method of claim 1, further comprising extracting the public resource for the target application from a target application package.

5. The method of claim 1, wherein the public resource comprises an application icon for the target application.

6. The method of claim 1, further comprising defining an initiator component in the manifest file, wherein the initiator component is configured to cause the loader to execute.

7. The method of claim 1, wherein the target application package comprises a target application executables file stored in the local storage area, and the loader loads the target application into memory by utilizing a class loader that loads at least one executable stored within the target application executables file into memory.

15. The non-transitory computer-readable medium of claim 7, wherein the target application package comprises a target application executables file stored in the local storage area, and the loader loads the target application into memory by utilizing a class loader that loads at least one executable stored within the target application executables file into memory.

8. A non-transitory computer-readable medium storing a plurality of computer instructions executable by a computing device for generating a managed application package for distribution to a plurality of devices, the managed application package being based on a target application package, the plurality of computer instructions being configured to cause the computing device to at least:

generate an executables file for a managed application, wherein the executables file comprises an executable for a loader that is configured to load a target application into memory;

generate a resource file for the managed application, wherein the resource file comprises a public resource for the target application;

generate a manifest file for the managed application, wherein the manifest file comprises manifest data for the target application;

bundle the executables file, the resource file, and the manifest file into the managed application package;

distribute the managed application package to the plurality of devices for installation, wherein the managed application package is installed on the plurality of devices; and

distribute the target application package to the plurality of devices, wherein the target application package is stored in a local storage area, and the loader intercepts a request from the target application for access to resources referenced by the resource file, the request being redirected to the local storage area of the target application package, wherein the loader and the target application are executed by at least one of the plurality of devices.

9. The non-transitory computer-readable medium of claim 8, wherein the executables file further comprises an additional executable for a compliance rule enforcer for the target application.

10. The non-transitory computer-readable medium of claim 9, wherein the plurality of computer instructions are further configured to cause the computing device to at least define an initiator component in the manifest file, wherein the initiator component is configured to cause the compliance rule enforcer to execute.

11. The non-transitory computer-readable medium of claim 8, wherein the executables file comprises bytecode configured to be interpreted by a virtual machine.

12. The non-transitory computer-readable medium of claim 8, wherein the executables file comprises native code.

13. The non-transitory computer-readable medium of claim 8, wherein the plurality of computer instructions are further configured to cause the computing device to at least extract the public resource for the target application from a target application package.

14. The non-transitory computer-readable medium of claim 8, wherein the public resource comprises an application icon for the target application.

16. A system for generating a managed application package for distribution to a plurality of devices, the managed application package being based on a target application package, comprising:

a computing device; and

a managed application package generator executable by the computing device, wherein the managed application package generator, when executed by the computing device, is configured to cause the computing device to at least;

generate an executables file for the managed application package, wherein the executables file comprises an executable for a compliance rule enforcer for a target application and a loader that loads the target application into memory;

generate a resource file for the managed application package, wherein the resource file comprises a public resource for the target application;

generate a manifest file for the managed application package, wherein the manifest file comprises manifest data for the target application; and

bundle the executables file, the resource file, and the manifest file into the managed application package, wherein;

the computing device distributes the managed application package to the plurality of devices for installation, wherein the managed application package is installed on the plurality of devices; and

distribute the target application package to the plurality of devices, wherein the target application package is stored in a local storage area, and the loader intercepts a request from the target application for access to resources referenced by the resource file, the request being redirected to the local storage area of the target application package, wherein the loader and the target application are executed by at least one of the plurality of devices.

17. The system of claim 16, wherein the managed application package generator is further configured to cause the computing device to at least transmit the managed application package to a client device that is managed by an enterprise management system.

18. The system of claim 16, wherein the managed application package generator is further configured to cause the computing device to at least define an initiator component in the manifest file, wherein the initiator component is configured to load the compliance rule enforcer.

19. The system of claim 16, wherein the target application package comprises a target application executables file stored in the local storage area, and the computing device loads the target application into memory by utilizing a class loader that loads at least one executable stored within the target application executables file into memory.