Web Experience Management with CS10

Hi, Can someone advice on implementing WEM (Web experience management) with CS10. Our understanding is that WEM can be used as front end with actual contents and search engine stored in Content server at backend. An architecture design diagram for implementing WEM with CS10 will be more helpful.

Apart from that, how will openText portal will be helpful in doing above implememtation.

Kindly advice at the earliest as we need to propose solution to customer.

Find more posts tagged with

Comments

Evan_Bench

in version 8.1, Content Server is integrated with WEM using "External Content Sources" and acts not as the "main" repository for WEM but as a way to import content into WEM from Content Server. Active content is still stored in the WEM management stage but Content Server becomes an additional source for content for the management stage.

Content Server is also the repository for "OpenText Archive" for WEM. In this integration content is still stored in the WEM management stage resources but is synchronized with Content Server (based on events such as unpublishing, versioning, or deletion). As you know the WEM management stage contains 'active' content. That is, content created and managed by Business Users for approval and publishing to 'live' sites (running in Portal). The Content Server integration provides Library Services and Document Management to WEM. A business user can delete, edit, approve, version, unapprove, publish, unpublish as they normally would (using content stored in the WEM management stage). But then Content Server would store archived 'versions' of this content allowing a Business User to focus on the tasks at hand while being provided with archive, library, document services from Content Server.

Portal is simply the JEE front-end that is used to render the content in a webpage. That is, Portal provides the JEE framework for rapidly creating navigation, authorization, authentication, portlets, etc. used to present the content coming from the WEM management and delivery stages. WEM is the back-office (xml world) and Portal is the front office (jsp/html world).

You can find all the documentation you need to understand the Content Server integration on knowledge. We also have a nice workshop that provides enablement in WEM integration with Archive Server and using CS as a source of content.

Evan

Praveen_R

Hi Evan, Thanks for the info . By the way for Installing WEM, can we have any Case Study material for that. If there in KC already, please share the link.

Because, We aren't able to get clear picture on below areas and how should it be handled during actual implementation.

1) Management Stage

2) Delivery stage

Regards,

Praveen

Evan_Bench

During implementation the Management Stage is given default resources (an Application Services database resource, and a default file source). In many cases these work just fine. But, if you need to integrate WEM with other sources (CS10) then you can use "Configure External Sources" on the AppSvcs instance on the managment stage (configconsole).

If you are using external sources it may be needed to also configure the delivery stage resources to support this new resource (especially if there are any additional content types involved).

The Delivery Stage is a collection of CDS's, and a CDS is a collection of resources that support content publishing. When you implement a new delivery stage you are prompted to configure both an Application Services database resource (for database-backed xml content), and a file resource (for static files). In many cases this is sufficient but the configuration framework available in WEM supports a great deal of flexibility in the design of your deployment architecture! In many cases, you will need to configure at least two CDS instances (both under the same delivery stage). One will be on the JEE host, and the other will be a static docroot CDS feeding an HTTP server (apache). You may wish to optionally locate the Deployment Agents on the WEM Server host and treat the remote CDS as disconnected end-points (this gives greater flexibility to achieve a high-availability solution).

The details of all this are well documented in the WEM Installation and Planning Guide as well as the Administration Guide. You will also need to take a look at the Planning and Implementation Guidelines for OpenText Archive Server.

Evan