How tro Lock a stream
I was trying to see if a whole stream can be locked (like locking a branch). There is this techote:
http://www-01.ibm.com/support/docview.wss?rs=3488&context=SSCP65&dc=DB560&dc=DB520&uid=swg21380329&loc=en_US&cs=UTF-8&lang=en&rss=ct3488rational
It says the version is 1.x, but not 2.x, so I was wondering if the answer is different in 2.x. Also, I dont understand how to do what they say to do. I need some explicit instructions that even my non-tech Mom could do. :)
http://www-01.ibm.com/support/docview.wss?rs=3488&context=SSCP65&dc=DB560&dc=DB520&uid=swg21380329&loc=en_US&cs=UTF-8&lang=en&rss=ct3488rational
It says the version is 1.x, but not 2.x, so I was wondering if the answer is different in 2.x. Also, I dont understand how to do what they say to do. I need some explicit instructions that even my non-tech Mom could do. :)
2 answers
Hi,
the tech note still applies. The idea is to make the stream owned by a team that does not provide delivery permissions. In the Library you can find http://jazz.net/library/article/291 describing how permissions are handled.
the idea of the tech note is in general to remove permissions to deliver for everyone. There are at least two ways to achieve that.
1. You can remove the permission to deliver for everyone in the team the stream is owned by.
2. You can have a special team that does not grant delivery permissions and make the stream owned by a team. The effort to do this and especially to reverse it is very low compared to solution 1 there fore it is proposed in the tech note.
To do 2 right open the stream. On the Stream Editor look for the Team owning the stream. On said editor select a team prepared with no delivery permissions (deselect the permission in the process customization of said team) as new owner to lock the stream. To reverse change the owner of the stream back to the desired team.
It is not rocket science and your Mom could do it, provided you allow her to play with RTC. 8-)
the tech note still applies. The idea is to make the stream owned by a team that does not provide delivery permissions. In the Library you can find http://jazz.net/library/article/291 describing how permissions are handled.
the idea of the tech note is in general to remove permissions to deliver for everyone. There are at least two ways to achieve that.
1. You can remove the permission to deliver for everyone in the team the stream is owned by.
2. You can have a special team that does not grant delivery permissions and make the stream owned by a team. The effort to do this and especially to reverse it is very low compared to solution 1 there fore it is proposed in the tech note.
To do 2 right open the stream. On the Stream Editor look for the Team owning the stream. On said editor select a team prepared with no delivery permissions (deselect the permission in the process customization of said team) as new owner to lock the stream. To reverse change the owner of the stream back to the desired team.
It is not rocket science and your Mom could do it, provided you allow her to play with RTC. 8-)
I was trying to see if a whole stream can be locked (like locking a branch). There is this techote:
http://www-01.ibm.com/support/docview.wss?rs=3488&context=SSCP65&dc=DB560&dc=DB520&uid=swg21380329&loc=en_US&cs=UTF-8&lang=en&rss=ct3488rational
It says the version is 1.x, but not 2.x, so I was wondering if the answer is different in 2.x. Also, I dont understand how to do what they say to do. I need some explicit instructions that even my non-tech Mom could do. :)
AH!!!! Your explanation was much more clear than the technote! Thanks so much!!!! As for my Mom, think I'll keep her to the web version so she can see pretty graphs. :D
Hi,
the tech note still applies. The idea is to make the stream owned by a team that does not provide delivery permissions. In the Library you can find http://jazz.net/library/article/291 describing how permissions are handled.
the idea of the tech note is in general to remove permissions to deliver for everyone. There are at least two ways to achieve that.
1. You can remove the permission to deliver for everyone in the team the stream is owned by.
2. You can have a special team that does not grant delivery permissions and make the stream owned by a team. The effort to do this and especially to reverse it is very low compared to solution 1 there fore it is proposed in the tech note.
To do 2 right open the stream. On the Stream Editor look for the Team owning the stream. On said editor select a team prepared with no delivery permissions (deselect the permission in the process customization of said team) as new owner to lock the stream. To reverse change the owner of the stream back to the desired team.
It is not rocket science and your Mom could do it, provided you allow her to play with RTC. 8-)
I was trying to see if a whole stream can be locked (like locking a branch). There is this techote:
http://www-01.ibm.com/support/docview.wss?rs=3488&context=SSCP65&dc=DB560&dc=DB520&uid=swg21380329&loc=en_US&cs=UTF-8&lang=en&rss=ct3488rational
It says the version is 1.x, but not 2.x, so I was wondering if the answer is different in 2.x. Also, I dont understand how to do what they say to do. I need some explicit instructions that even my non-tech Mom could do. :)