3.3Services and their configuration
The cmsWorks application server consists of a variety of services, each one serving a special purpose like the preview of contents, connections to a database and so forth. See the "cmsWorks service list" for more information about the services and their fields of activity/functionality.
Every service has a bundle of parameters that define the behavior of the service. Any of these parameters for service parameterization are found in the folder <cmsWorks-installdir>/run/properties and are referenced in the properties file <cmsWorks-installdir>/run/topas.properties with their name, leaded by a #include-statement.
For example in topas.properties:
#include properties/email.properties
# ------------------------------------------------------------------
# Including properties for different types of tasks for the cms
# package.
# ------------------------------------------------------------------
#include properties/database.properties
#include properties/cms.properties
#include properties/generator.properties
#include properties/scriptserver.properties
#include properties/search.properties
Description how services work in cmsWorks
Every service serves a special, well defined task, his field of activity. Services may talk to each other or better: services may take use of each other.
The CMSCore-service, for example, is the interface to obtain content resources or folders (the resources are structured in). Therefore it has to access the database via the database service CMSDB: The CMSDB-service provides database connections and database connection pooling.
The GeneratorPreview-service which renders previews of output (i.e. a HTTP page) needs to obtain resources from the CMSCore service, which eventually asks the CMSDB service for a database connection to get the resource from the database and so forth.
cmsWorks service list
Following a list of (standard) services in cmsWorks with their service name and a description of the field of activity/functions these services occupy.
Service name | Description |
Service that connects to a database the content is stored in | |
Base service and interface for requesting information about content and caching these informations internally | |
Service beeing a CMS service only returning published resources (omitting resources not published) | |
Providing the cmsWorks editors desktop user interface for the browser | |
Preview generator produces a website based on all available documents with their current contents | |
Generator produces a website using only the latest published version of documents | |
Service that provides the cmsWorks scripting engine | |
Search engine managing search indexes | |
Collector service that passes content into the search-service for the WebUI | |
Collector service that passes content into the search-service for the online site |
Detailed configuration options and how to change the configurations of these services are explained in the following chapters.