Server

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,
• staging (live content) which is for users of offers,
• and fall-back (all content).

The Sophora primary servers can be clustered and the staging servers can be operated in a network.

Robust Architecture for Rapid & Fail Safe Publishing

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

The Primary Server sends the content to all connected Staging Servers. You can connect as many Staging 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 Staging Server in the default configuration uses a fully encapsulated Java database. This reduces the administrative workload and means additional servers can be rapidly deployed.

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

A fallback server is readily available in an emergency.