Adding Servers to the Log In list of Studio for InDesign and InCopy

Using Studio for InDesign and InCopy involves logging in to an instance of Studio Server. The server to log in to can be chosen from the Server list in the Log In window.

Figure: A list of Servers in the Server list of the Login window in Studio for InDesign and InCopy.

To access the Log In window, choose Log In... from the WoodWing Studio menu.

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 Studio for InDesign and InCopy is installed
• By adding them to the configserver.php file in Studio Server

Adding Server instances to the WWSettings.xml file

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.

For information about the location of this file, see Configuring Studio for InDesign and InCopy.

Note: This list is used by all applications that can log in to Studio Server. This also includes Studio for InDesign and InCopy and Smart Browser.

Step 2. Add the instances of Studio 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 Studio Server

<SCEnt:Servers> 
<SCEnt:ServerInfo name="Studio Server" 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

Info: Performing the described step requires direct server access. Depending upon how your system is hosted and the level of access you have to that system, coordination may be required with your Partner or WoodWing Support team. For a full overview of the steps that need to be done by WoodWing and how to request them, see WoodWing Cloud - Change management.

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 Studio Server is installed.

Step 1. Access the configserver.php file (recommended: config_overrule.php file) for the installed Studio 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.

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

Step 6. Save the file.