Apart from adding the ObixService and possible use of Obix “export” objects (all copied from the tridiumx/obix jar), the following additional configuration changes may be necessary in R2 JACE stations, depending on the intended transition of an R2 Web Supervisor to Supervisor.
Before making any of the changes below, please read the related AX sections in this document to understand current limitations.
Currently, there is no known utility to “convert” the existing application database (appdb) of an R2 Web Supervisor into a
format that can be “merged” into the existing Supervisors collection of histories and alarm database.
-
If mastering R2 Schedule objects from an Supervisor (or another AX JACE), and they are currently “slaved” to another R2 Schedule, you need to first unlink those slaved R2 Schedules (remove externalSubscription at “slaveIn” input). For more information on engineering for the “AX side,” see Supervisor engineering.
-
Depending on how log archiving is to continue for any R2 JACE station, you may wish to change the setup of the station’s LogService, with the following Config tab properties:
-
archiveMode — from “archive_remote” to “archive_local”.
-
archiveAddress — uncheck Supervisor entry
For related details on archiving R2 logs as histories to an Supervisor, see R2ObixClient Histories (logs and archives).
-
-
Depending on alarm/alert management is to continue for any R2 JACE station, you may wish to change the setup of the station’s NotificationService, with the following Config tab properties:
-
alarmArchiveAddress — uncheck Supervisor entry
-
archiveMode — from “archiveRemote” to “archive_local” (if a JACE-4/5, “archive_local_no_SQL”).
For related details on R2 alarms/alerts at an Supervisor, see R2ObixClient Alarms.
-