Acquia Content Hub attempts to simplify the setup process by removing most of the initial configuration options. Once the subscribing website is configured and connected to your publishing website using the webhook, the subscribing website queues data for import as it’s exported by your publishing website.
Configuring an Acquia Content Hub publisher website requires the following information:
If you don’t have this information, see Configuring Acquia Content Hub.
Acquia Content Hub also requires a valid SSL certificate for normal operation.
Note
Websites without a valid SSL certificate must configure their webhooks to
use http, not https.
To create an Acquia Content Hub subscribing website:
Sign in to your Acquia Content Hub publishing website as a user with the Administrator role.
In the admin menu, click Extend.
Select the checkboxes next to:
The Subscriber module handles the syndication import process. The Curation module provides an interface to create Cloud Filters.
Click Install.
In the admin menu, go to Configuration > Acquia Content Hub.
Enter the following information:
subscriber_test.
Client names should be unique per website and environment
and not contain special characters. The Content Hub service uses the
client name across the websites to distinguish where your content was
created.Click Register site.
Note
To register a webhook with Content Hub, the publicly accessible URL must be
an externally accessible URL. It can’t be behind a firewall or use password
protection such as the Shield
module or an .htaccess password. Content Hub must communicate with a
subscriber’s website, and receive a valid response from the URL. If you
require password protection of a website, you must allowlist the webhook
URL path to be publicly accessible.
Acquia Content Hub tries to register with the Content Hub service. If no errors are displayed, the website has connected.
To filter imports in the Acquia Content Hub service, you can configure Cloud Filters on your publishing website. Cloud Filters deploy to each registered webhook in your platform.
To enable Cloud Filters for your websites, see Managing Cloud Platform Filters.
Acquia Content Hub subscribing websites rely on an import queue to add or update content on a subscribing website. Drush is the easiest and most reliable method to perform queued tasks. To process your import queue, use the following Drush command:
drush queue:run acquia_contenthub_subscriber_import
The command performs the following actions:
The import process repeats until all the data necessary to support the syndicated entities is present. The process reduces the number of imports and ensures future subscribing websites receive both the content and configuration required to support the entities provided by your publishing website.
Note
To delete items in the import queue, you can click Purge on the Import
Queue page. This deletes all the items in
acquia_contenthub_subscriber_import.
53 State Street, 10th Floor
Boston, MA 02109
United States
Phone: 888-922-7842