Business processes and clients can communicate multiple times to complete a single task. Also, multiple clients can communicate with the same business process at the same time. Conversations provide a straightforward way to keep track of data between calls and to ensure that a service always responds to the right client.
Conversations uniquely identify a communication between a client and a service, so that messages are always returned to the correct client.
Conversations maintain state between calls to a service, that is, they keep track of the data associated with a particular client between calls. Conversations ensure that the data associated with a particular client is saved until it is no longer needed or the operation is complete.
To learn about conversations in business processes, see the following topics:
You use the @jws:conversation-lifetime annotation in the JPD file to specify the maximum age and the maximum idle-time for a conversation. The valid specifications for conversation lifetime include:
To Specify the jws:conversation-lifetime Annotation
:: * @jws:conversation-lifetime max-age="5 day" */:
You can use the JpdProxySession interface to set and get the conversation ID used when a business process is invoked using a JPD proxy. To learn how, see About Conversation Management in Calling Business Processes. The JpdProxySession is in the WebLogic Integration Javadoc, which is available at the following URL:
http://e-docs.bea.com/wli/docs81/javadoc/com/bea/wli/bpm/proxy/JpdProxySession.html
Designing Conversational Web Services
@jws:conversation-lifetime Annotation
![]() |
|