Open alarms need to be easily accessible in a station and
cleared alarms need to be archived for historical and regulatory purposes.
This procedure sets up a remote Orion alarm database for cleared alarms
and configures when to back up these alarms from the local file alarm
database to the remote Orion alarm database. Use this procedure if
you currently have only the default local file alarm database in your
station.
Your station is licensed for the archive alarm feature. You
are working in Workbench and are connected to the station. You have a remote Orion
database connected and ready to use for archiving cleared alarms.
- Open one of the relational database palettes based on your
type of database.
The palettes are:
rdbHsqlDb supports the
default HSQL database that comes by default with a controller.
rdbMySQL supports a MySQL database.
rdbOracle supports an Oracle database.
rdbSqlServer supports a Microsoft Sql Server.
- Add the RdbmsNetwork to your station’s container.
The framework uses a network and device model to configure an
RDBMS.
- Add the database component (HsqlDbDatabase, MySQLDatabase, OracleDatabase or SqlServerDatabase) to the RdbmsNetwork.
This defines the type of remote Orion alarm database on
your network.
- Configure the database component (device) to connect to
your remote RDBMS server.
- Open the Orion palette and add an OrionService component to the container.
- Open the AlarmOrion palette and add
the OrionArchiveAlarmProvider to the AlarmService
and double-click the provider.
The
OrionArchiveAlarmProvider Property Sheet opens.

- Set Enabled to true and configure Rdb Ord to point to the RDBMS
you configured earlier.
- Expand Execution Time and configure
when to trigger an archive of cleared alarms by setting: Trigger Mode (frequency) and Time Of Day (time).
- Save your changes and restart the station.
This configures the file alarm database in your station to
store open alarms and to periodically transfer cleared alarms to the
new remote Orion alarm database.