# US 2009/0276769 A1 · Computer System and a Method of Deploying an Application in a Computer System

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

- Number: US 2009/0276769 A1
- Document ID: US20090276769A1
- Status: Published application
- Kind: A1
- Application number: 12/400,885
- Filed: 2009-03-10
- Published: 2009-11-05
- Earliest claimed: 2008-04-30
- Assignees: SpringSource Limited
- Inventors: Samuel Hugh Brannen, JR.; Adrian Mark Colyer; Rob Harrop; Glyn Normington; Andy Wilkinson
- Web page: https://patentgrep.com/patent/US20090276769A1

## CPC

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

## Abstract

A computer system has a runtime environment (e.g. Java) and a deployment system (e.g. a Spring framework layer) arranged to deploy an application into the runtime environment. The application comprises bundles (e.g. OSGi bundles or JSR modules) each with manifest metadata defining dependencies for the respective bundle. A deployment management unit refers to one or more personality specific deployers to determine which of the bundles have a specific personality from a predetermined set of personality types. The personality specific deployers transform the respective personality-specific bundles by inserting one or more additional dependencies into the metadata of the bundle according to their personality type. The deployment management unit applies one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment and deploys those bundles not having a specific personality type. The personality specific deployers deploy the personality-specific bundles according to their respective personality types.

## Claims

### Claim 1

A computer system, comprising:
a processor;
a memory comprising at least one computer-readable storage medium coupled to the processor;
a runtime environment arranged to support execution of an application program with respect to the memory and the processor, wherein the application program is divided into a plurality of bundles and wherein each of the bundles comprises metadata that includes a definition of zero or more dependencies related to the respective bundle; and
a deployment system arranged to deploy the application program into the runtime environment, the deployment system comprising a deployment management unit and one or more personality specific deployers;
wherein the deployment management unit comprises:
a personality determining unit arranged to determine whether each bundle of the plurality of bundles is a personality-specific bundle having a personality selected from among a predetermined set of personality types, or else is a generic bundle not having a specific personality;
an operator unit arranged to apply one or more operations to each of the plurality of bundles, including installing each of the bundles ready for deployment; and
a generic deployment unit arranged to deploy each of the generic bundles installed by the operator unit into the runtime environment; and
wherein each of the one or more personality specific deployers comprises:
a transformer unit arranged to transform each of the personality-specific bundles by inserting one or more additional dependencies into the metadata of the bundle according to the personality of the respective personality-specific bundle; and
a specific deployment unit arranged to deploy each of the personality-specific bundles installed by the operator unit into the application runtime environment, according to the respective personality of the personality-specific bundles.

### Claim 2 (depends on 1)

The computer system of claim 1, wherein the operator unit is arranged to apply the one or more operations to each of the plurality of bundles in a like manner, including both the personality-specific bundles having a specific personality type and the generic bundles not having a specific personality type; and the transformer unit is arranged to transform only the personality-specific bundles having a particular one of the set of personality types.

### Claim 3 (depends on 1)

The computer system of claim 1, wherein the operator unit is arranged to apply the one or more operations to the plurality of bundles to act upon both the metadata which was originally received in the bundles and also on the additional dependencies which were inserted into the metadata by the personality specific deployers.

### Claim 4 (depends on 1)

The computer system of claim 1, wherein each of the personality types relates to a predetermined programming model.

### Claim 5 (depends on 1)

The computer system of claim 1, wherein the set of personality types include at least a web personality type, and wherein the transformer unit related to the web personality type is arranged to add the additional dependencies to import one or more web-specific packages including one or more servlet interface packages.

### Claim 6 (depends on 1)

The computer system of claim 1, wherein the set of personality types include at least a batch personality type and wherein the transformer unit related to the batch personality type is arranged to add the additional dependencies to import one or more batch-specific packages.

### Claim 7 (depends on 1)

The computer system of claim 1, wherein the personality determining unit is arranged to query each of the one or more personality-specific deployers to determine which of personality-specific deployers is adapted to process a particular candidate bundle from the application.

### Claim 8 (depends on 7)

The computer system of claim 7, wherein at least one of the personality specific deployers is arranged to determine whether or not it is adapted to process the candidate bundle by analyzing the physical structure of the bundle.

