Command line scenarios
See
See also
Adding a UNICOM Intelligence server to the cluster
It is assumed that the UNICOM Intelligence software has already been installed on the virtual or physical computer.
1 Configure the server using the ServerConfig.exe utility.
Run the ServerConfig.exe utility on the new virtual computer image or physical computer. The purpose is to collect information regarding which UNICOM Intelligence products and roles are installed on the image/computer, and to update the image/computer configuration to match the destination server cluster. For example:
ServerConfig.exe <cluster configuration file>
If the UNICOM Intelligence software was installed on the virtual computer image with a different service user, or with an anonymous user other than the normal cluster users, and the cluster configuration file does not contain the encrypted password for the users, the user will be prompted to enter the service user and anonymous user passwords.
Silent installation creates encrypted passwords.
2 Adding the server with the Cluster Editor utility.
Run the ClusterEditor.exe utility on the cluster's primary server. The purpose is to add the new server to the cluster according to the defined server configuration file. For example:
ClusterEditor.exe <cluster_configuration_file> [-attach <server_name>]
See also
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 <server_name>.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
Removing a server from the cluster
There are two options for removing a server from a cluster.
Detach
Run ClusterEditor.exe, using the -detachparameter, on the cluster's primary server. The purpose is to remove the server from the cluster and update the server's status to detached in the cluster configuration file. For example:
ClusterEditor.exe <cluster_configuration_file> [-detach <server_name>]
Delete
When removing an attached server, run ClusterEditor.exe, using the -delete parameter, on the cluster's primary server. The parameter first detaches the server, then removed the server from the cluster configuration file.
ClusterEditor.exe <cluster_configuration_file> [-delete <server_name>]
You will be asked to confirm the server removal.
See also