The CoreMedia Content Server is the central component in the CoreMedia system. Among other things, it manages the content repository and the user authorization. Like all CoreMedia components it is based on Java technology. At least two CoreMedia Content Servers are required to run an online editorial system. The CoreMedia Content Management Server is the production system used to create and administrate content.

In the Content Delivery Environment the Master Live Server receives the approved content from the Content Management Server and makes it available to the CAE which generate websites or documents in other formats like PDF. If you are using the CoreMedia Multi-Master Management Extension, content from different top-level folders can be published to different Master Live Servers.

For highest stability and scalable performance, the Content Delivery Environment can be expanded by so called Replication Live Servers (see Section 2.2, “Replication Live Servers”).

The CoreMedia Content Servers and the other CoreMedia components communicate using CORBA. To build up a CORBA connection with the server, a client first has to send an HTTP request to the server to get the IOR, which contains the necessary connection parameters. To be able to connect, each host involved in the CORBA connection must be able to resolve the name of the other host through DNS. The Content Server caches requested resources in memory, therefore reducing database queries and improving the performance.