System and method for installing applications on a computer on an as needed basis

• US 5,960,204 A
• Filed: 10/28/1996
• Issued: 09/28/1999
• Est. Priority Date: 10/28/1996
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: JD Edwards World Source Company
• Inventors: Foos, James L., Yinger, Glenn S., McVaney, Charles E.
• Primary Examiner(s): Stamber, Eric W.
• Application Number:
  US08/740,360
• Time in Patent Office: 1,065 Days
• Field of Search: 395/712, 395/200.5, 395/200.51, 395/200.52, 395/651, 395/652, 395/653
• US Class Current: 717/176
• CPC Class Codes: G06F 8/61 Installation

Abstract

A data processing system for computer application installation on a client/server network on an as needed basis is disclosed. The server computer includes an installation unit, a system application repository, and a user information file. The client computer includes a menu driver, an application check unit, a local application repository, and a local version repository. A user on the client computer selects an application to execute through the menu driver. The application check unit searches the local application repository and the local version repository for the application and, if found, determines whether it is the most current version unless the most current version is already installed on the client computer. After installation is completed on the client computer, the application is automatically executed. Further, the present invention includes a method for installing a computer applications and/or update on an as needed basis.

Claims

1. In a computing system having a first node for storing available applications in the computer system and a second node for executing a desired application from the available applications, a system to install at least a potion of the desired application from the first node to the second node, comprising:

a system application repository, located in the first node, for storing a plurality of application specifications defining the available applications, the application specifications including dynamic link library information defining application modules for the available applications, function information accessed by said dynamic link library information to describe functionality associated with said application modules, form information describing display information for said application modules through said dynamic link library information, and

a menu driver, located in the second node, for selecting the desired application;

a local application repository, located in the second node, for storing the application specifications required to execute the desired application;

a check unit, located in the second node and coupled to the menu driver, for determining whether said required application specifications are stored in the local application repository;

an installation unit, coupled to the first node and the second node, for installing said required applications specifications from the first node to the local application repository in response to the check unit determining that one or more of said required application specifications are not stored in the local application repository, at least a portion of the installed required application specifications being used to define the desired application for execution; and

a middleware unit, coupled to the system application repository and the local application repository, for transmitting said required application specifications between the system application repository and the local application repository.

2. The system as in claim 1, wherein the system application repository further comprises a relational database for storing said specification information.

3. The system as in claim 1, further comprising a local version repository located in the second node, for storing version information or the desired application defined at the local application repository, the version information being based on the portion of the required application specifications used to define the desired application.

4. The system as in claim 3, wherein the installation unit updates the local version repository with current version information for the desired application.

5. The system as in claim 4, wherein the local application repository further comprises an application file having a specification file for storing said specification information of the desired application defined at the local application repository.

6. The system as in claim 1, wherein the system further comprises a user information file, located in the first node, for providing user information on the desired application available to each user of the system.

7. The system as in claim 1, wherein the system application repository further comprises:

a relational database, for storing said specification files;

a specification library, coupled to the relational database, for storing said form information;

a dynamic link library, coupled to the relational database and the specification library, for storing said dynamic link library information; and

an object library for storing said function information.

8. In a computer system including a first node having a system application repository for storing a set of available applications in the computer system and a second node having a local application repository for storing a desired application from the set of available applications, the second node having a menu, a method for installing at least a portion of the desired application from the first node to the second node, comprising:

storing application specifications in the system application repository including dynamic link library information defining application modules for the available applications, function information accessed by said dynamic library information to describe functionality associated with said application modules, form information describing display information for said application modules through said dynamic link library information, and specification information defining said function information and said form information;

listing at least a subset of the available applications, including the desired application, on the menu;

selecting the desired application from the menu;

determining whether said application specifications required to execute the desired application is installed in the local application repository;

installing said required application specifications from the system application repository to the local application repository in response to determining that one or more of said required application specifications are not installed at the second node;

identifying an installation version of said required application specifications for the desired application in the local application repository in response to determining that said required application specifications are installed in the local application repository; and

installing a current version of said required application specifications from the system application repository to the local application repository in response to identifying the installation version of said required application specifications at the second node as not the current version.

9. The method as in claim 8, wherein installing the desired application, further comprises:

linking, through a middleware unit, the system application repository to the local application repository;

copying said required application specifications associated with the desired application from the system application repository to the local application repository;

reading said required specification information associated with the desired application into a local specification file in the local application repository;

storing said required dynamic link library information in a local dynamic link library file; and

maintaining said local specification file and said local dynamic link library file in a local application file to define the desired application in the local application repository.

10. The method as in claim 9, further comprising executing the desired application at the second node.

11. The method as in claim 10, wherein the executing further comprises loading the desired application into a memory of a client computer.

12. The method as in claim 11, wherein loading the desired application further comprises loading an application entry point.