How to set TS Group in targetTeamsite deploy?

While doing the mandatroy RTFM-ing, I thought I'd ask here also:

We're doing a reverse deploy into a TeamSite workarea from a remote non-TeamSite machine.

The basic mechanics of the deployment are working, and the files are getting sucked into the workarea - but we're having problems with assigning them to the correct group in the workarea. User is no problem, just the group.

If we don't declare any Permission rules, the group & user from the reverse source is applied to the files in the TS workarea, which isn't what we want.

If we try to specifiy a TeamSite group name, the deployment fails with, essentially, 'no such group'.

If we specify the one OS group that I've lumped all of the TS users into, iwglobal, I get 'nobody' as the group assigned in the workarea.

We've also tried assigning the g+s sticky bit to all of the directories within the workarea and then removed the Permission rules, and I'm back to square one. It assigns the remote source's user and group - and removes the g+s sticky bit from the directory.

So - is there a way to assign a TeamSite group to files / directories being deployed into a TeamSite workarea?

Many thanks,
Wally Box
Nike, Inc.

Environment is TS 6.7.1 on Solaris, OD 6.2 base on the TS machine.

I've attached the deploy config (renamed to .txt) for your perusal.

Find more posts tagged with

Comments

ISCBorisB

While doing the mandatroy RTFM-ing, I thought I'd ask here also:

We're doing a reverse deploy into a TeamSite workarea from a remote non-TeamSite machine.

The basic mechanics of the deployment are working, and the files are getting sucked into the workarea - but we're having problems with assigning them to the correct group in the workarea. User is no problem, just the group.

If we don't declare any Permission rules, the group & user from the reverse source is applied to the files in the TS workarea, which isn't what we want.

If we try to specifiy a TeamSite group name, the deployment fails with, essentially, 'no such group'.

If we specify the one OS group that I've lumped all of the TS users into, iwglobal, I get 'nobody' as the group assigned in the workarea.

We've also tried assigning the g+s sticky bit to all of the directories within the workarea and then removed the Permission rules, and I'm back to square one. It assigns the remote source's user and group - and removes the g+s sticky bit from the directory.

So - is there a way to assign a TeamSite group to files / directories being deployed into a TeamSite workarea?

Many thanks,
Wally Box
Nike, Inc.

Environment is TS 6.7.1 on Solaris, OD 6.2 base on the TS machine.

I've attached the deploy config (renamed to .txt) for your perusal.

Have you run the Deployment as root? If you haven't, do so with the desired permissionRules element and see if that helps.
Alternatively you may try to run a Deploy as the desired User belonging to the desired Primary Group and use special keywords
"_iwod_user_" and "_iwod_group_", see this old article.

If it doesn't help contact Support. I *seem* to remember some similar issues with the Reverse Deploy. Can not find an article though Smiley Sad

Migrateduser

Thanks for that reply. I'll look into it.

The Permissions options I've tried seem to only allow an OS group to be assigned - not a TeamSite group. And we use only one OS group (iwglobal) for the TeamSite users (using TeamSite groups on top of that), which works great for our typical TeamSite usage.

I was hoping that using iwglobal as the group would allow the g+s to apply the correct TeamSite group, but no luck so far.

Wally

Oh - and I do have a Support case open, but haven't worked with them yet on it.

Adam Stoller

Have you looked into the groupTranslation mapping sub-element of the permissionRules element?

Assuming that the different groups associated with the files on the source side can be mapped to specific groups desired on the target side, and that you are running the receiver as root - that should do what you want, I think.

LooseCannon

So - is there a way to assign a TeamSite group to files / directories being deployed into a TeamSite workarea?

Many thanks,
Wally Box
Nike, Inc.

Environment is TS 6.7.1 on Solaris, OD 6.2 base on the TS machine.

I've attached the deploy config (renamed to .txt) for your perusal.

As of 2 months ago, OD did not support TeamSite groups.

One way around this issue is to apply TeamSite groups with a DNR script.

reportContext.rptdesign

Migrateduser

Thanks Ghoti & LooseCannon -

As for Ghoti's suggestion, I bet the group translation works with OS groups and not with TeamSite groups. Since all the users are lumped into a single OS group, there's not a translation to be made.

I believe LooseCannon's comment about TS groups not being supported, but I'll find that out when I talk to Support, which is supposed to be soon.

If that's true, then I need to weigh whether:
- I go the dnr route and figure out how to apply iwchgrp to the new files in the workarea, or
- I create an OS group for this workarea and manage it the way we did back in TS version 6.1 and before, or
- something else.

Mostly, I think I was just suprised to find out that I couldn't set the group in the Permissions section of the OD config. to apply a TeamSite, and not an OS, group.

There's still the issue of the OD process not honoring the g+s group sticky bits on directories within the TeamSite workarea. We've had that working nicely with TeamSite import, samba, ftp, etc. - but OD's blowing it out.

Wally