Home Communities

BPM

Up to Conversations in BPM

This Question is Answered

1 "correct" answer available (4 pts)

1 2 Previous Next

"short lock" in workspace browser or iProcess

Created on: Feb 7, 2010 6:13 PM

Created by: Andriy

Hi All

How do i can use short lock in workspace browser or in iPriocess ObjectServer

As i see workspace browser alway do LongLock. But the problem exists if user has any network failure or even simply press close button on the form in workspace browser the workitem left LongLocked.

It is much more interesting to have short lock while user work with workitem. or to have ability to lose long long lock in reasonable time.

The even place I found information about short lock is a TIBCO iProcess™ Server Objects (Java)

Programmer’s Guide

What’s the Difference Between a “Lock” and a “Long Lock”?

There are two types of locks possible for a work item:

•A lock is one that is established from the Work Queue Manager (for those that are using the

TIBCO iProcess Workspace (Windows)). If the work item is locked in this way, the

vWorkItem.isLocked method will return True. This type of lock is not persistent — if the cli-

ent exits, the work item is automatically unlocked.

•A long lock is one that is established using the TIBCO iProcess Server Objects lockItems

method. If the work item is locked in this way, the vWorkItem.isLongLocked method will

return True. This type of lock is persistent — if the client exits, the work item will remain

locked.

But I have not found any other information about short lock or how to prevent persistent lock on opening form in workspace browser.

Tags: iprocess, workspace_browser, forms, ipe, spo, sso, iprocess_server_objects, workspace, iprocess_workspace_browser

Binaya Kumar Lenka

227 posts since
Jun 12, 2009

1. Feb 8, 2010 11:04 AM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi,

I already Reply to this type of question plz check the below url

Regards

Binaya

Andriy

24 posts since
Jan 13, 2010

2. Feb 8, 2010 5:45 PM

in response to: Binaya Kumar Lenka

Re: "short lock" in workspace browser or iProcess

Binaya Kumar Lenka, I see no link in your answer.

John Foster

571 posts since
Apr 29, 2008

3. Feb 8, 2010 7:53 PM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Long locks are created by the web client, and persist until they are explicitly over-ridden by an administrator or by the original user logging in again.

Short locks are created when logging in via the Windows client - this sort of client is persistent and the server can observe if the client disappears. this sort of lock persists until it is over-ridden by an administrator or by the server being restarted.

Binaya Kumar Lenka

227 posts since
Jun 12, 2009

4. Feb 8, 2010 9:47 PM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi,

Please check the below url.

http://www.tibcommunity.com/message/34903#34903

Andriy

24 posts since
Jan 13, 2010

5. Feb 9, 2010 5:54 AM

in response to: John Foster

Re: "short lock" in workspace browser or iProcess

Do we have any API to use short lock in our application?

With long locks I see many problems.

If we have some problems with connection we will have persistens locks on some workitems and we need to wait Administrator to correct this.

Also there is no way to check how long workitem is locked. so short locks looks like more interesting for using in application.

So do we have any APi to use short locks?

or how to automate unlocking for workitems wich were locked by some network errors.

Karthick P

68 posts since
Oct 22, 2008

6. Feb 9, 2010 7:35 AM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi Andriy

Short locks come into picture only when using iProcess windows client .When using sso api's it is always a long lock.

So,either you have to use the below swutil command or unlock using the sso API

swutil UNLOCKMAIL queuename reqid:hostname [/t]
where:
• queuename is the work queue that contains the work item you want to unlock. Either
specify a queue name or use:
— ALL to specify all work queues.
— $UNDELIV to specify the Undelivered Work Items queue.

reqid:hostname is the unique identifier (in the format reqid:hostname for example,
10245:node1) of the work item that you want to unlock.
/t is an optional parameter which should be used if queuename is a test queue.

This is a command line option only.Also to unlock a work item this way you must have a MENUNAME of ADMIN .

Also check out this code snippet to unlock a workitem using Java sso api

public void unlockWorkItem(String nodeName, String queueName, vNodeId vnode, String loginName, String passWord,String workItemTag) throws vException {
sWorkQ sworkq = null;
vWorkItem[] checkItem;
String[] strtag;

sworkq = new sWorkQ(vWorkQ.makeTag(nodeName, queueName, true),vnode, loginName,passWord);
strtag = new String[1];

strtag[0] = workItemTag;
checkItem = sworkq.getWorkItems(strtag,new vWIContent());

if (checkItem[0].isLocked() == false) {
sworkq.unlockItems(strtag); //unlock the work item
}
}

Regards

Karthick

John Foster

571 posts since
Apr 29, 2008

7. Feb 9, 2010 9:16 AM

in response to: Karthick P

Re: "short lock" in workspace browser or iProcess