### Claim 9 (depends on 7)

The computer system of claim 7, wherein one or more of the bundles comprises an explicit metadata flag denoting the personality type of that bundle and at least one of the personality specific deployers is arranged to determine whether or not it is adapted to process the candidate bundle by examining the explicit metadata flag.

### Claim 10 (depends on 1)

The computer system of claim 1, wherein the runtime environment further comprises a bundle management layer and the operator unit is arranged to install each of bundles with respect to the bundle management layer, including satisfying the additional dependencies created in the metadata by the personality specific deployers.

### Claim 11 (depends on 1)

The computer system of claim 1, wherein the operator unit further comprises a scoping unit arranged to scope the metadata of each of the bundles to produce a set of bundles which are unique to the application.

### Claim 12 (depends on 1)

The computer system of claim 1, wherein the operator unit further comprises a synthesiser unit comprising an extractor unit arranged to examine the metadata and extract export statements from the metadata, a converter unit arranged to convert each of the export statements into a corresponding import statement defining a respective exported package as an imported package, and a creator unit arranged to create an additional synthetic bundle comprising metadata and a class loader, insert the import statements into the metadata of the synthetic bundle, and add the synthetic bundle to the application; and wherein the synthesiser unit is further arranged to set a thread context class loader associated with the application in the runtime environment to delegate class loading to the class loader of the synthetic bundle and the class loader of the synthetic bundle is arranged to load each of the exported packages of the plurality of bundles as the imported packages from the synthetic bundle.

### Claim 13

A method of deploying an application program into an application runtime environment of a computer system, the method comprising the computer-implemented steps of:
receiving the application program divided into a plurality of bundles, each bundle comprising metadata relating to zero or more dependencies of the bundle;
determining whether or not each of the plurality of bundles is a personality-specific bundle having a specific personality type from amongst a predetermined set of personality types;
transforming each of the personality-specific bundles by inserting additional dependencies into the metadata of the bundle according to the personality type of the respective personality-specific bundle;
applying one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment;
deploying each of the installed personality-specific bundles into the application runtime environment according to the respective personality of the personality-specific bundles; and
deploying each of the remaining bundles not having a specific personality type into the application runtime environment.

### Claim 14

The method of clam 13, further comprising the steps of:
extracting export statements from the metadata;
converting each of the export statements into a corresponding import statement;
creating an additional synthetic bundle comprising metadata and a class loader, inserting the import statements into the metadata of the synthetic bundle and adding the synthetic bundle to the application program; and
setting a thread context class loader of the runtime environment associated with a thread of the application program to delegate class loading to the class loader of the synthetic bundle.

### Claim 15

A computer-readable storage medium having recorded thereon instructions to form a deployment system which when implemented by a computer system deploys an application program into a runtime environment of the computer system, wherein the application program is divided into a plurality of bundles, each bundle comprising metadata relating to zero or more dependencies of the bundle, the medium comprising:
code configured to determine whether or not each of the plurality of bundles is a personality-specific bundle having a specific personality type from amongst a predetermined set of personality types;
code configured to transform each of the personality-specific bundles by inserting additional dependencies into the metadata of the bundle according to the personality type of the respective personality-specific bundle;
code configured to apply one or more operations to all of the plurality of bundles, including installing each of the bundles ready for deployment; and
code configured to deploy each of the bundles into the application runtime environment, including deploying the personality-specific bundles according to their respective personality.

### Claim 16

A computer-readable storage medium having recorded thereon instructions to form an application program executable in a runtime environment of a computer system, the medium comprising:
code configured to provide a plurality of bundles comprising metadata including export statements defining exported packages; and
an explicit metadata flag provided in the metadata of at least one of the bundles denoting the personality type of that bundle.

### Claim 17 (depends on 16)

The computer-readable storage medium of claim 16, further comprising:
code configured to provide an additional synthetic bundle comprising metadata and a class loader, wherein the metadata of the synthetic bundle comprises import statements corresponding to each of the export statements in the metadata of the plurality of bundles; and
code configured to set a thread context class loader of the runtime environment associated with a thread of the application program to delegate class loading to the class loader of the synthetic bundle.
