After content has been added to the Publishing queue, it can be viewed in the Publishing Queue screen (Site -> Publishing Queue).
The Pending tab displays a list of all scheduled publishing jobs:
To remove content from the queue before it gets added to the result bundle, select the content and click Delete from Queue.
To delete all the content scheduled to publishing or expire at the same time, check the box next to the Publish Date or Expire Date and click Delete from Queue.
After a job has finished running a Bundle file will be created with all the content to be published. The Bundle file can be found in the folder dotCMS/assets/bundles/[[bundleID]] in the dotCMS distribution folder.
The Status tab displays a list of all publishing jobs, both currently active and historical. Once a job begins to be pushed to the Endpoints, it will display in the Status tab, along with the current status of the bundle being published.
From this list, you may inspect check the status or the contents of any of the bundles in the list. For more information, please see the Publishing Status documentation.
The Bundles tab displays a list of all Bundles which have been created but not yet push published to an Endpoint. When you select content and Add to Bundle from the Site Browser or Content Search screens, the Bundle created is shown in this list.
From this list, you may push publish, download, or delete any of the bundles. For more information, please see the Bundles documentation.
If dotCMS encounters connection errors communicating with the Endpoint or Remote Publishing the bundle, dotCMS will attempt to republish the bundle.
- Attempts to republish the Bundle will only be made in case of failures to communicate with an EndPoint.
- dotCMS will not make attempts to retry publishing the Bundle if it encounters internal errors while creating the Bundles.
- By default dotCMS will attempt to publish the Bundle 3 times, but the number of retry attempts can be changed by modifying the PUBLISHER_QUEUE_MAX_TRIES property in the dotmarketing-config.properties file.
- It is strongly recommended that all changes to the dotmarketing-config.properties file be made through a properties extension file.