Technical information

Getting Started
42
RMS Enterprise - NetLinx Programmer’s Guide
ONLINE-UNREGISTERED
When the RMS Client enters the ONLINE-UNREGISTERED state, it means that the RMS Client Gateway has successfully been
registered with the RMS system, but the Client Gateway has not been approved/accepted by a RMS administrator and assigned to
a location in the RMS system. In this state, the RMS Client will not perform any asset management or any other functions. It will
only poll the RMS server for client pending messages and will only take action on a REINITIALIZE message received from the
RMS server.
Upon receiving a REINITIALIZE message, the RMS Client will transition to the REINITIALIZE state. A REINITIALIZE
message is automatically queued for the RMS client when a RMS administrator approves and assigns the Client Gateway to a
location in the RMS system.
Refer to the Accepting RMS Client Gateway in RMS Web User Interface section on page 42 topic for details on how to approve and
assign a new RMS Client Gateway. If at any point in the client message polling with the RMS server, if a connection cannot be
established with the RMS server, then the RMS Client will transition to the CONNECT-FAIL state.
REINITIALIZE
When the RMS Client enters the REINITIALIZE state, it will restart an immediate connection attempt to the RMS server by
transitioning directly to the CONNECT-CLIENT state.
ONLINE
When the RMS Client enters the ONLINE state, it means that the RMS Client Gateway has successfully been registered with the
RMS system, has been licensed and approved by a RMS administrator, and assigned to a location in the RMS system. At this point
the RMS Client will begin asset management and monitoring registration and synchronization and begin polling the RMS server
on regular intervals for any client pending messages from the RMS server. In this connection state, the RMS Client is functional.
Upon receiving a REINITIALIZE message, the RMS Client will transition to the REINITIALIZE state. If at any point in the client
message polling with the RMS server, if a connection cannot be established with the RMS server, then the RMS Client will
transition to the CONNECT-FAIL state.
Programming the RMS Client
A RMS integrated program must be compiled and deployed to a NetLinx master before the system can participate in the RMS
system.
Configure the RMS Client
Before the RMS Client can connect to a RMS server, the RMS Client must be enabled and configured with the server path URL
and access credentials.
The easiest way to configure the RMS Client is to access the NetLinx system's web configuration pages and use the RMS Client
Web Configuration page to enable RMS and apply the proper settings. See the RMS Client Web Configuration section on page 14
for more information.
An alternate method to establish the RMS configuration is to programmatically define the connection settings in NetLinx code.
See the Programmatically Setting the Client Configuration section on page 115 for more information.
Accepting RMS Client Gateway in RMS Web User Interface
After the RMS Client has been programmed and configured to access the RMS server, a RMS administrator must approve the
RMS Client gateway's participation in the RMS system and assign the Client Gateway to a location in the RMS system. This
process takes place in the RMS Application Web User Interface.
All newly registered Client Gateway's will appear on the RMS Hotlist (FIG. 18).
Unregistered Client Gateways can also be accessed under Manage / Client Gateways from the main menu. Unregistered clients
will appear in the “Unassigned Client Gateways” group container (FIG. 19).
FIG. 18 RMS Hotlist - Newly Registered Client Gateway