How public conversation management integrated with local business process management

In order for enterprises to collaborate at the business-process level, they must deal with two kinds of processes: the public conversation processes specifying inter-enterprise document flows, and the private business processes specifying local workflows of document manipulation and other related tasks. The provisioning, interaction and integration of conversation management and business process management, have become the common interest of the e-business (electronic business) industry. We discuss the relationship and interaction between conversation management and business process management; point out the difference between public conversation processes (e.g. BPSS processes) and peer-conversation processes (e.g. BPEL4WS processes). We then illustrate our collaborative process management system that has functionally separated conversation manager and business process manager. The conversation manager is based on the ebXML (Extensible Markup Language) BPSS (Business Process Execution Language) standard; it is used for validating document exchange at run-time and for activating corresponding process tasks. We have also proposed the conversation model driven asynchronous task activation mechanism for interaction between a conversation process and the coupled business process dynamically. With this mechanism, generic APIs (application program interfaces) between the conversation manager and the business process manager can be easily defined and used by multiple plugged-in conversation managers.