Implementing a middleware component using factory patterns

• US 8,752,066 B2
• Filed: 11/23/2009
• Issued: 06/10/2014
• Est. Priority Date: 11/23/2009
• Status: Active Grant

• Current Assignee: Raytheon Company (Rtx Corporation)
• Original Assignee: Raytheon Company (Rtx Corporation)
• Inventors: Lipasek, John J., Schilling, Scott A., Sedlmeyer, Robert
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): Huaracha, Willy W
• Application Number:
  US12/623,567
• Publication Number:
  US 20110126212A1
• Time in Patent Office: 1,660 Days
• Field of Search: 719/313, 719/315, 719/316
• US Class Current: 719/313
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

In one aspect, a method to use a middleware component includes receiving a request from an application to interact with a platform using a service and using an abstract factory pattern corresponding to the service. The abstract factory pattern is associated with a first factory pattern stored in the middleware component. The method also includes determining if the first factory pattern is associated with the platform and invoking the service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

Claims

1. A method to use a middleware component comprising service components to facilitate a plurality of services, the method comprising:

providing the service components, a service component facilitating a respective one of the plurality of services comprising a messaging service, an invocation service, a logging service and a persistence data service, each service component comprising an abstract factory pattern and a delegate configured to receive a request for a platform from an application and to invoke the abstract factory pattern;

receiving the request from the application to interact with a platform using a first service of the plurality of services;

using an abstract factory pattern stored in a first service component of the service components to encapsulate a plurality of factory patterns that enable access to more than one platform, the first service component facilitating the first service, the plurality of factory patterns comprising a first factory pattern, each of the plurality of factory patterns associated with a corresponding one platform;

determining if the first factory pattern is associated with the platform; and

invoking the first service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

2. The method of claim 1 wherein receiving the request from the application to interact with the platform using the first service comprises receiving a request from an application to interact with a platform using the messaging service.

3. The method of claim 1 wherein receiving the request from the application to interact with the platform using the first service comprises receiving a request from an application to interact with a platform using the invocation service.

4. The method of claim 1 wherein receiving the request from the application to interact with the platform using the first service comprises receiving a request from an application to interact with a platform using the logging service.

5. The method of claim 1 wherein receiving the request from the application to interact with the platform using the first service comprises receiving a request from an application to interact with a platform using the persistence data service.

6. The method of claim 1 wherein the plurality of factory patterns are configured to facilitate interaction with at least two of:

JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

7. The method of claim 1 wherein the platform is a first platform, the request is a first request and the plurality of factory patterns comprises a second factory pattern and further comprising:

receiving a second request from the application to interact with a second platform different from the first platform using the first service;

determining if the second factory pattern is associated with the second platform; and

using the first service with the second platform if the second factory pattern is associated with the second platform.

8. The method of claim 1 wherein the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising:

receiving a second request from the application to interact with the platform using a second service;

using a second abstract factory pattern stored in a second service component of the service components to encapsulate a second plurality of factory patterns that enable access to more than one platform, the second service component facilitating the second service, the second plurality of factory patterns comprising a second factory pattern, each of the second plurality of factory patterns associated with a corresponding one platform;

determining if the second factory pattern is associated with the platform; and

using the second service with the platform if the second factory pattern is associated with the platform.

9. An article comprising a non-transistory machine-readable medium that stores executable instructions to invoke a first service on a platform using a middleware component comprising service components, a service component facilitating a respective one of a plurality of services comprising a messaging service, an invocation service, a logging service and a persistence data service, each service component comprising an abstract factory pattern and a delegate configured to receive a request for a platform from an application and to invoke the abstract factory pattern, the instructions causing a machine to:

receive the request from the application to interact with the platform using the first service;

use an abstract factory pattern stored in a first service component of the service components to encapsulate a plurality of factory patterns that enable access to more than one platform, the first service component facilitating the first service, the plurality of factory patterns comprising a first factory pattern, each of the plurality of factory patterns associated with a corresponding one platform;

