TOKEN data in iwidmap output file

Hi,

We have got a scenario like we have two different stores kept in two different servers(Teamsite versions are also different ). Now we are migrating to one server and we have got iwidmap generated for both of them.

When I see the output of iwidmap , it is having below structure

<IDMAP>
<RECORD>
<TOKEN data = "100"/>
<ID data ="S-1-1-0"/>
<NAME data="Everyone"/>
</RECORD>
<RECORD>

......

<IDMAP>

We want to merge both iwidmap files but I see <TOKEN data = "some number"/> is same/repeated in both the files. I doubt we can directly merge and since "Token data" number is an autogenerated one , Can we change them manually for each item or Is there any method to achieve this.

I am looking forward for your responses.

Let us know if you have suggestion while running iwidmap iteslf.

Thanks in advance

Pavan

Find more posts tagged with

Comments

Adam Stoller

You don't actually merge the id-maps.

You use the information in the "old" id-map as a guide to updating the "new" id-map.

If you bring the content over from the other server - and then dump the idmaps for both users and groups - you should be looking for entries where the NAME data looks like a SID (e.g.: S-****-****-xx). Those entries will either be:

Local server accounts (users or groups) on the other server, which can either be mapped to the corresponding local server account on the new server or perhaps a domain account on the new server
Domain accounts for users or groups which no longer exist in the Active Directory - in which case you just choose someone / some group to map them to

Pavan1

Hi ,

Thanks for your reply.

Let me reframe my question here:

When I merge the both idmap output in one file I can see there the token ids which are getting repeated so for that id i would like to know is that ok if we have two or more than that same token id in same output file ?

Topic_39056__Using a filter.rptdesign

Adam Stoller

Let me rephrase my answer - you do NOT want to merge the idmaps that way.

Pavan1

Hi,

We have made changes for NAME DATA element. I understand we can not manually merge.

Now we need to import tha same to our new server. Can we achive them using below commands ,

iwidmap -u -a -I c:\store.idmap \USDANRMMD1MS352_store\iw-store\default
iwidmap -u -a -I c:\store_1.idmap \iw-store\default

Where \USDANRMMD1MS352_store\default is location of 1st store and \iw-store\default is 2nd store in the new server and where store.idmap and store_1.idmap are exported iwidmaps for those two stores from their current server(OLD) respectively.

Can we import them as above in our new server ? or If not Can you suggest here ?

Regards,

Pavan

Adam Stoller

Do yourself a favor - go to the support site and search for KB articles regarding iwidmap - I know there are several good ones there - read them.

What you're talking about just isn't a good idea as far as I know, and I don't have the energy to try to explain it right now.

Book1.xlsx

Topic_39063__Change Excel Worksheet via Property Binding.rptdesign

Rick Poulin

ghoti wrote:
What you're talking about just isn't a good idea as far as I know, and I don't have the energy to try to explain it right now.

Confirmed, it's a terrible idea. The reason is that iwidmap isn't just a listing of users on the server. It's a mapping of each (OS) UID to an "entity record" for TeamSite. Thus, merging two idmaps from different servers doesn't make any sense, because you're just going to horribly corrupt your entity database.

It sounds to me like maybe you're trying to add users that aren't already there? If that's the case, generate a list of all users that should have access to the box, then compare that with the output of `iwuseradm list-users -t`. For each user that doesn't appear in that output, call `iwuseradm add-user [username]`.

Pavan1

I have cristal clarity about what you are saying. Probably this scenario could be new(Bringing two stores together).

Scenario:-

We had two stores on two different servers. Users using those two stores are also different.

Now we have brought both stores into one place(in new server where teamsite is freshly installed).

*********************************

When we are going through articles we came to know that we can export the users and their associated groups from the old. Then the same can be imported to the new location so that all the users and their association with the groups remains same.

We have well followed this. But now our question, Since we have brought two stores together onto to new server , how do we import them ?

There are no users new here.

Adam Stoller

Are the two stores named different (i.e.: storeA, storeB) such that you expect to have multiple stores on the new server (license fee - additional $$) - or are they the same named store (i.e.: default, default) such that you need to merge them into a single store on the new server (default)?

Assuming the latter (old-1/default + old-2/default > new/default).

Is there any pre-existing content on the new server that needs to be kept, or is the new server just that, a new server with no content at this time?

Assuming the latter.

If at least one of the old servers (e.g.: old-1) is the same version as the new server (and the other is either the same or older) - the process would be something like:

Stop TS on new server
Remove /iw-store/default
Copy old-1:/iw-store/default to new:/iw-store/default
Copy old-2:/iw-store/default to new:/old-2/default
Modified iw.cfg on new server to contain reference to /old-2/default as [temporary] second store (old2_default)
Bring up TS on new server
Activate old2_default, deactivate [new] default
Use iwmigrate to migrate branches from old2_default to default
Deactivate old2_default, activate default
Use iwfsshrink to remove redundencies in default backing store
Use iwidmap to dump user / group mappings from both old-1 and old-2 servers (e.g.: old1_uidmap.xml, old1_gidmap.xml, old2_uidmap.xml, old2_gidmap.xml)
Use iwidmap to dump user / group mappings from new server (e.g.: new_uidmap.xml, new_gidmap.xml)
Look through the latter for any entries that have NAME entries that match their ID entries.
Look through the old maps to see if you can find the same ID entry with a different NAME value (that will tell you who it is supposed to be)
Look through the new map to see if you can find a reasonable match for the actual NAME value (this would most likely be due to their being local server accounts rather than domain accounts on Windows, or local accounts with different UID/GID values on Unix)
If you find the correct entry - fix it in the new map, otherwise (this would most likely be due to the account being an old one that no longer exists in the system at all) choose some defacto value to use for the NAME value
Once done, import the revised new map into the new default store using iwidmap and then use iwstoreadm to deactivate / [re-]activate the default store.