Shared service funtionality invocation

• US 20020032783A1
• Filed: 01/02/2001
• Published: 03/14/2002
• Est. Priority Date: 12/30/1999
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Tuatini, Jeffrey T.
• Application Number:
  US09/755,621
• Publication Number:
  US 20020032783A1
• Time in Patent Office: Days
• US Class Current: 709/229
• CPC Class Codes: H04L 67/288 Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

An application architecture allowing applications to inter-communicate is provided. The application framework receives requests for services from clients, identifies application action handler components that can service the requests and application view handler components that can format the responses, invokes the identified action handlers to service the requests, and invokes identified view handlers to format and send the responses to the clients. When an application component needs to access functionality provided by remote shared services, the component uses a local messaging service to communicate with the remote service. In particular, the local messaging service retrieves configuration information for a proxy of the shared service that is stored in a globally accessible location, instantiates a copy of the proxy, and sends a message to the proxy to be forwarded to the shared service. Responses from the shared service are returned to the application component via the local messaging service.

Claims

1. A method in a computer system for executing applications to request services from remote shared service providers each able to provide services to multiple executing applications, each remote shared service provider having an associated distinct proxy component for communicating with the remote shared service provider, comprising:

under control of a first of the executing applications,

instantiating a local messaging component within the first application, the local messaging component able to communicate with each of the associated proxies;

notifying the local messaging component to request a specified service from a remote shared service provider identified with a unique name; and

under control of the local messaging component, requesting the specified service by,

determining based on the unique name identified in the notification to request the specified service from a first of the remote shared service providers;

retrieving configuration information for the first remote shared service provider that identifies a first proxy component associated with the first remote shared service provider;

when the first proxy component is not already instantiated within the first application, instantiating the first proxy component within the first application;

sending a message to the first proxy component requesting that the first remote shared service provider provide the specified service; and

receiving a response from the first remote shared service provider via the first proxy component, and notifying the first application of the received response, so that an application can communicate with any of the remote shared service providers via a local messaging component that interacts with a proxy component associated with the remote shared service provider.

2. The method of claim 1 including, under control of the first application:

notifying the local messaging component to request a second specified service from a remote shared service provider identified with a second unique name; and

under control of the local messaging component, requesting the second specified service by,

determining based on the second unique name identified in the notification to request the second specified service from a second of the remote shared service providers;

retrieving configuration information for the second remote shared service provider that identifies a second proxy component associated with the second remote shared service provider;

sending a message to the second proxy component requesting that the second remote shared service provider provide the second specified service; and

receiving a response from the second remote shared service provider via the second proxy component, and notifying the first application of the received response.

3. The method of claim 1 including:

under control of a second of the executing applications,

instantiating a second local messaging component within the second application, the second local messaging component able to communicate with each of the associated proxies;

notifying the second local messaging component to request a specified service from a remote shared service provider identified with the unique name of the first shared service provider; and

under control of the second local messaging component, requesting the specified service by,

determining based on the unique name identified in the notification to request the specified service from the first remote shared service provider;

retrieving the configuration information for the first remote shared service provider that identifies the associated first proxy component;

when the first proxy component is not already instantiated within the second application, instantiating the first proxy component within the second application; and

sending a message to the first proxy component requesting that the first remote shared service provider provide the specified service.

4. The method of claim 1 including, under control of the first proxy component:

receiving the sent message from the local messaging component;

identifying based on the received message one of multiple services provided by the first remote shared service provider that is requested;

requesting the first remote shared service provider to provide the identified service;

receiving a response from the first remote shared service provider; and

sending the received response to the local messaging component.

5. The method of claim 4 including, under control of the first remote shared service provider:

receiving the request from the first proxy component to provide the identified service;

performing processing associated with the identified service, the processing generating a response; and

sending the generated response to the first proxy component.

6. The method of claim 1 wherein the first remote shared service provider has multiple associated proxy components each for communicating with the first remote shared service provider to request distinct services provided by the first remote shared service provider, wherein the notifying of the local messaging component further identifies a name of the specified service, and wherein the identifying of the first proxy component from the retrieved configuration information is based at least in part on the identified name of the specified service.

7. The method of claim 1 wherein the local messaging component and the first proxy component are software modules, and wherein the instantiating of the components within the first application includes executing the software modules.

8. The method of claim 1 wherein the local messaging component and the first proxy component are instances of object classes, and wherein the instantiating of the components within the first application includes creating the instances.

9. The method of claim 8 wherein the notifying of the local messaging component includes invoking an interface method of the local messaging component instance.

10. The method of claim 8 wherein the sending of the message to the first proxy component includes invoking an interface method of the first proxy component instance.

11. The method of claim 1 wherein the configuration information is retrieved from storage via a directory service using the unique name of the first remote shared service provider.

12. The method of claim 11 including, before the executing of the first application, storing the configuration information using the directory service.

13. The method of claim 1 wherein the retrieved configuration information includes initialization information for the first proxy component, and wherein the instantiating of the first proxy component includes providing the initialization information to the first proxy component for use as part of its initialization.

