Technical information

RMS Enterprise NetLinx Programmer’s Guide
2
RMS Enterprise - NetLinx Programmer’s Guide
Upgrading From RMS v3.3 to RMS Enterprise
RMS Enterprise (SDK4) supports SDK3 legacy client connections without question and without making any changes to the code.
In fact, many features will be available without any code changes (such as multi-stage and time delayed notifications and power
use based on device type).
However, several advanced SDK features (including monitored power through PDU, Duet device native support, system modes,
and web configured RMS clients) utilize SDK4 changes that will require registration of the room as new, with a corresponding loss
of all history.
If a user migrates from RMS v3.3 to RMS Enterprise and changes the code from 3.3 SDK to 4.0 SDK they will have all
their locations with 3.3 Client Gateways assigned but now OFFLINE and a completely new set of unassigned 4.0 client
gateways.
If you intend to upgrade your system (Server and SDK) completely from RMS 3.3 to RMS Enterprise, it is necessary to
delete the 3.3 Client Gateway from the location and assign the corresponding 4.x client gateway.
Once the 3.3 Client Gateway has been deleted, there will be a loss of all of the history associated with the 3.3 masters
and assets.
Terms and Concepts
RMS Enterprise introduces several new concepts and new terminology intended to more accurately convey their roles in the RMS
system.
Location Groups
Location groups are logical containers used to organize your physical environment into hierarchical structures in RMS. Location
groups may represent buildings, floors, cities, countries, etc. Location groups can contain Locations and/or child location groups
(FIG. 1).
Locations
Locations (formerly known as 'Rooms') are logical containers that typically represents a Room or Home, or Equipment Closet
where physical devices are present.
A Location must be contained in a Location Group and a location can only contain Assets (devices).
Client Gateway
Client Gateway is a new term in RMS Enterprise that represents the device that is running an instance of the RMS SDK and
communicating directly with the RMS server.
In RMS 3.x this is analogous to the “System” entity; however the “System” entity was not only the connection point but also the
physical control system master. In RMS Enterprise, the Client Gateway is a more abstract concept, it is the communication bridge
between assets (devices) and the RMS system and in most cases it resides on the NetLinx control system platform; however in
RMS Enterprise there is a separate asset record that is registered that is intended to represent the physical control system master.
The Client Gateway is a communication portal for assets. When first connected to a RMS server, the Client Gateway must be
approved by a RMS administrator and assigned to a default location. All assets registered through this client gateway will show up
in this default assigned location. Multiple client gateways can be assigned to a single location if needed.
FIG. 1 Example of Location Groups