Ask our Experts
Didn't find what you are looking for? Ask our experts!
Launch of Consumer/Home Owner registration process! We are pleased to announce the commencement of the Consumer/Home Owner Registration Process on Community. Consumers/Home Owners may now proceed to register by clicking on Login/Register. The process is straightforward and designed to be completed in just a few steps.
Schneider Electric support forum about SmartConnector applications for integration of other building management systems (BMS) into EcoStruxure Building Operation.
Search in
Posted: 2021-06-18 06:25 AM
Link copied. Please paste this link to share this article on your social media post.
Hi
I configured both SoapEwsRestProvider and SboEwsRestProvider for an ES.
And tried GET Values/{id} with Swagger APIs interfaces.
With same id provided, the Soap one could not find the value. While the Sbo could find it.
I have attached the responses body for the two requests.
The configurations:
The Soap one (configured on port 8089) and server is http://ip_of_ES/EcoStruxure/DataExchange
The Sbo one (configured on port 8083) and server is http://ip_of_ES
What might be the reasons caused the differences? 🙂
Thank you!
Link copied. Please paste this link to share this article on your social media post.
Hi Na,
You have not posted the ID you used, but if you are using the exact same ID for both, then I would suspect this would not work.
Because the SOAP Provider uses EcoStruxure Web Services as it's underlying data provider, the ID provided must be the EWS ID. In EBO the EWS of a Value Item always starts with 01 (If it is a Value item itself) or 11 (if it is property of a Value Item). In the case of the SBO Provider, this prefix was not needed.
Example:
SBO Provider ID: /Server 1/Values/Temperature
SOAP Provider ID: 01/Server 1/Values/Temperature
Best Regards,
-Jeff
Link copied. Please paste this link to share this article on your social media post.
Hi Na,
You have not posted the ID you used, but if you are using the exact same ID for both, then I would suspect this would not work.
Because the SOAP Provider uses EcoStruxure Web Services as it's underlying data provider, the ID provided must be the EWS ID. In EBO the EWS of a Value Item always starts with 01 (If it is a Value item itself) or 11 (if it is property of a Value Item). In the case of the SBO Provider, this prefix was not needed.
Example:
SBO Provider ID: /Server 1/Values/Temperature
SOAP Provider ID: 01/Server 1/Values/Temperature
Best Regards,
-Jeff
Posted: 2021-06-18 01:16 PM
Link copied. Please paste this link to share this article on your social media post.
Hi Jeff,
I was using exact the same id for the request that configured via Soap and Sbo providers.
And after adding the prefix 01 to the id, the Soap one works now.
Many thanks for the answers.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.