Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
uniqueness of ComponentID
martinxue
Hi,
I am downloading/exporting components from one sitepublisher to another.
the components can be imported to the new sitepublisher environment, (after running "/u01/iw/app/TeamSite/bin/iwextattr -s TeamSite/LiveSite/Type=component //vpathtocomponent".
The issue comes up for uniqueness of componentID, how can I make sure that the componentID that imported from other system won't be duplicated in the new system?
by looking at the forum, it seems that the uniqueID is generated by:
com.interwoven.livesite.common.util.UniqueIDGenerator.UniqueIDGenerator.getInstance().newID();
Are there backend database table to store those componentID? How Livesite knows that the getId() method will return a unique ID in the system?
I tried to copy an existing component to a new name, import it to sitepublisher, both these 2 components have the same componentID (since I copied it), it seems that these 2 components can both be saved to the system without complaint.
I'd appreciate it if anyone can shed some lights on this issue.
Thanks very much.
Best Regards
Martin
Find more posts tagged with
Comments
tec_iwov
the unique id generator is based on a timestamp so it should be unique within the system
martinxue
Hi,
If that's the case, how to maintain the uniqueness in the following senario:
- if several users happen to open the "create new component" at the same time? (maybe synchronization of that getId() method can handle that?)
- if the system reset the time (i.e. winter/summer time in some areas)?
- when the components were imported from other system (which may have different timestamp).
Still not quite sure...
Thanks in advance.
Regards
Martin
martinxue
Hi,
the reason that I am keen on this issue is that I was importing components from one TeamSite/sitepublisher server to another, I want to make sure that those components and the ones that will be created later won't have duplicate componentID.
Any suggestions will be greatly appreciated.
Thanks in advance.
Martin