Use Cases for Lock Expired Notification

The following use cases describe the lock expired notification for parties.

Create Party with Immediate Lock, say Lock 1

<ser:createPartyRequest businessTransactionId="?" correlationId="?" sessionId="?">
<par:entity>
<com:type>enterprise</com:type>
<com:status>active</com:status>
<!--Optional:-->
<com:id>Party1</com:id>
<com:lock>Party1_KEY_1</com:lock>
</par:entity>
</ser:createPartyRequest>

Update the Party with Delayed Lock

<ser:updatePartyRequest businessTransactionId="?" correlationId="?" sessionId="?">
<par:entity>
<com:id> Party1</com:id>
<com:lock>
<com:key> Party1_KEY_2</com:key>
<com:priority>10</com:priority>
<com:timeout>800</com:timeout>
</com:lock>
</par:entity>
</ser:updatePartyRequest>
Note: As Party1_KEY_1 is an immediate lock, and as Party1_KEY_1 is not removed by the owner, Party1_KEY_2 will expire automatically after timeout (800 seconds). You get (Party1_KEY_2) lock expired notification on topic "com.tibco.inventory.notification.lock.expired.topic.tibco".