** NOTE: TeamSite product is now owned by OpenText and the information below is dated **
On Nov 10, 2011 and again in 2012, 2013 and 2014, Gartner released it’s annual “Magic Quadrant for Web Content Management“. As seen in the quadrant, HP Autonomy product stack is a clear leader. In this post we take each fundamental WCM feature that Gartner puts forth and discuss it from an HP Autonomy Product stack’s implementation perspective.
Gartner’s comments are in italics and bold. Read on, and feel free to provide your comments below.
Among enterprise-class web experience management systems, the two most sophisticated systems that are often pitted against each other are HP TeamSite and Adobe Experience Manager. Both Forrester and Gartner rank these products highly and often place them as leaders in the digital experience (aka content marketing/ web experience management/digital engagement/ customer experience management) space.
Technologically, at their core, the products are very different. A developer may cringe to read “similar” and these product names in the same sentence. However, we are going to look at it from the perspective of a business user – a marketer who potentially uses this system versus a technical administrator or developer.
At autowoven we have seen our share of new TeamSite implementations as well as migration / upgrade projects. While there are quite a few reasons why migration projects could fail. Here are the top 5 reasons.
- Not following the proper TeamSite version upgrade path
- Project led by an entity (team lead / professional services team) not having prior migration experience
- Not allocating necessary down time of systems
- Not considering encoding issues (visual format/ tinymce)
- Assuming APIs used in customizations are forward compatible
UPDATED September 16, 2014 – to reflect new, on-the-field, experiences delivering Mobile First design…
Starting TeamSite 7.4, HP users can avail the mobile add-on module. Here are 5 things you need to know about this module:
Migrating TeamSite Installations
This article describes how to take an existing TeamSite installation and rebuild or replicate it on a new server or on a new TeamSite release. It describes particular compatibility issues with backing store migration and lists some of the configuration and customization information that needs to be copied. Although this document is meant to address migration issues across all the supported platforms, it also gives steps needed to migrate from old TeamSite 6.x on Linux or AIX to TeamSite 7.1 on Linux.
HP TeamSite 7.4.1 along with LSCS and LSDS has over 100 updates and bug fixes since version 7.3.2.
While this includes several usability features, the new 7.4.1 version does have a bug. This blog post gives some background on the affected feature and the bug information. If you are not an existing HP TeamSite user, you may ignore this blog post 🙂
There could be multiple business reasons to consider when you upgrade your enterprise content management system based on HP TeamSite. However, the following 7 technical factors should not be ignored.
There’s an informative article by Michael Kriggsman on ZDNet titled “Do our customers love us?” It talks about how customers crave for solutions and not just features. Michael writes:
“Adopting an outcomes-based perspective in enterprise software requires the vendor to develop a detailed understanding of customer aspirations and pain points across the entire buying and usage cycle.”
HP Customers we talk to are overall pretty happy with the “enterprise” features offered by the product stack, but like with every solution, they would like to see improvements. Based on feedback we received, we have compiled a short list of pain points that we would like HP as a product vendor to solve.
And here’s the wish list for 2014: