US8726271B1 - Method and system for installing software - Google Patents

Method and system for installing software Download PDF

Info

Publication number
US8726271B1
US8726271B1 US11/322,491 US32249105A US8726271B1 US 8726271 B1 US8726271 B1 US 8726271B1 US 32249105 A US32249105 A US 32249105A US 8726271 B1 US8726271 B1 US 8726271B1
Authority
US
United States
Prior art keywords
software application
installation
template
computing system
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US11/322,491
Inventor
Richard Douglas Weathersby
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
United Services Automobile Association (USAA)
Original Assignee
United Services Automobile Association (USAA)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by United Services Automobile Association (USAA) filed Critical United Services Automobile Association (USAA)
Priority to US11/322,491 priority Critical patent/US8726271B1/en
Assigned to UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA) reassignment UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA) ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: WEATHERSBY, RICHARD DOUGLAS
Application granted granted Critical
Publication of US8726271B1 publication Critical patent/US8726271B1/en
Application status is Active legal-status Critical
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment
    • G06F8/61Installation
    • G06F8/63Image based installation; Cloning; Build to order
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management

Abstract

Method and system are disclosed for providing multiple installations of a software application. The method/system creates an installation template from a single correct or “golden” installation of the software application and uses the installation template to produce additional installations of the software application. In one embodiment, any references to a specific host or computing system in the files or directories of the installed software application are replaced with a temporary variable in the installation template. The installation template may then be stored on a designated server and uploaded to any computing system needing a new installation of the software application. Once uploaded, the variable is replaced with system-specific references to complete the new installations. Since the installations are produced from the installation template and not from floppy disks or CD-ROMs, the process takes significantly less time.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related in subject matter to, and hereby incorporates by reference, the following co-pending U.S. patent application Ser. No. 11/322,403, entitled METHOD AND SYSTEM FOR INSTALLING SOFTWARE, filed Dec. 30, 2005 (Applicant Reference No. US-0077.02); application Ser. No. 11/322,494, entitled METHOD AND SYSTEM FOR INSTALLING SOFTWARE, filed Dec. 30, 2005 (Applicant Reference No. US-0077.03); and application Ser. No. 11/323,207, entitled METHOD AND SYSTEM FOR INSTALLING SOFTWARE, filed Dec. 30, 2005 (Applicant Reference No. US-0077.01).

TECHNICAL FIELD

The disclosed embodiments relate generally to software applications and particularly to a method and system for installing the software applications on multiple computing systems.

BACKGROUND

Advances in software programming and computing technology have made increasingly sophisticated and feature-rich software applications available to consumers and businesses alike. These powerful software applications provide a growing list of benefits in terms of improved accuracy, efficiency, and convenience for numerous tasks performed on a regular basis. Industry indicators predict that this trend is likely to continue and may even accelerate in the years ahead.

However, as software applications become more sophisticated, their installation and maintenance become correspondingly more difficult. E-commerce and online transaction-related software applications are particularly unwieldy in terms of size and complexity. Consequently, most companies retain a highly-trained technical support group or department dedicated to setting up and supporting various software applications used within their organizations. Users who need a software application may simply submit a request through the appropriate channels listing their specific requirements. The technical support department thereafter prepares the needed computing system (i.e., hardware and operating system), installs the requested software application, and presents the completed installation to the users.

An example of the procedure described above is illustrated in FIG. 1 via a system 100. A user 102 of the system 100 begins the procedure by submitting a request for a particular software application through designated channels to an organization's technical support department. Technical support personnel then obtain an appropriate computing system 104 a, 104 b, or 104 c for installation of the requested software application, perform the installation, and test the installed software application to ensure proper operation. The installations are usually performed manually by inserting one or more portable media 106 (e.g., floppy disks or CD-ROMs) into an appropriate disk drive of the selected computing system 104 a, 104 b, or 104 c, usually one disk at a time. After the installation is complete, the technical support personnel either physically deliver the computing system 104 a, 104 b, or 104 c to the user or else make it available over a network connection (not expressly shown).

A drawback of the above procedure is that every request for the software application must be installed from the beginning on each computing system 104 a, 104 b, and 104 c via the portable media 106. Even for highly-trained technical support personnel, such a procedure is often fraught with potential problems and delays. For example, in addition to the lengthy installation time required, hardware and/or software incompatibilities may exist (e.g., a resource conflict between the operating system and the software application). Furthermore, the software application may require one or more patches or fixes, sometimes in a certain sequence or order, that can add to an already long installation time. Moreover, there may sometimes be human errors, such as clicking the wrong button, striking the wrong key, inserting the wrong disk, and so forth, that frequently lengthen the installation time even more. All of these problems are exacerbated when the software application is large, complex, and is required to be installed numerous times on multiple computing systems.

Accordingly, what is needed is a more efficient way to make a software application available on multiple computing systems without having to install the software application from the beginning via floppy disks, CD-ROMs, or other portable media for each computing system.

SUMMARY

The disclosed embodiments are directed to a method and system for providing multiple installations of a software application. The method/system creates an installation template from a single correct or “golden” installation of the software application and uses the installation template to produce additional installations of the software application. In one embodiment, any references to a specific host or computing system in the files or directories of the installed software application are replaced with a temporary variable in the installation template. The installation template may then be stored on a designated server and uploaded to any computing system needing a new installation of the software application. Once uploaded, the variable is replaced with system-specific references to complete the new installation. Since the installations are produced from the installation template and not from floppy disks or CD-ROMs, the process takes significantly less time.

In general, in one aspect, the embodiments are directed to a method of distributing multiple instances of a software application over a network. The method comprises creating an installation template of a software application, the installation template containing configuration directories and configuration files for the software application. The method further comprises using one or more software tools to transfer the installation template to a computing system over a network, retrieve the configuration directories and the configuration files from the installation template, and insert in the configuration directories and the configuration files any computing system-specific references required by the software application with respect to the computing system.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other advantages of the invention will become apparent from the following detailed description and upon reference to the drawings, wherein:

FIG. 1, previously described, illustrates a system for installing multiple instances of a software application according to the prior art;

FIG. 2 illustrates a system for installing multiple instances of a software application;

FIG. 3 illustrates a computing system for installing multiple instances of a software application;

FIG. 4 illustrates another system for installing multiple instances of a software application;

FIG. 5 illustrates an installation tool for installing multiple instances of a software application; and

FIG. 6 illustrates a method for installing multiple instances of a software application.

DETAILED DESCRIPTION

Following is a detailed description of illustrative embodiments with reference to the drawings wherein the same reference labels are used for the same or similar elements. As used throughout this description and the claims, the terms “a” and “an” are intended to mean “one or more.”

As mentioned above, existing procedures for installing multiple instances of a software application, particularly a large and complex software application, are inefficient and fraught with potential problems and delays. Various embodiments provide a method and system for more efficiently installing software applications. A correct or “golden” (i.e., error-free) installation of a software application is used to create an installation template. The installation template may then be uploaded to any computing system requiring a copy of the software application. Since the installation template is based on a correctly-installed instance of the software application, all subsequent installations made from the installation template are also correct. And since the subsequent installations are made from the installation template, the process takes significantly less time.

