TST 6.7.1 - iwgroup create

TeamSite 6.7.1 SP1/RedHat

I'm working on a process to programmatically migrate Unix groups to TeamSite groups. The script simply reads the groups file, saves the groups and group members information to a Hash, and writes the Hash to an XML file. Easy enough…

The issue is with creating the TeamSite groups file from the generated XML. Running the following cmd gives a "ERROR:00017: Item already exists" error and tsgroups.xml never gets updated.


/p01/app/iw/tsite/iw-home/bin/iwgroup create -if /home/lid6nl8/groups/tsgroups_TEMP.xml -of /home/lid6nl8/groups/tsgroups.xml

My first thought was, oh, I must have generated the XML in an incorrect format, which is causing iwgroup to bomb. But the format looked identical to the example in the admin manual.

Even though the XML looked good, I replaced it with the example XML and re-ran the cmd. Thinking maybe my eyes missed something, and if the problem was with my input XML, using Interwoven's example would resolve it. Unfortunately, I got the same error. Following is the xml from the input file.


<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<iwgroups>
<iwgroup name="newgroup1" id="1"/>
<iwgroup name="newgroup2" id="2"/>
</iwgroups>

I'm running the iwgroup command as 'root/, so permissions can be ruled out.

I'm at a loss. Has anyone successfully updated the tsgroups.xml file from an input file?

I'll open a ticket with support, but thought maybe you guys have seen this before.

Find more posts tagged with

Comments

Phanie

Hi, As far I am aware of, the iwgroup CLT is for administering TeamSite groups. When iwgroup is matching the group name that you provide it checks OS as well as TeamSite groups to see if one by that name exists.

The reason iwgroup checks the OS groups at all is because there is an operation for creating a TeamSite group. Iwgroup will need to know what OS groups exist so you do not create a TeamSite group of the same name.

Correct me if I am wrong.

--
Phanie

LooseCannon

Hi, As far I am aware of, the iwgroup CLT is for administering TeamSite groups. When iwgroup is matching the group name that you provide it checks OS as well as TeamSite groups to see if one by that name exists.

The reason iwgroup checks the OS groups at all is because there is an operation for creating a TeamSite group. Iwgroup will need to know what OS groups exist so you do not create a TeamSite group of the same name.

That's how I understand iwgroup, as well.

The Unix (OS) groups are being brought over from a different server and do NOT exist on the Linux box, where the iwgroup operation is being run. So a clash of OS and TeamSite groups can be ruled out as the problem

Adam Stoller

Try not including the id attribute in your XML file
It's conceivable that the problem you are having is that there is already a group with the id of either '1' or '2' present (like perhaps the iwEveryone group)

LooseCannon

I'm still working with support, but some progress has been made.

The physical server, that TeamSite is installed, uses Active Directory for main authentication. When attempting to build the TS groups I did NOT check for groups of the same name in AD, just in /etc/groups. DOH!

So, I'm working with Info Security to shield these groups from the OS by assigning them an OU that the OS won't/can’t read, like OU="teamsite".

Having the groups in AD allows Info Security to mange them, which is our corp standard.

My plan is to synchronize the TS groups file (tsgroup.xml) with groups from AD, nightly.

I'm still working with support on:

1) why the -of flag doesn't work for iwgroup, as shown in the examples
2) why the next available ID number is NOT assigned to a new group, when the specified one is already taken.

Migrateduser

I'm getting this error in TS7.1 Win2003.
Do I understand this thread correctly; that the groups can't alreayd be defined as OS groups?

I get the error no matter what groups I put in. Thanks for any help.