Adding an non-UNICOM Intelligence server to the cluster
1 Manually prepare the server configuration file.
The server configuration file format resembles the following:
<Server name="ServerName" status="Configured">
<Roles>
<Role name="RoleName">
<Property name="Port" value="80" />
<Property name="Protocol" value="HTTP" />
<Property name="Instances" value="1" />
<!--PhoneInterviews only configured with Accessories role-->
<Property name="PhoneInterviews" value="TRUE" />
<!--RemoteAdministration only configured with Accessories role-->
<Property name="RemoteAdministration" value="TRUE" />
</Role>
</Roles>
</Server>
status
The server status should be set as Configured.
Role name
The available roles are:
▪AccessoriesServer
▪InterviewServer
▪WebServer
▪SurveyTabulationServer
▪SurveyReporterServer
▪AuthorServer
Port
The value must be a positive integer between 1 and 65535.
Protocol
The value must be HTTP or HTTPS.
Instance
The value must be a positive integer between 1 and 64.
PhoneInterviews
The value must be TRUE or FALSE.
RemoteAdministration
The value must be TRUE or FALSE.
2 Run ClusterEditor.exe on the cluster's primary server in order to update the cluster configuration file (in accordance with the server configuration file from the previous step). The silent response file <ServerName>.iss files is created in the same path as the cluster configuration file. For example:
ClusterEditor.exe <cluster configuration file> [-new <server configuration file>]
3 If a DPM login is required, the utility tries to login to DPM with LoginUsingWindowsAccount() and LoginAsTrustedWindowsAccount(). If both login attempts fail, the utility asks the user to input an appropriate DPM user name and password.
4 Run the UNICOM Intelligence Server installer on the new server (using normal or silent mode).
5 Run the ClusterEditor.exe utility on the cluster's primary server. The purpose is to add the new server to the cluster (now that UNICOM Intelligence Server is installed). For example:
ClusterEditor.exe <cluster configuration file> [-attach <server name>]
See also