EBO workstation problem when Creating EWS server

[mohameds277]

Greetings everyone , 

I am facing a problem when creating an EWS in EBO workstation , 

The EWS server name is set to (localhost) 

port number : 5300

and the call service is SmartConenctor username and password ( image_1 shows the EWS configuration ) .

after the the edit wizard is done , the server becomes online for a small duration then it becomes offline , and it shows error in the list view in the hardware section (image_2 displays the error )  

Am I missing a step ? 
My objective is to connect the EBO with smart connector using EWS 

@Mahmoud_Sayed 

[Erwin-vd-Zwart]

Is your service started now? You reported in another thread that it refused to start the service.

Can you browse the EWS server in the SC framework and see all datapoints?

Is there any other server with the same port in the SC framework?

Have you checked any firewall settings that might block your EWS port?

[mohameds277]

thank you for your response,  yes the smartConnector service is working right now 
the thing that I don't understand is the EWS server tap menu in the SmartConnector Portal 
Is it for starting an EWS server or to assign the smartConnector with a pre-running EWS server ? 

And after hours of searching I found out that the EWS server is initialized using  a EBO workstation software   named device administrator , is there any way to obtain this software , or at least can I make my own custom EWS server that retrieve and sends  SOAP Requests ?  

[mohameds277]

do you mean the smartconnector service , if yes , its working 

[Erwin-vd-Zwart]

The EWS server tab in the framework is meant for a Hybrid Setup, There are 2 ways to connect to EBO, 1 is directly from your written SC extension to EBO via a discovery procedure in your code, or by using a "virtual" server in the middle.

In this "virtual" EWS server you can create folders and datapoints from your code and read/write updates to and from so all your processes are running without the need of an EBO system, from EBO you can than create a EWS interface that links into this 'virtual' server.

There is no need for Device Admin to create a server in the framework, the DA is usually used for setting up real HW servers. For performing SOAP requests to an EBO server you don't need a "virtual" EWS server in between the framework..