Use Cases for Lock Removal Notification

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

Create Party with Immediate Lock

<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, say Lock 2 with Timeout 240 Seconds

<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>240</com:timeout>
</com:lock>
</par:entity>
</ser:updatePartyRequest>

Update the Same Party to Remove the Lock, say Lock 2

<ser:updatePartyRequest businessTransactionId="?" correlationId="?" sessionId="?">
<!--Optional:-->
<!--1 or more repetitions:-->
<par:entity>
<com:id>Party1</com:id>
<com:unlock>
<com:key> Party1_KEY_2</com:key>
</com:unlock>
</par:entity>
</ser:updatePartyRequest>
Note: Here, Party1_KEY_2 is removed explicitly which is waiting for party till its timeout. You get (Party1_KEY_2) lock removed notification on topic "com.tibco.inventory.notification.lock.removed.topic.tibco".