6.5 OS(Solaris) groups v/s TeamSite groups

We are trying to upgrade from 6.1 to 6.5 ,but have one question. Presently we have BRANCHES etc owned by OS groups, now since we are moving towards teamsite groups, do we migrate our backing store and then run iwchgrp to change the ownership for each BRANCH to the newly created TeamSite group? If that is the case, I have almost 50 branches, do I need to tackle them one by one, ? Can I create a teamsite group with the same name as the previous OS group and change the gid? Please share...

Find more posts tagged with

Comments

Adam Stoller

We are trying to upgrade from 6.1 to 6.5 ,but have one question. Presently we have BRANCHES etc owned by OS groups, now since we are moving towards teamsite groups, do we migrate our backing store and then run iwchgrp to change the ownership for each BRANCH to the newly created TeamSite group? If that is the case, I have almost 50 branches, do I need to tackle them one by one, ? Can I create a teamsite group with the same name as the previous OS group and change the gid? Please share...

You can find a lot of information about this in [thread=10216]this thread[/thread] - which shows how you can use iwidmap to remap all the old OS groups to new TS groups.

stacktrace.PNG

tik

Will try that,but have a doubt on the same lines. The install manual ( 6.7)talks about the migration invoked by installer as well as the migration steps to invoke manually- and as part of the manual process following gets created:

1> a list of users created in tsusers.xml or tsldapuserscache.xml based on our uid files or LDAP auth
2> assignment of permissions at each level
3>description of ts groups created for assigning group permission.

I was under the impression that the TS groups are created automatically based on uid files and our OS groups? Would you mind clarifying this doubt.

We are looking to migrate from 6.1 to 6.7, rather than 6.5.

Thanks

Adam Stoller

Will try that,but have a doubt on the same lines. The install manual ( 6.7)talks about the migration invoked by installer as well as the migration steps to invoke manually- and as part of the manual process following gets created:

1> a list of users created in tsusers.xml or tsldapuserscache.xml based on our uid files or LDAP auth
2> assignment of permissions at each level
3>description of ts groups created for assigning group permission.

I was under the impression that the TS groups are created automatically based on uid files and our OS groups? Would you mind clarifying this doubt.

We are looking to migrate from 6.1 to 6.7, rather than 6.5.

Thanks

TeamSite Groups are not automatically created from scratch. The .uid files define users not groups.

In order to create groups you need to use the iwgroup CLT, or there might be a method for doing it from the Administration tab in the CCPro UI (don't know).

smenon

1> a list of users created in tsusers.xml or tsldapuserscache.xml based on our uid files or LDAP auth
2> assignment of permissions at each level
3>description of ts groups created for assigning group permission.

When you upgrade to TS 6.7.0, the roles have to be assigned at the branch level instead of in .UID files.. Hence there is a user/role migration step that needs to be performed.

The installation will take all of your existing users and let TeamSite store/cache them locally in the tsusers.xml or tsldapuserscache.xml file. This is step 1 in your three items.

Then you need to manually run the iwaccessmigrate CLT to allow teamSite to examine the users in your roles files and apply them to whichever branch the users currently have access to. This is step 2 which is automated by the CLT.

While performing step 2, if a number of users have the same role on a branch, the CLT will also give you the option of creating a TeamSite Group to group all of those users and apply the role to the Group instead of each individual user. The group that is created is a TeamSite Group with an auto-generated group name. This is step 3 in the list.

However, you can choose to run the CLT in a "create manifest" mode that will create an XML file as a report of what permissions it is going to apply. You can choose to modify the group names (which are auto-generated) in the manifest file. You can then re-run the CLT and provide it with the XML manifest file with the changed group names.

I hope this clarifies things..

thanks

Adam Stoller

The .uid files define users not groups.

Sigh - don't know what the heck I was thinking about when I said that - sheesh ;-)