Application connector parallelism in enterprise application integration systems
First Claim
Patent Images
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 Assignments
0 Petitions
Accused Products
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.
-
Citations
13 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A non-transitory 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.
-
Specification