When using the standard iProcess Workspace Browser client, if a user disappears leaving a workitem long-locked, then when that user logs back in and goes to that workitem, it allows them to over-ride the lock.

Andriy

24 posts since
Jan 13, 2010

8. Feb 9, 2010 1:32 PM

in response to: Karthick P

Re: "short lock" in workspace browser or iProcess

1) Can we get the timestamp when workitem was locked ?

2) Do I correctly undestand that we have no ability to use short lock in our application?

Binaya Kumar Lenka

227 posts since
Jun 12, 2009

9. Feb 10, 2010 10:54 AM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi,

Yes you can get the timestamp by audittrail data by using sso ,

As we discuss the short lock is only in iprocess modler.

Can i know why u want a short lock in your application?

Which scenario you belive short lock is helpful to you?

Regards

Binaya

Andriy

24 posts since
Jan 13, 2010

10. Feb 10, 2010 11:15 AM

in response to: Binaya Kumar Lenka

Re: "short lock" in workspace browser or iProcess

the scenario is next.

We have few users works with the same group queue simultaneously,

User open the screen,

Workitem is became locked

His http connection droped and he is offline for a long time.

As result another users cant work with locked workitem because they have no right and the second they does not know does use realy online and work with workitem or it simply lefted locked

So with short lock I have seen this to be unlocked when user became offline or some similar. With long lock I see no way to repair this situation. (even special person with unlock ability cant know does user work with workitem or it is lefted locked and use does not work with it)

I have set property

0 WIS 0 WIS_QCHANGE_EXTENDED_CHECK I 1

But in workspace browser in history i have not see any locking activity.

Binaya Kumar Lenka

227 posts since
Jun 12, 2009

11. Feb 11, 2010 3:45 AM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi Andiry,

I have two question for you.

question 1:

Whether the Http connection is dropped or the person is going offline .

You want the other user is going to work on that.Do you here you are automating your processes

( how you are going to know whether a person is offline)either you are going or manually checking for it or

you define a scheduler which will running each time or you define SLA for it.

question 2:

Again according to you you are using Workspace Browser and you change the WIS_QCHANGE_EXTENDED_CHECk value set to 1 means when changes the workitem status so it will incement the counter.

Can you tell me are you monitoring the OREC version after you unlock the status of the workitem which is locked by some body.

According to me the short lock is only applicable to the iprocess workspace modeler.

Solution:The solution i found for you to forward the workitem when you fell that the workitem is locked and you want to assign to some body.

Manually doing for backened is not the exact way to do it. bcoz we want it automated.

Andriy

24 posts since
Jan 13, 2010

12. Feb 11, 2010 9:04 AM

in response to: Binaya Kumar Lenka

Re: "short lock" in workspace browser or iProcess

question 1:

>Whether the Http connection is dropped or the person is going offline .

>You want the other user is going to work on that.Do you here you are automating your processes

>( how you are going to know whether a person is offline)either you are going or manually checking for it or

>you define a scheduler which will running each time or you define SLA for it.

Ok. How I imadgin the workflow. Some on open the workitem. See it on the screeen and working with it. No one will try to work with it because it is locked.

Looks like "select from update" in DB. But I want that in reasonable amount of time this lock are droped. As in DB transaction when connection to client is droped the lock is droped and there can be timeout too.

Currently I can find any way to do the same in Tibco iProcess.. The lock is persistent and have no connection to the user http connection and also can find the time when lock appear.

For short locking i have read that it is attached to SAL session and it was looks like what i want.

So currently i'm trying to find a way to resolve this issue.

I was trying to find the lock activity in the Worklspace Browser UI

Open Case -> History

I dont see any lock activity there,

Binaya Kumar Lenka

227 posts since
Jun 12, 2009

13. Feb 11, 2010 9:57 AM

in response to: Andriy

Re: "short lock" in workspace browser or iProcess

Hi,

I have a approach for you.

Like you add a custom audit like 260:%DESC LOCKED BY %USER in auditusr.mesc

After that call the custom audit script in you step status tab- intial command of a step.

You dynamically provide a STEP SLA to you step which is act asa deadline for you.

Once a person is going to lock the workitem a entry is made to audit trail as well as A deadline is set for the step.

once the dealine is over and workitem is still lock then you can come to know that the person's sla time over but still workitem is pending in his/her queue.

Now you can unlock it.

Regards

Binaya

Andriy

24 posts since
Jan 13, 2010

14. Feb 11, 2010 10:17 AM

in response to: Binaya Kumar Lenka

Re: "short lock" in workspace browser or iProcess

Do I can some how automate this audit message or I need to do it in my code on each lock function call?

So do I can hide it some where in iProcess not to loose this step in application development and to have ability to switch it on/off in one place.

Go to original post 1 2 Previous Next

Go to original post

BPM

This Question is Answered

"short lock" in workspace browser or iProcess

Actions

More Like This