2Introduction to services
The kernel of cmsWorks consists of several so-called "services" (or "microservices") residing in the cmsWorks application stack which interact with each other or even the outer world.
Every one of these services has its own function, i.e. to perform search queries on the content, provide the editors desktop or even the connections to the database.
As a first example a GeneratorService will be described here.
A GeneratorService
- accepts http-requests and handles them
- provides methods to build URLs
- provides access to the CMS-service to JSPs so that they can display stored content
- provides methods to include (html) content from other sources
- is specialized within the task it has to fulfill (i.e. there is a preview generator and a live generator which deliver specialized views on the stored content, but due to the html-nature of the editors user interface, a specialized generator (WebUI-service) generates the cmsWorks desktop, too)
This way, different services serve different functions and to achieve this, they have to interact with the CMS-service (CMSCore). The CMS-service
- provides methods to access folders, documents and their content
- all other services (i.e. the GeneratorServices) who want to access these information have to access the CMS-service to get them
To obtain information, the CMS-service has to read and write them from and to a database. Responsible for the connection to the database is the database service (CMSDB).
A list of available services in cmsWorks - and services in general - are discussed in more detail in the chapter Services and their configuration.