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.
So your friendly marketing executive calls to say he needs a Vanity URL for a page on your AEM hosted site. And you cringe. How do you get this done right without getting penalized by Search Engines? Should you do this at the Load Balancer level? Within AEM Dispatcher configurations? within AEM Publish instance? What about horizontal replication of these configurations? And oh, who’s going to maintain this? It’s not like your Dev Ops team is necessarily twiddling their thumbs waiting for work.
This post will address a few different ways to accomplish Vanity URLs within an Adobe AEM implementation and discuss some pros and cons.
Even before the Adobe Summit, that took place in March 9th to 13th, 2015 in Salt Lake City, UT, Forrester had this to say “Adobe was a runaway winner across a broader digital experience delivery portfolio”.
Adobe put a great show (including a concert by Imagine Dragons!) and displayed a wide range of digital marketing products and integrations. It was fun. It was Radioactive!
“Marketing” for marketing aside, there was a lot of ‘meat’ in the conference as well. So, without much ado, here are our 6 takeaways from Adobe Summit 2015.
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
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 🙂