Ingredients of a HP's Web Engagement 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 Hewlett Packard Enterprise Services
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 (Note: TS 7.4.1 is the latest version),
FormsPublisher – comes built-in with TeamSite,
SitePublisher – built into TeamSite starting with versions 7.0,
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 a good architecture, once the solution is built, modifying your system to react and pro-actively address market conditions is trivial and non technical.
Stay tuned for more updates on how to develop highly engaging enterprise websites.
With TS 7.3.1, HP-Autonomy’s reference architecture for a WEM solution has extended a bit. A reference architecture, like it says, is only for reference and not necessarily a de-facto design.
Although LSCS comes with IDOL, HP-Autonomy would like it’s customers to include the fully licensed IDOL – which comes with all it’s connectors and advanced features.
The reference architecture also includes Autonomy Explore – a dashboard like tool to analyse user interactions within IDOL. The various components in this new reference architecture are listed below:
* TeamSite 7.3.x,
* SitePublisher – WYSIWYG editor,
* LiveSite Display Services 7.3.x – for website rendering
* LiveSite Content Services 7.3.x – includes stripped down IDOL
* IDOL – with full features. Often a separate license. This stand alone IDOL (potentially multiple instances) serves SiteSearch, Personalization, Social Media Integration and Targeting and Recommendations,
* Autonomy Explore
This brings up the question, if you as a customer have the technical skills to develop and maintain an enterprise solution like above. When implementing such a solution, do not rely on your (very friendly) Sales guy alone, but work with someone like autowoven who can be on your side to provide the facts.