This article describes how to integrate Drupal 7 in Enterprise to make it possible to publish from Enterprise to a Web environment based on Drupal 7.
Note: For other versions of Drupal, see:
Steps to perform
Steps need to be performed in Drupal and in Enterprise Server.
Steps in Enterprise Server
Step 1. Set up a default installation of Drupal by following the instructions as outlined on www.drupal.org:
Step 2. Install the Drupal Modules by following these steps:
Step 2a. Download the following Drupal modules:
- Chaos tools suite (ctools). Download this from the Drupal Web site.
- OAuth. Download this from the Drupal Web site.
- WoodWing Enterprise. Download the file named Enterprise Drupal 7 Integration from the software download page.
Step 2b. Unzip the downloaded files.
Step 2c. Copy the folders to the following location:
Note: If the directory is not available yet, create the directory.
Step 2d. Enable the installed modules.
Note: The Drupal 7 Enterprise module will appear as "WoodWing Enterprise"
The components of a Drupal post (a title, teaser, body text, images and so on) are configured in Drupal as fields in a content type. Enterprise can import these content types and convert them into Publish Form templates. The content type fields are used as custom properties in the Publish Form template.
Step 3. Create a content type in Drupal for each type of Drupal post and add the required fields.
In Drupal, access Structure > Content Types and click + Add content type.
Example: Content types that could be created are those for a news article, blog post, recipe, poll, and so on.
Note: Restrictions exist for the types of fields and their properties that can be imported by Enterprise. For more information, see Supported Drupal fields for use in Publish Form templates in Enterprise 9.
OAuth provides a secure connection between Enterprise Server and Drupal.
Step 4. Configure OAuth by following these steps:
Step 4a. Log in to Drupal as administrator.
Step 4b. Navigate to Configuration > Web Services > OAuth.
Step 4c. Click Add Context.
Step 4d. Configure the settings as follows:
- Context title: Enterprise Server
- Signature Methods: only select "HMAC-SHA256"
Step 4e. Click Save.
Using OAuth requires setting up a Consumer Key and a Consumer Secret.
Step 5. Create these by following these steps:
Step 5a. In the top menu bar, click People.
Step 5b. Click Edit for the user account that is going to be used for publishing content.
Note: To create previews from Content Station the user must have an administrator role.
Step 5c. Click OAuth Consumers > Add Consumer.
Step 5d. Enter or choose the following settings:
- Consumer name: WoodWing Enterprise
- Callback URL: http://localhost
- Application context: Enterprise Server
Step 5e. Click Save.
Step 5f. Navigate back to OAuth Consumers.
Step 5g. Click Edit for the WoodWing Enterprise consumer.
Step 5h. Click Show Secret. The Consumer Key and Consumer Secret are shown. (These are needed later in step 7.)
The Drupal functionality in Enterprise needs to be enabled by enabling the "Drupal 7 - Publish Forms" Server plug-in.
Step 6. Enable the plug-in by following these steps:
Step 6a. Log in to Enterprise Server.
Step 6b. Click Server Plug-ins in the Maintenance menu or on the Home page. The Server Plug-ins page appears.
Step 6c. Enable the plug-in named Drupal 7 - Publish Forms by clicking the Unplugged icon . It changes to a Plugged In icon .
Publishing to your Drupal 7 Web site from Enterprise is done through a Publication Channel.
Step 7. In Enterprise Server, create a new Publication Channel for a Brand:
Step 7a. In the Name field, enter a name.
Step 7b. In the Description field, enter a description.
Step 7c. From the Publication Channel Type list, choose Web.
Step 7d. From the Publish System list, choose Drupal 7 — Publish Forms.
Step 7e. (Optional, only when tags should be automatically suggested. See About adding tags to Web articles). From the Suggestion Provider list, choose the provider for suggesting tags.
Info: This feature requires Enterprise Server version 9.1 or higher.
Note: The default Suggestion Provider in Enterprise is the one from OpenCalais.
Step 7f. Click Create. The Drupal Account options appear.
Step 7g. Fill out the properties:
- Web Site URL: the URL of your Drupal site
Note: Make sure that the URL ends with a forward slash "/".
- Consumer Key: The consumer key as generated on Drupal in step 5.
- Consumer Secret: The consumer secret as generated on Drupal in step 5.
- Certificate: (Optional, required for HTTPS (SSL) connections only.) The full file path of the local CA certificate file (in PEM format). See the SSL SDK for how to generate certificates.
Step 7h. Click Update.
Step 7i. Create an Issue by clicking the Add Issue button and subsequently entering at least a name for the Issue.
Step 7j. Click Update.
Step 8. Test if the integration has been performed successfully by following these steps:
Step 8a. Log in to Enterprise Server.
Step 8b. In the Maintenance menu, click Advanced. A page showing links to advanced Enterprise options appears.
Step 8c. Click Health Check. The Health Check page appears.
Step 8d. Run the Publish to Drupal - Publish Forms test. The test result is displayed.
Step 8e. (Optional, only if the test failed). Follow the instructions and run the test once more after making any changes to the Drupal configuration. Repeat this process until the test is performed successfully.
The content types that were set up in Drupal need to be imported into Enterprise so that they can be used as Publish Form templates. Similarly, any taxonomies that are defined in Drupal can be imported for use as tags in a Publish Form.
Step 9a. Access the Drupal 7 Maintenance page in Enterprise Server.
- In Enterprise Server, click Integrations in the Maintenance menu or on the Home page. A page with all integrated services appears.
- Click Drupal 7. The "Import Content Types from Drupal" Maintenance page appears.
Step 9b. (Optional and only available in Enterprise Server 9.3 or higher) From the Publication Channels list, choose the channel from which you want to import.
Step 9c. Make sure that the check boxes for importing content types and taxonomies are both selected (only available in Enterprise Server 9.3 or higher).
Step 9d. Click Import.
The import is performed and the result of the import action is displayed.