Alarm Command protocol
The Alarm Command SOAP web service provides access to working with events and alarms in the VMS from a non .NET environment.
Some of the functionalities provided are:
- Creating alarms and events
- Updating and acknowledging alarms
- Getting new alarms and events as they are coming into the system
- Querying existing alarms and events from the system
- Getting alarm history and statistics
There are two versions of the Alarm Command web service: AlarmCommand and AlarmCommandToken. The former is for use with Windows users, while the latter is for use with Basic users.
In order to use the AlarmCommandToken interface you need to get hold of a token and keep it valid. See the documentation on the Server SOAP Protocol for further information about how to do this.
The AlarmCommand and AlarmCommandToken web services are hosted by the Event Server and will thus be exposed on the machine and port used by this.
On a default installation on the local machine with no encryption set for the Event Server, you can access the WSDL on these addresses:
http://localhost:22331/Central/AlarmService2?singleWsdlhttp://localhost:22331/Central/AlarmServiceToken?singleWsdl
In case encryption for the Event Server is enabled, you can access the WSDL on these addresses:
https://localhost:22331/Central/AlarmService2?singleWsdlhttps://localhost:22331/Central/AlarmServiceToken?singleWsdl
Sample
For further information on how to use these web services, have a look at the Alarm List sample.