Inheriting permissions from parent branch folder

Hi,

I am creating a DCR using Java Code in Teamsite 6.7.1 sp1.

On creating the DCR I need to set permissions to it in the code itself, so I am looking for a Command line Tool which will let me set permissions of the parent branch folder to created DCR.

Thanks,

Krithika

Find more posts tagged with

Comments

Bhargav Coca

What is your OS? If you are in Unix you can always use the chmod inside the perlscript being called by your Javascript.

Thanks

krits

Hi Lilly,

Thanks for your reply.

The OS is Solaris, yes we are trying to use the chmod but while creating the DCR we would not know the parent branch permissions, so if there is some CLT provided by teamsite which would read the permissions of the parent branch folder and provide it to us, we could use chmod to set the same to the newly created DCR.

Best Regards,
Krithika

sumitk

What I understand from your explanation is that you have different branch permission on different branches. But to my knowledge, the branch permission setting is defined in iw.cfg file. So unless you are changing the branch permission settings explicitly after creating it, its always going to be the same as what you have defined in iw.cfg. In this case, you don't need to check permission and simply assign the same permissions to file. In fact, you can specify the default file permission in iw.cfg file.
Thanks,
Sumit

Adam Stoller

What I understand from your explanation is that you have different branch permission on different branches. But to my knowledge, the branch permission setting is defined in iw.cfg file. So unless you are changing the branch permission settings explicitly after creating it, its always going to be the same as what you have defined in iw.cfg. In this case, you don't need to check permission and simply assign the same permissions to file. In fact, you can specify the default file permission in iw.cfg file.
Thanks,
Sumit

The permissions for /default/main are the only branch permissions set in iw.cfg - which I don't think is the issue here.

I've posted the CLT approach for getting permission information on a given branch in terms of users and roles - but if you're interested in the OS permissions - I'd think that Java would have a stat() call of some sort that should allow you to get the owner / group information for the branch or workarea folder and then a chmod() call of some sort that would allow you to set it on the newly created file.

If you're on Solaris, and you want to make sure that the group that shares the branch is always the group owner of files and directories within that branch (even before the files get submitted) - use chmod g+s groupname on all the directories starting from the workarea directory -- do this from the command line at the beginning, and from that point on any new files or directories created within there will then inherit that group ownership (this is useful when you have a group-for-sharing which is not the user's primary group).

AXCHU

If you're on Solaris, and you want to make sure that the group that shares the branch is always the group owner of files and directories within that branch (even before the files get submitted) - use chmod g+s groupname on all the directories starting from the workarea directory -- do this from the command line at the beginning, and from that point on any new files or directories created within there will then inherit that group ownership (this is useful when you have a group-for-sharing which is not the user's primary group).

That was exactly how we handled it in 6.5. However, we are having the problem with 6.7.1 SP1 because the new "Permission" button in the UI will remove the 's' bit. This became a big problem for us because new files created under the any new folders will now lose the proper group assignment. I can't imagine that we are the only company affected here. Does any one have any idea what the solution is or best practice?

Thanks,

Alan.