FIG. 2 illustrates a system 200 that may be used for providing multiple installations of a software application. The system 200 includes a technical support computing system 202 (also referred to herein as a template server) connected to a number of user computing systems 204 a, 204 b, and 204 c over a network 206. A software application is installed from the portable media 106 onto the template server 202 (e.g., by technical support or other appropriate personnel) instead of one or more of the computing systems 204 a, 204 b, or 204 c. The installed software application is subsequently used to create an installation template from which further installations of the software application may be performed. The installation template may then be transferred to each user computing system 204 a, 204 b, or 204 c as needed over the network 206 to install the software application. Such an arrangement allows additional installations of the software application to be created on the user computing systems 204 a, 204 b, and 204 c, perhaps without resorting to the portable media 106.

FIG. 3 illustrates the template server 202 in more detail. In the implementation shown, the template server 202 includes a bus 300 or other communication mechanism for communicating information and a processor 302 coupled with the bus 300 for processing information. The template server 202 also includes a main memory 304, such as a random access memory (RAM) or other dynamic storage device, coupled to the bus 300 for storing computer-readable instructions to be executed by the processor 302. The main memory 304 also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor 302. The template server 202 further includes a read-only memory (ROM) 306 or other static storage device coupled to the bus 300 for storing static information and instructions for the processor 302. A computer-readable storage device 308, such as a magnetic disk or optical disk, is coupled to the bus 300 for storing information and instructions for the processor 302.

The template server 202 may be coupled via the bus 300 to a display 310, such as a cathode ray tube (CRT), for displaying information to a user. An input device 312, including, for example, alphanumeric and other keys, is coupled to the bus 300 for communicating information and command selections to the processor 302. Another type of user input device is a cursor control 314, such as a mouse, a trackball, or cursor-direction keys for communicating direction information and command selections to the processor 302 and for controlling cursor movement on the display 310. The cursor control 314 typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

The term “computer-readable instructions” as used above refers to any instructions that may be performed by the processor 302 and/or other components. Similarly, the term “computer-readable medium” refers to any storage medium that may be used to store the computer-readable instructions. Such a medium may take many forms, including, but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media include, for example, optical or magnetic disks, such as the storage device 308. Volatile media include dynamic memory, such as main memory 304. Transmission media include coaxial cables, copper wire and fiber optics, including wires of the bus 300. Transmission media can also take the form of acoustic or light waves, such as those generated during radio frequency (RF) and infrared (IR) data communications. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, DVD, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read.

Various forms of the computer-readable media may be involved in carrying one or more sequences of one or more instructions to the processor 302 for execution. For example, the instructions may initially be borne on a magnetic disk of a remote computer. The remote computer can load the instructions into its dynamic memory and send the instructions over a telephone line using a modem. A modem local to the template server 202 can receive the data on the telephone line and use an infrared transmitter to convert the data to an infrared signal. An infrared detector coupled to the bus 300 can receive the data carried in the infrared signal and place the data on the bus 300. The bus 300 carries the data to the main memory 304, from which the processor 302 retrieves and executes the instructions. The instructions received by the main memory 304 may optionally be stored on the storage device 308 either before or after execution by the processor 302.

The template server 202 also may include a communication interface 316 coupled to the bus 300. The communication interface 316 provides a two-way data communication coupling between the template server 202 and the network 206. For example, the communication interface 316 may be an integrated services digital network (ISDN) card or a modem used to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface 316 may be a local area network (LAN) card used to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface 316 sends and receives electrical, electromagnetic, optical, or other signals that carry digital data streams representing various types of information.

In one embodiment, a software application 318 is installed on the template server 202, for example, on the storage device 308. The installed software application 318 may then be used to create an installation template 320 from which subsequent installations of the software application 318 may be made. The installation template 320 may thereafter be transferred to each user computing system 204 a, 204 b, or 204 c as needed over the network 206 to install the software application 318. Such an arrangement allows additional installations of the software application 318 to be created on the user computing systems 204 a, 204 b, and 204 c, perhaps without resorting to the portable media 106 (see FIG. 1).

The installed software application 318 is preferably a correct or “golden” installation, meaning that it has been tested and observed to work properly and that all needed patches, fixes, modifications, and customizations have been applied. The use of a “golden” installation ensures that the installation template 320 is correct and that installations of the software application 318 based on the installation template 320 are also correct. To this end, the installation of the software application 318 is preferably performed manually from original portable media 106. Although this task is tedious and time-consuming, it need only be performed correctly once to create the installation template 320. It is also possible to install the software application 318 from, for example, a set of installation files stored on an application server (not expressly shown). If necessary, a trial-and-error approach may be used and the installation repeated until the software application 318 is determined to be correctly installed, (i.e., a “golden” installation).

In some cases, the installation of the software application 318 may produce one or more custom files and/or directories that are specific to the host computing system (i.e., the template server 202). The term “directories” as used herein refers to all types of directories, including main directories and sub-directories. Certain enterprise integration software applications, for example, WebSphere™ from International Business Machine (IBM) Corp., create directories that contain the name of the host computing system in the directories (e.g., “/WebSphere/AppServer/ . . . /ServerA/ . . . ”). One or more files for these software applications, including the configuration files, may also contain references to the host computing system. An example of a WebSphere™ directory listing taken using a standard “dir” command is shown in Example 1, where some of the directories have been truncated for economy of the description.

/opt/WebSphere51/DeploymentManager/temp/testopslasjtManager

/opt/WebSphere51/DeploymentManager/logs/preload

/opt/WebSphere51/DeploymentManager/installedApps/testopslasjtNetwork

/opt/WebSphere51/DeploymentManager/config/temp/cells/testopslasjtNetwork/nodes/

/opt/WebSphere51/DeploymentManager/config/temp/cells/testopslasjtNetwork

/opt/WebSphere51/DeploymentManager/config/cells/testopslasjtNetwork/nodes/testopslasjt

/opt/WebSphere51/DeploymentManager/config/cells/testopslasjtNetwork/opt/WebSphere51/

/opt/WebSphere51/DeploymentManager/bin/wsinstance/configdefaults/cells/testopslasjt

/opt/WebSphere51/AppServer/logs/preload

/opt/WebSphere51/AppServer/installedApps/

/opt/WebSphere51/AppServer/config/temp/cells/testopsllsjtNetwork/nodes/testopslasjt

/opt/WebSphere51/AppServer/config/cells/testopsllsjtNetwork/nodes/testopslasjt

/opt/WebSphere51/AppServer/config/backup/base/cells/testopslasjt/nodes/testopslasjt

/opt/WebSphere51/AppServer/config/backup/base/cells/testopslasjt

/opt/WebSphere51/AppServer/bin/wsinstance/configdefaults/cells/testopslasjt/nodes/

/opt/WebSphere51/AppServer/bin/wsinstance/configdefaults/cells/testopslasjt

Example 1

As can be seen from the above example, a number of directories have names that contain a reference to a specific computing system, namely, “testopslasjt.” Therefore, for software applications such as WebSphere™, the installed software application 318 must be generalized before the installation template 320 is crea2erjted. This means that references to a specific computing system (e.g., the template server 202) may be temporarily replaced with a generic reference (e.g., “RICK”) or variable (e.g., “X”) before creating the installation template 320. The generic reference or variable may then be replaced with the name of one of the user computing systems 204 a, 204 b, or 204 c (e.g., Server A, Server B, Server C, etc.) when the installation template 320 is used to install the software application 318 on that user computing system.

