Deploying software modules in computer system

• US 8,869,140 B2
• Filed: 04/29/2009
• Issued: 10/21/2014
• Est. Priority Date: 05/09/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Todorova, Mariela
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Huynh, Tina
• Application Number:
  US12/431,774
• Publication Number:
  US 20090282401A1
• Time in Patent Office: 2,001 Days
• Field of Search: 717168-178
• US Class Current: 717/175
• CPC Class Codes: G06F 11/1433 during software upgrading
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 8/61 Installation
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Methods and systems are disclosed herein for deploying software modules in a computer system. In one embodiment, a number of containers are registered with a deployer. At least one container provides runtime environment for a corresponding type of software module in the computer system. The software modules are one of standalone software modules and components of software applications. From an archive file a number of files that include deployable software modules are extracted. The software modules corresponding to at least one of the containers are detected based on container specific detecting mechanisms. The detected software modules are validated in order to test their functionality and interoperability. When the software modules are validated, they are distributed for implementation in the corresponding containers.

Claims

1. An article of manufacture comprising a non-transitory computer-readable medium having computer readable instructions stored thereon for execution by a processor to:

register a plurality of containers, wherein at least one of the plurality of containers provide a runtime environment for a corresponding type of software module in the computer system;

extract a plurality of files from an archive on a storage, wherein the plurality of files comprise one or more software modules to be deployed in the plurality of containers;

extract configuration metadata from at least one annotation and at least one deployment descriptor provided by at least one of the plurality of files extracted from the archive;

detect a software module of the one or more software modules corresponding to a container of the plurality of containers based on the extracted configuration metadata according to a logic of a module detector mechanism implemented by the container;

validate a container specific model according to a logic for building a model implemented by the container, wherein the container specific model comprises the extracted configuration metadata;

validate the detected software module based on the configuration metadata through the container specific model implemented by the container; and

distribute the detected software module to the corresponding container based on the validations.

2. The article of manufacture of claim 1, wherein registering the plurality of containers comprises:

receiving a subscription for a set of software modules, wherein the set of software modules is defined by a criteria selected from a group consisting of software module file name, software module file extension and software module; and

receiving a logic for one or more of detecting, generating and removing software modules corresponding to the container.

3. The article of manufacture of claim 1, wherein extracting the plurality of files from the archive comprises:

creating a temporary directory structure to store the plurality of files extracted from the archive based on a definition of the temporary directory structure in the archive.

4. The article of manufacture of claim 1, wherein detecting the software module corresponding to the container comprises:

identifying one or more of a file name, a file extension and a software type of a file of the plurality of files extracted from the archive.

5. The article of manufacture of claim 1, wherein detecting the software module corresponding to the container comprises:

dynamically checking a content of a file of the plurality of files extracted from the archive.

6. The article of manufacture of claim 1, wherein detecting the software module corresponding to the container comprises:

identifying a version of the software module; and

based on the version, parsing one of a deployment descriptor and an annotation, wherein the deployment descriptor is a file of the plurality of files extracted from the archive and the annotation is selected from the at least one annotation extracted from the archive.

7. The article of manufacture of claim 1 comprising the non-transitory computer-readable medium having computer readable instructions stored thereon for execution by a processor further to:

generate a software module according to a logic relative to the container and to the detected software module.

8. The article of manufacture of claim 1 comprising the non-transitory computer-readable medium having computer readable instructions stored thereon for execution by a processor further to:

remove a software module according to a logic relative to the container and to the detected software module.

9. A method for deploying software in a computer system comprising:

registering a plurality of containers, wherein at least one of the plurality of containers provide a runtime environment for a corresponding type of software module in the computer system;

extracting a plurality of files from an archive on a storage, wherein the plurality of files comprise one or more software modules to be deployed in the plurality of containers;

extracting configuration metadata from at least one annotation and at least one deployment descriptor provided by at least one of the plurality of files extracted from the archive;

detecting a software module of the one or more software modules corresponding to a container of the plurality of containers based on the extracted configuration metadata;

validating a container specific model according to a logic for building a model implemented by the container, wherein the container specific model comprises the extracted configuration metadata;

validating the detected software module through the container specific model implemented by the container; and

distributing the detected software module to the corresponding container based on the validations.

10. The method of claim 9, wherein registering the plurality of containers comprises:

receiving a subscription for a set of software modules, wherein the set of software modules is defined by a criteria selected from a group consisting of software module file name, software module file extension and software module; and

receiving a logic for one or more of detecting, generating and removing software modules corresponding to the container.

11. The method of claim 9, wherein extracting the plurality of files from the archive comprises:

creating a temporary directory structure to store the plurality of files extracted from the archive based on a definition of the temporary directory structure in the archive.

12. The method of claim 9, wherein detecting the software module corresponding to the container comprises:

identifying one or more of a file name, a file extension and a software type of a file of the plurality of files extracted from the archive.

13. The article of method of claim 9, wherein detecting the software module corresponding to the container comprises:

dynamically checking a content of a file of the plurality of files extracted from the archive.

14. The method of claim 9, wherein detecting the software module corresponding to the container comprises:

identifying a version of the software module; and

based on the version, parsing one of a deployment descriptor and an annotation, wherein the deployment descriptor is a file of the plurality of files extracted from the archive and the annotation is selected from the at least one annotation extracted from the archive.

15. The method of claim 9 further comprising:

generating a software module according to a logic relative to the container and to the detected software module.

16. The method of claim 9 further comprising:

removing a software module according to a logic relative to the container and to the detected software module.

17. A system comprising:

a storage to store a plurality of files extracted from an archive, wherein the plurality of files comprise a plurality of software modules;

a processor in communication with the storage; and

a memory in communication with the processor, the memory comprising a plurality of containers operable to provide a runtime environment for the plurality of software modules, and a deployer operable to;

register the plurality of containers;

extract configuration metadata from at least one annotation and at least one deployment descriptor provided by at least one of the plurality of files extracted from the archive;

for a container of the plurality of containers, detect a corresponding software module based on the extracted configuration metadata by a module detector mechanism implemented by the container;

validate a container specific model according to a logic for building a model implemented by the container, wherein the container specific model comprises the extracted configuration metadata;

validate the detected software module through the container specific model implemented by the container; and

distribute the software module to the container based on the validations.

18. The system of claim 17, wherein the memory further comprises:

a container interface to receive data comprising;

a subscription for a set of software modules, wherein the set of software modules is defined by a criteria selected from a group consisting of software module file name, software module file extension and software module type; and

a logic for one or more of detecting, generating and removing software modules corresponding to the container.

19. The system of the claim 17, wherein the deployer comprises:

a module detector to determine a correspondence between the software module and the container based on a content of a file of the plurality of files extracted from the archive.

20. The system of the claim 17, wherein the deployer comprises:

a module generator to one of generate and remove a software module according to a logic relative to the container and the detected software module.