• More
Menu Search

OpenText Content Hub For Publishers

  • CHP Introduction
  • Features
  • Architecture Overview

OpenText Content Hub for Publishers has been designed to meet the unique demands of the challenging changes in publishing. Publishers that adopt it will:

  • Gain a solution focused on editorial operations with over fifteen years of proven history.  It began as the first national newspaper digital photo archive in the UK.  Today it provides the cornerstone of content management for some of the largest newspapers in the world and many leading consumer magazine brands.  It is capable of handling hundreds of millions of pictures, articles, pages, graphics, video and sound
  • Benefit from over a hundred years of accumulated knowledge from people with invaluable experience and expertise in newspaper and magazine operations and technologies.
  • Join a growing number of publishers taking advantage of the latest developments and advances in modern newsroom and magazine production solutions to better face today’s and tomorrow’s challenges.
  • Work with a global software company with commitment to the highest standards of customer service and on-going development in key technologies and solutions.

Using Content Hub for Publishers will enable publishers to:

  • Improve the process of content creation and reduce the effort needed to publish to different channels – print, web, mobile and tablet
  • Increase the re-use of existing content and reduce costs of content acquisition
  • Provide a single central location for the storage, sharing and use of assets
  • Have deeper and better control over rights and access to reduce risks
  • Automate the planning, commissioning and payments processes with a platform designed specifically to meet these business imperatives and remove the manual cost inefficiencies associated with such processes
  • Leverage a content hub designed to foster agility and responsiveness to rapidly changing market conditions and channel specific opportunities.

It has been designed in conjunction with the journalists and editors who use it. This invaluable insight from the industry means that the latest version has greatly extended both the User Interface and User Experience.

Previous versions concentrated on high volume picture processing and archive libraries.

The introduction of a new authoring tool provides publishers with a central repository for editorial content creation for multi channel publishing. Sound and video can be managed and stored. Preparing and packaging content for print, digital, smartphone and tablet channels is easy.

A rich set of APIs enables seamless integration with print editorial systems and tools across website, mobile and tablet devices.

OpenText Content Hub for Publishers is a highly modular and functionally rich platform for publishers to receive, analyse and tag, create, package distribute and store all forms of content effectively and simply.  The slides below aim to provide a glimpse into the main features of the solution.

Content Hub for Publishers (CHP) is designed as a classic tiered architecture – where each major component and service can be clustered to provide resilience and scalability. The following outlines the set of services and applications provided within CHP.


Figure 1 – CHP Architecture

Application Overview
CHP The application that end users interact with. This is entirely browser based, and requires a HTML5 compliant browser.
Web Services CHP provides a web services interface based upon an implementation of the open standard CMIS specification.
System Management The System Management application provides a set of consoles for managing all aspects of CHP – users, background processing tasks, system queues, locks, etc.
Syndication Portal The Syndication Portal provides a public interface for partners and clients to access and download selected content. Access to download content can be restricted by a workflow, to only allow access to authorised content. The portal includes an engine that can be used to automatically apply pricing policies.
Application Overview
RDBMS CHP requires a relational database to store core metadata structures. CHP is not provided with an embedded database engine – Oracle 11i is recommended for enterprise scale deployments.
Asset Storage The asset storage subsystem embedded within CHP support storage tiering to allow different classes of digital asset to be stored on appropriately performing storage devices.
Search/Index The Search/Index tier provides high-performance indexing and searching of content.
LDAP CHP can be integrated with directory services such as Active Directory, via an LDAP interface. This allows a centralised user authentication system (user groups are currently still managed within CHP).
Transformation Engine The embedded transformation engine is CHP performs all image and video manipulated functions.
Content Analytics Engine CHP is provided with an embedded OpenText Content Analytics (OTCA) engine. This delivers text mining based features (taxonomies, faceted search, automatic tagging, more like this, etc).

Software architecture

The core of the Content Hub for Publishers product is built as a J2E application, and is typically deployed under the Jboss application server (although has also been deployed under other application servers). Some CHP services are provided as platform-native builds in order to deliver high performance (for example, the transformation engine).


The CHP product has been deployed under Solaris, Linux (Red Hat) and Windows (Server) platforms. It is recommended that a 64-bit architecture is provisioned to allow JVM to access large amounts of memory on critical tiers.

Different tiers can be deployed on different platforms if required. Tiers can also be deployed into a virtual estate; however it is recommended that some analysis is completed in order to ensure that the product can deliver the required performance.


CHP has resilience features built in from the ground up – such as connection pooling, queuing, and resource clustering; all of which work together to allow the application suite to handle multiple resource and service failures.


CHP provides the ability to create redundant copies of data, such as indexing across multiple instances to provide resilience. OpenText recommends that database technologies are used to provide redundancy of data – for example, Oracle DataGuard.