System and method using asynchronous messaging for application integration

• US 20030093471A1
• Filed: 10/15/2002
• Published: 05/15/2003
• Est. Priority Date: 10/18/2001
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Upton, Mitch
• Application Number:
  US10/271,423
• Publication Number:
  US 20030093471A1
• Time in Patent Office: Days
• US Class Current: 709/203
• 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

The J2EE Connector architecture (JCA) does not provide for the use of asynchronous messaging. Embodiments of the present invention utilize a call-back listener passed with a request or service invocation to listen for responses from a JCA-compliant server or enterprise system. A client application passing the request can go about other processing instead of waiting for a response. A unique identifier can be used with an application view component that provides the interface to the enterprise system or server. This identifier can be used to track and filter messages for a particular client application.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for asynchronous messaging between integrated applications, comprising:

an application view component adapted to provide an interface to an enterprise system for a client application;

a request queue adapted to store request messages from the application view for retrieval by an enterprise system;

a response queue adapted to store response messages from the enterprise system; and

a call-back listener adapted to notify the client application when a response message is stored in the response queue.

2. A system according to claim 1, further comprising:

a resource adapter adapted to invoke functionality in the enterprise system and expose that functionality to the application view component.

3. A system according to claim 1, further comprising:

an application integration server adapted to contain the application view component.

4. A system according to claim 3, further comprising:

an event routeradapted send an event message from the enterprise system to the response queue.

5. A system according to claim 4, wherein:

the call-back listener is further adapted to notify the client application when an event message is being stored in the response queue.

6. A system according to claim 4, further comprising:

an event generator adapted to generate an event in an enterprise system to be sent by the event router.

7. A system according to claim 4, wherein:

the call-back listener is adapted to listen for related event messages.

8. A system according to claim 4, wherein:

the call-back listener is adapted to listen for related event messages, related event messages associated with a topic.

9. A system according to claim 1, further comprising:

a request handler adapted to direct requests from a client application to an appropriate request queue.

10. A system according to claim 1, wherein:

the application view component has a unique identifier that can be used for filtering requests and responses.

11. A system according to claim 1, wherein:

at least one of the request queue and response queue is a JMS queue.

12. A method for asynchronous messaging between integrated applications, comprising:

creating a request to invoke a service in an enterprise system;

passing a call-back listener with the request;

posting the request onto a request message queue for retrieval by the enterprise system;

putting a response from the enterprise system onto a response queue; and

monitoring the response queue with the call-back listener and notifying the application creating the request when a response is present in the response queue.

13. A method according to claim 12, further comprising:

using an application view component as an interface to the enterprise system.

14. A method according to claim 13, further comprising:

using a resource adapter to invoke functionality in the enterprise system and expose that functionality to the application view component.

15. A method according to claim 12, further comprising:

sending an event message from the enterprise system to the response queue using an event router.

16. A method according to claim 15, further comprising:

notifying the client application when an event message is being stored in the response queue.

17. A system according to claim 15, further comprising:

specifying the call-back listener to listen for related event messages.

18. A system according to claim 12, further comprising:

using a request handler to direct requests from a client application to an appropriate request queue.

19. A system according to claim 13, further comprising:

assigning the application view component a unique identifier that can be used for filtering requests and responses.

20. A method for asynchronous messaging between integrated applications, comprising:

posting a request onto a request message queue for retrieval by an enterprise system;

putting a response from the enterprise system onto a response queue; and

monitoring the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.

21. A computer-readable medium, comprising:

means for posting a request onto a request message queue for retrieval by an enterprise system;

means for putting a response from the enterprise system onto a response queue; and

means for monitoring the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.

22. A computer program product for execution by a server computer for integrating applications, comprising:

computer code for posting a request onto a request message queue for retrieval by an enterprise system;

computer code for putting a response from the enterprise system onto a response queue; and

computer code for monitoring the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.

23. A system for asynchronous messaging, comprising:

means for posting a request onto a request message queue for retrieval by an enterprise system;

means for putting a response from the enterprise system onto a response queue; and

means for monitoring the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.

24. A computer system comprising:

a processor;

object code executed by said processor, said object code configured to;

post a request onto a request message queue for retrieval by an enterprise system;

put a response from the enterprise system onto a response queue; and

monitor the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.

25. A computer data signal embodied in a transmission medium, comprising:

a code segment including instructions to post a request onto a request message queue for retrieval by an enterprise system;

a code segment including instructions to put a response from the enterprise system onto a response queue; and

a code segment including instructions to monitor the response queue with a call-back listener and notifying the application posting the request when a response is present in the response queue.