Method, system, and program product for deploying a platform dependent application in a grid environment

• US 20070209034A1
• Filed: 03/01/2006
• Published: 09/06/2007
• Est. Priority Date: 03/01/2006
• Status: Active Grant

• Current Assignee: Kyndryl Incorporated (Kyndryl Holdings, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Kozakov, Lev, Grabarnik, Genady, Shwartz, Larisa, Kim, Moon, Meliksetian, Dikran, Kofman, Galina, Doganata, Yurdaer
• Granted Patent: US 8,117,611 B2
• Time in Patent Office: Days
• US Class Current: 717/174
• CPC Class Codes: G06F 2209/5017 Task decomposition
• CPC Class Codes: G06F 9/505 considering the load
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine
• CPC Class Codes: G06F 9/548 Object oriented; Remote method invocation [RMI] non-remote method invocation G06F9/449

Abstract

Under the present invention, it is determined whether sufficient resources exist for deploying a platform dependent application on its specific “native” platform in a grid environment. If not, a platform dependent portion of the application is identified, and the application is split into the platform dependent portion and a platform independent portion. Thereafter, the platform dependent portion is deployed on its corresponding native platform, while the platform independent portion is deployed on another platform in the grid environment based on available resources. Interconnections between the two portions can then be automatically generated. This can include, for example, creating remote method invocation facade interfaces, creating remote method invocation-enabled facade classes, and building a remote method invocation server for the first platform.

Claims

1. A method for deploying a platform dependent application in a grid environment, comprising:

identifying a platform dependent portion of the platform dependent application;

splitting the platform dependent application into the platform dependent portion and a platform independent portion;

deploying the platform dependent portion on a first platform and the platform independent portion on a second platform in the grid environment; and

generating interconnections between the platform dependent portion and the platform independent portion.

2. The method of claim 1, wherein the generating comprises automatically generating the interconnections.

3. The method of claim 1, wherein the generating comprises:

creating remote method invocation facade interfaces;

creating remote method invocation-enabled facade classes; and

building a remote method invocation server for the first platform.

4. The method of claim 1, wherein the deploying is performed by a grid job scheduler.

5. The method of claim 1, further comprising determining available resources for the platform dependent application, wherein the platform dependent application is split if sufficient resources do not exist for running the platform dependent application on the first platform.

6. The method of claim 1, wherein the first platform is specific to the platform dependent portion, and wherein the second platform is selected based on available resources in the grid environment.

7. A system for deploying a platform dependent application in a grid environment, comprising:

a system for determining available resources for running the platform dependent application on a first platform of the grid environment;

a system for identifying a platform dependent portion of the platform dependent application;

a system for splitting the platform dependent application into the platform dependent portion and a platform independent portion;

a system for deploying the platform dependent portion on a first platform and the platform independent portion on a second platform in the grid environment; and

a system for generating interconnections between the platform dependent portion and the platform independent portion.

8. The system of claim 7, wherein the system for generating automatically generates the interconnections.

9. The system of claim 7, wherein the system for generating creates remote method invocation facade interfaces, creates remote method invocation-enabled facade classes, and builds a remote method invocation server for the first platform.

10. The system of claim 7, wherein the system for deploying comprises a grid job scheduler.

11. The system of claim 7, wherein the platform dependent application is split if the system for determining determines that sufficient resources do not exist for running the platform dependent application on the first platform.

12. The system of claim 7, wherein the first platform is specific to the platform dependent portion, and wherein the second platform is selected based on available resources in the grid environment.

13. A program product stored on a computer useable medium for deploying a platform dependent application in a grid environment, the computer useable medium comprising program code for causing a computer system to perform the following steps:

determining available resources for running the platform dependent application on a first platform of the grid environment;

identifying a platform dependent portion of the platform dependent application;

splitting the platform dependent application into the platform dependent portion and a platform independent portion;

deploying the platform dependent portion on a first platform and the platform independent portion on a second platform in the grid environment; and

generating interconnections between the platform dependent portion and the platform independent portion.

14. The program product of claim 13, wherein the generating step comprises automatically generating the interconnections.

15. The program product of claim 13, wherein the computer useable medium comprises program code for causing the computer system to perform the following steps:

creating remote method invocation facade interfaces;

creating remote method invocation-enabled facade classes; and

building a remote method invocation server for the first platform.

16. The program product of claim 13, wherein the platform dependent application is split if the system for determining determines that sufficient resources do not exist for running the platform dependent application on the first platform.

17. The program product of claim 13, wherein the first platform is specific to the platform dependent portion, and wherein the second platform is selected based on available resources in the grid environment.

18. A method for deploying a platform dependent application in a grid environment, comprising:

providing a computer infrastructure being operable to;

identify a platform dependent portion of the platform dependent application;

split the platform dependent application into the platform dependent portion and a platform independent portion;

deploy the platform dependent portion on a first platform and the platform independent portion on a second platform in the grid environment; and

generate interconnections between the platform dependent portion and the platform independent portion.

19. The method of claim 18, wherein the computer infrastructure is further operable to automatically generate the interconnections.

20. The method of claim 18, wherein the computer infrastructure is further operable to:

create remote method invocation facade interfaces;

create remote method invocation-enabled facade classes; and

build a remote method invocation server for the first platform.

21. The method of claim 18, wherein the computer infrastructure comprises a grid job scheduler to deploy the platform dependent portion and the platform independent portion.

22. The method of claim 18, wherein the computer infrastructure is further operable to determine available resources for the platform dependent application, wherein the application is split if sufficient resources do not exist for running the platform dependent application on the first platform.

23. The method of claim 18, wherein the first platform is specific to the platform dependent portion, and wherein the second platform is selected based on available resources in the grid environment.