Flexible deployment of software applications

• US 7,665,085 B2
• Filed: 03/09/2005
• Issued: 02/16/2010
• Est. Priority Date: 03/15/2004
• Status: Active Grant

• Current Assignee: Ramco Systems Limited
• Original Assignee: Ramco Systems Limited
• Inventors: Sundararajan, Parthasarathy, Devalla, Raghuram, Krishnan, Natarajan, Pandimani, Srirangan, Sathiavageeswaran, Suresh, Jayaraman, Shyamala, Meenakshisundaram, Krishnamoorthy
• Primary Examiner(s): DENG, ANNA CHEN
• Application Number:
  US11/075,500
• Publication Number:
  US 20050204354A1
• Time in Patent Office: 1,805 Days
• Field of Search: 717168-178, 717103-104, 709/201, 709/205
• US Class Current: 717/174
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A system and method for deploying software is disclosed. In one embodiment, information regarding software components and their interactions, deliverables and deployment descriptors, hardware topology, layer information, and database information are all captured in a model. The model in then used to install the software on a particular machine. In another embodiment, an organizational structure is used to create an access map, and access rights to the installed software are generated and enforced.

Claims

1. A model-driven method for automated deployment of software on a hardware platform in an organization comprising:

retrieving a software structure from a repository, residing in a server processing system or in a client processing system or both, based on a business view of software;

mapping artifacts of said software to said software structure, wherein said software structure comprise presentation layer, middle layer, and resource manager layer, and wherein components in said presentation layer and said middle layer are mapped to a machine and an appropriate application server instance, and required components in resource manager layer are mapped to machines where database servers are available;

creating a map of an organizational structure of said organization;

creating a map of a hardware topology of said hardware platform;

creating an access map by mapping map of said organizational structure and map of said hardware topology;

mapping said software structure onto said access map thereby creating a deployment map;

installing said software thereby mapping said artifacts onto map of said hardware topology;

setting up said deployment map including involves setting up and maintaining an organization unit, mapping said organization unit to said organization structure, creating users-roles mapping and role-deployment mapping in said deployment map;

using said deployment map to deploy changes in said software structure, changes in said artifacts, changes in map of said hardware topology, and changes in map of said organizational structure; and

creating access rights for users to access said software by using role information and user information from map of said organizational structure.

2. The method of claim 1, further comprising validating said mapping in map of said hardware topology.

3. The method of claim 1, further comprising validating map of said hardware topology for connectivity.

4. The method of claim 1, further comprising deploying said artifacts over a technology platform.

5. The method of claim 1, further comprising depositing said software structure in a specification repository.

6. A model-driven method for automated deployment of software on a hardware platform in an organization comprising:

capturing information about software components and interactions of said software components in a model, wherein said information about said software components and interactions of said software components comprises a type of application server, instances of application servers in a machine, services offered by said software components and services used by said software components;

packaging deliverables, wherein said deliverables are for said software components in said model can be automatically packaged along with necessary deployment descriptors;

capturing topology of hardware including configuration information, and details of machines on which software components shall be deployed in said model;

capturing layer information of said software in said model including information of presentation layer, middle layer, and resource manager layer;

capturing database information in said model, wherein said database information comprises information about databases and database servers; and

deploying said software by using said topology of hardware, said layer information, said database information and said packaged deliverables in said model, wherein deploying further comprise;

developing said software components as a set of business components, and implementing organizational functions as business components,

modeling business functions in a deployment repository,

modeling hardware information,

superimposing said hardware model with said business functions model thereby producing a composite model comprising a software layer, a hardware platform, a business function, and an organizational structure mapping,

installing artifacts on a hardware platform by using said composite model, and

generating required router information for routing information across different layers.

7. The method of claim 6, further comprising installing said software components on a machine based on said model information.

8. The method of claim 6, further comprising combining said model deployment scheme and a JMX architecture.

9. The method of claim 6, further comprising using said composite model to generate router information.

10. An article comprising a storage medium having instructions that when executed by a computing platform, result in execution of a model-driven method for deployment of software on a hardware platform in an organization comprising:

retrieving a software structure from a repository, residing in a server processing system or in a client processing system or both, based on a business view of software;

mapping artifacts to said software structure, wherein said software structure comprise presentation layer, middle layer, and resource manager layer, and wherein components in said presentation layer and said middle layer are mapped to a machine and an appropriate application server instance, and required components in resource manager layer are mapped to machines where database servers are available;

creating a map of an organizational structure of said organization;

creating a map of a hardware topology of said hardware platform;

creating an access map by mapping map of said organizational structure and map of said hardware topology;

mapping said software structure onto said access map thereby creating a deployment map;

installing software thereby mapping said artifacts onto map of said hardware topology;

setting up said deployment map including involves setting up and maintaining an organization unit, mapping said organization unit to said organization structure, creating users-roles mapping and role-deployment mapping in said deployment map;

using said deployment map to deploy changes in said software structure, changes in said artifacts, changes in map of said hardware topology, and changes in map of said organizational structure; and

creating access rights for users to access said software by using role information and user information from map of said organizational structure.

11. The article of claim 10, further comprising instructions for validating said mapping of map of said hardware topology.

12. The article of claim 10, further comprising instructions for depositing said software structure in a specification repository.

13. The article of claim 10, further comprising instructions for validating map of said hardware topology for connectivity.

14. The article of claim 10, further comprising instructions for deploying said artifacts over a technology platform.

15. An article comprising a storage medium having instructions that when executed by a computing platform, result in execution of a model-driven method for automated deployment of software on a hardware platform in an organization comprising:

capturing information about software components and interactions of said software components in a model, wherein said information about said software components and interactions of said software components comprises a type of application server, instances of application servers in a machine, services offered by said software components and services used by said software components;

packaging deliverables, wherein said deliverables are for said software components in said model can be automatically packaged along with necessary deployment descriptors;

capturing topology of hardware including configuration information, and details of machines on which software components shall be deployed in said model;

capturing layer information of said software in said model including information of presentation layer, middle layer, and resource manager layer;

capturing database information in said model, wherein said database information comprises information about databases and database servers; and

deploying said software by using said topology of hardware, said layer information, said database information and said packaged deliverables in said model, wherein deploying further comprise;

developing said software components as a set of business components, and implementing organizational functions as business components,

modeling business functions in a deployment repository,

modeling hardware information,

superimposing said hardware model with said business functions model thereby producing a composite model comprising a software layer, a hardware platform, a business function, and an organizational structure mapping,

installing artifacts on a hardware platform by using said composite model, and

generating required router information for routing information across different layers.

16. The article of claim 15, further comprising instructions for installing said software components on a machine based on said model information.

17. The article of claim 15, further comprising instructions for combining said model deployment scheme and a JMX architecture.

18. The article of claim 15, further comprising instructions for using said composite model to generate router information.