# US 2012/0254848 A1 · Deploying and distributing content management code

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

- Number: US 2012/0254848 A1
- Document ID: US20120254848A1
- Status: Published application
- Kind: A1
- Application number: 13/523,648
- Filed: 2012-06-14
- Published: 2012-10-04
- Earliest claimed: 2006-03-30
- Assignees: EMC Corporation
- Inventors: Don Robertson; Meir Amiel; Victor Spivak
- Web page: https://patentgrep.com/patent/US20120254848A1

## CPC

- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 9/44521: {Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading}
- G06F 9/44552: {Conflict resolution, i.e. enabling coexistence of conflicting executables}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Deploying and distributing content management code is disclosed. A software object class is received at a repository. The software object class is stored at the repository. The software object class is downloaded from the repository to an application server associated with the repository.

## Claims

### Claim 1

A system of deploying computer code, comprising:
a processor configured to:
receive at a repository a software object class;
store the software object class at the repository; and
download the software object class from the repository to an application server based at least in part on a request to instantiate an object received at the application server; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 2 (depends on 1)

The system of claim 1, wherein the downloading further comprises: the application server determining whether the software object class is available in a local cache, and in the event that the software object class is not available in the local cache, checking whether the software object class is available to a shared class loader in an associated local cache.

### Claim 3 (depends on 2)

The system of claim 2, wherein in the event that the software object class is not available to the shared class loader in the associated local cache, the shared class loader is configured to request the software object class from the repository.

### Claim 4 (depends on 1)

The system as recited in claim 1, wherein the software object class is stored in a content store associated with the repository.

### Claim 5 (depends on 1)

The system as recited in claim 1, wherein downloading the software object class to the application server is based at least in part on a determination that the software object class has not been previously downloaded from the repository to the application server.

### Claim 6 (depends on 1)

The system as recited in claim 1, wherein the software object class comprises one of at least a subset of said plurality of software object classes to be downloaded to the application server.

### Claim 7 (depends on 1)

The system as recited in claim 1, wherein the application server comprises a first application server associated with the repository and wherein the processor is configured to download the software object class to a second application server associated with the repository.

### Claim 8 (depends on 1)

The system as recited in claim 1, wherein the repository comprises a first repository and the application server is configured to download from the first repository one or more software object classes configured to be used to access content stored in the first repository and to download from a second repository one or more software object classes configured to be used to access content stored in the second repository.

### Claim 9 (depends on 1)

The system as recited in claim 1, wherein the repository comprises a shared repository configured to store and distribute one or more software object classes to be used by the application server to access content across two or more other repositories.

### Claim 10 (depends on 1)

The system as recited in claim 1, wherein the software object class comprises a new or updated software object class and wherein the processor is further configured to update a change record at the repository to reflect that the new or updated software object class is available from the repository.

### Claim 11 (depends on 10)

The system as recited in claim 10, wherein the change record comprises a global change record associated with a plurality of software object classes and the global change record is updated each time a new software object class is added to the plurality of software object classes or one or more software object classes included in the plurality of software object classes are updated.

### Claim 12 (depends on 10)

The system as recited in claim 10, wherein the change record comprises a global change record and the application server is configured to periodically check the global change record to determine whether any new or updated software object classes have become available for download from the repository.

### Claim 13 (depends on 12)

The system as recited in claim 12, wherein if the application server determines by checking the global change record that a change has occurred at the repository, the application server is configured to iterate through at least a subset of software object classes downloaded previously to the application server from the repository and to determine for each whether a new or updated software object class is available for download from the repository.

### Claim 14

A method of deploying computer code, comprising:
receiving at a repository a software object class;
storing the software object class at the repository; and
downloading the software object class from the repository to an application server based at least in part on a request to instantiate an object received at the application server.

### Claim 15 (depends on 14)

The method of claim 14, wherein the downloading further comprises: the application server determining whether the software object class is available in a local cache, and in the event that the software object class is not available in the local cache, checking whether the software object class is available to a shared class loader in an associated local cache.

### Claim 16 (depends on 15)

The method of claim 15, further comprising in the event that the software object class is not available to the shared class loader in the associated local cache, the shared class loader is configured to request the software object class from the repository.

### Claim 17 (depends on 14)

The method of claim 14, wherein the software object class is stored in a content store associated with the repository.

### Claim 18 (depends on 14)

The method of claim 14, wherein downloading the software object class to the application server is based at least in part on a determination that the software object class has not been previously downloaded from the repository to the application server.

### Claim 19 (depends on 14)

The method of claim 14, wherein the application server comprises a first application server associated with the repository and further comprising downloading the software object class to a second application server associated with the repository.

### Claim 20 (depends on 14)

The method of claim 14, wherein the repository comprises a first repository and the application server is configured to download from the first repository one or more software object classes configured to be used to access content stored in the first repository and to download from a second repository one or more software object classes configured to be used to access content stored in the second repository.

### Claim 21 (depends on 14)

The method of claim 14, wherein the repository comprises a shared repository configured to store and distribute one or more software object classes to be used by the application server to access content across two or more other repositories.

### Claim 22 (depends on 14)

The method of claim 14, wherein the software object class comprises a new or updated software object class and further comprising updating a change record at the repository to reflect that the new or updated software object class is available from the repository.

### Claim 23 (depends on 22)

The method of claim 22, wherein the change record comprises a global change record associated with a plurality of software object classes and the global change record is updated each time a new software object class is added to the plurality of software object classes or one or more software object classes included in the plurality of software object classes are updated.

### Claim 24

A computer program product for deploying computer code, the computer program product being embodied in a computer readable medium and comprising computer instructions for:
receiving at a repository a software object class;
storing the software object class at the repository; and
downloading the software object class from the repository to an application server based at least in part on a request to instantiate an object received at the application server.
