Two layer middleware architecture with an intermediate target independent interface

• US 20030188043A1
• Filed: 03/27/2002
• Published: 10/02/2003
• Est. Priority Date: 03/27/2002
• Status: Abandoned Application

• Current Assignee: Raytheon Company (Rtx Corporation)
• Original Assignee: Raytheon Company (Rtx Corporation)
• Inventors: Kuckelman, Mark J., Woodall, Thomas R.
• Application Number:
  US10/108,020
• Publication Number:
  US 20030188043A1
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

An innovative middleware architecture for interfacing between a user Application Programming Interface (API) (12) and a target API (16) comprised of two layers with an Intermediate Target Independent Interface (34). This architecture divides the middleware into two separate and distinct layers separated by an Intermediate Target Independent Interface (ITII). The front-end layer (32) maps the user API (12) to the ITII (34), and then the backend layer (36) maps the ITII (34) to the target API (16). In the preferred embodiment, the implementation of each layer would be via a software library, although each library can be divided into sub-libraries. The key feature is the ITII. The ITII defines the fixed interface between the front end of the middleware and the backend of middleware. Each layer will translate between ITII and the other interface while handling various issues associated with that translation. Such issues include initialization, error handling, and programming language differences.

Claims

1. A program for interfacing between a user Application Programming Interface (API) and a target API comprising:

first means for interfacing between said user API and an intermediate target independent interface (ITII) and

second means for interfacing between said ITII and said target API.

2. The invention of claim 1 wherein said intermediate target independent interface is a set of generic functions or procedures.

3. The invention of claim 2 wherein said first means defines functions from said user API using functions from said ITII.

4. The invention of claim 2 wherein said second means defines functions from said ITII using functions from said target API.

5. The invention of claim 1 wherein said first means is a front-end library of software functions.

6. The invention of claim 1 wherein said second means is a backend library of software functions.

7. The invention of claim 5 wherein said front-end library includes multiple sub-libraries or modules.

8. The invention of claim 7 wherein said front end library may completely satisfy the API call, without any interaction with the backend library or target API.

9. The invention of claim 6 wherein said back-end library includes multiple sub-libraries or modules.

10. The invention of claim 9 wherein said backend library may completely satisfy the API call, without any interaction with the target API.

11. The invention of claim 1 wherein said target API includes an operating system API.

12. The invention of claim 1 wherein said target API includes a hardware interface.

13. The invention of claim 1 wherein said target API includes low-level software API.

14. A system for running a legacy software application on a target operating system comprising:

a processor;

memory;

a software application utilizing a user Application Programming Interface (API);

an operating system utilizing a target API; and

a two layer middleware for interfacing between said application and said operating system wherein said two layer middleware includes;

a first program for interfacing between said user API and an intermediate target independent interface (ITII), and

a second program for interfacing between said ITII and said target API,

wherein said application, operating system, and two layer middleware are implemented in software residing in said memory and executed by said processor.

15. A method for interfacing between a user Application Programming Interface (API) and a target API including the steps of:

interfacing between said user API and an intermediate target independent interface (ITII) and

interfacing between said ITII and said target API.