Skip to main content
Logo
There is a newer version of Contensis. Click to find out more and download the latest version.

Contensis components

This article provides an overview to the components and services that are used by Contensis.

Database

All webpages and documents created within Contensis are stored in the database. In addition to content, the database also stores all other information such as user details, audit information and metadata.

User interface

Users of Contensis access the user interface via a web browser to use Contensis. The user interface is a set files which are served by IIS, this is a web server that is installed on a Windows Server. The files for the user interface exist in a folder called CMSEngine which is located on the application server. The location of these files is specified during the installation process.

Messaging framework

The messaging framework uses RabbitMQ as it's underlying technology. RabbitMQ is a messaging broker - an intermediary for messaging. It gives Contensis a common platform to send and receive messages, and your messages a safe place to live until received.

We use RabbitMQ to connect together different parts of our application, for example when indexing entries into Elasticsearch we use RabbitMQ to connect our indexing service to Elasticsearch.

Search

The Contensis search uses Elasticsearch at its core. Elasticsearch is a highly scalable open-source full-text search and analytics engine. It allows you to store, search, and analyze big volumes of data quickly and in near real time. In 9.0 we use Elasticsearch for the entries search.

Services

Contensis services are Windows services that are installed as part of the installation process. There are 13 such services, and each one is responsible for specific tasks as detailed below:

  • Active Directory (AD) synchronisation service

    This service is scheduled to synchronise AD users into Contensis.
  • Application monitor service

    This service monitors 3rd party applications such as winword.exe for hung processes to ensure they don’t affect the publishing/indexing service.
  • Command processor service

    This service executes out of process commands to off-load work from other Contensis services, an example of this is generating thumbnails of webpages for use in reports and notifications.
  • Content synchronisation service

    This service performs the synchronisation operations within Contensis.
  • Database replication service

    This service replicates data between the Contensis database and the published website databases.
  • FTP cleaner service

    This service ensures old or rogue files that are not present in Contensis are deleted from published websites.
  • Indexing service

    This service indexes content within Contensis to enable content searches.
  • Notifications service

    This service processes notifications generated within Contensis and sends emails to relevant recipients.
  • Publishing service

    This service publishes content authored within Contensis to published websites via FTP.
  • Quality Assurance (QA) service

    This service processes web pages to ensure compliance with WCAG recommendation of accessibility and W3C XHTML Standards.
  • Service host

    This service hosts services related to content types and entries. The services it hosts carry out operations such as search indexing and publishing of entries.
  • Task scheduler service

    This service runs general tasks at specified times or intervals. An example of a scheduled task is the Google Analytics data import.