Generic wait service: pausing and resuming a plurality of BPEL processes arranged in correlation sets by a central generic wait server
First Claim
1. A method of pausing processing of a plurality of business processes by a plurality of service-oriented application (SOA) instances running on one or more application servers, wherein each of the plurality of business processes is processed by at least one associated SOA instance of the plurality of SOA instances, each of the plurality of business processes is processed by at least one associated event producer of a plurality of event producers running on one or more event servers, and each of the plurality of business processes is associated with a processing status corresponding to the processing performed on the business process, the method comprising:
- receiving, by a generic wait server, a plurality of initiation messages from the plurality of SOA instances when each of the plurality of SOA instances are entering pause states, wherein each of the plurality of initiation messages comprises;
a reference to the business processes of the plurality of business processes being processed by the associated SOA instance entering the pause state that sent the initiation message, wherein the business process is distinct from the associated SOA instance; and
an exit criterion that identifies a condition that must be satisfied by a status of the business processes before the associated SOA instance exits its pause state;
generating, by the generic wait server, one or more correlation sets, wherein;
each of the one or more correlation sets are associated with a particular business process of the plurality of business processes; and
each of the one or more correlation sets groups together a plurality of SOA instances to each associated business process;
receiving, by the generic wait server, a plurality of notifications from the plurality of event producers, wherein each of the plurality of notifications comprises;
a reference to the business process of the plurality of business processes being processed by the associated event producer, wherein the business process being processed by the associated event producer is distinct from the associated event producer; and
a status of the business process being processed by the associated event producer; and
for each notification in the plurality of notifications;
identifying, by the generic wait server, a correlation set whose particular business process corresponds to the business process referenced in the notification;
determining, by the generic wait server, whether the status of the business process in the notification satisfies the condition of the exit criterion of each of the plurality of associated SOA instances of the identified correlation set; and
causing, by the generic wait server, the plurality of SOA instances for which the associated conditions have been satisfied to exit their pause states and resume processing of their associated business processes.
1 Assignment
0 Petitions
Accused Products
Abstract
A method of pausing a plurality of service-oriented application (SOA) instances may include receiving, from an instance of an SOA entering a pause state, an initiation message. The initiation message may include an exit criterion that identifies a business condition that must be satisfied before the instance of the SOA exits the pause state. The method may also include receiving a notification from an event producer, the notification comprising a status of a business event and determining whether the status of the business event satisfies the business condition of the exit criterion. The method may additionally include sending, in response to a determination that the status of the business event satisfies the business condition of the exit criterion, an indication to the instance of the SOA that the business condition has been satisfied such that the instance of the SOA can exit the pause state.
-
Citations
20 Claims
-
1. A method of pausing processing of a plurality of business processes by a plurality of service-oriented application (SOA) instances running on one or more application servers, wherein each of the plurality of business processes is processed by at least one associated SOA instance of the plurality of SOA instances, each of the plurality of business processes is processed by at least one associated event producer of a plurality of event producers running on one or more event servers, and each of the plurality of business processes is associated with a processing status corresponding to the processing performed on the business process, the method comprising:
-
receiving, by a generic wait server, a plurality of initiation messages from the plurality of SOA instances when each of the plurality of SOA instances are entering pause states, wherein each of the plurality of initiation messages comprises; a reference to the business processes of the plurality of business processes being processed by the associated SOA instance entering the pause state that sent the initiation message, wherein the business process is distinct from the associated SOA instance; and an exit criterion that identifies a condition that must be satisfied by a status of the business processes before the associated SOA instance exits its pause state; generating, by the generic wait server, one or more correlation sets, wherein; each of the one or more correlation sets are associated with a particular business process of the plurality of business processes; and each of the one or more correlation sets groups together a plurality of SOA instances to each associated business process; receiving, by the generic wait server, a plurality of notifications from the plurality of event producers, wherein each of the plurality of notifications comprises; a reference to the business process of the plurality of business processes being processed by the associated event producer, wherein the business process being processed by the associated event producer is distinct from the associated event producer; and a status of the business process being processed by the associated event producer; and for each notification in the plurality of notifications; identifying, by the generic wait server, a correlation set whose particular business process corresponds to the business process referenced in the notification; determining, by the generic wait server, whether the status of the business process in the notification satisfies the condition of the exit criterion of each of the plurality of associated SOA instances of the identified correlation set; and causing, by the generic wait server, the plurality of SOA instances for which the associated conditions have been satisfied to exit their pause states and resume processing of their associated business processes. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A non-transitory computer-readable medium comprising instructions which, when executed by one or more processors, cause the one or more processors to pause processing of a plurality of business processes by a plurality of service-oriented application (SOA) instances running on one or more application servers, wherein each of the plurality of business processes is processed by at least one associated SOA instance of the plurality of SOA instances, each of the plurality of business processes is processed by at least one associated event producer of a plurality of event producers running on one or more event servers, and each of the plurality of business processes is associated with a processing status corresponding to the processing performed on the business process, by performing operations comprising:
-
receiving, by a generic wait server, a plurality of initiation messages from the plurality of SOA instances when each of the plurality of SOA instances are entering pause states, wherein each of the plurality of initiation messages comprises; a reference to the business processes of the plurality of business processes being processed by the associated SOA instance entering the pause state that sent the initiation message, wherein the business process is distinct from the associated SOA instance; and an exit criterion that identifies a condition that must be satisfied by a status of the business processes before the associated SOA instance exits its pause state; generating, by the generic wait server, one or more correlation sets, wherein; each of the one or more correlation sets are associated with a particular business process of the plurality of business processes; and each of the one or more correlation sets groups together a plurality of SOA instances to each associated business process; receiving, by the generic wait server, a plurality of notifications from the plurality of event producers, wherein each of the plurality of notifications comprises; a reference to the business process of the plurality of business processes being processed by the associated event producer, wherein the business process being processed by the associated event producer is distinct from the associated event producer; and a status of the business process being processed by the associated event producer; and for each notification in the plurality of notifications; identifying, by the generic wait server, a correlation set whose particular business process corresponds to the business process referenced in the notification; determining, by the generic wait server, whether the status of the business process in the notification satisfies the condition of the exit criterion of each of the plurality of associated SOA instances of the identified correlation set; and causing, by the generic wait server, the plurality of SOA instances for which the associated conditions have been satisfied to exit their pause states and resume processing of their associated business processes. - View Dependent Claims (12, 13, 14, 15, 16, 17)
-
-
18. A system comprising:
-
one or more processors; and one or more memory devices comprising instructions which, when executed by one or more processors, cause the one or more processors to pause processing of a plurality of business processes by a plurality of service-oriented application (SOA) instances running on one or more application servers, wherein each of the plurality of business processes is processed by at least one associated SOA instance of the plurality of SOA instances, each of the plurality of business processes is processed by at least one associated event producer of a plurality of event producers running on one or more event servers, and each of the plurality of business processes is associated with a processing status corresponding to the processing performed on the business process, by performing operations comprising; receiving, by a generic wait server, a plurality of initiation messages from the plurality of SOA instances when each of the plurality of SOA instances are entering pause states, wherein each of the plurality of initiation messages comprises; a reference to the business processes of the plurality of business processes being processed by the associated SOA instance entering the pause state that sent the initiation message, wherein the business process is distinct from the associated SOA instance; and an exit criterion that identifies a condition that must be satisfied by a status of the business processes before the associated SOA instance exits its pause state; generating, by the generic wait server, one or more correlation sets, wherein; each of the one or more correlation sets are associated with a particular business process of the plurality of business processes; and each of the one or more correlation sets groups together a plurality of SOA instances to each associated business process; receiving, by the generic wait server, a plurality of notifications from the plurality of event producers, wherein each of the plurality of notifications comprises; a reference to the business process of the plurality of business processes being processed by the associated event producer, wherein the business process being processed by the associated event producer is distinct from the associated event producer; and a status of the business process being processed by the associated event producer; and for each notification in the plurality of notifications; identifying, by the generic wait server, a correlation set whose particular business process corresponds to the business process referenced in the notification; determining, by the generic wait server, whether the status of the business process in the notification satisfies the condition of the exit criterion of each of the plurality of associated SOA instances of the identified correlation set; and causing, by the generic wait server, the plurality of SOA instances for which the associated conditions have been satisfied to exit their pause states and resume processing of their associated business processes. - View Dependent Claims (19, 20)
-
Specification