Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F8/00—Arrangements for software engineering
  • G06F8/60—Software deployment
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F9/00—Arrangements for program control, e.g. control units
  • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
  • G06F9/44—Arrangements for executing specific programs
  • G06F9/445—Program loading or initiating
  • G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files

Definitions

• Virtual applications can be implemented in a series of operations. Initially, an application can be packaged in a packaging environment to generate a virtual application package. Packaging is the process of taking the application and defining its data (such as files and registry entries) and metadata (configuration items such as items in *.ini files and registry settings), so that the package can include the application data and metadata to run in a target environment without actually being installed as a native application.
• data such as files and registry entries
• metadata configuration items such as items in *.ini files and registry settings
• a package can be deployed to a target environment to instantiate a virtual application instance.
• the virtual application instance can run in a capsule, which includes the application as well as virtual resources to run the application.
• a capsule is referred to herein as a "sandbox".
• a package includes the information (files, metadata, etc.) that is taken from the packaging of the application, and the package can be deployed to instantiate the application.
• the package may be split into multiple parts, and some parts may be transmitted in different ways and/or at different times.
• the tools and techniques described and claimed herein can allow a virtual application package and a deployment configuration to be deployed to instantiate a specific instance of an application.
• the deployment configuration can include one or more configuration items, such as items that are discovered when packaging the application.
• the deployment configuration may be included with or separate from the virtual application package, and the deployment configuration may be edited after the application is packaged.
• the deployment configuration can be applied in the instantiated virtual application. For example, the deployment configuration may be applied to configure the application while deploying the application and/or after the application has been deployed.
• the tools and techniques can include automatically discovering configuration items for a software application, and packaging the application to form a virtual application package.
• the virtual application package can be deployed to instantiate the application.
• a deployment configuration can be applied in the instantiated application, where the deployment configuration includes settings for the configuration items.
• a software application can be packaged to form a virtual application package.
• a deployment configuration for the application can be set after packaging the application. Setting a deployment configuration includes confirming and/or changing the configuration. For example, one or more default settings for configuration items in the deployment configuration can be confirmed automatically or in response to specific user input. As another example, one or more settings for configuration items can be added or modified, such as adding or modifying automatically or in response to specific user input.
• the virtual application package can also be deployed to instantiate the application, and the deployment configuration can be applied in the instantiated application.
• the deployment configuration can be applied in the instantiated application.
• settings of configuration items in the deployment configuration may be applied in the application while the application package is being deployed (e.g., by interleaving deployment and configuration operations), and/or after the application package has been deployed.
• configuration items for a software application can be discovered.
• the application can be packaged to form a virtual application package.
• the configuration items can be presented with a user interface device.
• a selected configuration item can be changed in response to user input indicating the change.
• the virtual application package can be deployed to instantiate the application, and the configuration items can be applied to the instantiated application.
• FIG. 1 is a block diagram of a suitable computing environment in which one or more of the described embodiments may be implemented.
• FIG. 2 is a block diagram of a virtual application deployment configuration computing environment.
• FIG. 3 is a flowchart of a virtual application deployment configuration technique.
• Fig. 4 is a flowchart of another virtual application deployment configuration technique.
• FIG. 5 is a flowchart of yet another virtual application deployment configuration technique.
• Embodiments described herein are directed to techniques and tools for improved packaging, deployment, and/or instantiation of virtual applications. Such improvements may result from the use of various techniques and tools separately or in combination.
• Such techniques and tools may include allowing a virtual application package and a deployment configuration to be deployed to instantiate a specific instance of an application in a target environment. For example one or more configuration items for a software application may be automatically discovered.
• a deployment configuration that includes the items can be set after an application is packaged as a virtual application package.
• the configuration item(s) may be presented to a user with a user interface device (e.g., by displaying representations of the configuration item(s) on a computer display) after packaging the application.
• the configuration item(s) may be changed in response to user input indicating the change to be made.
• the package can be deployed to instantiate an instance of the application, and the deployment configuration can be applied in the application instance.
• a packaging engineer user conducting packaging
• the packager computing component that performs packaging
• some configuration items may be tied to a particular machine, user or application instance.
• a user acceptance testing organization may have the application connect to a database named "sql qa”. However, when the application is run in its intended production target environment, the application may connect to a database named "sql_production”.
• an administrator user conducting deployment
• a single package can be deployed to instantiate different instances with different machines and/or users. This may be done without having to modify the package itself (except possibly modifying the configuration items if they are included in the package) and without having to repackage the application. For example, this may be beneficial because one general package can be packaged and tested, but this tested general package can be deployed to a number of different instances with different deployment configuration settings. If items in the package other than the deployment configuration were modified for each deployment or if the application were entirely repackaged, the original testing may not be valid.
• Fig. 1 illustrates a generalized example of a suitable computing environment (100) in which one or more of the described embodiments may be implemented.
• one or more such computing environments can be used as a packaging environment, deployment environment, and/or target environment.
• various different general purpose or special purpose computing system configurations can be used. Examples of well-known computing system configurations that may be suitable for use with the tools and techniques described herein include, but are not limited to, server farms and server clusters, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
• the computing environment (100) is not intended to suggest any limitation as to scope of use or functionality of the invention, as the present invention may be
• the computing environment (100) includes at least one processing unit (110) and memory (120).
• the processing unit (110) executes computer-executable instructions and may be a real or a virtual processor. In a multi-processing system, multiple processing units execute computer-executable instructions to increase processing power.
• the memory (120) may be volatile memory (e.g., registers, cache, RAM), non- volatile memory (e.g., ROM, EEPROM, flash memory), or some combination of the two.
• the memory (120) stores software (180) implementing virtual software application deployment configurations.
• FIG. 1 Although the various blocks of Fig. 1 are shown with lines for the sake of clarity, in reality, delineating various components is not so clear and, metaphorically, the lines of Fig. 1 and the other figures discussed below would more accurately be grey and blurred. For example, one may consider a presentation component such as a display device to be an I/O component. Also, processors have memory. The inventors hereof recognize that such is the nature of the art and reiterate that the diagram of Fig. 1 is merely illustrative of an exemplary computing device that can be used in connection with one or more
• a computing environment (100) may have additional features.
• the computing environment (100) includes storage (140), one or more input devices (150), one or more output devices (160), and one or more communication connections (170).
• An interconnection mechanism such as a bus, controller, or network interconnects the components of the computing environment (100).
• operating system software provides an operating environment for other software executing in the computing environment (100), and coordinates activities of the components of the computing environment (100).
• the storage (140) may be removable or non-removable, and may include non- transitory computer-readable storage media such as magnetic disks, magnetic tapes or cassettes, CD-ROMs, CD-RWs, DVDs, or any other medium which can be used to store information and which can be accessed within the computing environment (100).
• the storage (140) stores instructions for the software (180).
• the input device(s) (150) may be a touch input device such as a keyboard, mouse, pen, or trackball; a voice input device; a scanning device; a network adapter; a CD/DVD reader; or another device that provides input to the computing environment (100).
• the output device(s) (160) may be a display, printer, speaker, CD/DVD-writer, network adapter, or another device that provides output from the computing environment (100).
• the communication connection(s) (170) enable communication over a communication medium to another computing entity.
• the computing environment (100) may operate in a networked environment using logical connections to one or more remote computing devices, such as a personal computer, a server, a router, a network PC, a peer device or another common network node.
• the communication medium conveys information such as data or computer-executable instructions or requests in a modulated data signal.
• a modulated data signal is a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
• communication media include wired or wireless techniques implemented with an electrical, optical, RF, infrared, acoustic, or other carrier.
• Computer-readable media are any available media that can be accessed within a computing environment.
• Computer-readable media include memory (120), storage (140), and combinations of the above.
• program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
• the functionality of the program modules may be combined or split between program modules as desired in various embodiments.
• Computer-executable instructions for program modules may be executed within a local or distributed computing environment. In a distributed computing environment, program modules may be located in both local and remote computer storage media.
• FIG. 2 is a block diagram of a virtual software application deployment
• the computing environment (200) can include a packaging environment (210).
• a nonvirtual application (212) can be packaged by a packager (214) into a virtual application package (220).
• the packager (214) may be a packager from application virtualization software such as Microsoft's Application Virtualization (App-V) software.
• App-V Application Virtualization
• the packager (214) can also identify in the nonvirtual application (212) one or more configurations to be included in a deployment configuration (230) as configuration items (232).
• the identification may be done automatically (i.e., the searching and identification may be automatic, although this automatic identification may be prompted by user input requesting that the configuration items be automatically identified).
• the packager (214) may suggest whether one or more of the configuration items (232) are to be mandatory configuration items that have to be set in response to user input at deployment time, or optional configuration items that may or may not be set in response to user input at deployment time.
• the deployment configuration (230) may be in the form of a separate file, such as an XML file with configuration items indexed by location (e.g., file or registry location). Alternatively, the deployment configuration (230) may be in some other form, such as in multiple files and/or attributes in one or more files that also include other application data and/or metadata.
• the configuration items (232) may also be presented to a user on a user interface device, such as one of the output device(s) (160) discussed above with reference to Fig. 1.
• the user may provide user input to edit one or more of the configuration items (232) in the deployment configuration (230), and the configuration items (232) can be edited in response to the user input.
• a user may provide user input requesting that one of the items (232) be deleted from the deployment configuration (230); that a name or label for one of the items (232) be changed; that a mandatory item (232) be changed to an optional item (232); that an optional item (232) be changed to a mandatory item (232); that a default setting for an item (232) be added, changed or deleted; or that some other change to one or more of the items (232) be made.
• a configuration item may be a database connection string.
• the packager (214) may delegate automatic identification of database-related items to a database subsystem of the packager (214).
• the database subsystem may search for database-related items.
• the database subsystem may monitor API (application programming interface) calls when the nonvirtual application (212) is being installed, and extract particular strings from those calls.
• the database subsystem can then produce configuration items or search for items related to those extracted strings in the application state, such as in application files (e.g., *.ini and xml files) and registry entries.
• the database subsystem can identify the string as a configuration item (232). The subsystem may also make other determinations related to the configuration item (232), such as whether the item (232) is mandatory or optional, what the name of the item is, and what, if any, default setting is to be included for the configuration item (232).
• Similar entries could be used for other items such as xml and *.ini elements.
• the packager (214) may store the file path and an XPath expression to identify the location, allowing differentiation between elements with the same name.
• a configuration item (232) may be an account name for NT services, and a subsystem of the packager (214) that deals with NT services could identify the account name.
• the account name may be listed in the deployment configuration (230) by an identifier, which an NT services component will recognize when instantiating the application.
• the account name may be set by an API call.
• configuration items (232) may include user accounts and passwords that are managed by Microsoft's Internet Information Services (US).
• An IIS subsystem of the packager (214) can recognize user accounts and passwords managed by IIS, and the packager (214) can include configuration items for the accounts and passwords in the deployment configuration (230), listed by appropriate identifiers.
• the package (220), which can include the deployment configuration (230), can be sent to a deployment environment (240).
• the deployment configurations (230) can be presented to a user, and the deployment configurations can be set (such as by confirming default settings, editing the settings, etc.).
• the settings may have to be confirmed and/or edited in response to user input before deployment of the package (220) will be allowed to proceed.
• the deployment configuration (230) may be included in a file (e.g., an xml file), and the file can be opened and displayed as a document to be edited.
• a graphical representation of the deployment configuration can be presented (e.g., the configuration items (232) can be presented in one or more dialogs).
• User input can be received (e.g., from an administrator conducting deployment of the package (220)), and in response to the user input, an editing component (242) can edit the configuration items (232) in the deployment configuration (230), as indicated by the user input.
• a deployment component (244) can take the package and deploy it to a target environment (260).
• the deployment component (244) and the editing component (242) may both be part of the same software product or part of different software products.
• the editing component (242) and a component for presenting the deployment configuration on a user interface device may be part of a data center manager software product, while the deployment component (244) may be part of an application virtualization software product.
• the editing component (242) can be a simple editor such as a generic XML editor, which can be used to directly view and edit the deployment configuration file.
• the package (220) can be deployed to the target environment (260) to be instantiated.
• the instantiation in the target environment (260) can be conducted by a virtual application host (262), which can be a client component of application virtualization software that also includes the editing component (242) and the packager (214).
• the application can be instantiated as a virtual application instance (264) in a sandbox (266) in the target environment (260).
• the configuration items (232) in the deployment configuration (230) can be applied in the virtual application instance (264) (i.e., the instantiated application).
• the entire application may be deployed and then configured as the virtual application instance (264).
• the deployment of the package (220) and the configuration of the virtual application instance (264) can be interleaved, with a portion of the package (220) being deployed and configured, followed by another portion of the package (220) being deployed and configured, etc. This interleaved deployment and configuration can continue until the entire application is instantiated as the virtual application instance (264).
• Applying the deployment configuration (230) may be done in various ways, such as overwriting metadata and/or making API calls to configure the application instance (264). This configuring may be done in the deployment environment (240) and/or in the target environment (260). As another example, the virtual application can be left in an unconfigured state in storage.
• the deployment configuration information can be merged with the application information at runtime. For example, when an application opens an *.ini file, the *.ini file can be read from storage and merged with deployment
• API calls can be hooked and the behavior of the API calls can be changed to return the values from the deployment configuration (230) at runtime.
• registry API's can be hooked to detect when the virtual process for the virtual application instance (264) is reading a registry value that has been overridden by a deployment configuration item (232). When that occurs, the value from the deployment configuration item (232) can be returned instead of the value in the registry.
• the identification, editing, and/or application of the deployment configuration (230) could be done in environments that differ from the computing environment (200) discussed above.
• the virtual application package (220) could be deployed directly from the packaging environment (210) to the target environment (260).
• packaging, deployment, instantiation, and execution of the virtual application may all be done in the same environment.
• each technique may be performed in a computer system that includes at least one processor and a memory including instructions stored thereon that when executed by the at least one processor cause the at least one processor to perform the technique (a memory stores instructions (e.g., object code), and when the processor(s) execute(s) those instructions, the processor(s) perform(s) the technique).
• a memory stores instructions (e.g., object code), and when the processor(s) execute(s) those instructions, the processor(s) perform(s) the technique).
• one or more computer-readable storage media may have computer-executable instructions embodied thereon that, when executed by at least one processor, cause the at least one processor to perform the technique.
• the technique can include automatically discovering (310) one or more configuration items for a software application.
• the configuration item(s) may be presented (312) with a user interface device.
• User input may be received (314), and in response to receiving (314) the user input, one of the configuration item(s) can be edited (316).
• this changing or editing (316) of the configuration may include deleting the configuration item, modifying a name or label associated with the
• the application can be packaged (320) to form a virtual application package.
• the configuration item(s) may again be presented (322) with a user interface device. Also after packaging (320), user input can be received (324), and one or more configuration item settings can be edited (326). Other features of the configuration item(s) may also be edited at that time. Accordingly, the presentation of configuration item(s), receipt of user input, and responsive editing may be done before packaging (320) is complete (e.g., at packaging time) and/or after packaging (320) (e.g., at deployment time) is complete. In addition, the package may be deployed (330) to instantiate the application. A deployment configuration, which can include one or more settings for the configuration item(s), can be applied (340) in the instantiated application.
• the technique can also include applying a second deployment configuration in the instantiated application to change setting(s) for the configuration item(s). Applying the second deployment configuration can be done after the instantiated application has been configured with the original deployment configuration. This other deployment configuration can be different from the first deployment configuration, so that the instantiated application can be reconfigured by applying the second deployment configuration.
• technique can also include discovering one or more
• configuration items for the software application in response to user input that identifies the item(s), and the deployment configuration can further include one or more settings for these manually-discovered configuration item(s).
• the same package may be deployed to instantiate the application multiple times, with different deployment configuration settings being applied to in different instances of the application.
• the application may be deployed to be instantiated in multiple target environments with different deployment configuration settings for target environments that are configured differently.
• deploying (330) the virtual application package to instantiate the application can include deploying the virtual application package to instantiate the application as a first instance of the application, and applying (340) the deployment configuration can include applying the deployment configuration in the first instance of the application.
• the technique can further include deploying (330) the virtual application package to instantiate the application as a second instance of the application, and applying (340) the deployment configuration in the second instance of the application.
• applying (340) the deployment configuration in the first instance of the application and applying (340) the deployment configuration in the second instance of the application can include applying different settings for at least one of the configuration item(s) in the first and second instances of the application.
• the technique can include discovering (410) one or more configuration items for a deployment configuration, and packaging (420) a software application to form a virtual application package.
• the discovering (410) can be performed before completing the packaging (420). For example, the discovering (410) may be performed during packaging (420) and/or prior to packaging (420). However, discovering (410) may be performed after packaging (420) is completed, such as by using a tool that scans a package to identify and/or produce a deployment configuration document.
• the technique can also include setting (430) a deployment configuration for the virtual application package after packaging (420).
• Setting (430) the deployment configuration can include editing one or more configuration items in the deployment configuration (e.g., by editing setting(s) for the configuration item(s)) and/or confirming existing configuration item(s) in the deployment configuration.
• setting (430) the deployment configuration can be done in response to receiving user input.
• At least one of the configuration item(s) may be marked as optional or mandatory.
• Setting (430) the deployment configuration can include determining for each of the configuration item(s) whether the item is marked as mandatory, and if so then requiring user input for that item before deploying the virtual application package. For example, such user input may confirm an existing default setting, modify an existing default setting, or enter a setting where there is no default setting.
• the virtual application package can be deployed (440) to instantiate the application, and the deployment configuration can be applied (450) in the instantiated application.
• the package may be deployed multiple times, possibly with different deployment configurations for different deployments.
• the deployment configuration can be a first deployment configuration.
• Deploying (440) the virtual application package to instantiate the application can include deploying the virtual application package to instantiate the application in a first instance of the application.
• applying (450) the deployment configuration in the instantiated application can include applying the first deployment configuration in the first instance of the application.
• the technique can further include setting a second deployment configuration for the virtual application package after packaging the software application, deploying the virtual application package to instantiate the application in a second instance of the application; and applying the second deployment configuration in the second instance of the application.
• the first instance of the application can be on a first machine with a first machine configuration and the second instance of the application can be on a second machine with a second machine configuration.
• the first and second instances of the application could be on the same machine, or on different machines that both have the same configuration.
• the technique can include discovering (510) one or more configuration items for a software application. Some or all of the discovering (510) can be done automatically.
• the configuration item(s) can be presented (520) on a user interface device and at least one of the configuration item(s) can be changed (530).
• the changing (530) can be done in response to receiving user input indicating a change.
• the application can be packaged (540) to form a virtual application package, but the presentation (520) and changing (530) can be done before packaging (540) is complete. Additionally, the configuration item(s) can be presented (550) with a user interface device after packaging (540) the application. In response to user input indicating a change to a selected configuration item of the configuration item(s), the selected configuration item can be changed (560).
• the virtual application package can be deployed (570) to instantiate the application, and the configuration item(s) can be applied (580) in the instantiated application.

Landscapes

• Engineering & Computer Science (AREA)
• Software Systems (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Stored Programmes (AREA)

Priority Applications (3)

Applications Claiming Priority (2)

Publications (2)

Family

ID=44532264

Family Applications (1)

Country Status (5)

Cited By (2)

Families Citing this family (33)

Citations (2)

Family Cites Families (19)

• 2010
  • 2010-03-08 US US12/719,008 patent/US8826268B2/en active Active
• 2011
  • 2011-03-04 JP JP2012557138A patent/JP5726214B2/ja active Active
  • 2011-03-04 WO PCT/US2011/027300 patent/WO2011112467A2/en not_active Ceased
  • 2011-03-04 EP EP11753847.0A patent/EP2545445B1/en active Active
  • 2011-03-04 CN CN201180012985.4A patent/CN102792268B/zh active Active
• 2014
  • 2014-07-29 US US14/445,390 patent/US9152403B2/en active Active
• 2015
  • 2015-08-28 US US14/839,808 patent/US10318263B2/en active Active
• 2019
  • 2019-04-29 US US16/397,168 patent/US20190354355A1/en not_active Abandoned

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events