Hello @rtirak,
Sorry for the confusion, I should have read all of the history of the post in detail instead of skimming. I do not believe that you can use the Eventing service within SOAP UI or Postman after looking through it. I believe they need to come from an HTTP Post server so that it can accept the responses. Unfortunately I do not have any experience with HTTP Posts.
For your other question, about acknowledge alarms or hidden alarms, you can use the service for getAcknowledgementHistoryForAlarm which is outlined in the DCE_WS_DEVELOPMENT.doc file.
Start by polling the system for all active alarms:
http://{{DCE_Server_IP}}/integration/services/ISXCentralAlarmsService_v2_0 <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<soapenv:Header/>
<soapenv:Body>
<isx:getAllActiveAlarmsRequest>
<!--Optional:-->
<isx:locale>?</isx:locale>
</isx:getAllActiveAlarmsRequest>
</soapenv:Body>
</soapenv:Envelope>
Request Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<ns1:getAllActiveAlarmsResponse>
<ns1:ArrayOfISXCAlarm>
<ns2:ISXCAlarm xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">
<ns2:ISXCElement>
<ns2:ISXCElementType>ALARM</ns2:ISXCElementType>
<ns2:id>nbErrorCond_maintenance_Skc9QrKk</ns2:id>
</ns2:ISXCElement>
<ns2:activeTime>2020-07-18T14:26:24.267-04:00</ns2:activeTime>
<ns2:ISXCAlarmSeverity>INFORMATIONAL</ns2:ISXCAlarmSeverity>
<ns2:ISXCAlarmState>ACTIVE</ns2:ISXCAlarmState>
<ns2:description>Notifications have been disabled for maintenance on this device.</ns2:description>
<ns2:deviceID>B9C25C7_nbSNMPEnc7DCD36FA</ns2:deviceID>
<ns2:recommendedAction></ns2:recommendedAction>
<ns2:resolvedTime xsi:nil="true" />
<ns2:sensorID>B9C25C7_nbSNMPEnc7DCD36FA_MAINTENANCEERROR</ns2:sensorID>
</ns2:ISXCAlarm>
You can then grab each of id's of the alarms and use the below steps to determine if they are still active or not.
Get Request:
GET: http://{{DCE_Server_IP}}/integration/services/ISXCentralAlarmsService_v2_0? <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<soapenv:Header/>
<soapenv:Body>
<isx:getAcknowledgmentForAlarmRequest>
<isx:alarmID>B1db239_nbErrorCond_5AE3CEC1</isx:alarmID>
</isx:getAcknowledgmentForAlarmRequest>
</soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<ns1:getAcknowledgmentForAlarmResponse>
<ns1:alarmID>B1db239_nbErrorCond_5AE3CEC1</ns1:alarmID>
<ns1:isAlarmAlertSuppressed>false</ns1:isAlarmAlertSuppressed>
<ns1:isAlarmHidden>false</ns1:isAlarmHidden>
</ns1:getAcknowledgmentForAlarmResponse>
</soap:Body>
</soap:Envelope>
You can see that there are two values returned for "isAlarmAlertSuppressed" and "isAlarmHidden".
In regards to the status on an alarm, you can see the if an alarm is still active by taking the alarmID and using that with the getAlarmByID request.
Get Request:
GET: http://{{DCE_Server_IP}}/integration/services/ISXCentralAlarmsService_v2_0
Request Body:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:isx="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<soapenv:Header/>
<soapenv:Body>
<isx:getAlarmByIDRequest>
<isx:ISXCElementID>B1db239_nbErrorCond_5AE3CEC1</isx:ISXCElementID>
<!--Optional:-->
<isx:locale>?</isx:locale>
</isx:getAlarmByIDRequest>
</soapenv:Body>
</soapenv:Envelope>
Response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soap:Body xmlns:ns1="http://www.apc.com/stdws/xsd/ISXCentralAlarms-v2">
<ns1:getAlarmByIDResponse>
<ns1:ISXCAlarm>
<ns2:ISXCElement xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">
<ns2:ISXCElementType>ALARM</ns2:ISXCElementType>
<ns2:id>B1db239_nbErrorCond_5AE3CEC1</ns2:id>
</ns2:ISXCElement>
<ns2:activeTime xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">2020-09-01T14:29:33.931-04:00</ns2:activeTime>
<ns2:ISXCAlarmSeverity xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">WARNING</ns2:ISXCAlarmSeverity>
<ns2:ISXCAlarmState xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">ACTIVE</ns2:ISXCAlarmState>
<ns2:description xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">The battery measured life test indicates that the battery is near the end of life. The battery should be replaced.</ns2:description>
<ns2:deviceID xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">B1db239_nbSNMPEnc06CCB693</ns2:deviceID>
<ns2:recommendedAction xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10">Recommended Action: Replace all faulty batteries. You can use the APC Product Selectors (http://www.apc.com/go/direct/index.cfm?tag=selectors) page to order new batteries.</ns2:recommendedAction>
<ns2:resolvedTime xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10" xsi:nil="true" />
<ns2:sensorID xmlns:ns2="http://www.apc.com/stdws/xsd/ISXCentral/2009/10"></ns2:sensorID>
</ns1:ISXCAlarm>
</ns1:getAlarmByIDResponse>
</soap:Body>
</soap:Envelope>
Using the ISXCAlarmState value, you can then know if the alarm is still active or not. When an alarm is resolved, there will also be a value for "resolvedTime".
Not sure if this will work for your setup, but you should be able to request All alarms, run a comparison with what you are still showing as active, and then request updates (getAlarmByID) for the ones that are missing from the most recent pull, which means that they should have cleared.
Regards,
Cory
... View more
