System and method for implementing an event adapter

• US 7,552,443 B2
• Filed: 10/15/2002
• Issued: 06/23/2009
• Est. Priority Date: 10/18/2001
• Status: Expired due to Term

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch
• Primary Examiner(s): Nguyen; Van H
• Application Number:
  US10/271,157
• Publication Number:
  US 20030093403A1
• Time in Patent Office: 2,443 Days
• Field of Search: 719310-316, 719/328, 719/330, 719/318, 707/101, 707/104, 707/109, 707/102, 717/109, 717/120, 717/123
• US Class Current: 719/315
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: G06Q 10/103 Workflow collaboration or project management
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

Events can be extracted from a resource such as an enterprise system using an application view component in combination with an event adapter. The event can be pulled by a client application or pushed by the enterprise system. The application view component can provide an interface to the enterprise system for the client application. The event adapter allows the enterprise system to initiate communication with, or receive communication from, the client application. The event adapter can extract data about the event from the enterprise system, create an object such as an XML-based object containing the data, and notify the application view component. The application view component can pass the event to the client application.

Claims

1. A computer system having a processor and a computer readable storage medium for connecting a client application to an enterprise system, said computer system comprising:

a service adapter that invokes a specific function in the enterprise system to update at least one record in a database, said service adapter being stored on the computer readable storage medium;

an event adapter that enables the enterprise system to initiate communication with the client application by triggering an event within the enterprise system, said event adapter being stored on the computer readable storage medium, wherein the event represents an action occurring in the enterprise system, the client application having registered its interest to be notified of the action'"'"'s occurrence; and

an application view component that integrates the client application with the enterprise system by providing the client application with a unified interface to services and events in the enterprise system, wherein said services are exposed by the service adapter and said events are exposed by the event adapter, said application view component being stored on the computer readable storage medium;

wherein the event adapter reads data that describes the event from the enterprise system and transforms the data from a format specific to the enterprise system into an XML-based object and notifies the application view component; and

wherein the application view component extracts the data about the event from the enterprise system through the event adapter and propagates the data in the XML-based object to the client application and further provides the client application with an XML schema that describes the XML-based object.

2. The computer system according to claim 1, wherein:

the event adapter allows the enterprise system to initiate communication with the client application only for types of events specified by the client application.

3. The computer system according to claim 1, wherein:

the application view component is further adapted to propagate the data in an XML document.

4. The computer system according to claim 1, wherein:

the event adapter is further adapted to extract data about the event from the enterprise system, and makes that data available to the application view component.

5. The computer system according to claim 1, wherein:

the event adapter is adapted to transform the data from a format specific to the enterprise system to an XML document.

6. The computer system according to claim 5, wherein the XML schema is based on metadata in the enterprise system.

7. The computer system according to claim 6, wherein:

the XML document conforms to the XML schema.

8. The computer system according to claim 1, wherein:

the event adapter is Java 2 Enterprise Edition (J2EE) compliant.

9. The computer system according to claim 1, wherein:

the event adapter has an adapter logical name that represents the event adapter.

10. The computer system according to claim 1, wherein:

the application view component is further adapted to allow the client application to register interest in a type of event.

11. The computer system according to claim 10, wherein:

the application view component is further adapted to notify the client application whenever an event within the target application for which the client application has registered interest.

12. The computer system according to claim 1, wherein:

the event adapter is further adapted to allow for asynchronous messaging between the enterprise system and the client application.

13. The computer system according to claim 1, wherein:

the event adapter is further adapted to allow bi-directional communication.

14. The computer system according to claim 1, wherein:

the event adapter is further adapted to support an event at the business level.

15. The computer system according to claim 1, wherein:

the event adapter is an in-process event adapter, adapted to execute within the same process as the enterprise system for extracting event data.

16. The computer system according to claim 1, wherein:

the event adapter is an out-of-process adapter, adapted to execute in a separate process than the enterprise system for extracting event data.

17. The computer system according to claim 1, wherein:

the event adapter is further adapted to propagate the data for the event to an event context, the event context being obtained from the application view component.

