Maintaining SDL Web
A number of maintenance tasks help you to keep your SDL Web installation running smoothly.
- SDL Web Content Manager configuration (MMC Snap-in)
You can configure various Content Manager settings using the SDL Web MMC Snap-in, the configuration interface in the Microsoft Management Console. Start the MMC Snap-in by selecting Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu. - 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 logging for a Content Delivery Role
You already set up logging when you installed your Roles. But you can configure logging in more detail by editing thelogback.xml, the configuration file for the Logback logging framework used by Content Delivery. - Microservice memory footprints
The various Content Delivery microservices have default Java maximum heap size settings preconfigured in their startup scripts. The actual maximum heap size needed by your microservices depends on the loads placed on them. - 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.