Deploy ThingWorx on Standby Servers
Before starting ThingWorx on the standby server, ensure the following is in place.
• The standby server has copies of these files in its ThingworxPlatform folder.
◦ platform-settings.json
◦ keystore-password
◦ license_capability_response.bin
• The primary and standby server always uses the same files under ThingworxStorage
◦ keystore.jks
• The primary and standby server always access the same file repository folder.
To install ThingWorx on the standby server, follow the same guidelines used to install ThingWorx on the primary server. However, note the following:
• There should be no need to modify platform-settings.json
• Do not encrypt the database or license passwords. That is best performed on the primary server before the secondary server is started.
Once the install process is complete, ThingWorx is up and running through the standby server.
If there are additional standby servers to be configured, shutdown the current ThingWorx service and repeat this process until all standby servers are established.
At this point, ThingWorx can run on the primary or secondary servers. The next step is to deploy Apache ZooKeeper to coordinate the ThingWorx servers.
Optional: Create a cron job on each ThingWorx server to restart the Tomcat service if its process has stopped. The cron job should attempt to restart Tomcat through its service call. For more information, see
Cron Job to Restart Tomcat.