Options for graceful shutdown, decommissioning and synchronization of components for publishing
Various new tools and scripts help to maintain and manage the new publishing environment more easily. The features described here do not work with the deprecated old publishing framework.
- Pausing the Publisher service
-
System administrators who want to temporarily pause the Publisher service can do so. Doing so means that the Publisher does not pick up any new transactions, but does keep processing deployment feedback.
- Graceful shutdown of Publisher service
-
System administrators who want to shut down the Publisher service for whatever reason can now be sure that the following business rules are applied before a shutdown:
- The shutdown procedure places all transactions that have not yet been transported back in the publish queue, with their transaction state set to Waiting For Publish.
- The shutdown procedure waits until all transactions that have the transaction state Scheduled for Deployment have sent their commit packages to transport.
- Graceful deactivation and reactivation of a Content Delivery environment
-
Taking down a Content Delivery environment for maintenance is now possible in a graceful way from the Content Manager server.
- Decommissioning of a Content Delivery environment
-
You can decommission an entire Content Delivery environment without having to unpublish content first.