Content Station 9 full installation

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.

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.

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.

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.

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.

Step 2b. Unzip the downloaded file.

Step 2c. Double-click the Content Station installer to start the installation.

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.

Step 2b. Unzip the downloaded file.

Step 2c. Double-click the Content Station installer to start the installation.

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

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.

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.

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.

<brands> 

<brand id="default"> 
   <components> 
      <component name="head" parastyle="head" allowmultipleinstances="false"/> 
      <component name="subhead" parastyle="subhead" allowmultipleinstances="false"/> 
      <component name="intro" parastyle="intro" allowmultipleinstances="false"/> 
      <component name="byline" parastyle="byline" allowmultipleinstances="true"/> 
      <component name="body" parastyle="body" allowmultipleinstances="true"/> 
      <component name="caption" parastyle="caption" allowmultipleinstances="true"/> 
      <component name="credit" parastyle="credit" allowmultipleinstances="true"/> 
      <component name="crosshead" parastyle="crosshead" allowmultipleinstances="true"/> 
      <component name="graphic" parastyle="graphic" allowmultipleinstances="true"/> 
      <component name="highlight" parastyle="highlight" allowmultipleinstances="true"/> 
   </components> 
</brand> 

</brands>

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">

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.

<brands> 

<brand id="default"> 
   <components> 
      <component name="head" parastyle="head" allowmultipleinstances="false"/> 
      <component name="subhead" parastyle="subhead" allowmultipleinstances="false"/> 
      <component name="intro" parastyle="intro" allowmultipleinstances="false"/> 
      <component name="byline" parastyle="byline" allowmultipleinstances="true"/> 
      <component name="body" parastyle="body" allowmultipleinstances="true"/> 
      <component name="caption" parastyle="caption" allowmultipleinstances="true"/> 
      <component name="credit" parastyle="credit" allowmultipleinstances="true"/> 
      <component name="crosshead" parastyle="crosshead" allowmultipleinstances="true"/> 
      <component name="graphic" parastyle="graphic" allowmultipleinstances="true"/> 
   <component name="highlight" parastyle="highlight" allowmultipleinstances="true"/> 
</components> 
</brand> 

<brand id="1"> 
   <components usedefaults="false"> 
      <component name="head" parastyle="head_web" allowmultipleinstances="false"/> 
      <component name="subhead" parastyle="subhead_web" allowmultipleinstances="false"/> 
      <component name="intro" parastyle="intro_web" allowmultipleinstances="false"/> 
      <component name="byline" parastyle="byline_web" allowmultipleinstances="true"/> 
      <component name="body" parastyle="body_web" allowmultipleinstances="true"/> 
      <component name="caption" parastyle="caption_web" allowmultipleinstances="true"/> 
      <component name="credit" parastyle="credit_web" allowmultipleinstances="true"/> 
      <component name="crosshead" parastyle="crosshead_web" allowmultipleinstances="true"/> 
      <component name="graphic" parastyle="graphic_web" allowmultipleinstances="true"/> 
      <component name="highlight" parastyle="highlight_web" allowmultipleinstances="true"/> 
   </components> 
</brand> 

</brands> 

In Enterprise Server, click Integrations in the Maintenance menu or on the Home page, followed by InDesign Servers.

• 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

• 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/');

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 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

In Enterprise Server, click Server Plug-ins in the Maintenance menu or on the Home page.