Queue handling in asynchronous publishing
As of version 4.5 Exponential is set up with a new and improved system, eZ Asynchronous Publishing, for deferring publishing requests to a queue for asynchronous handling of the published objects. The feature aims at increasing the number of objects that can be published concurrently. This is typically a function used in an advanced environment with a large simultaneous load on the database.
A daemon handles the publishing requests and the queue in the background. As a user you will only get information as to the status of your published objects, all processing of the queue is automatic and no user interaction/intervention is possible.
Feature limitation: The asynchronous publishing is not supported on the Windows platform.
In this section
- Enable the publishing queue functionality Asynchronous publishing is disabled by default and needs to be enabled by overriding a setting in content.ini. Please enter the setting as described below:
- Setting up the asynchronous publishing service with an in... This is the method that we recommend on production. Standard init scripts are provided, and can be used to have the daemon started on boot.
- Starting the daemon manually The daemon can be started manually by running the following, as your web server user:
- Various configurations There are limitations as to how the daemon can be setup in different configurations. The basic principle is one daemon per database and it can be summarized like this:
- Publishing objects asynchronously When you have enabled "Asynchronous publishing" in "content.ini" and started the daemon, the system will handle your publishing requests as described below.
- Make prioritizations in the queue via filtering hooks The asynchronous publishing system comes with filtering hooks that can easily be implemented in order to prevent items from being published asynchronously.
Contributors
- Geir Arne Waaler Updated
Comments
Add a comment