Converged Call Flow and Web Service Application Integration Using a Processing Engine

1. A method for providing converged application integration, the method comprising: receiving a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components, a plurality of call flow segments, each of the plurality of call flow segments having a series of message steps, and at least one binding between a given Web services component within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determining, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, performing an interaction operation based on the binding interaction type; consuming, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generating, by the converged application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converged application.

2. The method of claim 1 , wherein determining whether the interaction is invoked comprises: listening, by the converged application integration engine, to signaling sent between the converged application and its clients.

3. The method of claim 2 , wherein the signaling comprises session initiation protocol signaling from a session initiation protocol platform.

4. The method of claim 2 , wherein the signaling comprises Web services invocations from a service oriented application integration platform.

5. The method of claim 1 , further comprising: storing, by the converged application integration engine, state information for the converged application.

6. The method of claim 5 , further comprising: responsive to the given call flow segment reaching a predetermined binding point, making a Web service invocation with state information corresponding to the predetermined binding point.

7. The method of claim 6 , wherein the state information is a simple object access protocol attachment.

8. The method of claim 6 , wherein the state information comprises changes in operation parameters or changes in execution history since a last time an interaction of the same type occurred.

9. A computer program product comprising a computer storage medium having a computer readable program stored thereon, wherein the computer readable program, when executed on a computing device, causes the computing device to: receive a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components a plurality of call flow segments, each of the plurality of call flow segments having a series of message steps, and at least one binding between a given Web services component and a given call flow segment within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determine, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, perform an interaction operation based on the binding interaction type; consume, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generate, by the converged application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converged application.

10. The computer program product of claim 9 , wherein determining whether the interaction is invoked comprises: listening, by the converged application integration engine, to signaling sent between the converged application and its clients.

11. The computer program product of claim 10 , wherein the signaling comprises session initiation protocol signaling from a session initiation protocol platform.

12. The computer program product of claim 10 , wherein the signaling comprises Web services invocations from a service oriented application integration platform.

13. The computer program product of claim 9 , wherein the computer readable program, when executed on a computing device, further causes the computing device to: store, by the converged application integration engine, state information for the converged application.

14. The computer program product of claim 13 , wherein the computer readable program, when executed on a computing device, further causes the computing device to: responsive to the given call flow segment reaching a predetermined binding point, make a Web service invocation with state information corresponding to the predetermined binding point.

15. The computer program product of claim 14 , wherein the state information is a simple object access protocol attachment.

16. A data processing system for providing converged application integration, the data processing system comprising: a processor, and a memory coupled to the processor, wherein the memory contains instructions which, when executed by the processor, cause the processor to: receive a converged application in a converged application integration engine, wherein the converged application defines a plurality of Web services components, a plurality of call flow segments, each of the call flow segments having a series of message steps, and at least one binding between a given Web services component and a given call flow segment within the plurality of Web services components and a given call flow segment within the plurality of call flow segments, wherein the binding is associated with an interaction and has a binding interaction type; determine, by the converged application integration engine, whether the interaction is invoked by the given Web services component or the given call flow segment; responsive to invocation of the interaction, perform an interaction operation based on the binding interaction type; consume, by the converged application integration engine, a Web services description language document with call flow extensions to form the converged application, wherein the Web services description language document describes a pre-existing application; and generate, by the converted application integration engine, one or more Web service implementations and one or more session initiation protocol servlets for the converted application.