Moving a server and its nodes to a different site

When moving a Spotfire server and its nodes from one site to another site, you must edit the nodemanager.properties file for each node. This procedure should also be used to move upgraded servers and nodes from the Default site to a site that you created.

Before you begin

You have created the site to which you want to assign the server; for instructions, see Creating sites.

About this task

For general information about sites, see Sites.

Procedure

Stop the Spotfire server and its nodes. For instructions, see Start or stop Spotfire Server and Starting or stopping a node manager.
Assign the Spotfire server to the new site by using the set-site command:
Example:
```
config set-site -n 1234abcd-ab1-1a23-1234-ab1234c5678 -s Tokyo
```
where:

-n value is the ID of the server.

-s value is the name of the site to which you want to assign the server.

Tip: If you do not know the ID of the server, use the list-nodes command to find the IDs of all the servers and nodes in the environment.
Start the Spotfire server. (Do not start the node managers.)
Do the following for each node that is connected to the server:
1. Open the following file in a text editor or XML editor: <node manager installation directory>\nm\config\nodemanager.properties.
  Example of the nodemanager.properties file:
```
#Supervisor changed
#Wed Feb 16 22:27:19 CET 2017
nodemanager.host.names=Comp_A,10.101.10.10
nodemanager.communication.port=9443
server.backend.registration.port=9080
nodemanager.registration.port=9080
nodemanager.host=
server.name=Comp_12
nodemanager.supervisor.known=Comp_C:9443-9080,Comp_D:9443-9080,Comp_12:9443-9080
nodemanager.bundle.version=42.0.6127.7990
server.backend.communication.port=9443
```
  The nodemanager.supervisor.known property lists the servers in the current site.
2. Delete the line that begins with nodemanager.supervisor.known.
3. Edit the server.backend.registration.port, server.name, and server.backend.communication.port to point to a Spotfire Server in the site to which you are moving.
  Example of the edited nodemanager.properties file:
```
#Supervisor changed
#Wed Feb 16 22:27:19 CET 2017
nodemanager.host.names=Comp_A,10.101.10.10
nodemanager.communication.port=9443
server.backend.registration.port=9080
nodemanager.registration.port=9080
nodemanager.host=
server.name=Comp_5
nodemanager.bundle.version=42.0.6127.7990
server.backend.communication.port=9443
```
4. Save and close the file.
5. Start the node manager.
The nodemanager.supervisor.known property is added back into the nodemanager.properties file. It should contain the names of the servers in the new site.
In the administrative interface, verify that the node manager comes online in the correct site.

Note: When you move a node, its service instances are removed from any resource pools they may have previously been assigned to.