Node manager installation
To deploy Spotfire services (like Spotfire Web Player, Spotfire Automation Services, the TERR service, and Spotfire Service for Python) on a node, you must first install the node manager software to manage the service.
Service | Windows | Linux |
---|---|---|
Spotfire Web Player | x | x |
Spotfire Automation Services | x | x |
TIBCO® Enterprise Runtime for R - Server Edition (TERR Service) | x | x |
Spotfire Service for Python | x | x |
- Windows:
- Option 1: Installing a node manager (interactively on Windows)
- Option 2: Installing a node manager (silently on Windows)
Important: The installation of the Windows node manager creates a Windows service that runs as the LocalSystem account.If you change the node manager service account, make sure that the account is a local administrator and that it has read and write access to the node manager installation directory and subdirectories.
- Linux:
- Option 1: Installing a node manager (RPM on Linux)
- Option 2: Installing a node manager (tarball on Linux)
Parameter | Description | Default |
---|---|---|
INSTALLDIR
|
The node manager installation directory. | |
NODEMANAGER_REGISTRATION_PORT
|
Node manager registration port:
nodemanager.properties: nodemanager.cleartext.port
Important: In a production environment, it
is not advisable to run the node manager and the
Spotfire Server
on the same computer. However, if you are installing the node manager on the
same computer as the server, this port must be different than the
Spotfire Server
backend communication port.
|
9080 |
NODEMANAGER_COMMUNICATION_PORT
|
Node manager communication port (TLS):
nodemanager.properties: nodemanager.port
Important: If you are installing the node manager on the same computer as
Spotfire Server,
this port must be different than the
Spotfire Server
backend communication port.
|
9443 |
SERVER_NAME
|
nodemanager.properties: nodemanager.supervisor
Note: Valid
hostnames can only contain alphabetic characters, numeric characters, hyphens,
and periods.
|
|
SERVER_BACKEND_REGISTRATION_PORT
|
Server backend registration port:
nodemanager.properties: nodemanager.supervisor.cleartext.port
|
9080 |
SERVER_BACKEND_COMMUNICATION_PORT
|
Server backend communication port (TLS):
nodemanager.properties: nodemanager.supervisor.port
|
9443 |
NODEMANAGER_HOST_NAMES
|
A comma-separated list of IP addresses,
hostnames, and FQDN names that can be used by backend trust. These should be
for the interface(s) on the computer where the node manager is installed.
Note: Valid
hostnames can only contain alphabetic characters, numeric characters, hyphens
and periods.
Note: If you do not
enter any values, the installer automatically provides values. After
installation, confirm that these are correct in the following file:
<node manager installation
dir>\nm\config\nodemanager.properties.
|
|
NODEMANAGER_HOST
|
The computer where the node manager is installed. |
For administrators of large implementations who want to be able to quickly scale their Spotfire system as necessary, an automated method of installing and configuring services and service instances is available. For details, see Automatically installing services and instances.
For more information, see Nodes and services introduction.
- Installing a node manager (interactively on Windows)
You can install a node manager interactively on Windows, using the installation wizard. - Installing a node manager (silently on Windows)
You can install a node manager silently on Windows by running the installer from the command prompt. - Installing a node manager (RPM Linux)
You can install a node manager on Linux using the RPM-based installer. - Installing a node manager (tarball Linux)
You can install a node manager on Linux using the tarball installer. - Running Web Player or Automation Services on Linux
If you install a node manager on a Linux host with the intention to use it for a Spotfire Web Player or Automation Services service, there are a few additional things required. You should also be aware of some differences that your end users might encounter when opening analyses on clients running on different operating systems (for example, if the authors of the analyses use Spotfire Analyst (on Windows), and the consumer users run a web client from a Web Player service on Linux). - Starting or stopping a node manager (as a Windows service)
Start or stop a node manager Windows service from the Control Panel on the node manager computer. - Starting or stopping a node manager (Linux)
Follow these instructions to start or stop a node manager on a Linux computer. - Trusting a node
After installing a node manager, add it in the Spotfire Server as a trusted node. - Automatically trusting new nodes
To speed up the process of adding nodes to your Spotfire implementation, you can configure the system so that all new nodes are automatically trusted by Spotfire Server, or you can limit the automatic trust to specific nodes. In combination with the automatic process for installing services and instances, administrators of large Spotfire implementations in private sub-nets can quickly scale up their system as needed. - Automatically installing services and instances
To quickly and automatically add services and instances to your Spotfire implementation whenever you add and trust a new node, you can prepare a node template file that is triggered when a new node manager comes online and is trusted. This method is most appropriate for large and growing Spotfire implementations.
- Installing a node manager (interactively on Windows)
You can install a node manager interactively on Windows, using the installation wizard. - Installing a node manager (silently on Windows)
You can install a node manager silently on Windows by running the installer from the command prompt. - Installing a node manager (RPM Linux)
You can install a node manager on Linux using the RPM-based installer. - Installing a node manager (tarball Linux)
You can install a node manager on Linux using the tarball installer. - Running Web Player or Automation Services on Linux
If you install a node manager on a Linux host with the intention to use it for a Spotfire Web Player or Automation Services service, there are a few additional things required. You should also be aware of some differences that your end users might encounter when opening analyses on clients running on different operating systems (for example, if the authors of the analyses use Spotfire Analyst (on Windows), and the consumer users run a web client from a Web Player service on Linux). - Starting or stopping a node manager (as a Windows service)
Start or stop a node manager Windows service from the Control Panel on the node manager computer. - Starting or stopping a node manager (Linux)
Follow these instructions to start or stop a node manager on a Linux computer. - Trusting a node
After installing a node manager, add it in the Spotfire Server as a trusted node. - Automatically trusting new nodes
To speed up the process of adding nodes to your Spotfire implementation, you can configure the system so that all new nodes are automatically trusted by Spotfire Server, or you can limit the automatic trust to specific nodes. In combination with the automatic process for installing services and instances, administrators of large Spotfire implementations in private sub-nets can quickly scale up their system as needed. - Automatically installing services and instances
To quickly and automatically add services and instances to your Spotfire implementation whenever you add and trust a new node, you can prepare a node template file that is triggered when a new node manager comes online and is trusted. This method is most appropriate for large and growing Spotfire implementations.