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
6. Installing and configuring InDesign Server
9. Activating the Content Station license
10. Enabling Content Station for using Overruled Issues
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.
Note: Non-Asian languages are all languages except Chinese, Japanese, Korean and Malayalam.
Step 1a. Download Content Station Web from the software download page by downloading the file that does not have '[CJK]' in its file name.
Example: Download the file named Content Station 9.x.x Build xxx - Web instead of Content Station 9.x.x Build xxx - Web [CJK] |
Step 1b. Unzip the file and re-name the resulting folder to contentstation.
Step 1c. Copy the folder to the root folder of the Enterprise server (that means: in the same folder where the config and server folders are also located.) The location is dependent on the system and HTTP Server used (Apache/IIS), but should normally be in one of the following locations:
- Mac OS: /Library/Web Server/Documents/Enterprise
- Windows: c:\inetpub\wwwroot\Enterprise
- Linux: /var/www/html/Enterprise
Step 1a. Download Content Station Web from the software download page by downloading the file that has '[CJK]' in its file name.
Example: Download the file named Content Station 9.x.x Build xxx - Web [CJK] instead of Content Station 9.x.x Build xxx - Web |
Step 1b. Unzip the file and re-name the resulting folder to contentstation.
Step 1c. Copy the folder to the root folder of the Enterprise server (that means: in the same folder where the config and server folders are also located.) The location is dependent on the system and HTTP Server used (Apache/IIS), but should normally be in one of the following locations:
- Mac OS: /Library/Web Server/Documents/Enterprise
- Windows: c:\inetpub\wwwroot\Enterprise
- Linux: /var/www/html/Enterprise
Info: This feature requires Content Station version 9.5.0 or higher.
Step 1a. Download Content Station Web from the software download page by downloading the file that has '[CJK]' in its file name.
Example: Download the file named Content Station 9.x.x Build xxx - Web [CJK] instead of Content Station 9.x.x Build xxx - Web |
Step 1b. Unzip the file and re-name the resulting folder to contentstation.
Step 1c. Copy the folder to the root folder of the Enterprise server (that means: in the same folder where the config and server folders are also located.) The location is dependent on the system and HTTP Server used (Apache/IIS), but should normally be in one of the following locations:
- Mac OS: /Library/Web Server/Documents/Enterprise
- Windows: c:\inetpub\wwwroot\Enterprise
- Linux: /var/www/html/Enterprise
Step 1d. Set the Malayalam font for Content Station by enabling and defining the following setting:
- File: WWSettings.xml
- Name of option: Font
- Area: Anywhere between the
<SCEnt:ContentStation>
and</SCEnt:ContentStation>
tags - Value: malayam.swf
- Example:
<Setting name="Font" value="style/malayalam.swf"/>
Important: Make sure to validate the WWSettings.xml file for correct content. See Validating the WWSettings.xml file.
Step 2. Installing Adobe Flash Player.
- On each system, download and install Flash Player from http://get.adobe.com/flashplayer.
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.
Note: Non-Asian languages are all languages except Chinese, Japanese and Korean.
Step 2a. Download Content Station AIR from the software download page by downloading the file that does not have '[CJK]' in its file name.
Example: Download the file named Content Station Mac 9.x.x Build xxx - Air instead of Content StationMac 9.x.x Build xxx - Air [CJK] |
Step 2b. Unzip the downloaded file.
Step 2c. Double-click the Content Station installer to start the installation.
This can happen on Mac OS X 10.8 (Mountain Lion) systems after running an installer which has been downloaded from the Internet (as opposed to obtaining it from an FTP site or network).
Make sure to select the option “Don’t warn me when opening applications on this disk image”.
Note: When not selecting this option, Content Station is correctly installed but when launching it, the following message appears: “Content Station” can’t be opened because it is from an unidentified developer. |
Step 2d. Click Install.
The Settings window appears.
In the Installation Preferences section, the check box to automatically start Content Station after installation is selected by default.
Step 2e. (Optional) Clear the check box Start Application After Installation when Content Station should not be started when the installation is completed.
In the Installation Location section, the default location is entered where Content Station will be installed:
- Mac OS X: /Applications
- Windows: C:/Program Files
Step 2f. (Optional) To change the location, do one of the following:
- Manually enter a new location
- Click the Folder icon to browse to a location
Step 2g. Click Continue.
Content Station will now be installed.
When Content Station is successfully installed and the check box to automatically start Content Station was cleared, a message appears that the installation is completed.
When the check box to automatically start Content Station was selected, Content Station appears.
Step 2h. (Optional, for non-English Windows platforms only) Set the path to the WWSettings.xml file by installing the correct install.xml file:
From the unzipped build folders, locate the config folder and copy the correct file for your type of operating system to the folder where Content Station was installed (each file holds the path to the location of the WWSettings.xml file):
- Windows Vista: WinVista\install.xml
Step 2a. Download Content Station AIR from the software download page by downloading the file that has '[CJK]' in its file name.
Example: Download the file named Content Station Mac 9.x.x Build xxx - Air [CJK] instead of Content StationMac 9.x.x Build xxx - Air |
Step 2b. Unzip the downloaded file.
Step 2c. Double-click the Content Station installer to start the installation.
This can happen on Mac OS X 10.8 (Mountain Lion) systems after running an installer which has been downloaded from the Internet (as opposed to obtaining it from an FTP site or network).
Make sure to select the option “Don’t warn me when opening applications on this disk image”.
Note: When not selecting this option, Content Station is correctly installed but when launching it, the following message appears: “Content Station” can’t be opened because it is from an unidentified developer. |
Step 2d. Click Install.
The Settings window appears.
In the Installation Preferences section, the check box to automatically start Content Station after installation is selected by default.
Step 2e. (Optional) Clear the check box Start Application After Installation when Content Station should not be started when the installation is completed.
In the Installation Location section, the default location is entered where Content Station will be installed:
- Mac OS X: /Applications
- Windows: C:/Program Files
Step 2f. (Optional) To change the location, do one of the following:
- Manually enter a new location
- Click the Folder icon to browse to a location
Step 2g. Click Continue.
Content Station will now be installed.
When Content Station is successfully installed and the check box to automatically start Content Station was cleared, a message appears that the installation is completed.
When the check box to automatically start Content Station was selected, Content Station appears.
Step 2h. (Optional, for non-English Windows platforms only) Set the path to the WWSettings.xml file by installing the correct install.xml file:
From the unzipped build folders, locate the config folder and copy the correct file for your type of operating system to the folder where Content Station was installed (each file holds the path to the location of the WWSettings.xml file):
- Windows Vista: WinVista\install.xml
3. Installing Enterprise Agent
Note: You can skip this step when:
|
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
Source files
In Enterprise 9.2.1 and higher, the creation of a new article is based on the following source files:
- One or more article templates in which the default article components and the styles for formatting the text are defined. Multiple article templates can be set up within a Brand, each with different components and/or styling. This way, individual templates can be set up for each Publication Channel.
- A configuration file named componentDefs.xml in which the article components are defined that can optionally be added to the article after it has been created.
When the files are retrieved
When the user logs in to Content Station, the following is retrieved from Enterprise Server and cached in Content Station:
- A list of article templates that the user has access to
- The componentDefs.xml file
The required article template is retrieved from Enterprise Server at the moment when Content Station actually needs to create the article.
How Content Station determines which template to use
See How Content Station 9 determines which article template to use.
Setting up the article template
The article template determines the default article components and the styles for formatting the text. By assigning it to a Brand/Publication Channel/Category combination, it can be targeted to a specific form of output.
Step 1. Create the article template.
Note: This can only be done by using either InDesign or InCopy. Both have their advantages and disadvantages:
Note though that if the article template is only going to be used in Content Station, the article template only needs to have one component. This is because the actual number of article components is controlled by the componentDefs.xml file. Article templates that are also going to be used in InDesign or InCopy are not controlled by this file and therefore need to be set up in the way they are going to be used. For an environment in which the article template is going to be used in InDesign, InCopy and Content Station, creating the template in InDesign is therefore the best method. |
Steps for the InDesign workflow
Step 1a. Create a new layout.
Step 1b. Create one or more text frames and assign an appropriate Element label.
Step 1c. Define the required paragraph styles and character styles.
Step 1d. Save this article as an article template. Assign it to a specific Brand/Publication Channel/Category combination to target it for use to that particular output.
Step 1e. Repeat these steps to create as many article templates as needed.
Steps for the InCopy workflow
Step 1a. Create a new document in InCopy.
Step 1b. Create any paragraph styles and character styles as necessary.
Step 1c. Save this article as an article template. Assign it to a specific Brand/Publication Channel/Category combination to target it for use to that particular output.
Step 1d. Repeat these steps to create as many article templates as needed.
Setting up the componentDefs.xml file
The componentDefs.xml file defines which article components can be added to the article after it has been created.
The file can be configured to work across all Brands and/or to work across specific Brands.
Step 1. Access the componentDefs.xml file.
<Enterprise Server path>/config
The article components are defined between the <components> </components>
tags.
The following syntax is used:
<component name="name" allowmultipleinstances="true"/>
name
is the name of the component. Make sure that it corresponds with the name of the components that are set up in other areas of Enterprise, such as in Smart Connection for InDesign and InCopy.allowmultipleinstances
defines if the component can be used more than once. Possible values: "true" and "false".
Note: When this value is set to "false", the component is removed from the Components list in Content Station as soon as the component is part of the article. This is the case when the component is already part of the article component, or when it is manually added by the user.
Example: You might want to use set this option to 'true' for graphic components while setting it to 'false' for the header component.
Step 2. Configure the required components as necessary.
Example:
|
Configuration for all Brands versus configuration for specific Brands
The <components> </components>
tags are themselves placed between the <brand> </brand>
tags. These carry an ID by which you can define to which Brands the settings apply.
When only one Brand is defined, the ID is set to "default" and all settings are used across all Brands:
<brand id="default">
To make the settings specific to a Brand, we can replace "default" by the Brand ID:
<brand id="1">
Step 1. Open a Web browser and log in to Enterprise Server.
Step 2. In the Maintenance menu or on the Home page, click Brands. A page showing a list of all Brands appears.
Step 3. Click on the Brand for which you need the ID.
The Brand Maintenance page appears. The Brand ID is shown at the end of the URL in the address bar of the browser.
Example: Here, the Brand ID is 1:
|
We also have to add the following line of code to make sure that the default settings for the Brand are overridden:
<components usedefaults="false">
Note: When this line of code is not provided or is set to 'true', the settings for the default Brand are used.
Typically, you would have settings set up for a default Brand, plus additional settings for each specific Brand.
Example: Here, settings for a default Brand is set up and one additional group of settings for Brand with ID '1'.
|
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 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.
In Enterprise Server, click Integrations in the Maintenance menu or on the Home page, followed by InDesign Servers.
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:
- File: configserver.php file
- Name of option: WEBEDITDIR
- Possible values: the location where the Enterprise Server will put files for use by the InDesign Server(s)
- Default setting: a folder as defined by WOODWINGSYSTEMDIRECTORY
- Example: (for all platforms)
define ('WEBEDITDIR', WOODWINGSYSTEMDIRECTORY.'/WebEdit/');
The default values for the WOODWINGSYSTEMDIRECTORY are:
- Mac OS X: /FileStore/_SYSTEM_
- Windows: c:\FileStore\_SYSTEM_
Therefore, the resolved default location of WEBEDITDIR is:
- Mac OS X: /FileStore/_SYSTEM_/WebEdit
- Windows: c:\FileStore\_SYSTEM_\WebEdit
Note: It is important that Enterprise Server has Read and Write access to the following folder:
|
- File: configserver.php file
- Name of option: WEBEDITDIRIDSERV
- Possible values: The location where the InDesign Server(s) will look up files that have been made available by the Enterprise Server. Typically this is a mounted (network) folder. Physically the folder is the same folder as defined in the WEBEDITDIR setting. The InDesign Server process must be able to read existing files and write new files to this folder.
- Default setting: a folder as defined by WOODWINGSYSTEMDIRECTORY
- Examples:
In these examples, WebEdit is a share created on the Enterprise Servers machine mounted on the InDesign Servers machine. The share gives read/write access to the InDesign Server process and is mapped onto the WEBEDITDIR location on the Enterprise servers machine.
define ('WEBEDITDIRIDSERV', WOODWINGSYSTEMDIRECTORY.'/WebEdit/');
define (WEBEDITDIRIDSERV, '/Volumes/WebEdit/');
define (WEBEDITDIRIDSERV, '//170.0.0.101/WebEdit/');
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 1a. In the Maintenance menu or on the Home page, click Advanced. A page showing links to advanced Enterprise options appears.
Step 1b. Click Health Check. The Health Check page appears.
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:
Step 1. Open a new Terminal window.
Step 2. Change to the following directory:
/Applications/InDesign <version> Server/
Step 3. Enter ./InDesignServer port 18383
Step 1. Open a command prompt.
Step 2. Change to the following directory:
C:\Program Files\Adobe\Adobe InDesign <version> Server\
Step 3. Enter indesignserver port 18383
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.
In Enterprise Server, click Server Plug-ins in the Maintenance menu or on the Home page.
Step 2. Locate the plug-in named Content Station Overrule Compatibility. It will most likely be deactivated as indicated by the red 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.
Comment
Do you have corrections or additional information about this article? Leave a comment! Do you have a question about what is described in this article? Please contact Support.
0 comments
Please sign in to leave a comment.