CspClient Support for EBO > 3.0.x.xxx

[KarimHussain]

Hello,

Are there any plans to add support for EBO > 3.0.x.xxx in CspClient?

Br, Karim

[JeffBowman]

Hi Karim,

In theory the CSP client should work in 3.0.XXX, but I am sure maybe there are some features that are missing, or things that simply don't work with it as it is currently.

If you come across specifically that you would like to see added or fixed, please let us know and we can get it on the backlog :).

Best Regards,

-Jeff

[KarimHussain]

Hello,

Right now I can't connect to EBO 3.1.1 servers, I was assuming it was unsupported but maybe I was wrong. Was guessing it had something to do with the SE.WorkStation.Communication beeing version 2.0.0.1801 but when I try to reference the newer one from my Workstation install folder (v3.1.1.312) it doesn't work. But then again I don't even know if that's the issue 🙂

This is the error I get, note the "Incorrect server type" message. It is of type server.ES same as in 2.0 so it should work.. So my question is why it's not working (but works on 2.0 servers).

[JeffBowman]

Hi Karim,

I remember that I had to actually decompile the CSP Communication library and change it so that it wasn't version limited. I checked into it, and that still is true, so the version of the server shouldn't be affected.That said, it is very possible 3.x.x versions are doing something different with server types.. I will need to look into it. I will get back to you as soon as I can have some time to figure something out.

Best Regards,

-Jeff

[KarimHussain]

Ah okey that sound like a probability. Let me know if I can be of help in some way. 

BR, Karim 

[Anonymous user]

Hi @KarimHussain,

Did you find your answer to the replies above?

If yes, please click on "Accept as Solution" at the bottom right corner of the answer which helps you.

You can also thank the members who tried to help you by liking their comments!

Have a nice day.

[KarimHussain]

Hello, 

No, this issue has not yet been resolved. I'm still waiting for it. 

[JeffBowman]

Hi Karim,

Sorry for the delay on this.

I do have an update, but it isn't the best news, short answer is that I am still working on a solution.

Long Answer:

I have updated all the libraries that Smart Connector uses to communicate via CSP (e.g. updated the WorkStation communication libraries). When I did this, I noticed that the APIs actually changed, and took additional parameters and when all said and done, it worked! But only partially.. because it worked great for EBO 3.1, but didn't work for EBO 2.x or 1.9.. I think this has to do with the CFR-11 stuff since it seems to add the ability to add digital signatures in some requests.

So at the moment, I am trying to find a way to resolve this.. If there is a way to use the new comm libraries then great! If not, I will have to find a way to load multiple .dlls on-demand in their own app domains by first checking the version (likely with EWS), then I will also maintain two separate APIs, one for older versions and one for newer versions.

In either case, it is likely a lot of work :).

I will keep you updated! 

Best Regards,

-Jeff

[KarimHussain]

Thanks for the update! Yes I can see what you mean now, it seems that the method signature change for alot of the common CSP commands with the electric signature implementation.

I hope you manage to solve it some way and let me know I can do anything to help or test something!