IP Library Granted Patent US 9,015,697
Granted Patent B2
US 9,015,697 · App. 13/517,546 · Granted Apr 21, 2015

On-demand software module deployment

Inventors: Bruce R. Baker (Ontario, CA); Daniel A. Rose (Ontario, CA)
Assignee: International Business Machines Corporation
G06F8/61
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,015,697
App. No.
13/517,546
Granted
Apr 21, 2015
Kind
B2
Abstract

A method, system, program product and signal bearing medium embodiments of the present invention provide for deploying software modules for software application use in a computer system thereby reducing load time as well as memory requirements. Deployment of a plurality of software modules and associated deployment descriptors into a software module depository and creation of a deployment information repository from the associated deployment descriptors occurs. A name service is initialized with information from the deployment information repository and a requested software module identifier is then mapped to a respective enabler. Having mapped the requested software module to an enabler, the respective software module is enabled for the software application use. On-demand deployment in this manner saves start-up time as well as initial and ongoing memory allocation.

Claims (48)

1. A method of deploying software modules for use by a software application in a computer system, said method comprising:

deploying a plurality of software modules into a software module depository;

populating a deployment information repository with parsed inputs from deployment descriptors associated with each of said plurality of software modules, wherein said deployment information repository is separate from said software module depository and the software application; and

providing a mapping between an identifier for each said deployed software module and a respective software enabler.

2. The method of claim 1 , wherein said mapping further comprises:

receiving said identifier from said software application;

locating a respective software enabler for said identifier in said deployment information repository; and

enabling said software module associated with said identifier for said software application use.

3. The method of claim 2 , wherein said locating is performed by a name service in communication with said deployment information repository.

4. The method of claim 2 , wherein said deployment information repository is selected from a group comprising: a property file, an array, an indexed array, a database table and a simple name-value pair list.

5. The method of claim 1 , whereupon completion of said software application use, said software module is released.

6. The method of claim 5 , wherein releasing said software module further includes garbage collection.

7. The method of claim 6 , wherein said step of releasing further comprises:

determining said software module is a priority software module upon completion of said software application use, maintaining availability of said software module within said software module depository; otherwise,

releasing said software module.

8. The method of claim 7 , further comprising maintaining a list of prioritized said software modules within said software module depository.

9. The method of claim 1 , wherein said software module is an Enterprise Java Bean module.

10. The method of claim 1 , further comprising:

enabling a plurality of designated software modules.

11. The method of claim 1 , wherein said mapping further comprises:

receiving said identifier from said software application;

determining said identifier represents a designated software module, returning said software module to said application for use, otherwise;

locating a respective software enabler for said identifier in said deployment information repository; and

enabling said software module associated with said identifier for said software application use.

12. The method of claim 11 , wherein said plurality of designated software modules is a subset of software modules associated with said software application.

13. A deployment system for deploying software modules for use by a software application in a computer system, comprising a hardware processor configured to include:

a first deployer for deploying a plurality of software modules into a software module depository;

a second deployer for populating a deployment information repository with parsed inputs from deployment descriptors associated with each of said plurality of software modules,

wherein said deployment information repository is separate from said software module depository and the software application; and

a mapper for mapping between an identifier for each said deployed software module and a respective software enabler.

14. The deployment system of claim 7 , wherein said mapper further comprises:

receiver for receiving said identifier from said software application;

locator for locating a respective software enabler for said identifier in said deployment information repository; and

enabler for enabling said software module associated with said identifier for said software application use.

15. The deployment system of claim 14 , wherein said locator is a name service in communication with said deployment information.

16. The deployment system of claim 15 , wherein said deployment information repository is a property file.

17. The deployment system of claim 16 , wherein said deployment information repository is selected from a group comprising: a property file, an array, an indexed array, a database table and a simple name-value pair list.

18. The deployment system of claim 17 , further comprising a release mechanism for releasing said software module upon completion of said software application use.

19. The deployment system of claim 18 , wherein said release mechanism further includes garbage collection.

20. The deployment system of claim 19 , wherein said release mechanism further comprises:

a comparator for determining said software module is a priority home object upon completion of use by said software application, maintaining availability of said software module; and

a discarder for releasing said corresponding one of said plurality of home objects when not maintained.

21. The deployment system of claim 20 , further comprising a maintainer for maintaining a list of prioritized home objects within said EJB container.

22. A computer program product having a computer readable storage memory comprising a device tangibly embodying computer readable program code for instructing a computer to deploy software modules for use by a software application in a computer system, said code, when executed by a computer, causes the computer to perform the steps comprising:

deploying a plurality of software modules into a software module depository;

populating a deployment information repository with parsed inputs from deployment descriptors associated with each of said plurality of software modules,

wherein said deployment information repository is separate from said software module depository and the software application; and

providing a mapping between an identifier for each said deployed software module and a respective software enabler.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 19, 2022
From: INTERNATIONAL BUSINESS MACHINES CORPORATION
To: KYNDRYL, INC.
Reel/Frame 061706/0202 →
Priority Claims (1)
CA 2449534 · Nov 14, 2003 · national
Continuity (2)
Continuation 10989152 · Nov 15, 2004
Related Publication 20120254855A1 · Oct 4, 2012