CoreMedia CMS is a distributed web content management system (WCMS) for creation, management and delivery of context dependent content. Most of the applications of CoreMedia CMS are deployed as web applications in a servlet container. Only the Site Manager and the server utilities are deployed as stand-alone applications. All applications can be deployed into the Cloud.
A CoreMedia system is separated into a management environment where the editors are working and a delivery environment where the customers access the website. The environments can be separated by a firewall for security reasons. The applications communicate via HTTP and CORBA, see Section 4.2, “Communication between the System Applications” for details. Table 2.1, “CoreMedia applications” shows all applications of CoreMedia CMS, describes what they do, if there are multiple instances and with which applications they communicate:
| Application | Purpose | Multiple Instances | Communicates with |
|---|---|---|---|
| Content Management Server | Manages the content in the Management Environment and publishes content to the Master Live Server. | No |
|
| Master Live Server | Manages the content in the Delivery Environment | Multiple instances when Multi-Site is used |
|
| Replication Live Server | Serves content to the CAEs | Multiple instances can be attached to one Master Live Server |
|
| Workflow Server | Executes workflows | No | Content Management Server |
| Site Manager | Management tool for workflows and users. | Yes |
|
| Studio | Content editing and management. Hosts management extensions for Elastic Social and Adaptive Personalization. | One web application |
|
| Search Engine | Indexes content and provides searches functionality. | Yes. |
|
| CAE Feeder | Feeds content beans into the Search Engine | Multiple instances possible, for example when reindexing. |
|
| Content Feeder | Serves content to the Search Engine | Multiple instances possible, for example when reindexing. |
|
| Content Application Engine | Serves sites to the customer. Hosts Elastic Social and Adaptive Personalization extension. | Multiple instances can be attached to one Master Live Server or Replication Live Server |
|
| Importer | Imports content into the Content Management Server. | Yes |
|
| Watchdog | Monitors CoreMedia applications and databases | Yes | Monitored applications |
Table 2.1. CoreMedia applications
Figure 2.1, “Architectural Overview” shows a simple deployment of CoreMedia CMS.
As shown in Figure 2.1, “Architectural Overview” CoreMedia CMS requires some third-party software for operation, which is not delivered with CoreMedia CMS. In detail, the following software has to be installed:
A Java installation.
A relational database for the content storage.
A servlet container as a runtime environment for most of the applications.
A MongoDB database for Elastic Social.
A browser for CoreMedia Studio.
In addition, you can run CoreMedia CMS with an LDAP server. Find a list of all supported environments at the CoreMedia Online Documentation.
CoreMedia CMS is not shipped with an installer. Instead, it comes as a development workspace, where you can customize it to your needs. By default, this workspace produces RPM and ZIP artifacts that you can install as usual. See CoreMedia Digital Experience Platform 8 Developer Manual for more details about the workspace.
The communication between all applications can be secured. See Section 4.2, “Communication between the System Applications” for details.
All applications of CoreMedia CMS use Logback for logging. See Section 4.7, “Logging” for details. By default all CoreMedia applications register relevant resources via JMX as MBeans for management and monitoring purposes. So, you can use a common JMX client such as JConsole to change or check the configuration, to start tasks or to get statistic data. If you only want to have a look at the configured JMX-Parameter and its values, you can simply use the CoreMedia utility jmxdump, which simply prints out this information, as described in section "JMXDump" of the Content Server Manual. CoreMedia CMS comes with two applications specific for monitoring, that is the Probedog and the Watchdog. You can use these applications to monitor the status of CoreMedia applications and to restart a server.
 |  | |
 |