WoodWing Help Center

Adding Servers to the Sign In list of Content Station 9

 

Adding Servers to the Sign In list of Content Station 9

In order to use Content Station, it needs to be logged in to an instance of Enterprise Server. The Server to log in to can be chosen from the Server list in the Sign In window.

The Server list in the Sign In window

Figure: A list of Servers in the Server list of the Sign In window in Content Station

Instances of Enterprise Server are added to the list by defining them between the <SCEnt:Servers> </SCEnt:Servers> tags of the WWSettings.xml file.

The Server instances in the list can be added in the following ways:

  • By adding them to the WWsettings.xml file on each system on which Content Station is installed
  • By adding them to the configserver.php file in Enterprise Server

Adding Server instances to the WWSettings.xml file

When using this method, the WWSettings.xml file on each of the systems on which Content Station is installed needs to be updated each time a Server reference is added or modified.

When using this method, the WWSettings.xml file on each of the systems on which InDesign and InCopy is installed needs to be updated each time a Server reference is added or modified.

Step 1. Access the WWSettings.xml file.

Note: This list is used by all applications that can log in to Enterprise. Apart from Content Station, this also includes Smart Connection and Smart Browser.

Step 2. Add the instances of Enterprise Server between the <SCEnt:Servers> </SCEnt:Servers> tags in the following syntax:

<SCEnt:ServerInfo name="name" url="URL"/>

  • name is the name as it will appear in the list
  • url is the URL of the instance of Enterprise Server

Example

<SCEnt:Servers> 
<SCEnt:ServerInfo name="Enterprise" url="http://localhost/Enterprise/index.php"/> 
</SCEnt:Servers> 

Step 3. Save the file.

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

Adding Server instances to the configserver.php file

When using this method, the list of Server instances is configured on the Server, thereby making it easier to roll-out changes throughout the company, for example when a new version of Enterprise Server is installed.

When using this method, the list of Server instances is configured on the Server, thereby making it easier to roll-out changes throughout the company, for example when a new version of Enterprise Server is installed.

Step 1. Access the configserver.php file for the installed Enterprise Server.

Step 2. Locate the APPLICATION_SERVERS section.

// APPLICATION_SERVERS:
// List of available application servers (returned through GetServersReponse SOAP 
// call).
// To return only 'this' application server, just comment out the APPLICATION_SERVERS 
// definition as follows:
//    //define( 'APPLICATION_SERVERS', serialize( array() ) );
// To return NO application servers (and so let clients use wwsettings.xml), define 
// empty APPLICATION_SERVERS as follows:
//    define( 'APPLICATION_SERVERS', serialize( array() ) );
//
define( 'APPLICATION_SERVERS', serialize( array(
   //  ServerInfo( Name, URL [, Developer] [, Implementation] [, Technology] 
   //  [, Version] [, array of Feature] [, Cryptkey (file path)] )
   new ServerInfo( SERVERNAME, SERVERURL, SERVERDEVELOPER, SERVERIMPLEMENTATION, SERVERTECHNOLOGY, SERVERVERSION, unserialize(SERVERFEATURES), defined('ENCRYPTION_PUBLICKEY_PATH') ? ENCRYPTION_PUBLICKEY_PATH : null ), // this server
   new ServerInfo( 'WoodWing.net', 'http://demo.woodwing.net/Enterprise/index.php', SERVERDEVELOPER, SERVERIMPLEMENTATION, SERVERTECHNOLOGY,
   	'', 	// version unknown - may not be null
   	array() )// feature set unknown - may not be null
)));

Two Servers are already present: one that is defined by internal definitions such as SERVERNAME and SERVERURL, and a custom Server named 'WoodWing.net'.

Step 3. Replace the example Server by your own Server and add additional Servers as needed.

Step 4. Save the file.

Step 5. In the WWSettings.xml file of each system, make the following change:

Note: This step only needs to be performed once; once in place, only the configserver.php file needs to be updated for any future changes.

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

Step 5a. Comment out or remove the <SCEnt:Servers> </SCEnt:Servers> section.

Step 5b. Add a single <SCEnt:ServerInfo> element directly under the Settings node, defining the Server containing the modified configserver.php file.

Example:

<Settings xmlns:SCEnt="urn:Smart Connection Enterprise" xmlns:SC="urn:SmartConnection" xmlns:WoodWing="urn:WoodWing Software">

<SCEnt:ServerInfo name="Enterprise" url="http://localhost/Enterprise/index.php"/>

Note: In this scenario, only one <SCEnt:ServerInfo> element is allowed. During startup, the defined Enterprise Server instance is accessed and the list of Servers is retrieved from the configserver.php file.

Step 6. Save the file.

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.