14. The method of claim 1 wherein the notifying of the request of the specified service includes a message to be sent to the first remote shared service provider, and wherein the message sent to the first proxy component is the included message.

15. The method of claim 1 wherein the notifying of the request of the specified service includes a message to be sent to the first remote shared service provider, and wherein the message sent to the first proxy component is a version of the included message that is transformed under the control of the local messaging component before the sending.

16. The method of claim 1 wherein the first application includes multiple action handler components each for responding to requests from external clients with responses generated in a format used by the action handler component, and wherein the notifying of the request of the specified service is prompted by a request generated by one of the action handler components.

17. The method of claim 16 wherein the first application includes multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, and including, after the notifying of the received response from the first remote shared service provider, using one of the view handler components to transform the received response into a format compatible with an external client.

18. A computer-readable medium whose contents cause a computing device to execute applications able to request services from remote shared service providers each able to provide services to multiple executing applications, each remote shared service provider having an associated proxy component for communicating with the remote shared service provider, by:

under control of a first of the executing applications,

instantiating a local messaging component, the local messaging component able to communicate with each of the associated proxies;

notifying the local messaging component to request a specified service from a remote shared service provider; and

under control of the local messaging component, requesting the specified service by,

determining based on the notifing to request the specified service from a first of the remote shared service providers;

retrieving configuration information for the first remote shared service provider that identifies a first proxy component associated with the first remote shared service provider;

when the first proxy component is not already instantiated, instantiating the first proxy component;

sending a message to the first proxy component requesting that the first remote shared service provider provide the specified service; and

receiving a response from the first remote shared service provider via the first proxy component.

19. A computing device for executing applications to request services from remote shared service providers each able to provide services to multiple executing applications, each remote shared service provider having an associated proxy component for communicating with the remote shared service provider, comprising:

a first application capable of, during execution, instantiating a local messaging component able to communicate with each of the associated proxies and of notifying the local messaging component to request a specified service from a remote shared service provider; and

the local messaging component capable of, during execution, determining based on the notification to request the specified service from a first of the remote shared service providers, of retrieving configuration infornation for the first remote shared service provider that identifies a first proxy component associated with the first remote shared service provider, of instantiating the first proxy component, of sending a message to the first proxy component requesting that the first remote shared service provider provide the specified service, and of receiving a response from the first remote shared service provider via the first proxy component.

20. A method in a computer system for an executing application to communicate with remote services via a local messaging service, each of the remote services having an associated proxy for communicating with the remote service, the method comprising:

for each of multiple of the remote services,

notifying the local messaging service to send a message to the remote service;

under control of the local messaging service,

identifying the proxy associated with the remote service by retrieving information associated with the remote service; and

sending the message to the identified proxy for communication to the remote service; and

receiving a response to the sent message from the remote service via the identified proxy.

21. The method of claim 20 including, under control of each of the identified proxies:

receiving the sent message from the local messaging service that is to be communicated to a remote service;

sending the received message to the remote service;

receiving a response from the remote service; and

sending the received response to the local messaging service.

22. The method of claim 21 including, before the sending of the received message to the remote service, transforming the received message into a format appropriate for the remote service.

23. The method of claim 20 wherein each of the remote services has multiple associated proxies, wherein the notifying of the local messaging service identifies a manner of sending the message to the remote service, and wherein the identifying of the associated proxy from the retrieved information includes selecting one of the multiple associated proxies based at least in part on the identified manner.

24. The method of claim 20 wherein the local messaging service and the proxies are created objects, and including creating the objects.

25. The method of claim 20 wherein the information associated with a remote service is retrieved from a directory service using a unique name of the remote service.

26. The method of claim 25 including storing the associated information with the directory service before the retrieving.

27. The method of claim 20 wherein the application includes multiple action handlers each able to respond to requests from external clients with responses generated in a format used by the action handler, and wherein the notifying of the local messaging service to send the messages is prompted by requests generated by the action handlers.

28. The method of claim 27 wherein the application includes multiple view handlers each able to transform a generated response in a format used by an action handler into a format compatible with at least one of the external clients, and including, after the receiving of the response from the remote service, using one of the view handlers to transform the received response into a format compatible with an external client.

30. The computer-readable medium of claim 29 wherein the computer-readable medium is a data transmission medium transmitting a generated data signal containing the contents.

31. The computer-readable medium of claim 29 wherein the computer-readable medium is a memory of a computer system.

29. A computer-readable medium whose contents cause a computing device to execute an application able to communicate with remote services via a local messaging service, each of the remote services having an associated proxy for communicating with the remote service, by:

for each of multiple of the remote services,

notifying the local messaging service to send a message to the remote service;

under control of the local messaging service,

identifying the proxy associated with the remote service by retrieving information associated with the remote service; and

sending the message to the identified proxy for communication to the remote service; and

receiving a response to the sent message from the remote service via the identified proxy.

