Logo Help Center

Content Station 9 full installation

Content Station 9 full installation

A full installation of Content Station 9 is an installation on a system on which Content Station is not yet installed.

The installation consists of various steps which should be performed in the following order:

1. Installing Content Station Web

2. Installing Content Station AIR

3. Installing Enterprise Agent

4. Installing the WWSettings.xml file

5. Creating a default article

6. Installing and configuring InDesign Server

7. Testing the installation

8. Starting InDesign Server

9. Activating the Content Station license

10. Enabling Content Station for using Overruled Issues

11. Starting Enterprise Agent

Content Station AIR versus Content Station Web

Content Station can either be run as a stand-alone application or from within a Web browser. The stand-alone version is referred to as Content Station AIR; the Web browser version is referred to as Content Station Web. Both versions require specific installation steps.

Content Station AIR makes use of WoodWing’s Enterprise Agent for receiving broadcast and multicast messages as well as for opening files in external applications. Enterprise Agent is part of the Content Station installation package.

Content Station Web also contains functionality used by the Text Editor in Content Station AIR; therefore Content Station Web always needs to be installed, even when it is itself not used as an application.

Smart Connection for InDesign Server

When making use of the Multi-Channel Text Editor and its layout preview and copyfit features, InDesign Server needs to be installed, together with the Smart Connection plug-ins.

1. Installing Content Station Web

Installation of Content Station Web is required when the following is planned:

  • Content Station Web is to be used as an application
  • The Text Editor of Content Station AIR is to be used

The installation of Content Station Web consists of the following steps:

Step 1. Installing Content Station Web.

Step 2. Installing Adobe Flash Player.

Note: For detailed information about the required version, see the Compatibility Matrix.

Step 3. Testing Content Station Web.

  • In a Web browser, enter the following URL:

<Server URL>/contentstation

Example: http://localhost/contentstation

The Sign In screen of Content Station should now appear.

2. Installing Content Station AIR

When used as a stand-alone application, Content Station runs by making use of Adobe AIR.

The installation of Content Station AIR consists of the following steps:

Step 1. Installing Adobe AIR.

  • Download Adobe AIR from http://get.adobe.com/air/, run the installer and follow the instructions on screen until the installation is completed.

Note: For detailed information about the required version, see the Compatibility Matrix.

Step 2. Installing Content Station AIR.

3. Installing Enterprise Agent

Note: You can skip this step when:

  • Only using Content Station Web and not Content Station AIR (Enterprise Agent is not used by Content Station Web).
  • Using Content Station AIR version 9.7.0 or higher (Enterprise Agent is embedded in these versions and automatically started).

Enterprise Agent is used for receiving broadcast and multicast messages from Enterprise Server as well as for opening files in external applications.

Step 1. From the downloaded and unzipped Content Station AIR file, unzip Enterprise_Agent_Buildxx_Mac.zip or Enterprise_Agent_Buildxx_Win.zip respectively.

Step 2. Copy the Enterprise Agent file to a central location on your system:

  • Mac OS: Enterprise Agent.app. Add this file to the Applications folder.
  • Windows: EnterpriseAgent.exe. Add this file to a folder in the Program Files folder.

4. Installing the WWSettings.xml file

Configuration of Content Station is done through the WWSettings.xml file.

Note: The WWSettings.xml file for Content Station is shared with other WoodWing applications. You may therefore find additional settings in the file compared to those described here.

To install the WWSettings.xml file or to add the Content Station settings to an existing file, follow these steps:

Step 1. Locate the WWSettings.xml file on your system:

  • Mac OS X: /Library/Application Support/WoodWing
  • Windows: c:\ProgramData\WoodWing

Note: This folder is hidden by default. To display this folder, change the folder options. (For more information about displaying hidden folders, see the Windows Vista Help file.)

Step 2. Depending on whether the file is present on your system or not, do one of the following:

  • If no WWSettings.xml file yet exists: copy the WWSettings.xml file that is supplied with the Content Station installation package to the location specified above.
  • If a WWSettings.xml file is already present: add the content of the WWSettings.xml file that is supplied with the Content Station installation package to that file.

Note: Be sure to include the sections <SCEnt:ContentStation> and <SCEnt:EnterpriseAgent>.

Step 3. (Optional) Configure the following settings for Enterprise Agent:

  • HostAddress. Address of the system on which Enterprise Agent is running.

<Setting name="HostAddress" value="localhost"/>

  • HostPort. Port that Content Station uses to communicate with Enterprise Agent. Change its value if it conflicts with other applications.

<Setting name="HostPort" value="8094"/>

  • LogLevel. Determines the type of information that is captured when an error occurs. Possible settings are: NONE, ERROR, WARN, INFO, DEBUG. The amount of information gets richer from left to right. NONE disables the low-level logging.

