We are currently in the exact same situation you are. We are implementing an enterprise version of K2, in addition to TS 6.5. According to Verity (actually Autonomy since the recent acquisition), the TeamSite version is not actually K2, so the indices are not compatible.
We are actually working on an integration that would involve a DNR (upon a successful publish) or an event table in our DB that would trigger incremental updates to the K2 index. Hope this helps.
In reply to: Thanks for this information - it confirmed what we have assumed. So, you have already spoke to Verity/Autonomy and have been told about incompatibility?
In reply to: It appears that we will have to take similar route, another separate K2 server, that would build its indices off TeamSite content and its metadata. Is that what your team has been doing? We see potential issues indexing TeamSite metadata. Did you look into this issue? Was this functionality, indexing TS metadata, needed for you?
In reply to: Actually we haven't run into any issues so far. We have a portal app with all metadata in a DB. K2 is actually indexing and building the collections from the DB. What are your specific concerns?
In reply to: Well, our current application infrastructure doesn't have any DB. Therefore, we have to, somehow, build K2 indices off TeamSite area metadata (this is in addition to indexing off the TeamSite content).It appears that K2 does not know how to index metadata of the content stored in TeamSite.Did anyone else had to work with similar issue?