In one embodiment, the template server 202 further includes one or more scripting routines 322 stored, for example, on the storage device 308, that are designed to remove specific references to the host computing system. The scripting routines 322 may reside on the template server 202 as shown in this example, or they may reside on some other computing system, then executed on the template server 202 over the network 206. When executed, the scripting routines 322 may recursively search through the directory names of the installed software application 318 looking for any computing system-specific directory names. The scripting routines 322 also search the content of all files for computing system-specific references in the files. The scripting routines 322 thereafter search for the found references, if any, and replace them with a temporary generic reference or variable.

An example of a PERL language scripting routine 322 for compressing the installed files of the software application 318 and for searching and replacing computing system-specific references in the files and directories of the software application 318 in a UNIX-based operating system is shown in Example 2 below. The various commands and statements used in such a scripting routine are believed to be well-understood by those having ordinary skill in the art and will therefore not be described in detail here. Other scripting routines for other operating systems (e.g., Solaris, Linux, Windows, DOS, etc.) running on the template server 202 may also be used without departing from the scope of the invention. Although the compression and file name and directory name searches have been combined in Example 2, it is certainly possible to create separate scripting routines 322 for the compression and the file name and directory name searches without departing from the scope of the invention. When searching and replacing directory names, the scripting routines 322 may proceed through the directory structure in reverse order (i.e., deepest sub-directories first). Otherwise, one or more child directories may not be accessible once the parent directory names have been changed.

#!/usr/bin/per1
###########################################
## This script creates the tar ball install ###
## template and replaces all of the hostname ###
## entries and replaces them with the variable ###
##       RICK ###
##     (directories and files) ###
###########################################
use File::Copy;
my $OS = ${circumflex over ( )}O;
chomp($OS);
print “OS = $OS\n”;
my $HOST = ‘hostname’;
chomp($HOST);
print “Host = $HOST\n”;
my $appFile = ‘/tmp/FILES.txt’;
if( -e $appFile ){ ‘rm $appFile’; }
my $dirFile = ‘/tmp/DIRS.txt’;
if(  -e $dirFile ){ ‘rm $dirFile’; }
my $fileCounter=0;
my $dirCounter=0;
my $Variable = “RICK”;
    #------- Obtaining List of Files to Modify -------------------#
    my @files = ‘find /opt/WebSphere51/ -type f -exec grep -q \“$HOST\” { } \\\; -print
> $appFile 2>/dev/null’;
    #------- Obtaining List of Directories to Modify -----------#
    my @dirs = ‘find /opt/WebSphere51/ -type d -name \“$HOST*\” > $dirFile
2>/dev/null’;
sleep(5);
#--------------------------------------------------------------#
#--- Changing files: hostname to RICK   -------#
#--------------------------------------------------------------#
open(APPFILE, “$appFile”);
@files=<APPFILE>;
close(APPFILE);
foreach $item ( @files )  {
   chomp($item);
   print “File: \t $item\n”;
   $itemBackup = $item .  “.BAK”;
   print “\t\tCopying $item to $itemBackup . . . \n”;
   move($item, $itemBackup) or die “Copy failed for $item: $!”;
   print “\t\tReplacing $HOST with $Variable . . . \n”;
   my $replace = ‘sed -e ‘s/$HOST/$Variable/g’ $itemBackup >> $item’;
   $fileCounter++;
}
print “NUMBER OF FILES CHANGED: $fileCounter\n”;
#-----------------------------------------------------------------#
#--- Changing directories: hostname to RICK    --#
#----------------------------------------------------------------#
sub backwards {$b cmp $a};
open(DIRFILE, “$dirFile”);
@dirs=<DIRFILE>;
close(DIRFILE);
my @SortedDirs = sort backwards(@dirs);
print “SORTED ARRAY:  \n@SortedDirs\n\n”;
foreach $item ( @SortedDirs ) {
     chomp($item);
    if( $item =~ /$HOST/i     ) {
     if( -d $item ) {
       print “\n ........New Entry.................\n”;
       print “Directory: \t $item\n”;
      my $orig = $item;
       $length = length($item);
       $sub = rindex($item, $HOST);
      $original = substr($item,$sub, $length);
      print “ORIGINAL = $original\n”;
      (my $Var = $original) =~ s/$HOST/$Variable/;
      print “Var = $Var  \n\n”;
       $substring = substr($item, 0, $sub);
       print “SubString: \t$substring\n”;
       $substring .= $Var;
      print “Final Substring: ..... $substring\n”;
      my $new = $substring;
      print “New Directory: $new\n”;
      print “Moving $orig to $new ..... \n”;
      ‘mv $orig $new’;
      $dirCounter++;
     }
    }
}
print “NUMBER OF DIRECTORIES CHANGED: $dirCounter\n”;
print “Removing all backpFiles made during this process ..... \n\n”;
my $BAK = ‘find /opt/WebSphere51/ -type f -name “*.BAK” | xargs rm’;
print “Process in complete ...... Installation template is ready to be tared up
.... \n\n”;
#-----------------------------------------------------------#
#---- Removing /wstemp & /config/temp dirs ------#
#-----------------------------------------------------------#

Example 2

After the software application 318 has been generalized, it may be used to create the installation template 320. To create the installation template 320, an archive or backup is made of the installed files of the generalized software application 318. The archive or backup may be compressed, or it may simply be backed up without any compression. The compression may be performed using any suitable compression format (e.g., .ZIP, .TAR, .RAR, etc.), provided that the directory structure for the compressed files is maintained.

In some cases, the installation template 320 may include more than one archive or backup file. For example, the archive or backup files may be organized according to their functions in the software application 318 or some other logical grouping, such as application server files and directories in one installation template file, deployment manager files and directories in another installation template file, and so forth. Note that the installed files of the software application 318 are used for the installation template 320 and perhaps not everything else on the computing system 202 (i.e., the installation template 320 is not an image of the hard drive of the computing system 202).

After the installation template 320 is created, it may be uploaded to any user computing system 204 a, 204 b, or 204 c requiring an instance of the software application 318. The upload may be conducted by a direct file transfer from the template server 202 to a user computing system 204 a, 204 b, or 204 c, or may be conducted over the network 206. The latter case allows any user computing system 204 a, 204 b, or 204 c connected to the network 206 to receive a copy of the installation template 320 regardless of the physical location of the template server 202. Such an arrangement may result in a much more efficient and convenient installation procedure than having to install the software application 318 manually on each computing system from the portable media 106.

Once uploaded, the installation template 320 may be decompressed, unpacked, expanded, or otherwise processed to retrieve the files and directories of the software application 318 onto the new user computing system 204 a, 204 b, or 204 c. The generic reference or variable may then be replaced with the name of the new user computing system. In some embodiments, the scripting routines 322 mentioned earlier may be used to perform the decompression/unpacking of the installation template 320 and insert the name of the new user computing system 204 a, 204 b, or 204 c. An example of a PERL language scripting routine 322 that may be used to decompress/unpack the installation template 320 and insert the name of the new user computing system 204 a, 204 b, or 204 c in a UNIX-based operating system is shown in Example 3 below. Other scripting routines may be used for other operating systems (e.g., Solaris, Linux, Windows, DOS, etc.) without departing from principles of the invention.

