Sounds like TeamSite is being put out to pasture....been a long time coming I suppose. I heard taps in the distant background as I read this article. https://t.co/7rXbcEdxjO
It is really a shocking news. Today after a long time I logged in to this forum and saw this thread. This looks like these transitions degraded the Interwoven tool so much.
Hope for the best. Let's wait for official confirmation.
I also read about this from another source.
I can't say I'm too surprised, TeamSite hasn't been getting much love the past few years. Most other organisations I know that use(d) it are transitioning to other products - us included.
OpenText employs 8,500 people and is well known in the Content Management space. For customers looking for a best-of-breed solution with a stable financial company behind it, TeamSite is probably still a good option. It is better than being stuck in the Printer business of HP! So, not all is lost for folks who have invested their time learning the inner workings of TeamSite, OpenDeploy and MediaBin.
Zaarin wrote: I also read about this from another source. I can't say I'm too surprised, TeamSite hasn't been getting much love the past few years. Most other organisations I know that use(d) it are transitioning to other products - us included.
Mind if I ask what product you're migrating to? We're in the market for a new platform...
Read this today, http://www.digitalclaritygroup.com/opentext-acquires-hp-teamsite/. So came back to the forum to understand how people like me is taking it.
I truly dont understand if its a good thing or bad. OpenText already has a content management system, hope they dont kill TeamSite/LiveSite alltogether.
OpenText's CMS platform is DAM and Document centric. They purchased Vignette in 2009, which was TeamSite's contender way back when (pre LiveSite). That is their closest thing to managing websites. SitePublisher and LiveSite would be their most modern WCM/ WEM platform - so my crystal ball says that TeamSite+LiveSite will continue to bob up and down the WCM market waves, but won't sink.
I wonder how IDOL fit's in all of this.
IDOL is teamsite search , IDOL is part of LSCS.
A lot of questions how this practically will go. Fourth company that I'll be dealing with.
I wonder how IDOL fit's in all of this.IDOL is teamsite search , IDOL is part of LSCS.
SitePublisher/ LiveSite was born when Interwoven acquired Austin based 13Colonies sofware. For some time after that, up until the Autonomy Acquisition, there was no IDOL embedded within TeamSite/LiveSite or even MediaBin. Autonomy had this wierd fascination of embedding IDOL - whether it was appropriate or not, into all of its acquired products.
What I'm saying is that SitePublisher and LiveSite do not need IDOL. In fact, a lot of LSCS implementations that do NOT use IDOL capabilities are better off than those that do - from a performance perspective.
I'm pretty confident OpenText can tear out the Autonomy vestiges and make TeamSite great again! But then, I'm sure there's a good argument that TeamSite has always been great
autowoven_dev wrote:
SitePublisher/ LiveSite was born when Interwoven acquired Austin based 13Colonies sofware. For some time after that, up until the Autonomy Acquisition, there was no IDOL embedded within TeamSite/LiveSite or even MediaBin. Autonomy had this wierd fascination of embedding IDOL - whether it was appropriate or not, into all of its acquired products.What I'm saying is that SitePublisher and LiveSite do not need IDOL. In fact, a lot of LSCS implementations that do NOT use IDOL capabilities are better off than those that do - from a performance perspective. I'm pretty confident OpenText can tear out the Autonomy vestiges and make TeamSite great again! But then, I'm sure there's a good argument that TeamSite has always been great
Not so simple with Search. It took a monumental effort to get Search to work properly once IDOL was pushed into it. I'm sure if they chose to use something other than IDOL (which I doubt they will) in Search, it will take another monumental effort to make it work properly again. What would be the point for such a minor part of the product? I would love for them to improve the Search interface, but they really don't need to muck with the engine again. I don't hold out much hope that they will invest much, if anything, in TeamSite going forward. It's archaic. At least when HP acquired Autonomy, you had some hope that they might actually do something good around every aspect that sucked about TeamSite (the support, the docs, the UI, the usability, etc.). Now that they've given up on it, I don't expect any of that. I have a feeling we will be looking at Adobe very hard, for good or for bad.
If OpenText continues to use IDOL they may have to pay HPE some royalty fee as it is an OEM product. That in itself may be a good reason to switch to Lucene/Solr or other search solution.
Last year when iManage bought back its WorkSite software from HP, it had the IDOL OEM installed and that will still continue to be.
So, the OpenText deal would be something similar.
Good point @reji_kv.
OpenText may have bought the royalties for OEM IDOL as well. In which case, they wouldn't want to spend any more money on something that's behind the scenes from a customer perspective.
OpenTest will probably continue ot OEM Idol, Changing it out would be a very difficult thing for customers to do. That being said, I always wanted to pull out Idol and see if SOLR would work better. We already put Idol on a different instance from LSCS, so everything is a REST call and file interaction. It amy be possible to do that with a bridge rather than changing LSCS code.
Did I miss something?
Is there some email I missed or press release that TS/LS/OD/... are all going away? Is it possible that OpenText may invest/integrate/... to make the suite better?
Is there some reason for all the long faces and doom-n-gloom?
Just from the general tone of the article I posted, it sounds like OpenText is a place where CMS systems go to spend their last days. You could be right, I suppose, but after being bought and sold so many times now, I wonder who will still be around that knows enough about the underlying architecture to be able to make any worthwhile changes. And the investment it will take to keep updating (or ever updating) the docs, and now another release strategy. On and on it goes. My company has hated the toolset for a while now - this only gives them more reason to toss it in a ditch. And I'm running out of reasons to fight for it. Let's face it, Dan - there are not a lot of ways you can spin this as great news.
Dan, Here's a link, if google isn't working for you:OpenText buys HP WCM
bowker wrote: Did I miss something? Is there some email I missed or press release that TS/LS/OD/... are all going away? Is it possible that OpenText may invest/integrate/... to make the suite better? Is there some reason for all the long faces and doom-n-gloom?
OT has been around for a while. They purchase products that are stagnant, sell some licenses and collect maintenance to keep the products up to date. I am not certain how many new features they will add, but TS will be around for a while.
I was hoping HP would actually grow the product and with 8.1 I thought that a possibility. Not certain how much growth we will see from OT.
but after being bought and sold so many times now, I wonder who will still be around that knows enough about the underlying architecture to be able to make any worthwhile changes.
There would be a few but not many. When we did the 7.5 upgrade last year one of the people we were talking to was part of the team that did the initial set up for us back in 2001/02.We never went down the Livesite/search path and stuck with Teamsite/OpenDeploy, which simplifies some things. I suspect though that 12 - 24 months from now we'll probably be on something else, still not a bad run, not many other CMSs would be able to stay in place for that long.
When I got the offical HP notification of the move to Opentext last week I did have a feeling that it was like playing a game of musical chairs.
We too have been using TeamsSite since around 2002. We will be moving away from it in the next few years as far as I can tell as our Marketing teams are looking to find something new.
We are old time users too, back when Interwoven actually owned the suite, but as someone else said our internal support is a skeleton crew and the users who used to love TS now hate Teamsite. We're moving away from .net and going all in with a Ruby on Rails stack so were looking at something like Prismic.io or other.
It's a shame given that Teamsite had so much potential, if at the very least HP would have made a push in the ui/ux direction I think they could have extended the staying power a bit further. Oh and a price cut would have made sense too.
All we ever wanted was something clean and simple, forms publisher, no fancy workflows, and OD to push to dev, test and prod. But the muddying of the waters with LiveSite, Mediabin, IDOL and kooky licencing made it too tempting to future plan a move to something else.
The CMS space is so commoditized now it almost seems like more of a feature than a product.
