As a content creator, you may need to export more than one of your publishing website’s entities to your Acquia Content Hub at the same time. To help you with your content management, Acquia Content Hub handles many entities at once through the use of an optional export queue. Each item in the export queue has entities to export to Acquia Content Hub.
You can export entities from the queue using either the user interface or Drush.
Note
For information about batch imports (instead of exports) of entities, see Importing multiple entities at once.
The Export Queue configuration page enables the export queue, and changes its behavior. To enable the queue:
The export queue is a Drupal batch process, and each item in the batch process has entities to export. To alter the queue configuration values, navigate to the Export Queue page to display the Queue Behavior Configuration section. The section includes the following settings:
Important
Increasing any of the values will place load on your publishing and subscribing sites, and should be done with caution.
If you make any modifications to the entered values on this page, be sure to click Save Configuration to save your changes.
To process all items in the export queue, use one of the following methods:
User interface
Drush: Open a command prompt window, and then execute the following Drush command:
queue-run acquia_contenthub_export_queue
If the export queue is not configured to operate on a publisher, the export of content to Acquia Content Hub occurs during the same page request executing the entity action (create, update, delete). The process sends a resource URL to the Content Hub service, which comes back to the website on the same resource URL to retrieve the entity in CDF format.
Content Hub visits the website anonymously (with HMAC headers). This may cause the callback to fail if the website has a caching layer blocking Content Hub, or if PHP/HTTP authentication or the PHP shield Drupal module are enabled.
The export queue processing sends the CDF information directly to Content Hub in the same request instead of the resource URL. This eliminates the need for a callback to the website.
In this situation, enabling the export queue is an easy way to solve the issue. It’s possible to automate the execution of the export queue by configuring scheduled jobs which run the queue at specific time intervals.