nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

iwmkbr and iwmkwa

anew

Hello

Windows 2003

We are migrating servers from TS 6.5 to 6.7.2. We have a script that recreates the branching and WA structure on the new TS server. 2 questions.

1. With each branch, we need to associate a group or groups with associated roles. How can I do that from the command line?

2. When using the iwmkwa CLT the private bit is set on the WA even when there is a group for sharing associated with it. Is there a way to not set this automatically?

Thanks

Find more posts tagged with

Comments

moonkhanna

Hello

Windows 2003

We are migrating servers from TS 6.5 to 6.7.2. We have a script that recreates the branching and WA structure on the new TS server. 2 questions.

1. With each branch, we need to associate a group or groups with associated roles. How can I do that from the command line?

2. When using the iwmkwa CLT the private bit is set on the WA even when there is a group for sharing associated with it. Is there a way to not set this automatically?

Thanks

I would have just migrated the store first instead of the running the above script\ CLTs on the new server.. your plan sounds like a not very good plan..

anew

Hi

Thanks for your response but there are reasons we are not migrating the backing stores using the migrate tool.

However, I would have thought there would be some way to associate groups to branches and remove the private bit set on the WA via a CLT.

Thanks

moonkhanna

Hi

Thanks for your response but there are reasons we are not migrating the backing stores using the migrate tool.

However, I would have thought there would be some way to associate groups to branches and remove the private bit set on the WA via a CLT.

Thanks

Since you are moving to a new server.. probably a better way would be to move the store itself and not run iwmigrate as well..

Once you are there, use iwidmap to map your local users and groups.. and then perform what you want to perform on the new server..

moonkhanna

Hi

Thanks for your response but there are reasons we are not migrating the backing stores using the migrate tool.

However, I would have thought there would be some way to associate groups to branches and remove the private bit set on the WA via a CLT.

Thanks

Check out the IW KB article on moving store to new server.. or moving store from 6.5 to 6.7.1...

moonkhanna

Hi

Thanks for your response but there are reasons we are not migrating the backing stores using the migrate tool.

However, I would have thought there would be some way to associate groups to branches and remove the private bit set on the WA via a CLT.

Thanks

There are no reasons, I have heard of, for which you would like to go through the path you are following... Its always better to have the store intact on the new server and then do the migration activities as per your Business Requirement there..

anew

Thanks again for your responses.

How about performance and stability? We've heard going with a new backing store vs. converting an old would help with performance.

In addition, we have been getting some errors in the iwtrace.log concerning points in the store.

This backing store was also converted from TS 5.5.2. So this would be the 3rd time it was converted.

So, starting with a new backing store has some appeal to us.

That said, we still wanted to find out how to edit the groups and roles on a branch via a CLT as well as manipulating the private bit on the WA.

Thanks

moonkhanna

Thanks again for your responses.

How about performance and stability? We've heard going with a new backing store vs. converting an old would help with performance.

In addition, we have been getting some errors in the iwtrace.log concerning points in the store.

This backing store was also converted from TS 5.5.2. So this would be the 3rd time it was converted.

So, starting with a new backing store has some appeal to us.

That said, we still wanted to find out how to edit the groups and roles on a branch via a CLT as well as manipulating the private bit on the WA.

Thanks

Where did you read\ hear, it is recommended to create a new store instead of conversion?

Jcse

1. With each branch, we need to associate a group or groups with associated roles. How can I do that from the command line?

If you want to associate a group or groups while making your branch,then use
iwmkbr CLT with the following options


iwmkbr [flags] parent brname comment rooted [ownerid [groupid]]

EXAMPLE
iwmkbr //IWSERVER/default/main myBranch 'test branch' INITIAL myGroup

crosstab_border.png

Jcse

Hello
2. When using the iwmkwa CLT the private bit is set on the WA even when there is a group for sharing associated with it. Is there a way to not set this automatically?
Thanks

iwmkwa CLT only makes an WA private when while creating WA using this you do not provide a groupid ,then it automatically set its private bit.

To avoid this use CLT with the groupid.


EXAMPLE

iwmkwa main/branch1 wa1 '' INITIAL myGroup(groupid)

i think it will work for you.

anew

If you want to associate a group or groups while making your branch,then use
iwmkbr CLT with the following options
iwmkbr [flags] parent brname comment rooted [ownerid [groupid]]

EXAMPLE
iwmkbr //IWSERVER/default/main myBranch 'test branch' INITIAL myGroup

Hello

Thanks for your post however using the iwmkbr, I was only able to add one group to the branch, and even as I did that, the group did not show up under the Users and Roles tab. I think the CLT needs to be updated, or what I was hoping for was a CLT that I missed that actually allows you to do this. Looks like the iwmkbr CLT is outdated, valid for versions of TeamSite when there was a branch to be added at branch creation. With TS 6.7.x adding a group for sharing to the branch is not done at branch creation anymore, but after the branch has been created. The CLT also needs to be able to allow you to select the role for that group.

Here's the example I used
iwmkbr "/default/main" "aaaaa" "" INITIAL argon\anew tswebprod\testGroup

The "testGroup" was never associated with the branch

Thanks

anew

iwmkwa CLT only makes an WA private when while creating WA using this you do not provide a groupid ,then it automatically set its private bit.

To avoid this use CLT with the groupid.
EXAMPLE

iwmkwa main/branch1 wa1 '' INITIAL myGroup(groupid)
i think it will work for you.

I've used the iwmkwa CLT with a group for sharing and without. Both times it set the private bit