32. A computing device for executing an application to communicate with remote services via a local messaging service, each of the remote services having an associated proxy for communicating with the remote service, comprising:

an application capable of, for each of multiple of the remote services, notifying the local messaging service to send a message to the remote service and receiving a response to the sent message from the remote service via a proxy associated with the remote service; and

the local messaging service capable of identifying the proxy associated with the remote service by retrieving information associated with the remote service and of sending the message to the identified proxy for communication to the remote service.

33. A computer system for executing an application to communicate with remote services via a local messaging service, each of the remote services having an associated proxy for communicating with the remote service, comprising:

means for, for each of multiple of the remote services, notifying the local messaging service to send a message to the remote service and receiving a response to the sent message from the remote service via a proxy associated with the remote service; and

means for identifying the proxy associated with the remote service by retrieving information associated with the remote service and sending the message to the identified proxy for communication to the remote service.

35. The method of claim 34 wherein each of the remote applications has multiple associated proxies for invoking distinct functions of the remote application, and wherein the identifying of the proxy associated with the remote application from the retrieved information is based at least in part on the specified function.

36. The method of claim 34 wherein the proxies are object instances, and wherein the instantiating of the proxies includes creating the object instances.

37. The method of claim 34 wherein the information is retrieved from a directory service using an identified name of the remote application.

38. The method of claim 34 wherein the retrieved information includes initialization information for the identified proxy, and wherein the instantiating of the proxy includes providing the initialization information to the proxy for use during initialization.

39. The method of claim 34 wherein the application includes multiple action handlers each able to respond to requests from external clients with responses generated in a format used by the action handler, and wherein the request to invoke the specified function is received from one of the action handler components.

40. The method of claim 39 wherein the application includes multiple view handlers each able to transform responses in formats used by action handlers into formats compatible with external clients, and including, after the receiving of the response from the invoking of the specified function, using one of the view handler components to transform the received response into a format compatible with an external client.

34. A method in a computer system for invoking functions of remote applications, each of the remote applications having an associated proxy for communicating with the remote application, the method comprising:

for each of multiple of the remote applications,

receiving a request to invoke a specified function of the remote application using at least one specified parameter value;

retrieving information associated with the remote application that identifies the proxy associated with the remote application;

when a copy of the identified proxy has not already been instantiated, instantiating a copy of the identified proxy;

notifying the identified proxy copy of the specified function and the specified parameter values;

under control of the identified proxy copy, invoking the specified function of the remote application using the specified parameter values; and

receiving a response from the invoking of the specified function.

41. A computer-readable medium whose contents cause a computing device to invoke functions of remote applications each having an associated proxy for communicating with the remote application, by:

for each of multiple of the remote applications,

receiving a request to invoke a specified function of the remote application using at least one specified parameter value;

retrieving information associated with the remote application that identifies the proxy associated with the remote application;

when a copy of the identified proxy has not already been instantiated, instantiating a copy of the identified proxy,

notifying the identified proxy copy of the specified function and the specified parameter values;

under control of the identified proxy copy, invoking the specified function of the remote application using the specified parameter values; and

receiving a response from the invoking of the specified function.

42. A computing device for invoking functions of remote applications each having an associated proxy for communicating with the remote application, comprising:

a first component capable of, for each of multiple of the remote applications, receiving a request to invoke a specified function of the remote application using at least one specified parameter value, retrieving information associated with the remote application that identifies the proxy associated with the remote application, instantiating a copy of the identified proxy, notifying the identified proxy copy of the specified function and the specified parameter values, and receiving a response from the invoking of the specified function; and

multiple proxy copies each capable of receiving a notification of a specified function and specified parameter values for one of the remote applications and of invoking the specified function of the remote application using the specified parameter values.

43. A method in a computer system for components of an executing application to communicate with remote services, each of the remote services having an associated proxy for communicating with the remote service, the executing application having a messaging service component for communicating with the associated proxies, having multiple action handler components each for responding to requests with responses generated in a format used by the action handler component, and having multiple view handler components each for transforming generated responses in formats used by action handler components into formats compatible with external clients, the method comprising:

under control of each of multiple of the action handler components,

receiving a request from a remote client to provide a service; and

providing the requested service by,

determining a need for functionality available from one of the remote services;

notifying the local messaging component to request the needed functionality from the one remote service;

receiving a response from the one remote service via the local messing component;

generating a response in a format used by the action handler component;

determining a view handler component able to transform the generated response from the format used by the action handler component to a format compatible with the remote client; and

providing the generated response to the determined view handler component for the transforming;

under control of the local messaging component,

receiving notifications from multiple action handler components each to request flmctionality from a remote service; and

for each received notification,

identifying the proxy associated with the remote service; and

sending a request for the functionality to the identified proxy for communication to the remote service;

receiving a response to the sent request from the remote service via the identified proxy; and

notifying the action handler component of the received response; and

under control of each of multiple of the view handler components,

receiving responses generated by at least one action handler component in a format used by the action handler component; and

for each received response, transforming the received response into a format that is compatible with the remote client for whom the received response was generated.