#!/usr/bin/per1
########################################### ###
## This script transforms the tar ball install ###
## template and replaces all of the “RICK” ###
## entries and replaces them with the hostname ###
##    of the node ..... ###
##     (directories and files) ###
########################################### ###
use File::Copy;
my $OS = ${circumflex over ( )}O;
chomp($OS);
print “OS = $OS\n”;
my $HOST = ‘hostname’;
chomp($HOST);
print “Host = $HOST\n”;
my $appFile = ‘/tmp/FILES2.txt’;
if( -e $appFile ){ ‘rm $appFile’; }
my $dirFile = ‘/tmp/DIRS2.txt’;
if(  -e $dirFile ){ ‘rm $dirFile’; }
my $fileCounter=0;
my $dirCounter=0;
my $Variable = “RICK”;
my $date = ‘date’;
chomp($date);
print “$date\n”;
    #------- Obtaining List of Files to Modify -------------------#
    my @files = ‘find /opt/WebSphere51/ -type f -exec grep -q \“$Variable\” { } \\\; -
print > $appFile 2>/dev/null’;
    #------- Obtaining List of Directories to Modify -----------#
    my @dirs = ‘find /opt/WebSphere51/ -type d -name \“$Variable*\” > $dirFile
2>/dev/null’;
sleep(5);
#--------------------------------------------------------------#
#--- Changing files: hostname to RICK    -------#
#--------------------------------------------------------------#
open(APPFILE, “$appFile”);
@files=<APPFILE>;
close(APPFILE);
foreach $item ( @files )  {
   chomp($item);
   print “File: \t $item\n”;
   if(-f $item) {
      $itemBackup = $item .  “.BAK”;
      print “\t\tCopying $item to $itemBackup . . . \n”;
      move($item, $itemBackup) or die “Copy failed for $item: $!”;
      print “\t\tReplacing $Variable with $HOST . . . \n”;
      my $replace = ‘sed -e ‘s/$Variable/$HOST/g’ $itemBackup >> $item’;
      $fileCounter++;
      unlink($itemBackup);
   }
}
print “NUMBER OF FILES CHANGED: $fileCounter\n”;
#-----------------------------------------------------------------#
#---   Changing directories: hostname to RICK    --#
#-----------------------------------------------------------------#
sub backwards {$b cmp $a};
open(DIRFILE, “$dirFile”);
@dirs=<DIRFILE>;
close(DIRFILE);
my @SortedDirs = sort backwards(@dirs);
print “SORTED ARRAY:  \n@SortedDirs\n\n”;
foreach $item1 ( @SortedDirs ) {
     chomp($item1);
    if( $item1 =~ /$Variable/i  ) {
     if( -d $item1 ) {
       print “\n ........New Entry.................\n”;
       print “Directory: \t $item1\n”;
      my $orig = $item1;
       $length = length($item1);
       $sub = rindex($item1, $Variable);
      $original = substr($item1,$sub, $length);
      print “ORIGINAL = $original\n”;
      (my $Var = $original) =~ s/$Variable/$HOST/;
      print “Var = $Var  \n\n”;
       $substring = substr($item1, 0, $sub);
       print “SubString: \t$substring\n”;
       $substring .= $Var;
      print “Final Substring: ..... $substring\n”;
      my $new = $substring;
      print “New Directory: $new\n”;
      print “Moving $orig to $new ..... \n”;
      ‘mv $orig $new’;
      $dirCounter++;
     }
    }
}
print “\n\nNUMBER OF DIRECTORIES CHANGED: $dirCounter\n”;
print “$date\n”;
print “\n +++++ Removing Temp Files ......+++++++\n”;
my $tempFiles = ‘rm /tmp/FILES*’;
my $tempDirs = ‘rm /tmp/DIRS*’;
print “\n\n +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n”;
print “ +++++++++++++++++ PLEASE LOG OUT AS ROOT NOW ++++++++++++++++\n”;
print “ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\n\n”;
#-----------------------------------------------------------#
#---- Removing /wstemp & /config/temp dirs ------#
#-----------------------------------------------------------#

Example 3

Thus far, the discussion has centered around creation of the installation template 320 on the template server 202. From there, the template server 202 may be uploaded to a selected computing system and decompressed/unpacked to complete installation of the software application 318. A technical support person usually performs the various tasks described (e.g., uploading, decompressing/unpacking, inserting computing system-specific references, etc.). In some embodiments, however, the technical support person may automate the various tasks by providing the installation template 320 to an installation tool along with the required scripting routines 322. The installation tool thereafter performs the uploading, decompressing/unpacking, insertion of computing system-specific references, and other related tasks as needed (e.g., in real time) or according to some predetermined schedule set by the technical support person.

FIG. 4 illustrates a system 400 in which an installation tool may be used for automatically providing multiple installations of a software application. The system 400 is similar to the system 200 of FIG. 2 except that a deployment server 402 has been connected to the network 206. The deployment server 402 is likewise similar to the template server 202 except that the computer-readable storage device of the deployment server 402 contains, among other things, an installation tool. Once the installation template 320 has been created, the technical support person may deposit or otherwise transfer the installation template 320, along with any required scripting routines 322, to the deployment server 402. The installation tool on the deployment server 402 thereafter performs the various installation-related tasks either as needed (e.g., in real time) or according to some predetermined schedule set by the technical support person.

FIG. 5 illustrates the installation tool of the deployment server 402 in more detail. As can be seen, an installation tool 500 includes or has access to a number of components needed for installing multiple instances of the software application 318. For example, the installation tool 500 includes or has access to the installation template 320, a file transfer program 502 for uploading the installation template 320 to a desired user computing system 204 a, 204 b, or 204 c, a decompression/unpacking program 504 for decompressing/unpacking the installation template 320, and one or more scripting routines 322 for removing generic references and inserting computing system-specific references into the software application 318. Other components that may be present include a user interface 506 for allowing the technical support person to interact with the installation tool 500. An example of such an installation tool is BladeLogic™ available from BladeLogic Corp. of Waltham, Mass.

In operation, the technical support person selects the particular user computing system 204 a, 204 b, or 204 c on which to install the software application 318 through the user interface 506. In some embodiments, the technical support person also specifies when the installation is to take place. The installation tool 500 thereafter automatically performs the installation in the manner described above at the appropriate date and time. The date and time of the installation may be in real time, according to some predetermined schedule, or may occur based on some other condition or criteria. Once the installation is complete, the software application 318 is ready to be used on the new user computing system 204 a, 204 b, or 204 c in significantly less time compared to installation from the portable media 106.

FIG. 6 illustrates a method 600 that may be used to install a software application. The method 600 begins at step 602, where an installation of the software application is performed. This installation may be accomplished using the original portable media in order to ensure a correct installation. Any patches, fixes, modifications, or customizations that may be needed are also applied to the software application at this time. Once a correct installation of the software application has been completed, computing system-specific references in the files, directories, and sub-directories of the installed software application may be replaced with a generic reference or variable at step 604. At step 606, an installation template is created from the files, directories, and sub-directories of the installed software application. In various embodiments, the installation template may be one or more compressed files containing all the files in the software application and their directory structures. In various other embodiments, the installation template is simply a backup or archive of the installed files and directory structure of the software application.