determine if the first factory pattern is associated with the platform; and

invoke the first service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

10. The article of claim 9 wherein the instructions to receive the request from the application to interact with the platform using the first service comprises instructions to receive a request from an application to interact with a platform using one of a messaging service, an invocation service, a logging service and a persistence data service.

11. The article of claim 9 wherein the plurality of factory patterns are configured to facilitate interaction with at least two of:

of JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

12. The article of claim 9 wherein the request is a first request and the plurality of factory patterns comprises a second factory pattern and further comprising instructions causing the machine to:

receive a second request from the application to interact with a second platform different from the first platform using the first service;

determine if the second factory pattern is associated with the second platform; and

use the first service with the second platform if the second factory pattern is associated with the second platform.

13. The article of claim 9 wherein the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising instructions causing a machine to:

receive a second request from the application to interact with the platform using a second service;

use a second abstract factory pattern stored in a second service component of the service components to encapsulate a second plurality of factory patterns that enable access to more than one platform, the second service component facilitating the second service, the second plurality of factory patterns comprising a second factory pattern;

determine if the second factory pattern is associated with the platform; and

use the second service with the platform if the second factory pattern is associated with the platform.

14. An apparatus to invoke a first service on a platform, the apparatus comprising a middleware component comprising service components, each service component facilitating a respective one of a plurality of services comprising a messaging service, an invocation service, a logging service and a persistence data service, each service component comprising an abstract factor pattern and a delegate configured to receive a request for a platform from an application and to invoke the abstract factory pattern, the middleware component comprising:

circuitry configured to;

receive the request from the application to interact with the platform using the first service of the plurality of services;

use an abstract factory pattern stored in a first service component of the service components to encapsulate a plurality of factory patterns that enable access to more than one platform, the first service component facilitating the first service, the plurality of factory patterns comprising a first factory pattern, each of the plurality of factory patterns associated with a corresponding one platform;

determine if the first factory pattern is associated with the platform; and

invoke the first service with the platform using the first factory pattern if the first factory pattern is associated with the platform.

15. The apparatus of claim 14 wherein the circuitry comprises at least one of a processor, a memory, programmable logic and logic gates.

16. The apparatus of claim 14 wherein the circuitry to receive the request from the application to interact with the platform using the first service comprises circuitry to receive a request from an application to interact with a platform using the first service component to facilitate one of a messaging service, an invocation service, a logging service and a persistence data service.

17. The apparatus of claim 14 wherein the plurality of factory patterns are configured to facilitate interaction with at least two of:

JAVA®

2, Enterprise Edition (J2EE®

), MICROSOFT®

WINDOWS®

, Common Object Request Broker Architecture (CORBA®

), Sun Solaris, Linux, HP Solaris, Mac OS, and System of Systems Common Operation Environment (SOSCOE) platforms.

18. The apparatus of claim 14 wherein the request is a first request and the abstract factory pattern is associated with a second factory pattern and further comprising circuitry to:

receive a second request from the application to interact with a second platform different from the first platform using the first service;

determine if the second factory pattern is associated with the second platform; and

use the first service with the second platform if the second factory pattern is associated with the second platform.

19. The apparatus of claim 14 wherein the abstract factory pattern is a first abstract factory pattern and the request is a first request and further comprising circuitry to:

receive a second request from the application to interact with the platform using a second service;

use a second abstract factory pattern stored in a second service component of the service components to encapsulate a second plurality of factory patterns that enable access to more than one platform, the second service component facilitating the second service, the second plurality of factory patterns comprising a second factory pattern;

determine if the second factory pattern is associated with the platform; and

use the second service with the platform if the second factory pattern is associated with the platform.

20. The apparatus of claim 14, wherein a service component to facilitate the invocation service further comprises an intercepting filter configured to provide at least one of compression or encryption to data sent to a platform.