Deployment of software across an enterprise system

• US 9,720,669 B2
• Filed: 05/30/2013
• Issued: 08/01/2017
• Est. Priority Date: 05/30/2013
• Status: Active Grant

• Current Assignee: The Boeing Co.
• Original Assignee: The Boeing Co.
• Inventors: Mitchell, Alexander James, Murray, Kenneth Todd, Spassov, Miroslav Iordanov
• Primary Examiner(s): Lee, Marina
• Application Number:
  US13/905,475
• Publication Number:
  US 20140359603A1
• Time in Patent Office: 1,524 Days
• Field of Search: 717177
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates

Abstract

Software is prepared for deployment across an enterprise system. The software initially included a base package and now includes an extended package. The extended package includes duplicate files and new files with respect to the base package. A method comprises using a computer to create indices of files for each of the base and extended packages, the indices identifying properties of the files; compare the properties of the files listed in the indices to identify the duplicate files and the new files in the extended package; and create a deployment package that includes only the new files.

Claims

1. A method of preparing software for deployment across an enterprise system, the software including a base package and an extended package, the extended package including duplicate files and new files with respect to the base package, the method comprising using a computer to:

create indices of files for each of the base and extended packages;

compute a hash of each one of the files in the indices for each of the base and extended packages to produce a fingerprint for each one of the files;

iterate the indices of the base and extended packages to identify the duplicate files, wherein the fingerprints are compared to identify the duplicate files and the new files in the extended package; and

create, at the computer, a deployment package that includes only the new files for installation on an end user computer in the enterprise system wherein the deployment package also includes a first validation file that identifies all files that should be installed on the end user computer;

the method further comprising using the end user computer to install the deployment package and create a second validation file for those files actually installed on the end user computer, and compare the first and second files, whereby installation is successful if the first and second validation files are identical.

2. The method of claim 1, further comprising sorting the packages by size.

3. The method of claim 1, further comprising sending the deployment package to a plurality of end user computers in the enterprise system.

4. The method of claim 1, wherein when a new extended package is made available, a new file index is created for the new extended package, and the new file index is compared to file indices of the earlier extended package to identify new files in the new extended package;

and wherein a new deployment package is created from only the new files in the new extended package.

5. The method of claim 4, wherein the deployment packages are unlinked.

6. The method of claim 4, wherein identifying the duplicate files includes comparing each extended package only to its immediate previous package.

7. The method of claim 1, wherein the software is CAD/CAM software, and wherein each package has at least 100,000 files.

8. The method of claim 1, wherein user-specific information is removed from the new files prior to creation of the deployment package, whereby an end user can add user-specific information after installation of the deployment package.

9. The method of claim 1, wherein creating the deployment package includes creating compressed files while enforcing number and file size requirements per compressed file.

10. A system comprising a first computer and an end user computer, the first computer programmed to:

create indices of files for an extended software package and a previous package, the indices identifying properties of the files for each of the extended software package and the previous package, the extended package including all files of the previous package plus new files;

compare the properties of the files listed in the indices to identify duplicate files in the extended package and the new files in the extended package; and

create, at the first computer, a deployment package that includes only the new files in the extended package for installation on the end user computer and also a first validation file that identifies all files that should be installed on an end user computer;

the end user computer programmed to install the deployment package and create a second validation file for those files actually installed on the end user computer, and compare the first and second files, whereby installation is successful if the first and second validation files are identical.

11. The system of claim 10, wherein the first computer is programmed to create a cryptographic hash function for each file;

and wherein the first computer is programmed to compare the files by comparing the cryptographic hash functions.

12. The system of claim 10, wherein the first computer is further programmed to send the deployment package to the end user computer and other end user computers in an enterprise system.

13. The system of claim 10, wherein identifying the duplicate files includes:

computing a hash of each one of the files in the indices to produce a fingerprint for each one of the files; and

iterating the indices of the base and extended packages to identify the duplicate files, wherein the fingerprints are compared to identify the duplicate files and the new files in the extended package.