MOVING ENTERPRISE SOFTWARE APPLICATIONS TO A CLOUD DOMAIN

• US 20130031158A1
• Filed: 06/03/2011
• Published: 01/31/2013
• Est. Priority Date: 08/20/2010
• Status: Active Grant

• Current Assignee: Michael A. Salsburg
• Original Assignee: Michael A. Salsburg
• Inventors: Salsburg, Michael A.
• Granted Patent: US 8,886,777 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 9/5072 Grid computing
• CPC Class Codes: G06F 9/5077 Logical partitioning of resources; Management or configuration of virtualized resources specific details on emulation or internal functioning of virtual machines G06F9/455
• CPC Class Codes: H04L 47/785 among multiple network domains, e.g. multilateral agreements

Abstract

Methods and systems for moving or porting an enterprise software application from an enterprise environment to a cloud domain are disclosed. An automated moving software program identifies enterprise components of an enterprise software application. The program assigns an enterprise component tag to the identified enterprise component. The program then assigns an enterprise attribute tag to the identified enterprise component and searches an attribute relationship map for at least one cloud attribute related to the assigned enterprise attribute. On identification of such a cloud attribute, the cloud attribute is assigned to the identified enterprise component and the enterprise component is converted to cloud component by creating a new cloud component to replicate the functions of the enterprise component or assigning a cloud component tag to the enterprise component, provided the enterprise component is render-able on the cloud domain resources.

Claims

1. A computer-implemented method for moving an enterprise software application from an enterprise environment to a cloud domain, the method comprising:

identifying, on a backend computing device, an enterprise component from the enterprise software application;

assigning, on the backend computing device, at least one enterprise component tag to each identified enterprise component;

assigning, on the backend computing device, at least one enterprise attribute tag to the identified enterprise component;

identifying, on the backend computing device, at least one cloud attribute for the enterprise attribute, wherein the cloud attribute shares a pre-defined relationship with the enterprise attribute;

assigning, on the backend computing device, the identified cloud attribute to the identified enterprise component; and

converting, on the backend computing device, the enterprise component into a cloud executable cloud component, wherein resources of the cloud domain render the cloud component, thereby generating at least one part of the enterprise software application.

2. The method according to claim 1, wherein the enterprise component comprises sub-components.

3. The method according to claim 1, wherein the enterprise component and the cloud component are computer-coded files.

4. The method according to claim 1, wherein the enterprise component and the cloud component are computer-coded file formats.

5. The method according to claim 1, wherein the pre-defined relationship with the enterprise attribute is based on analysis of type of file formats that is render-able by the resources of the cloud domain.

6. The method according to claim 1, further comprising:

processing the converted cloud component into add cloud functionality into the cloud component, wherein the cloud functionality includes at least one function selected from;

a) elastic scaling the cloud domain resources available to the converted cloud component;

b) measured service pay-per-use related to a user'"'"'s frontend use of the enterprise software application comprising the converted cloud component; and

c) on-demand self-service to a user of the enterprise software application comprising the converted cloud component, wherein on-demand self-service refers to a service of providing the enterprise software application to a user with additional cloud domain resources based on the user'"'"'s request for the enterprise software application and additional cloud domain resources.

7. The method according to claim 1, wherein the cloud domain resources include at least one among hardware resources, software resources, or personas.

8. The method according to claim 1, wherein converting the enterprise component into a cloud render-able cloud component is performed by

a) generating a new cloud component to replicate at least one function of the enterprise component, wherein the new cloud component is capable of rendering within the cloud domain resources, and providing the new cloud component in the place of the enterprise component to the enterprise software application as part of the enterprise software application to be rendered on the cloud domain resources;

or

b) retaining the same enterprise component, wherein the retained enterprise component includes additional functionalities of the cloud domain resources.

9. The method according to claim 1, wherein the cloud attribute comprises at least one attribute selected from the group consisting of an elasticity attribute, a self-service attribute, a utility attribute, a security attribute, and a ubiquity attribute.

10. The method according to claim 1, wherein the enterprise attribute comprises at least one attribute selected from the group consisting of a user-interface attribute, a security attribute, a scalability attribute, a database attribute, and a distribution attribute.

11. A computer-implemented system for moving an enterprise software application from an enterprise environment to a cloud domain, the system comprising:

a backend computing device that identifies at least one enterprise components from the enterprise software application;

the backend computing device that assigns at least one enterprise component tag to each identified enterprise component;

the backend computing device that assigns at least one enterprise attribute tag to the identified enterprise component;

the backend computing device that identifies at least one cloud attribute for the enterprise attribute, wherein the cloud attribute shares a pre-defined relationship with the enterprise attribute;

the backend computing device that assigns the identified cloud attribute to the identified enterprise component; and

the backend computing device that converts the enterprise component into a cloud executable cloud component, wherein resources of the cloud domain render the cloud component, thereby generating at least one part of the enterprise software application.

12. The system according to claim 11, wherein the enterprise component comprises sub-components.

13. The system according to claim 11, wherein the enterprise component and the cloud component are computer-coded files.

14. The system according to claim 11, wherein the enterprise component and the cloud component are computer-coded file formats.

15. The system according to claim 11, wherein the pre-defined relationship with the enterprise attribute is based on analysis of type of file formats that is render-able by the resources of the cloud domain.

16. The system according to claim 11, further comprising:

processing the converted cloud component into add cloud functionality into the cloud component, wherein the cloud functionality includes at least one function selected from;

a) elastic scaling the cloud domain resources available to the converted cloud component;

b) measured service pay-per-use related to a user'"'"'s frontend use of the enterprise software application comprising the converted cloud component; and

c) on-demand self-service to a user of the enterprise software application comprising the converted cloud component, wherein on-demand self-service refers to a service of providing the enterprise software application to a user with additional cloud domain resources based on the user'"'"'s request for the enterprise software application and additional cloud domain resources.

17. The system according to claim 11, wherein the cloud domain resources include at least one among hardware resources, software resources, or personas.

18. The system according to claim 11, wherein converting the enterprise component into a cloud render-able cloud component is performed using

a) generating a new cloud component to replicate at least one function of the enterprise component, wherein the new cloud component is capable of rendering within the cloud domain resources, and providing the new cloud component in the place of the enterprise component to the enterprise software application as part of the enterprise software application to be rendered on the cloud domain resources;

or

b) retaining the same enterprise component, wherein the retained enterprise component includes additional functionalities of the cloud domain resources.

19. The system according to claim 11, wherein the cloud attribute comprises at least one attribute selected from the group consisting of an elasticity attribute, a self-service attribute, a utility attribute, a security attribute, and a ubiquity attribute.

20. The system according to claim 11, wherein the enterprise attribute comprises at least one attribute selected from the group consisting of a user-interface attribute, a security attribute, a scalability attribute, a database attribute, and a distribution attribute.