<Setting name="LogLevel" value="DEBUG"/>

  • LogPath. Path to the log file to which Enterprise Agent appends logging. Note that for each session, data is added to the same file; its file size may therefore grow rapidly.

<Setting name="LogPath" value="/FileStore/Logs/EA.log"/>

Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.

5. Creating a default article

When a new article is created in Content Station for use in the default Multi-Channel Text Editor (see Defining which text editor to use), various source files are referenced. These are used to determine the following aspects of the created article:

  • Which and how many article components the article should contain
  • Which and how many article components should be available to add at a later stage
  • Which styles should be available for formatting the text

6. Installing and configuring InDesign Server

When making use of the Multi-Channel Text Editor (enabled by default), InDesign Server needs to be installed together with the Smart Connection for InDesign Server plug-ins in order to make use of the following functionality:

  • Ability to open InCopy CS4 articles. During this process, these types of articles (in WWCX format) are converted to a CS6 compatible file type (WCML format).
  • Making use of the layout preview and copyfit features.

Step 1. Install InDesign Server as per Adobe’s instructions.

For compatible versions, see Compatibility of Smart Connection for InDesign Server with Enterprise Server.

Step 2. Install the Smart Connection plug-ins for InDesign Server by running the Smart Connection installer on the machine(s) running InDesign Server.

See Installing Smart Connection.

Step 3. Define the InDesign Server host by following these steps:

Step 3a. Access the InDesign Server Maintenance page.

Step 3b. Click New InDesign Server.

Step 3c. Add the configuration settings:

  • Host Name (IP address): Defines the address on which the SOAP interface of InDesign Server is available.

Note: This is an http address. Enter either the host’s IP address or its DNS name.

Example: http://myidserver.

  • Port Number: The port you start the InDesign Server with.
  • Application Version: The version of InDesign Server. Click the Auto Detect Version button to automatically detect the installed version.
  • Description: Enter a descriptive name.
  • Active: Enable or disable the InDesign Server instance (enabled by default).

Step 3d. Click Update.

Step 4. Configure the following options:

7. Testing the installation

The next step involves testing the installation and configuration of the Multi-Channel Text Editor and InDesign Server.

Step 1. Access the Health Check page in Enterprise Server.

Step 2. Click Clear All to deselect all selected tests.

Step 3. Select the InDesign Server / CS Editor test.

Step 4. (Optional, only if CS4 compatible articles are going to be opened with the Multi-Channel Text Editor). Select the Content Station CS4 Article Conversion test.

Step 5. Click Test.

The test results are displayed next to the test and should display OK.

Note: If the test fails, an error is displayed together with instructions for how to solve it. Follow the instructions to fix the issue and then run the test once more.

8. Starting InDesign Server

To start InDesign Server with the SOAP interface enabled, the port to the application needs to be specified.

After completing the steps below, the soap interface of the server will be available on port 18383.

On the system(s) where InDesign Server is installed, follow these steps:

Tip: The startup of InDesign Server can also be automated using Macaroni (Mac) or Scheduled Tasks (Windows).

9. Activating the Content Station license

Before Content Station can be used, a license needs to be activated for it. This process takes place on Enterprise Server. For more information, see About licensing and Managing licenses.

10. Enabling Content Station for using Overruled Issues

In Enterprise Server, an Issue can be set up in such a way that it uses its own Categories, Workflow, and User Authorization definitions and not those defined in the Brand that the Issue is part of.

This is done by selecting the check box for the option 'Overrule Brand' when creating the Issue.

In order for such Issues to appear in Content Station, follow these steps:

Step 1. Access the Server Plug-ins page.

Step 2. Locate the plug-in named Content Station Overrule Compatibility. It will most likely be deactivated as indicated by the red icon Server plug-in disabled icon.

Step 3. Click the red icon. It should automatically turn green, indicating that the plug-in is now active.

Note: When this plug-in is active, overruled Issues are represented in Content Station as their own Brand with one Issue, meaning that if one Brand has been set up containing 2 overruled Issues, they appear as 2 separate Brands in Content Station. The naming format used is <Brand name> <Issue name>.

11. Starting Enterprise Agent

Note: You can skip this step when using Content Station AIR version 9.7.0 or higher (Enterprise Agent is embedded in these versions and is automatically started).

Step 1. Ensure that Enterprise Agents is run during startup of the system:

  • Mac OS: Add Enterprise Agent to the login items for the current user.
  • Windows: Add EnterpriseAgent.exe to the startup items.

Step 2. Run Enterprise Agent (Mac OS X) or EnterpriseAgent.exe (Windows) respectively.

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.