The worker process for Automation Services or the Web Player hosts an internal web server that binds to the system's network interfaces. How to configure it so that it does not use IPv6 when binding to addresses on the Windows node manager machine.

Windows Machine

The Spotfire Automation Services and Web Player do not provide a built-in option to prevent the worker process from using IPv6. Therefore, the recommended approach is to disable IPv6 at the operating system level on the Node Manager’s Windows machine.

Note: However, you can prevent Spotfire Server from using IPv6 to communicate with the node manager.

Steps to Update Backend Addresses on the Spotfire Server:

1. Navigate to the spotfire-bin directory and run the command config list-addresses to show you all configured addresses.
2. You need to use the set-addresses command to change them or add a new one.
3. First, stop the Spotfire server services and then run the below command (for example).

config set-addresses -A<fqdn> -A<shortname> -A<ipv4> -A<ipv6>

• (Replace <fqdn>, <shortname>, <ipv4>, and <ipv6> with your specific values.)

4. Start the Spotfire server services
5. and run the command config list-addresses to verify the new addresses.

Updating Node Manager Settings:
To reflect the new backend addresses on the Node Manager:

• Manually edit the nodemanager.properties file located in the nm/config directory.
• After making the changes, revoke and re-trust the nodes to apply the updates properly.

This article provides information on how to prevent the Spotfire Automation Services or Web Player worker process from binding to IPv6 addresses.

Doc: set-addresses

• https://docs.tibco.com/pub/spotfire_server/latest/doc/html/TIB_sfire_server_tsas_admin_help/server/topics/set-addresses.html

Doc: list-addresses

• https://docs.tibco.com/pub/spotfire_server/latest/doc/html/TIB_sfire_server_tsas_admin_help/server/topics/list-addresses.html