Smart Connector EWS Value not in sync with EBO

[LuxuryWaffles]

I would like to have EBO get data from 3rd party APIs,

For this, I used smart connector's REST Api Gateway using Moongoose.

After setting up the connection, I tried creating a value point which I will then use PUT /Values/{id}/Value to edit the value when I run my script to retrieve from the 3rd party.

However, after creating the value through the API, I am not able to see anything appear on EBO side, I am only able to see it appearing in the Smart Connector EWS server.

Did I setup incorrectly?

Images:
1) EBO EWS Interface setup and also empty System Tree where Values should be

2) Get Value able to see data

3) EWS Shows data
 

[LuxuryWaffles]

Hi, anyone able to help with this?

[Erwin-vd-Zwart]

@LuxuryWaffles Why are you using a “virtual” EWS server in the framework and why don’t you create an REST endpoint directly to the EWS of an ES or AS-P server?

[LuxuryWaffles]

@Erwin-vd-Zwart i was following guide on establishing connection between EBO and Smart Connector, and this is my first time setting this up and might have gotten to the wrong way.

I thought that by setting up an EWS on Smart Connector and an EWS interface in the EBO is the way to allow interactions with EBO through REST.

could you point me in the right direction? 

And also what does ES and ES-P stands for?

[Erwin-vd-Zwart]

Hi,

SmartConnector is a middleware that is running without EBO so only setting up “something” in the SC framework won’t interact with EBO by itself.

You can have a REST endpoint and an EWS in the framework like you have now, and make a EWS interface in EBO that uses your EWS server in the framework but it does not make any sense to have such a setup.

What you need to do is enable the EWS server in your Enterprise Server (ES) or Automation Server (AS-P) in EBO and create an REST endpoint in SmartConnector framework that points directly to your EWS in your  EBO server without the use of a “virtual” EWS server in the framework, those “virtual” servers are typically used for a hybrid setup when writing your own processor(s) and are normally not needed when using the RESTful gateway of SmartConnector

[LuxuryWaffles]

@Erwin-vd-Zwart I see, thanks so much for the explanation. I tried to enable EWS in the ES but do not really know what’s the full URL for the EWS, is it just 

localhost/EcoStruxure/DataExchange?

also would you recommend enabling EWS on the ES or the ASP since you mentioned EWS can be enabled on either oneself . Is there benefits over using EWS on one over the other?

[Erwin-vd-Zwart · Accepted solution]

@LuxuryWaffles The URL depends on where you have installed SmartConnector, when running on the same machine you can use localhost, but you have to check the ports used first in the software administrator, in my scenario port 81, resulting in server address: http://localhost:81/EcoStruxure/DataExchange

When using an ES you can access the full system (when permissions are set for it) and when using an AS-P you can only access that server.

Your EWS server settings should look like this:

[LuxuryWaffles]

this worked! I guess it is also related to my other post where I was connecting to the virtual EWS instead of EBO's EWS!
Cant thank you enough, @Erwin-vd-Zwart