The beta Remote CMS is available with smartServer 3.5 UPDATE 2 and higher.
Beginning with SmartServer 3.5, you have the option of configuring your SmartServer system to run with a Local CMS or Remote CMS. The following figure is an example of the SmartServer CMS. See SmartServer CMS Overview and SmartServer CMS Widgets Index for more information.
You can use the SmartServer Local CMS to provision, manage, monitor, and control all your devices from a single CMS integrated with a single SmartServer. With the Local CMS, you run the CMS on the SmartServer IoT Edge Server. The edge devices may be any mix of BACnet, LON, and Modbus devices. You can use the Local CMS integrated in the SmartServer, or you can create your own CMS using the IAP interfaces to the SmartServer.
You can use the SmartServer Remote CMS to provision, manage, monitor, and control devices provisioned onto multiple SmartServers using a single SmartServer Remote CMS. With the Remote CMS, you run the CMS on a host computer that you provide separate from the SmartServers. The edge devices may be any mix of BACnet, LON, and Modbus devices. The Remote CMS gives you a single pane of glass to set up and operate your system across multiple SmartServers. You can access the SmartServer Remote CMS from a web browser to communicate with the Remote CMS host, or you can create your own CMS using the IAP interfaces to the Remote CMS host.
The number of SmartServers that you can support with a single Remote CMS depends on the performance and available resources on the host that you use for the Remote CMS. See Set up the Remote CMS Host Computer for more information. Each SmartServer that you provision in the Remote CMS can deliver up to 50 events-per-second (EPS) to the Remote CMS. We have tested the Remote CMS on a Dell server computer with ten SmartServers, each generating 50 EPS for a total of 500 EPS delivered to the Remote CMS.
Cloned SmartServers are not supported in Remote CMS configurations. For cloned SmartServers, use Local CMS configurations.
Follow these steps to setup a Remote CMS (see Remote CMS Getting Started):