Overview    Features    Supported Platforms

Overview    Content Server    Content Center    Catalog Center    Personalization Center    Marketing Studio    Integration Center    Satellite Server

Downloads

Publish Eurisko Internet Advanced Search

Unsubscribe  |  Lists

About  - Contact  - Site Map

Feature	Benefit
Business Manager
Asset management	Any piece of content, (e.g. article, image, document) is treated as a reusable, self contained asset. Content assets can be associated, cross-referenced, and workflowed together. This enables enterprises to maximize their investment by providing a comprehensive, consistent view of their valuable content. Users can take advantage of the following asset management features;
Intuitive interface	An easy-to-use interface makes it possible for business managers such as marketers, product managers, and reviewers to perform editorial tasks without requiring IT intervention. This improves productivity, minimizes bottlenecks and lowers the total cost of ownership of the content management system.
Browser-based content entry and modification	A browser-based interface enables remote contribution of content and minimizes IT headaches of managing client software. Thin client architecture reduces the overhead of upgrades.
Workflow	A flexible, robust workflow mechanism creates efficiencies in content revision and reduces mistakes in site content. Content Center workflow provides the ability to apply rules to the life cycle of an asset. Processes such as editing, approval and publishing can be defined and enforced as a series of states to reflect business processes.
Site Tree	A hierarchical view of a web site provides an easy to follow view of the assets belonging to a particular site. The Site Tree organizes the pages that a site plans to publish.
Asset Types	Asset types is a way of describing a set of assets with a common purpose. Content Center ships with a number of pre-defined asset types (Article, Image, Linkset and Page) and accompanying metadata structure which will probably serve as delivered. Organizations can define their own.
Collections	A collection is a ranked group of assets (from a single asset type), created by and containing the results of a query. When a page is displayed on a site, the collection of assets (e.g. a set of related article links) is displayed in the order determined by the query or editors.
System Developer
Customizable content acquisition	Using a variety of mechanisms (e.g. XML Post) existing data stores (e.g. a legacy database) and external source (e.g. a newswire feed) can be used by Content Center. Such data can be merged with other rich content as part of the editorial process or passed directly through to delivery.
Templates	Templates control the look and feel of the pages that make up a Content Center managed site. Additionally, templates enable the dynamic display of data in these pages. To accomplish this, developers use a set of Content Server specific XML tags to interact with the database. Templates control the 'form' of the site. Content is provided via the assets.
Personalization	Content Center generated pages can be constructed for personalized or customized delivery based on user profile information or a variety of other criteria (e.g. time and season). Advanced personalization capabilities can be obtained with Personalization Center.
XML development environment	Template developers work with familiar XML code to create Content Center templates. As Content Center tags are extremely efficient and flexible, developers can avoid using SQL-saving time both during development upgrades and system changes. Of course, SQL can be used if a developer deems it necessary.
Asset Maker	Streamlines the process of creating new asset types. A Content Center asset consists of a Java object, a table, a set of XML elements and a set of templates. From an XML asset descriptor file, Asset Maker automatically creates the tables, elements and forms required for Content Center asset management, significantly reducing the time and complexity of asset creation.
Powerful search mechanisms	Key to any highly dynamic site is the ability to find and sort content efficiently. Template developers can rapidly employ a range of search and navigation techniques through Content Center XML tags. During the asset creation process, system developers can determine which assets should be indexed by a rich text indexing engine such as AltaVista and which should be used in a more traditional database search.
Content Server
Content Server/Content Center	Content Center leverages the strengths of Content Server to provide an open, scaleable platform for management and delivery of dynamic content. It runs on the three leading J2EE compliant Application Servers (BEA, iPlanet & IBM), taking full advantage of the inherent high performance and reliability. The following features directly leverage the functionality provided by Content Server;
Revision Tracking	Content Center utilizes the Content Server revision tracking system to manage elements, templates and content revisions. Revision tracking provides source control and versioning for individual assets. For example a Site Administrator can configure revision tracking to prevent more than one person from editing an asset at the same time. Revision tracking allows users to review an asset's history and rollback the asset to a prior version.
Publication and Delivery	Content Center provides the ability to deliver content to a variety of environments for any business requirement. Examples of these are as follows;
Dynamic	For pages whose content, design, or functionality is customized or personalized to the reader or browser
Static	Content Center can export content in multiple formats to flat files, including HTML and XML.
Simultaneous, multi-targeted	A single piece of content may be published to different publications using different templates. This is particularly important for co-branding applications or simultaneous publishing to the Web and wireless devices.
Incremental publish	Provides the ability to selectively publish assets only if they have changed. Incremental publish potentially improves publishing speed by reducing the number of assets to be published compared to the number to be checked.