Maintaining the Content Delivery environment
This section contains tasks for maintaining your Content Delivery environment, as well as some advanced configuration tasks.
- Performing basic health and info checks on Content Delivery microservices
You can do a basic health check, or obtain basic info, on any Content Delivery microservice by visiting a URL you construct. - Configuring logging for a Content Delivery software component
This task applies if you run Content Delivery software components in a Java/JSP web application. You already set up logging when you installed your Content Delivery software components. But you can configure logging in more detail by editing thelogback.xml, the configuration file for the Logback logging framework used by Content Delivery. You can also set environmental parameters to tweak your log output. - Scheduling a periodic cleanup of the State Store database
To prevent the State Store database (used by Content Deployer) from growing too large, schedule a periodic cleanup. - Decommissioning a Content Delivery environment
Using PowerShell scripts and the Core Service API, you can decommission a Content Delivery environment; that is, you can delete the environment from your publishing infrastructure without explicitly unpublishing its contents. Do not decommission a Content Delivery environment unless you have a pressing reason to do so. - Deactivating and reactivating a Content Delivery environment for maintenance
Shut down a Content Delivery environment gracefully if you want to deactivate that environment for maintenance reasons. In practice, this means that the Publisher does not pick up any new publish actions directed at the environment (which in turn means they remain in the Publish Queue until the environment is reactivated. - Configuring JVM memory settings for a microservice
Allocate less or more memory than the default for your microservice by editing its application.properties file, - Managing the Ehcache cache size for the Discovery Service in Content Interaction Libraries (CILs)
If your Discovery Service uses Ehcache (rather than Redis) for caching, then to reduce the risk of running out disk space, you may want to change its default heap size and off-heap size, in addition to configuring merely the maximum number of entries in the heap. To do so, edit the Ehcache configuration file as found inside the library discovery-lightweight-client.jar on your client. - Refreshing the OpenSearch index by running a script
The process of updating the OpenSearch index requires the Content Deployer to temporarily halt indexing while the index is updated. This is accomplished by "locking" the Content Deployer for the duration of the reindexing process. If this process takes a long time, you may want to consider creating a cron job to schedule a scripted reindex at regular intervals during quiet periods. This task explains which script to run and how to configure it. - Removing a concept scheme from the OpenSearch index
Because it is not possible to unpublish a concept scheme from the Content Manager, Tridion Sites comes with a management script that you can run on the server, and that enables you to remove a published concept scheme from the OpenSearch index directly. This is only possible if the concept scheme and its concepts are not being referenced by any content item.