Skip to content

How Autonomy WCM meets and beats Gartner’s WCM standards

On Nov 10, 2011 and again in 2012, Gartner released it’s annual “Magic Quadrant for Web Content Management“. As seen in the quadrant, 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 Autonomy Product stack’s implementation perspective.

Gartner’s comments are in italics and bold. Read on, and feel free to provide your comments below.

Functions:The WCM offering must be available as a stand-alone product, or suite of products, and include the following capabilities:For a detailed view of Autonomy’s WCM product stack and it’s reference architecture, we recommend you read our previous blog post here

  • A content repository with basic library services, such as check-in/check-out and versioning.

     

    TeamSite’s file-level (Submits to TeamSite STAGING)  and site-level versioning (EDITIONS) are powerful features out of box. On top of this, the content services API provides command line and Java API for powerful integrations with other corporate applications as needed. This may not sound all that thrilling, but in an enterprise eco-system consisting of upstream and downstream applications feeding into your WCM system – these capabilities are very important.

  • Authentication of users (authors, editors and reviewers) and assignment of permissions.

    Continue reading ›

Ingredients of an Autonomy products based WEM solution

You heard about WEM. You laughed at it’s silliness. Then you gave it some thought. Do we really need yet another buzzword to describe web-based marketing?  Maybe we don’t. We are not here to debate the need or redundancy of acronyms, but understand how to take actionable steps to produce results. As an expert in your domain/market, you know your core business and needs for user engagement- we are not here to discuss that either. The goal of this post is to define what you need to achieve your WEM business goals using technology from Autonomy Corporation.

WEM, or Web Engagement Management,  is all about having a dialogue with your web visitors, so you can better educate, sell products, or whatever it is you want do with your web content. The Autonomy ‘Promote’ line of products enable you to acheive this ‘WEM’ solution.  Time and again, we have heard customers ask: Do we need the whole suite of Promote products sold by Autonomy? What does each product do? Do we just install, and the products work automatically (or to what extent)? Or do you need to customize each product? What skills do you need to implement a holistic solution? How would the resulting solution look like?

While there are many permutations and combinations of products and customizations possible to achieve an enterprise web engagement management system, in this post we will talk about the necessary ingredients for one such solution.

So, without further ado, here are the ingredients:

TeamSite 7.2.1 (or 7.3  – promised to be released soon),
FormsPublisher – comes built-in with TeamSite,
SitePublisher – built into TeamSite starting with versions 7.0,
OpenDeploy,
LiveSite Content Services (LSCS),
LiveSite Display Services(LSDS),
IIS, Apache or other WebServer,
Oracle or SQLServer (database is optional – we’ll discuss this in more detail later on),
One of Windows 2003, Windows 2008, Solaris or RHEL Operating system.

In future posts, we’ll talk about how to develop a highly engaging enterprise website. We’ll discuss creating effective site layouts and templates – as it applies to SitePublisher and LiveSite,  developing rich, dynamic Components, audience targeting components using Segmentation and Targeting modules, etc. While some of this information is for a  technical/development audience, the end goal is for business users with no technical skills to easily manage the user web experience. In a good architecture, once the solution is built, modifying your system to react and pro-actively address market conditions is trivial and  non technical.