APPLICATION CONNECTOR PARALLELISM IN ENTERPRISE APPLICATION INTEGRATION SYSTEMS

• US 20080104619A1
• Filed: 12/26/2007
• Published: 05/01/2008
• Est. Priority Date: 09/17/2002
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Das, Pranta
• Granted Patent: US 7,900,210 B2
• Time in Patent Office: Days
• US Class Current: 719/328
• CPC Class Codes: G06F 2209/5011 Pool
• CPC Class Codes: G06F 2209/5018 Thread allocation
• CPC Class Codes: G06F 9/5055 considering software capabilities, i.e. software resources associated or available to the machine

Abstract

A system for responding to requests for processing made by an integration broker to an application having a single threaded application programmer interface, comprising receiving a request for processing; determining whether the received request is event-triggered or call-triggered; sending the request to a slave process assigned to event-triggered requests, when the request is event-triggered; and sending the request to a slave process assigned to call-triggered requests, when the request is call-triggered.

Claims

1. An application integration system for responding to requests for processing, comprising a processor configured to:

spawn, with a connector, at least one connector master process and a plurality of connector slave processes, each of the connector processes having a connection to an application;

receive at the connector master process the request for processing made by an integration broker to an application that has a single threaded or non-reentrant application programming interface;

determine whether the request is of a call-triggered or event-triggered type;

send the request to at least one of the plurality of connector slave processes normally dedicated to that type of request, when the connector slave process is available;

if the received request is event-triggered, send the event-triggered request to a connector slave process normally assigned to call-triggered requests when there are not any available connector slave processes assigned to event-triggered requests; and

if the received request is call-triggered, send the call-triggered request to a connector slave process normally assigned to event-triggered requests when there are not any available connector slave processes assigned to call-triggered requests.

2. The system of claim 1, wherein the determining step comprises determining whether the received request is call-triggered.

3. The system of claim 1, wherein the determining step comprises determining whether the received request is event-triggered.

4. The system of claim 2, wherein the sending step comprises sending the request to a slave process assigned to call-triggered requests, when the request is call-triggered.

5. The system of claim 3, wherein the sending step comprises sending the request to a slave process assigned to event-triggered requests, when the request is event-triggered.

6. The system of claim 1, wherein the processor is configured to tag each received request as one of event-triggered or call-triggered.

7. The system of claim 1, further comprising an integration broker for inter-operating with at least one connector for each application integrated by the system.

8. The system of claim 7 wherein the integration broker comprises a thread pool of threads comprising a subset of threads for processing event-triggered requests and a subset of threads for processing call-triggered requests.

9. The system of claim 1, wherein the connector comprises a request dispatcher for dispatching each received request to a queue based on the type of the request, either event-triggered or call-triggered.

10. The system of claim 1, wherein the connector comprises a plurality of resource class request queues for queuing requests.

11. The system of claim 1, wherein the connector comprises a resource cache comprising resource class pools and slave coordinators.

12. The system of claim 1, wherein the connector comprises a plurality of connector slave processes.

13. A machine-usable medium comprising program instructions comprising connector instructions for:

spawning, with a connector, at least one connector master process and a plurality of connector slave processes, each of the connector processes having a connection to an application;

receiving at the connector master process a request for processing from an integration broker requesting a service of the application that has a single threaded or non-reentrant application programming interface;

determining whether the request is of a call-triggered or event -triggered type;

determining whether a connector slave process is available;

sending the request to at least one of the plurality of connector slave processes normally dedicated to that type of request, when the connector slave process is available

if the request is event-triggered, sending the event-triggered request to a connector slave process normally assigned to call-triggered requests when there are not any available connector slave processes assigned to event-triggered requests; and

if the request is call-triggered, sending the call-triggered request to a connector slave process normally assigned to event-triggered requests when there are not any available connector slave processes assigned to call-triggered requests.