At step 608, the installation template is uploaded to a selected user computing system. The upload may occur over a network or it may be performed from one computing system (e.g., the template server 202) to another computing system. At step 610, the installation template is decompressed/unpacked or otherwise processed to place the files, directories, and subdirectories of the software application on the selected computing system. Generic references or variables may then be replaced with the name of the selected user computing system at step 612 to complete the installation of the software application on the selected computing system. This step may be done either manually by technical support personnel or via an automated installation tool such as BladeLogic™. At step 614, a determination may be made as to whether additional installations of the software application are needed. If the answer is yes, the method 600 returns to step 608 and the installation is repeated for the next computing system. If the answer is no, the method 600 is concluded.

The foregoing embodiments have been described with respect to the installation of a complex software application across an organization's local or private network. However, the embodiments are not limited thereto and may be used to install any software application across any network, including the Internet. In the latter case, the installation template may be stored on a web server and made available through a web site hosted by the web server. The installation template may then be downloaded and used to install a software application as needed. The download may occur free of charge (e.g., freeware, shareware), or as part of an online purchase or other e-commerce transaction (preferably with the appropriate security mechanisms in place). In such embodiments, the provider of the installation template may be a retailer of the software application and the receiver of the installation template may be a purchaser of the software application.

Any compression algorithms, scripting routines (e.g., for handling computing system-specific references), or other software tools may be transferred along with the installation template to the selected computing system. Alternatively, instead of several separate software tools, all required software tools may be bundled together in a single executable program (e.g., a “setup” file) written and compiled in an appropriate programming language (e.g., Java, Flash, Html, Xml, C++, etc.) and subsequently transferred to and executed on the selected computing system. In some embodiments, the executable program containing the software tools may be combined with the installation template as a single file. In any event, the above arrangement allows businesses and consumers alike to benefit from the highly efficient installation system and method discussed herein.

While the embodiments have been described with reference to one or more particular embodiments, those skilled in the art will recognize that many changes may be made thereto. Therefore, each of the foregoing embodiments and obvious variations thereof is contemplated as falling within the spirit and scope of the claimed invention, which is set forth in the following claims.

Claims (21)

What is claimed is:
1. A method of distributing a software application over a network with a computing device having a computer processor and computer-readable instructions stored on a non-transitory computer-readable storage medium and executable by the computer processor, the method comprising:
installing a software application on a template server;
creating an installation template of the software application using details of the installation of the software application on the template server, said installation template containing configuration directories and configuration files for said software application, wherein specific reference to the template server is replaced in said configuration directories and configuration files with a generic reference; and
using one or more software tools to transfer said installation template to a computing system over a network, retrieve said configuration directories and said configuration files from said installation template, and replace the generic reference in said configuration directories and said configuration files with any computing system-specific references required by said software application with respect to said computing system.
2. The method according to claim 1, wherein said network is the Internet.
3. The method according to claim 2, wherein said installation template is made available through a web site and said computing system is operated by a purchaser of said software application.
4. The method according to claim 2, wherein said one or more software tools used to retrieve and insert are transferred to said computing system along with or as part of said installation template.
5. The method according to claim 1, wherein said network is a private network of an organization.
6. The method according to claim 5, wherein said one or more software tools are controllable by a technical support person of said organization to automatically perform said transfer, said retrieve, and said insert.
7. The method according to claim 1, wherein said one or more software tools are stored on a deployment server for deploying said installation template over said network.
8. A system for distributing a software application over a network, said system comprising at least one subsystem, wherein the subsystem includes a computing device having a computer processor and computer-readable instructions stored on a non-transitory computer-readable storage medium and executable by the computer processor, to:
install a software application on a template server;
create an installation template of the software application using details of the installation of the software applicatoin on the template server, said installation template containing configuration directories and configuration files for said software application, wherein specific reference to the template server is replaced in said configuration directories and configuration files with a generic reference; and
use one or more software tools to transfer said installation template to a computing system over a network, retrieve said configuration directories and said configuration files from said installation template, and replace the generic reference in said configuration directories and said configuration files with any computing system-specific references required by said software application with respect to said computing system.
9. The system according to claim 8, wherein said network is the Internet.
10. The system according to claim 9, wherein said installation template is made available through a web site and said computing system is operated by a purchaser of said software application.
11. The system according to claim 9, wherein said one or more software tools used to retrieve and insert are transferred to said computing system along with or as part of said installation template.
12. The system according to claim 8, wherein said network is a private network of an organization.
13. The system according to claim 12, wherein said one or more software tools are controllable by a technical support person of said organization to automatically perform said transfer, said retrieve, and said insert.
14. The system according to claim 8, wherein said one or more software tools are stored on a deployment server for deploying said installation template over said network.
15. A computing device having a computer processor and computer-readable instructions for distributing a software application over a network stored on a non-transitory computer-readable storage medium and executable by the computer processor, said non-transitory computer-readable instructions comprising instructions for:
installing a software application on a template server;
creating an installation template of the software application using details of the installation of the software application on the template server, said installation template containing configuration directories and configuration files for said software application, wherein specific reference to the template server is replaced in said configuration directories and configuration files with a generic reference; and
using one or more software tools to transfer said installation template to a computing system over a network, retrieve said configuration directories and said configuration files from said installation template, and replace the generic reference in said configuration directories and said configuration files with any computing system-specific references required by said software application with respect to said computing system.
16. The computing device according to claim 15, wherein said network is the Internet.
17. The computing device according to claim 16, wherein said installation template is made available through a web site and said computing system is operated by a purchaser of said software application.
18. The computing device according to claim 16, wherein said one or more software tools used to retrieve and insert are transferred to said computing system along with or as part of said installation template.
19. The computing device according to claim 15, wherein said network is a private network of an organization.
20. The computing device according to claim 19, wherein said one or more software tools are controllable by a technical support person of said organization to automatically perform said transfer, said retrieve, and said insert.
21. The computing device according to claim 15, wherein said one or more software tools are stored on a deployment server for deploying said installation template over said network.
US11/322,491 2005-12-30 2005-12-30 Method and system for installing software Active 2031-01-16 US8726271B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/322,491 US8726271B1 (en) 2005-12-30 2005-12-30 Method and system for installing software

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/322,491 US8726271B1 (en) 2005-12-30 2005-12-30 Method and system for installing software
US14/249,585 US9513890B1 (en) 2005-12-30 2014-04-10 Method and system for installing software

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/249,585 Continuation US9513890B1 (en) 2005-12-30 2014-04-10 Method and system for installing software

Publications (1)

Publication Number Publication Date
US8726271B1 true US8726271B1 (en) 2014-05-13

Family

ID=50635817

Family Applications (2)

Application Number Title Priority Date Filing Date
US11/322,491 Active 2031-01-16 US8726271B1 (en) 2005-12-30 2005-12-30 Method and system for installing software
US14/249,585 Active US9513890B1 (en) 2005-12-30 2014-04-10 Method and system for installing software

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/249,585 Active US9513890B1 (en) 2005-12-30 2014-04-10 Method and system for installing software

Country Status (1)

Country Link
US (2) US8726271B1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140359599A1 (en) * 2013-05-28 2014-12-04 Wistron Corporation Operating System Deployment Method, Server and Electronic System
US9513890B1 (en) * 2005-12-30 2016-12-06 United Services Automobile Association (Usaa) Method and system for installing software

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106648648A (en) * 2016-12-14 2017-05-10 深圳中顺易金融服务有限公司 Zookeeper-based configuration management method and system

