APPLICATION CONNECTOR PARALLELISM IN ENTERPRISE APPLICATION INTEGRATION SYSTEMS

• US 20080052726A1
• Filed: 10/28/2007
• Published: 02/28/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 8,010,972 B2
• Time in Patent Office: Days
• US Class Current: 718/107
• 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 and method 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. A method for responding to requests with a connector, said method comprising steps of:

spawning, with the 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 an 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 the connector slave process is available; and

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.

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

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

4. The method 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 method 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 method of claim 3, further comprising sending the event-triggered request to a process normally assigned to call-triggered requests when there are not any available connector slave connector processes assigned to event-triggered requests.

7. The method of claim 2, further comprising sending the call-triggered request to a connector process normally assigned to event-triggered requests when there are not any available connector slave connector processes assigned to call-triggered requests.

8. 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; and

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

9. The system of claim 8, wherein the processor is configured to send an event-triggered request to a process normally assigned to call-triggered requests when there are not any available connector slave processes assigned to event-triggered requests.

10. The system of claim 8, wherein the processor is configured to send a call-triggered request to a process normally assigned to event-triggered requests when there are not any available connector slave processes assigned to call-triggered requests.

11. The system of claim 8, further comprising a connector for executing a connector master process.