GENERATING PACKAGES FOR MANAGED APPLICATIONS

• US 20160342788A1
• Filed: 05/21/2015
• Published: 11/24/2016
• Est. Priority Date: 05/21/2015
• Status: Active Grant

• Current Assignee: AirWatch LLC (Broadcom, Inc.)
• Original Assignee: AirWatch LLC (Broadcom, Inc.)
• Inventors: Xuan, Chaoting, Stuntebeck, Erich
• Granted Patent: US 10,223,526 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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, comprising:

generating an executables file for a managed application, 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, wherein the resource file comprises a public resource for the target application; and

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

2. The method of claim 1, further comprising generating an application package that comprises:

the executables file for the managed application;

the resource file for the managed application; and

the manifest file for the managed application.

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

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

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

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

7. 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.

8. A non-transitory computer-readable medium storing a plurality of computer instructions executable by a computing device, 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; and

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

9. 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 generate an application package that comprises:

the executables file for the managed application;

the resource file for the managed application; and

the manifest file for the managed application.

10. 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.

11. The non-transitory computer-readable medium of claim 10, 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.

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

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

14. 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.

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

16. A system, comprising:

a computing device; and

a managed application generator executable by the computing device, wherein the managed application generator, when executed by the computing device, is 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 compliance rule enforcer for a target application;

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

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

17. The system of claim 16, wherein the managed application generator is further configured to cause the computing device to at least generate an application package that comprises:

the executables file for the managed application;

the resource file for the managed application; and

the manifest file for the managed application.

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

19. The system of claim 16, wherein the executables file further comprises an additional executable for a loader that is configured to load the target application into memory.

20. The system of claim 16, wherein the managed application 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.