Citations (69)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5583983A (en) 1994-11-17 1996-12-10 Objectware, Inc. Multi-platform object-oriented software development and deployment system
US5768568A (en) 1994-04-29 1998-06-16 International Business Machines Corp. System and method for initializing an information processing system
US5797015A (en) 1995-04-18 1998-08-18 Pitney Bowes Inc. Method of customizing application software in inserter systems
US5860012A (en) 1993-09-30 1999-01-12 Intel Corporation Installation of application software through a network from a source computer system on to a target computer system
US5870611A (en) 1995-04-05 1999-02-09 International Business Machines Corporation Install plan object for network installation of application programs
US6093215A (en) 1997-08-12 2000-07-25 International Business Machines Corporation Method and apparatus for building templates in a component system
US6138153A (en) 1994-02-14 2000-10-24 Computer Associates Think, Inc. System for software distribution in a digital computer network
US6151643A (en) 1996-06-07 2000-11-21 Networks Associates, Inc. Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer
US6192518B1 (en) 1998-01-22 2001-02-20 Mis Only, Inc. Method for distributing software over network links via electronic mail
US6195794B1 (en) 1997-08-12 2001-02-27 International Business Machines Corporation Method and apparatus for distributing templates in a component system
US20020016955A1 (en) 2000-06-29 2002-02-07 International Business Machines Corporation Method and system for constructing a system, drawing a system configuration drawing, and generating a system configuration file
US20020104069A1 (en) 2000-07-07 2002-08-01 Gouge Christopher S. System and method for configuring software components
US20020104080A1 (en) 2000-03-29 2002-08-01 Virtual Access Networks, Inc. Server based extraction, transfer, storage and processing of remote settings, files and data
US6490722B1 (en) 1999-03-30 2002-12-03 Tivo Inc. Software installation and recovery system
US20020188939A1 (en) 2001-06-11 2002-12-12 Siemens Medical Solutions Health Services Corporation System and user interface for generation and processing of software application installation instructions
US6499137B1 (en) 1998-10-02 2002-12-24 Microsoft Corporation Reversible load-time dynamic linking
US20030182301A1 (en) 2002-03-19 2003-09-25 Hugo Patterson System and method for managing a plurality of snapshots
US20040015957A1 (en) 2001-05-10 2004-01-22 Zara Anna M. Method to map an inventory management system to a configuration management system
US20040015959A1 (en) * 2002-06-28 2004-01-22 Hiroki Kobayashi Software installing method for setting printing environment in a computer on an individual computer basis
US20040044643A1 (en) * 2002-04-11 2004-03-04 Devries David A. Managing multiple virtual machines
US20040060045A1 (en) 2002-09-19 2004-03-25 International Business Machines Corporation Programmatic application installation diagnosis and cleaning
US6725453B1 (en) * 2000-08-23 2004-04-20 Microsoft Corporation Remote software installation and maintenance
US20040148601A1 (en) 2000-08-02 2004-07-29 Kroening James L. Method and system for calculation and use of a disk image identifer
US20040204949A1 (en) 2003-04-09 2004-10-14 Ullattil Shaji Method and system for implementing group policy operations
US20040268298A1 (en) 2003-06-30 2004-12-30 Microsoft Corporation Generation of configuration instructions using an abstraction technique
US6865737B1 (en) 2000-08-23 2005-03-08 Microsoft Corporation Remote software installation and maintenance
US20050055667A1 (en) 2003-09-05 2005-03-10 Joerg Beringer Pattern-based software design
US20050120331A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Hosting environment abstraction agents
US20050120344A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Optimal component installation
US20050120347A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Script generation engine
US6954925B1 (en) 2000-10-17 2005-10-11 Cisco Technology, Inc. Method of parsing commands using linear tree representation
US20050251786A1 (en) 2004-05-07 2005-11-10 International Business Machines Corporation System and method for dynamic software installation instructions
US20050262503A1 (en) 2004-05-21 2005-11-24 Computer Associates Think, Inc. Distributed installation configuration system and method
US6973647B2 (en) 2000-07-15 2005-12-06 International Business Machines Corporation Preferable modes of software package deployment
US20060015839A1 (en) 2003-03-26 2006-01-19 Peter Owens Development of software systems
US20060048129A1 (en) 2004-08-31 2006-03-02 Microsoft Corporation Patch un-installation
US7093259B2 (en) 2001-12-20 2006-08-15 Cadence Design Systems, Inc. Hierarchically structured logging for computer work processing
US20060195839A1 (en) 2005-02-28 2006-08-31 Microsoft Corporation Computer system for deploying software on multiple computers
US20060206866A1 (en) 1999-05-17 2006-09-14 Invensys Systems, Inc. Methods and apparatus for control configuration using live data
US20060242626A1 (en) * 2005-04-21 2006-10-26 Pham Quang D Template configuration tool for application servers
US20060245354A1 (en) 2005-04-28 2006-11-02 International Business Machines Corporation Method and apparatus for deploying and instantiating multiple instances of applications in automated data centers using application deployment template
US7150014B2 (en) 2002-10-04 2006-12-12 Hewlett-Packard Development Company, L.P. Automatically deploying software packages used in computer systems
US20070028229A1 (en) 2005-07-28 2007-02-01 International Business Machines Corporation Method and system for dynamic generation of computer system installation instructions
US20070055972A1 (en) 2005-08-24 2007-03-08 International Business Machines Corporation Model-driven software deployment in an application server
US20070157185A1 (en) * 2005-12-30 2007-07-05 Semerdzhiev Krasimir P System and method for deployable templates
US20070162892A1 (en) * 2005-12-30 2007-07-12 Ingo Zenz Template-based configuration architecture
US20070214449A1 (en) 2004-03-02 2007-09-13 Choi Elliot M Portlet template based on a state design pattern
US20070294321A1 (en) 2003-09-30 2007-12-20 Christopher Midgley Systems and methods for backing up data files
US20080059950A1 (en) 2003-12-08 2008-03-06 Ebay Inc. Method and system to automatically generate software code
US20080127169A1 (en) 2006-08-29 2008-05-29 Ethan Malasky Software installation using template executables
US20080134163A1 (en) 2006-12-04 2008-06-05 Sandisk Il Ltd. Incremental transparent file updating
US20080155216A1 (en) 2005-02-17 2008-06-26 Dov Shoham Protection and Recovery System for Automatic Disk Recovery
US20080201705A1 (en) 2007-02-15 2008-08-21 Sun Microsystems, Inc. Apparatus and method for generating a software dependency map
US20080288934A1 (en) 2006-02-14 2008-11-20 Fujitsu Limited Patch application apparatus and program
US20090171705A1 (en) * 2007-12-28 2009-07-02 International Business Machines Corporation Defining and using templates in configuring information technology environments
US7577951B2 (en) 2002-05-30 2009-08-18 Hewlett-Packard Development Company, L.P. Performance of computer programs while they are running
US7617414B2 (en) 2002-07-15 2009-11-10 Symantec Corporation System and method for restoring data on a data storage system
US7680910B2 (en) 2005-04-18 2010-03-16 Research In Motion Limited System and method for efficient transfer of applications and data during device swap
US20100125841A1 (en) 2008-11-14 2010-05-20 Elizabeth Bauer Application restore points
US7770167B1 (en) 2005-12-30 2010-08-03 United Services Automobile Association (Usaa) Method and system for installing software
US7793087B2 (en) 2005-12-30 2010-09-07 Sap Ag Configuration templates for different use cases for a system
US7792799B2 (en) 2002-10-10 2010-09-07 Perlego Systems, Inc. Backing up a wireless computing device
US7802247B1 (en) 2005-12-30 2010-09-21 United Services Automobile Association (Usaa) Method and system for restoring software
US7831968B1 (en) 2005-12-30 2010-11-09 United Services Automobile Association (Usaa) Method and system for restoring software
US7840955B1 (en) 2005-12-30 2010-11-23 United Services Automobile Association (Usaa) Method and system for restoring software
US7840961B1 (en) 2005-12-30 2010-11-23 United Services Automobile Association (Usaa) Method and system for installing software on multiple computing systems
US8261232B2 (en) 2006-06-19 2012-09-04 International Business Machines Corporation Data locations template based application-data association and its use for policy based management
US8266254B2 (en) 2008-08-19 2012-09-11 International Business Machines Corporation Allocating resources in a distributed computing environment
US8566820B1 (en) 2005-12-30 2013-10-22 United Services Automobile Association (Usaa) Method and system for installing software

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9077611B2 (en) * 2004-07-07 2015-07-07 Sciencelogic, Inc. Self configuring network management system
US8726271B1 (en) * 2005-12-30 2014-05-13 United Services Automobile Association (Usaa) Method and system for installing software
US20090210871A1 (en) * 2008-02-20 2009-08-20 Zak Dechovich System and method for software application migration

