SboRestProvider Get/Alarms not working

[SteveGregory]

I am having issues trying to use the Get/Alarms with with EBO 3.0.2.33 and SmartConnector 2.4.22. The SBO REST provider returns a HTTP 500 error "Code=InvalidData..." and the SOAP REST provider returns "Buld Retrieve for alarm is not allowed".

Other functions of the web service are working fine and this has worked fine on previous versions. Can anyone suggest anything? Screen shots attached.

[JeffBowman]

Hi Steve,

You are correct about the SOAP provider, it simply doesn't support getting alarm items in bulk.

However, the SBO provider should in theory work.. However, because the SBO Provider uses EBO's CSP protocol behind the scenes, it is very possible they changed something in the protocol, that would need to be addressed in the REST Provider. Would it be possible for you you to turn on the Csp Client logging in Smart Connector and tell me what it shows when you send this request when using the SBO provider (also set logging level to trace).

Best Regards,

-Jeff

[SteveGregory]

See attached log file.

[JeffBowman · Accepted solution]

Hi Steve,

Just to finish up here, per our emails, it seems you actually wanted to use the /AlarmEvents endpoint and not the /Alarms endpoint. Is this all working correctly now?

Best Regards,

-Jeff

[SteveGregory · Accepted solution]

Yes it was actually the alarm events that I was after and that is working fine, thank you for pointing that out. However, should the GetAlarms still return something when using the CSP endpoint?

[JeffBowman · Accepted solution]

Hi Steve,

In theory it should! I will need to look if there were any changes in CSP in 3.x that would cause this to fail when searching. It seems between releases they break the search mechanism, so I wouldn't doubt it, if it stopped working.

Best Regards,

-Jeff