18. The computer system according to claim 1, wherein:

the event adapter is not specific to the enterprise system or client application.

19. The computer system according to claim 1, wherein:

the event adapter can be plugged into any application server that supports the Java 2 Enterprise Edition (J2EE) Connector Architecture specification.

20. The computer system according to claim 1, wherein:

the event adapter further comprises a user interface adapted to deploy application view components.

21. The computer system according to claim 1, further comprising

a connector architecture mechanism adapted to provide at least one of connection pooling, transaction management, and security services for the event adapter.

22. The computer system according to claim 1, further comprising:

a call-back listener adapted to handle a response for the application view that is received from the enterprise system.

23. The computer system according to claim 1, further comprising:

a Java Messaging Service (JMS) queue adapted to receive a request from the application view component and store the request until the request is passed to the enterprise system.

24. The computer system according to claim 1, further comprising:

an event generator adapted to generate an event for the enterprise system and post the event.

25. The computer system according to claim 24, further comprising:

an event router adapted to receive the post of the event from the event generator and route the event to a location where the event can be retrieved by the application view component.

26. The computer system according to claim 25, wherein:

the event router routes the event by publishing the event as an event message to an application view topic.

27. The computer system according to claim 26, further comprising:

an event listener adapted to listen to the application view topic.

28. The computer system according to claim 1, wherein:

the event adapter further comprises at least one Web page adapted to allow the event adapter to collect properties for the event.

29. The computer system according to claim 1, wherein:

the event service adapter is further adapted to transform data passing between the enterprise system and the client application.

30. The computer system according to claim 29, wherein:

the event adapter uses XML to transform the data.

31. The computer system according to claim 1, further comprising:

a run-time engine adapted to host the event adapter.

32. The computer system according to claim 31, wherein:

the run-time engine is further adapted to manage connections to the enterprise system.

33. The computer system according to claim 1, further comprising:

a managed connection instance for the event adapter, encapsulating resources necessary to communicate with the enterprise system.

34. The computer system of claim 1 wherein the application view is specific to a single adapter and defines a view of functions exposed by said single adapter.

35. The computer system of claim 1 wherein the application view brokers requests between the enterprise system and external applications.

36. A computer implemented method for propagating an event from an underlying enterprise system through an event adapter, comprising:

maintaining a service adapter that invokes a specific function in the enterprise system, said service adapter being stored on a computer readable storage medium;

maintaining an application view component implemented on top of the service adapter, wherein said application view component integrates a client application with the enterprise system by providing the client application with a unified interface to services and events in the enterprise system, said application view component being stored on the computer readable storage medium;

generating an event in the enterprise system, wherein the event represents an action occurring in the enterprise system, the client application having registered its interest to be notified of the action'"'"'s occurrence;

extracting data for the event from the enterprise system;

transforming the data for the event from enterprise specific format into an event message in an extensible markup language format;

routing the event message to a listener;

extracting the event message from the listener;

propagating the event message to the client application by the application view component; and

providing a schema that describes the event message to the client application, the schema based on metadata in the enterprise system.

37. The computer implemented method according to claim 36, wherein:

transforming the data further comprises transforming the data into an XML document.

38. A computer implemented method for pulling an event from an underlying enterprise system through an event adapter, comprising:

maintaining a service adapter that invokes a specific function in the enterprise system, said service adapter being stored on a computer readable storage medium;

maintaining an application view component implemented on top of the service adapter, wherein said application view component integrates a client application with the enterprise system by providing the client application with a unified interface to services and events in the enterprise system, said application view component being stored on the computer readable storage medium;

requesting an event from an enterprise system, wherein the event represents an action occurring in the enterprise system, the client application having registered its interest to be notified of the action'"'"'s occurrence;

extracting data for the event from the enterprise system;

transforming the data for the event from an enterprise specific format into an event message in XML format;

routing the event message to a component requesting the event by the application view component; and

providing the component requesting the event with an XML schema that describes the event message such that the component is able to read the event message.