Patent Citations (72)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5860012A (en) 1993-09-30 1999-01-12 Intel Corporation Installation of application software through a network from a source computer system on to a target computer system
US6138153A (en) 1994-02-14 2000-10-24 Computer Associates Think, Inc. System for software distribution in a digital computer network
US5768568A (en) 1994-04-29 1998-06-16 International Business Machines Corp. System and method for initializing an information processing system
US5583983A (en) 1994-11-17 1996-12-10 Objectware, Inc. Multi-platform object-oriented software development and deployment system
US5870611A (en) 1995-04-05 1999-02-09 International Business Machines Corporation Install plan object for network installation of application programs
US5797015A (en) 1995-04-18 1998-08-18 Pitney Bowes Inc. Method of customizing application software in inserter systems
US6151643A (en) 1996-06-07 2000-11-21 Networks Associates, Inc. Automatic updating of diverse software products on multiple client computer systems by downloading scanning application to client computer and generating software list on client computer
US6093215A (en) 1997-08-12 2000-07-25 International Business Machines Corporation Method and apparatus for building templates in a component system
US6195794B1 (en) 1997-08-12 2001-02-27 International Business Machines Corporation Method and apparatus for distributing templates in a component system
US6192518B1 (en) 1998-01-22 2001-02-20 Mis Only, Inc. Method for distributing software over network links via electronic mail
US6499137B1 (en) 1998-10-02 2002-12-24 Microsoft Corporation Reversible load-time dynamic linking
US6490722B1 (en) 1999-03-30 2002-12-03 Tivo Inc. Software installation and recovery system
US20060206866A1 (en) 1999-05-17 2006-09-14 Invensys Systems, Inc. Methods and apparatus for control configuration using live data
US20020104080A1 (en) 2000-03-29 2002-08-01 Virtual Access Networks, Inc. Server based extraction, transfer, storage and processing of remote settings, files and data
US20020016955A1 (en) 2000-06-29 2002-02-07 International Business Machines Corporation Method and system for constructing a system, drawing a system configuration drawing, and generating a system configuration file
US20020104069A1 (en) 2000-07-07 2002-08-01 Gouge Christopher S. System and method for configuring software components
US6973647B2 (en) 2000-07-15 2005-12-06 International Business Machines Corporation Preferable modes of software package deployment
US20040148601A1 (en) 2000-08-02 2004-07-29 Kroening James L. Method and system for calculation and use of a disk image identifer
US6725453B1 (en) * 2000-08-23 2004-04-20 Microsoft Corporation Remote software installation and maintenance
US6865737B1 (en) 2000-08-23 2005-03-08 Microsoft Corporation Remote software installation and maintenance
US6954925B1 (en) 2000-10-17 2005-10-11 Cisco Technology, Inc. Method of parsing commands using linear tree representation
US20040015957A1 (en) 2001-05-10 2004-01-22 Zara Anna M. Method to map an inventory management system to a configuration management system
US6968551B2 (en) 2001-06-11 2005-11-22 John Hediger System and user interface for generation and processing of software application installation instructions
US20020188939A1 (en) 2001-06-11 2002-12-12 Siemens Medical Solutions Health Services Corporation System and user interface for generation and processing of software application installation instructions
US7093259B2 (en) 2001-12-20 2006-08-15 Cadence Design Systems, Inc. Hierarchically structured logging for computer work processing
US20030182301A1 (en) 2002-03-19 2003-09-25 Hugo Patterson System and method for managing a plurality of snapshots
US20040044643A1 (en) * 2002-04-11 2004-03-04 Devries David A. Managing multiple virtual machines
US7577951B2 (en) 2002-05-30 2009-08-18 Hewlett-Packard Development Company, L.P. Performance of computer programs while they are running
US20040015959A1 (en) * 2002-06-28 2004-01-22 Hiroki Kobayashi Software installing method for setting printing environment in a computer on an individual computer basis
US7617414B2 (en) 2002-07-15 2009-11-10 Symantec Corporation System and method for restoring data on a data storage system
US20040060045A1 (en) 2002-09-19 2004-03-25 International Business Machines Corporation Programmatic application installation diagnosis and cleaning
US7150014B2 (en) 2002-10-04 2006-12-12 Hewlett-Packard Development Company, L.P. Automatically deploying software packages used in computer systems
US7792799B2 (en) 2002-10-10 2010-09-07 Perlego Systems, Inc. Backing up a wireless computing device
US20060015839A1 (en) 2003-03-26 2006-01-19 Peter Owens Development of software systems
US20040204949A1 (en) 2003-04-09 2004-10-14 Ullattil Shaji Method and system for implementing group policy operations
US20040268298A1 (en) 2003-06-30 2004-12-30 Microsoft Corporation Generation of configuration instructions using an abstraction technique
US20050055667A1 (en) 2003-09-05 2005-03-10 Joerg Beringer Pattern-based software design
US20070294321A1 (en) 2003-09-30 2007-12-20 Christopher Midgley Systems and methods for backing up data files
US20050120344A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Optimal component installation
US20050120331A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Hosting environment abstraction agents
US20050120347A1 (en) 2003-12-02 2005-06-02 International Business Machines Corporation Script generation engine
US20080059950A1 (en) 2003-12-08 2008-03-06 Ebay Inc. Method and system to automatically generate software code
US20070214449A1 (en) 2004-03-02 2007-09-13 Choi Elliot M Portlet template based on a state design pattern
US20050251786A1 (en) 2004-05-07 2005-11-10 International Business Machines Corporation System and method for dynamic software installation instructions
US20050262503A1 (en) 2004-05-21 2005-11-24 Computer Associates Think, Inc. Distributed installation configuration system and method
US20060048129A1 (en) 2004-08-31 2006-03-02 Microsoft Corporation Patch un-installation
US20080155216A1 (en) 2005-02-17 2008-06-26 Dov Shoham Protection and Recovery System for Automatic Disk Recovery
US20060195839A1 (en) 2005-02-28 2006-08-31 Microsoft Corporation Computer system for deploying software on multiple computers
US7680910B2 (en) 2005-04-18 2010-03-16 Research In Motion Limited System and method for efficient transfer of applications and data during device swap
US20100179942A1 (en) 2005-04-18 2010-07-15 Research In Motion Limited System and method for efficient transfer of applications and data during device swap
US20060242626A1 (en) * 2005-04-21 2006-10-26 Pham Quang D Template configuration tool for application servers
US20060245354A1 (en) 2005-04-28 2006-11-02 International Business Machines Corporation Method and apparatus for deploying and instantiating multiple instances of applications in automated data centers using application deployment template
US20080256531A1 (en) * 2005-04-28 2008-10-16 International Business Machines Corporation Method and Apparatus for Deploying and Instantiating Multiple Instances of Applications in Automated Data Centers Using Application Deployment Template
US20070028229A1 (en) 2005-07-28 2007-02-01 International Business Machines Corporation Method and system for dynamic generation of computer system installation instructions
US20070055972A1 (en) 2005-08-24 2007-03-08 International Business Machines Corporation Model-driven software deployment in an application server
US7831968B1 (en) 2005-12-30 2010-11-09 United Services Automobile Association (Usaa) Method and system for restoring software
US7840955B1 (en) 2005-12-30 2010-11-23 United Services Automobile Association (Usaa) Method and system for restoring software
US7802247B1 (en) 2005-12-30 2010-09-21 United Services Automobile Association (Usaa) Method and system for restoring software
US7840961B1 (en) 2005-12-30 2010-11-23 United Services Automobile Association (Usaa) Method and system for installing software on multiple computing systems
US20070157185A1 (en) * 2005-12-30 2007-07-05 Semerdzhiev Krasimir P System and method for deployable templates
US7793087B2 (en) 2005-12-30 2010-09-07 Sap Ag Configuration templates for different use cases for a system
US7770167B1 (en) 2005-12-30 2010-08-03 United Services Automobile Association (Usaa) Method and system for installing software
US20070162892A1 (en) * 2005-12-30 2007-07-12 Ingo Zenz Template-based configuration architecture
US8566820B1 (en) 2005-12-30 2013-10-22 United Services Automobile Association (Usaa) Method and system for installing software
US20080288934A1 (en) 2006-02-14 2008-11-20 Fujitsu Limited Patch application apparatus and program
US8261232B2 (en) 2006-06-19 2012-09-04 International Business Machines Corporation Data locations template based application-data association and its use for policy based management
US20080127169A1 (en) 2006-08-29 2008-05-29 Ethan Malasky Software installation using template executables
US20080134163A1 (en) 2006-12-04 2008-06-05 Sandisk Il Ltd. Incremental transparent file updating
US20080201705A1 (en) 2007-02-15 2008-08-21 Sun Microsystems, Inc. Apparatus and method for generating a software dependency map
US20090171705A1 (en) * 2007-12-28 2009-07-02 International Business Machines Corporation Defining and using templates in configuring information technology environments
US8266254B2 (en) 2008-08-19 2012-09-11 International Business Machines Corporation Allocating resources in a distributed computing environment
US20100125841A1 (en) 2008-11-14 2010-05-20 Elizabeth Bauer Application restore points

