# US 2012/0254855 A1 · On-demand software module deployment

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254855 A1
- Document ID: US20120254855A1
- Status: Published application
- Kind: A1
- Application number: 13/517,546
- Filed: 2012-06-13
- Published: 2012-10-04
- Earliest claimed: 2003-11-14
- Assignees: International Business Machines Corporation
- Inventors: Bruce R. Baker; Daniel A. Rose
- Web page: https://patentgrep.com/patent/US20120254855A1

## CPC

- G06F 8/61: Installation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## 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

### Claim 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; and
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.

### Claim 2 (depends on 1)

The method of claim 1, further comprises:
providing a mapping between an identifier for each said deployed software module and a respective software enabler.

### Claim 3 (depends on 2)

The method of claim 2, 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.

### Claim 4 (depends on 3)

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

### Claim 5 (depends on 3)

The method of claim 3, 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.

### Claim 6 (depends on 2)

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

### Claim 7 (depends on 6)

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

### Claim 8 (depends on 7)

The method of claim 7, 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.

### Claim 9 (depends on 8)

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

### Claim 10 (depends on 1)

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

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
enabling a plurality of designated software modules.

### Claim 12

(canceled)

### Claim 13 (depends on 2)

The method of claim 2, 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.

### Claim 14 (depends on 13)

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

### Claim 15

(canceled)

### Claim 16

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; and
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.

### Claim 17 (depends on 16)

The deployment system of claim 16, wherein the hardware processor is further configured to include:
a mapper for mapping between an identifier for each said deployed software module and a respective software enabler.

### Claim 18 (depends on 17)

The deployment system of claim 17, 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.

### Claim 19 (depends on 18)

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

### Claim 20 (depends on 19)

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

### Claim 21 (depends on 20)

The deployment system of claim 20, 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.

### Claim 22 (depends on 21)

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

### Claim 23 (depends on 22)

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

### Claim 24 (depends on 23)

The deployment system of claim 23, 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.

### Claim 25 (depends on 24)

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

### Claim 26

A computer program product having a computer readable storage medium 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; and
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.

### Claim 27

(canceled)
