Server

Server

The Sophora Server is the heart of the Sophora CMS.

The Sophora Server manages the entire content repository. The Sophora Server is a Java application that is designed to meet high expectations in terms of performance and reliability.

There are three roles that a Sophora Server can have:

  • primary (all content) - for editing,
  • delivery (live content) which is for users of offers,
  • and fall-back (all content).

The Sophora Primary Servers can be clustered and the Sophora Delivery Servers can be operated in a network.

Robust Architecture for Rapid & Fail Safe Publishing

Sophora divides tasks between a Sophora Primary Server for editing work and the Sophora Delivery Servers for content delivery.

The Sophora Primary Server sends the content to all connected Sophora Delivery Servers. You can connect as many Sophora Delivery Servers as necessary; all are fail-safe.

Each server saves the live content locally in its own repository and delivers it even if the other servers fail. Each Sophora Delivery Server in the default configuration uses a fully encapsulated Java database. This reduces the administrative workload and means additional servers can be rapidly deployed.

Typical Sophora Server Infrastructure
Typical Sophora Server Infrastructure (Image: subshell/CC BY)

Sophora also has a reliable fallback concept for the Sophora Primary Server. Fallback servers can be connected to the Sophora Primary Server and can be constantly provided with all content in all versions.

A fallback server is readily available in an emergency.

Features and Modules

Linkchecker

The Linkchecker verifies the availability of external websites. If a broken link is found in a linked document, the link checker takes the document offline so that no one ends up on "404" error pages.

If the website is available again, the link is set to the "Edited" state and the editors can publish the linked documents again.

The editorial team can easily find the "dead" links in an internal list, called the Sophora "proposal section".

LDAP

With Sophora LDAP, users can be authenticated via an LDAP server. A connection to an LDAP server is configured in the Sophora Server. Sophora only needs read access to the LDAP server. The users can be safely and comfortably managed in Sophora.

Content API

The Sophora Content API provides a REST-based interface.

With the Content API, content from Sophora can be accessed via HTTP in JSON format. Write and edit options are also available. The Sophora Content API is well suited for use cases that do not require a lot of individual business logic. For more complex use cases, the development of your own Content-API with Sophora resources is more suitable.

Server Modules

Binary Store

Binary Store

Binary Store makes it possible to store images and other binary files more efficiently.
Change Registry

Change Registry

The Sophora Change Registry provides an easy way to synchronize content changes to external systems.
Cloud Binary Store

Cloud Binary Store

Unified cloud image storage.
Sophora Cloud Delivery

Sophora Cloud Delivery

With Sophora Cloud Delivery, webapps and Sophora Delivery Servers can be scaled independently of one another.
Cluster

Cluster

With Cluster nightly updates are a thing of the past. Editors can work uninterrupted.
SoQL (Sophora Query Language)

SoQL (Sophora Query Language)

SoQL offers a standardized approach to formulating queries for Sophora Documents.

Details

ID
SERV
Docs
Documentation
Audience
Development
Compatible With
Sophora
Is an Add-on
No
Is Part Of
Sophora
Categories
Business, Developer
Type
Standalone
Creator
subshell GmbH
Administrators Developers
Sophora Delivers the News for the ZDFheute-App and zdf.de Emerging news and video content are fail-safe, even during peak traffic times and high hit rates.
Sophora IPTC The module extracts meta data from images and can save meta data in JPGs .
Sophora Content API The Content API enables simple retrieval of documents in simple use cases.
Icon