Logo Help Center

Exporting an Inception Story to Enterprise - installation and configuration

 

Exporting an Inception Story to Enterprise - installation and configuration

Stories that are created in Inception can be made part of the WoodWing Enterprise workflow by exporting them from Inception to Enterprise. During this process, a Dossier is created containing the Story in InCopy format (a .wwcml file) and all images that were used in the Story.

The communication between Inception and Enterprise Server is controlled through a plug-in that needs to be installed in Enterprise Server.

This article describes how to set up Enterprise Server and Inception to make exporting Stories possible. The process consists of the following steps:

  1. Installing the plug-in
  2. Configuring the plug-in
  3. Enabling the plug-in
  4. Testing the plug-in
  5. Configuring Inception
  6. Testing the export
  7. Advanced configuration

Before you start

Before you implement this feature, take note of the following issues and verify if they affect your setup:

  • CentOS 6 installations. When exporting to an Enterprise Server installation that runs on CentOS 6, the Story is exported as an empty article in Enterprise. This issue is related to the LibXML version used by that operating system.
  • Exporting to an unsecure (none-https) Enterprise Server installation may result in errors or unexpected behavior. Use the following workarounds:
  • Configure https on your Enterprise Server
  • Use http instead of https when logging in to Inception
  • Use Inception in Firefox and before starting the export, click on the shield in the address toolbar and select "disable insecure content protection".

1. Installing the plug-in

The plug-in that controls the communication between the two systems needs to be installed in Enterprise Server.

Step 1. Download the plug-in and unzip it:

EPContentSource_build146.zip (45KB, June 2017)

Step 2. Place the folder 'EPContentSource' to the following location:

<Enterprise Server path>/config/plug-ins

2. Configuring the plug-in

The settings of Inception need to be added so that the plug-in can establish a connection.

Step 1. Open the EPContentSource/config.php file.

Step 2. Modify the Elvis Cloud Server URL by doing the following:

Step 2a. Remove @TENANT from the end of the line:

define('EP_ELVIS_URL', 'https://vernon.woodwing.com/');

Step 2b. Change the URL to the one that matches your region:

  • Europe (Ireland): https://vernon.woodwing.com/
  • Asia Pacific (Sydney): https://vernon-ap-southeast-2.woodwing.com/
  • Asia Pacific (Singapore): https://vernon-ap-southeast-1.woodwing.com/
  • United States East (North Virginia): https://vernon-us-east-1.woodwing.com/

Step 2c. Enter the Inception user name in the Elvis user name setting:

define('EP_ELVIS_USERNAME', '');

Note: This should be the user name of the user who has access to the story in Inception.

Step 2d. Enter the Inception password for the user.

define('EP_ELVIS_PASSWORD', '');

Step 2e. (Optional) Define the Workflow Status that should be assigned to each file type in the EP_STATUSES setting.

define ('EP_STATUSES', serialize(array(
	'Article' => 'Draft text',
	'Image' => 'Images',
)));

Step 3. Save the file.

3. Enabling the plug-in

The installed plug-in needs to be enabled in Enterprise Server.

Step 1. In Enterprise Server access the Server Plug-in Maintenance page.

Step 2. Locate the plug-in named WoodWing Inception and click the icon to enable the plug-in.

The red icon should turn into a green icon.

4. Testing the plug-in

To verify if the installation and configuration has been done successfully, run the Health Check test.

Step 1. Access the Health Check page.

Step 2. Click Clear All, select the test named WoodWing Inception and click Test.

The test result is displayed.

Step 3. (Optional, only if the test failed). Follow the instructions and run the test once more. Repeat this process until the test is performed successfully.

5. Configuring Inception

In Inception, settings need to be added of the Enterprise Server instances to which Stories can be exported.

Step 1. In Inception, access the Publish channels page by clicking your Avatar and choosing Publish channels.

The Publish channels option

Step 2. In the menu on the left, click Enterprise Channels and click Add Channel.

The Publish channels page

The Enterprise Publish Channel page

Step 3. Fill out the details.

Note: Your changes are automatically saved.

  • Name: The name of Enterprise Server to connect to. This name will appear in the list of Publish channels that the user can choose from.
  • Enterprise Server URL: the URL of Enterprise Server.

Example: http://localhost/Enterprise/index.php

  • Brand name. The name of the Brand in which the Story content should be added.
  • Dossier Category name. The name of the Category to which the Dossier (in which the Story content is placed) should be assigned.
  • Dossier Status name. The Workflow Status that should be assigned to the Dossier.

6. Testing the export

To test the full setup, export a Story from Inception to Enterprise.

7. Advanced configuration

To further automate the process and to reduce the manual steps needed to prepare the article for production, you can configure the export to automatically assign Element Labels and paragraph styles to each article component.

Step 1. Create a single-component article using Content Station or InDesign / InCopy with Smart Connection installed. Make sure it contains all paragraph styles that you want to use.

Step 2. Save the article to your local system.

Step 3. Rename the file to storytemplate.wcml and place it in the following location (thereby overwriting the default file with the same name):

<Enterprise Server path>/config/plug-ins/templates

Step 4. Open the following file:

<Enterprise Server path>/config/plug-ins/conversion-rules.xml

Step 5. For each Inception component, change the name of the Element Label and paragraph style.

Note: For further details, see the comments in the file.

Step 6. Save the file and test the setup by exporting a Story.

Known issues

Exporting to an unsecure (none-https) Enterprise server may result in errors

Use the following workarounds:

  • Configure https on your Enterprise server
  • Use http instead of https when logging in to Inception
  • Use Firefox. Before exporting click on the shield in the address toolbar and select "disable insecure content protection"

No content is shown when opening an exported Inception story in Content Station

This is a known issue when Enterprise Server is installed on CentOS 6. It is related to the LibXML version used by that operating system.

Document History

  • 8 June 2017: New Content Source plug-in (build 146) added.
  • 18 October 2016: New Content Source plug-in (build 143) added, containing minor internal changes.
Was this article helpful?
0 out of 0 found this helpful / Created: / Updated:
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.