Non-Patent Citations (6)

* Cited by examiner, † Cited by third party
Title
"Installing software through the NAL." Xavier Information Systems & Services, viewed on Jun. 14, 2006 http://www.xu.edu/helpdesk/installing-software.htm.
"Installing software through the NAL." Xavier Information Systems & Services, viewed on Jun. 14, 2006 http://www.xu.edu/helpdesk/installing—software.htm.
"Integrating Pendragon Forms Distribution Toolbox with Pendragon SyncServer." Pendragon Software Corporation, viewed on Jun. 14, 2006 http://www.pendragon-software.com/forms3/toolboxesyncserver.html.
"WinINSTALL Software Distribution Suite (SDS)." OnDemand Software, viewed on Jun. 14, 2006 http://www.ondemandsoftware.com/sds.asp.
Alpem, et al. "PDS: A Virtual Execution Environment for Software Deployment", 2005, ACM, p. 175-185.
Hoek, A. "Configurable Software Architecture in Support of Configuration Management and Software Deployment", 1999, ACM, p. 732-733.

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9513890B1 (en) * 2005-12-30 2016-12-06 United Services Automobile Association (Usaa) Method and system for installing software
US20140359599A1 (en) * 2013-05-28 2014-12-04 Wistron Corporation Operating System Deployment Method, Server and Electronic System

Also Published As

Publication number Publication date
US9513890B1 (en) 2016-12-06

Similar Documents

Publication Publication Date Title
CA2468644C (en) Method and apparatus for managing components in an it system
US7287190B2 (en) Simultaneous execution of test suites on different platforms
US7334226B2 (en) Autonomic auto-configuration using prior installation configuration relationships
US7366706B2 (en) Method and apparatus for solution-template based deployment and management of an integration solution
US6691117B2 (en) Special purpose operating system for executing a database server
CN102648465B (en) Remote data collection systems and methods
US6151708A (en) Determining program update availability via set intersection over a sub-optical pathway
US5678044A (en) System and method for improved rehosting of software systems
US7149789B2 (en) Distributing software via distribution files
AU2007289177B9 (en) Dynamically configuring, allocating and deploying computing systems
US7735080B2 (en) Integrated system and method for the management of a complete end-to-end software delivery process
US7509638B2 (en) Method and apparatus for providing a pluggable and extendable J2EE architecture
US5732275A (en) Method and apparatus for managing and automatically updating software programs
US6567860B1 (en) Method and apparatus for new device driver installation by an operating system
US7437713B2 (en) Automated system that tests software on multiple computers
US6964034B1 (en) Application development server and a mechanism for providing different views into the same constructs within a strongly encapsulated environment
US7076778B2 (en) Method and apparatus for upgrading a software application in the presence of user modifications
US20070162894A1 (en) Method of and system for dynamic automated test case generation and execution
US9996341B2 (en) Infrastructure for the automation of the assembly of schema maintenance scripts
US8312430B2 (en) Guarding code check-in with test case execution results
US8122106B2 (en) Integrating design, deployment, and management phases for systems
US20060253849A1 (en) Method and apparatus for enhancing manageability of software catalog, abstracting software configuration, and desired state management
US20040177352A1 (en) Universal deployment tool
US7716414B2 (en) Method for updating a mobile device using an update package obtained from a remote server
CA2457440C (en) System and method for the automatic installation and configuration of an operating system

Legal Events

Date Code Title Description
AS Assignment

Owner name: UNITED SERVICES AUTOMOBILE ASSOCIATION (USAA), TEX

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WEATHERSBY, RICHARD DOUGLAS;REEL/FRAME:017410/0243

Effective date: 20051228

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551)

Year of fee payment: 4