I have always believed that only one HMI server is allowed per physical or virtual server. However, in testing some FTView upgrades on a non-live system without data servers, I created a test system with two HMI servers on the same physical server, each serving a separate application area. This setup surprised me as I thought it was not permitted. I am unsure if this is a recent change or if I have misunderstood something. Typically, I would use a single HMI server for small unrelated systems with all the displays organized in a flat file structure. However, the ability to have each system as its own HMI server poses some interesting possibilities, though I am not sure of the advantages it may offer. It may result in more overhead, but it does provide flexibility, especially when trying to merge two small systems on individual servers into a single server.
It is officially possible to host two HMI Servers on one machine, enabling each computer to serve as a redundant backup for the other. For instance, Computer A can act as the primary server for Area A and the backup for Area B, while Computer B can be the primary server for Area B and the backup for Area A. Despite Rockwell Automation suggesting a limit of two servers for performance reasons, there is no definitive restriction on the number of HMI Servers that can be hosted on a single machine.
Indeed, it's quite fascinating that you were able to setup two HMI servers on the same physical server, each handling a separate system. Typically, the notion has been one HMI server per physical or virtual server, but as technology advancements continue, new possibilities keep emerging. The advantage here, as you rightly pointed out, is the flexibility it provides, particularly when integrating smaller systems. Nonetheless, the overhead cost can't be overlooked. It's a scenario that calls for a delicate balance between efficiency and practicality, but it indeed opens up the room for innovative solutions. Keep experimenting!
Your experience is indeed interesting and not entirely surprising since HMI server limitations can often be contingent on the software version or even the hardware capabilities. Having multiple HMI servers on a single machine brings about the advantage of application area isolation, meaning that an issue in one area doesn't risk impacting the others. The overhead you mentioned is a valid point, it might be higher due to the need to manage more servers, which includes regular maintenance and potential troubleshooting. Overall, with a proper architecture and managed well, this could be a suitable solution for specific scenarios. It's always valuable to remember to tailor server configurations to fit the needs of the individual project for best results.
From my experience, it's indeed possible to run multiple HMI servers on the same physical or virtual machine, but it's not typically done due to potential conflicts. Your observation about overhead is spot on, as with each running instance you'd be increasing the burden on your server, not to mention the risk of confusion in deployment and maintenance down the line. However, having segregated HMI servers for different system areas can be beneficial in particular scenarios - it can provide better organization of resources, easier troubleshooting, and offer more control over individual system areas. It's more about understanding your specific use case and whether the benefits outweigh potential drawbacks.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Yes, it is possible to have multiple instances of the FTView SE HMI Server running on the same physical or virtual server, as observed by the user in the discussion thread.
Answer: - It is unclear if this capability is a recent change or if it has always been possible. The user in the discussion thread was surprised by the setup and questioned if they had misunderstood the limitations.
Answer: - Running separate HMI servers for different application areas can provide flexibility, especially when merging small systems from individual servers into a single server. However, it may result in increased overhead compared to using a single HMI server for all systems.
Answer: - While having separate HMI servers may offer flexibility, it is important to consider the potential impact on system performance due to increased overhead. Users should weigh the advantages of flexibility against the resource implications.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.