Execution of a BPEL process by simulating partners

Abstract

Mechanisms allow a user to test a BPEL process by simulating partner Web services. To simulate the partner Web services, a development environment is extended to include an intermediate component that intercepts messages intended for a partner Web service and displays those messages in a testing user interface. In the testing user interface, a user can create and send messages in direct response to the messages invoked while executing the BPEL process. The development environment may also include an alternate deployment descriptor, as part of a BPEL engine. The alternate deployment descriptor identifies where a message should be routed. For example, the alternate deployment descriptor lists the address of the intermediate component, rather than the actual partner Web service address, so that messages can be redirected to the testing user interface.

What is claimed is: 
     
       1. A machine implemented method for testing a business process, comprising:
 executing, by a computer processor, a portion of the business process comprising an original deployment descriptor describing a service web address for invoking a service provided by a business partner, and an alternate deployment descriptor describing a testing user interface address, wherein the business process is executed by a processing engine; 
 activating the alternate deployment descriptor, wherein the alternate deployment descriptor is loaded via a testing user interface to replace the original deployment descriptor within the business process; 
 receiving, by the testing user interface, first user input from a user; 
 generating, by the testing user interface, a user request message addressed to the business process using the first user input; 
 sending the user request message to the business process, wherein the business process, in response to receiving the user request message, invokes the service using the testing user interface address, so that the service is not actually invoked using the service web address; 
 receiving, by the testing user interface, a business partner request message sent by the business process in response to the invoking; 
 displaying, to the user by the testing user interface, the business partner request message; 
 receiving, by the testing user interface in response to the displaying, second user input from the user; 
 generating, by the testing user interface using the second user input, a business partner response message which simulates a response from the service; 
 sending, by the testing user interface, the business partner response message to the processing engine; and 
 processing, by the computer processor, the business partner response message to continue executing the business process as if the business partner response message had been an actual response from the service. 
 
     
     
       2. The method of  claim 1 , wherein receiving the business partner request message comprises:
 receiving the business partner request message by an intermediate component; and 
 forwarding, by the intermediate component, the business partner request message to the testing user interface. 
 
     
     
       3. The method of  claim 1 , wherein invoking the service using the testing user interface address comprises:
 obtaining, from the alternate deployment descriptor, the testing user interface address; and 
 generating the business partner request message addressed to the testing user interface address corresponding to an intermediate component. 
 
     
     
       4. The method of  claim 1 , further comprising:
 storing the business partner response message as a test case to be used for future testing of the business process. 
 
     
     
       5. The method of  claim 1 , wherein the service has not actually been implemented and is currently not provided by the business partner. 
     
     
       6. A non-transitory machine-readable storage medium comprising a set of instructions for performing the steps of:
 executing, by a computer processor, a portion of a business process comprising an original deployment descriptor describing a service web address for invoking a service provided by a business partner, and an alternate deployment descriptor describing a testing user interface address, wherein the business process is executed by a processing engine; 
 activating the alternate deployment descriptor, wherein the alternate deployment descriptor is loaded via a testing user interface to replace the original deployment descriptor within the business process; 
 receiving, by the testing user interface, first user input from a user; 
 generating, by the testing user interface, a user request message addressed to the business process using the first user input; 
 sending user request message to the business process, wherein the business process, in response to receiving the user request message, invokes the service using the testing user interface address, so that the service is not actually invoked using the service web address; 
 receiving, by the testing user interface, a business partner request message sent by the business process in response to the invoking; 
 displaying, to the user by the testing user interface, the business partner request message; 
 receiving, by the testing user interface, second user input from the user; 
 generating, by the testing user interface using the second user input, a business partner response message which simulates a response from the service; 
 sending, by the testing user interface, the business partner response message to the processing engine; and 
 processing, by the computer processor, the business partner response message to continue executing the business process as if the business partner response message had been an actual response from the service. 
 
     
     
       7. The non-transitory machine-readable storage medium of  claim 6 , wherein receiving the request message comprises:
 receiving the business partner request message by an intermediate component; and 
 forwarding, by the intermediate component, the business partner request message to the testing user interface. 
 
     
     
       8. The non-transitory machine-readable storage medium of  claim 6 , wherein invoking the service using the testing user interface address comprises:
 obtaining, from the alternate deployment descriptor, the testing user interface address; and 
 generating the business partner request message addressed to the testing user interface address corresponding to an intermediate component. 
 
     
     
       9. The non-transitory machine-readable storage medium of  claim 6 , the method further comprising:
 storing the business partner response message as a test case to be used for future testing of the business process. 
 
     
     
       10. The non-transitory machine-readable storage medium of  claim 6 , wherein the service has not actually been implemented and is currently not provided by the business partner.