EWS client logon events (and missing a logout event) and sessions question

[henrik_alarmdir]

Hello

We have developed an application which can browse and display the structure of the system in the application.

We are using the wsdl and are using SOAP, we are wondering about:

1. the constantly "messaging" user logon, it seems that it creates a new session for each request/response, is that to be expected? Could the application "reuse" an previous session e.g. 10 seconds later (user timeout is 10min)?
2. We never see any logout messages, would it be possible to close the session from the client or does it automatically close once the request/response is completed?
3. Is there a limit to the sessions EBO/EWS can handle?
4. If the max sessions has been reached, could that possibly cause a socket error 10054 connection reset by peer (EBO)? We get quite a lot of those 10054 errors when we have been requesting for some time, which causes us to think we are actuallty not closing sessions correctly?

Regards

Henrik

[JeffBowman]

Hi Henrik,

The issue you are currently seeing is one of the many reasons why we don't support direct SOAP connections to EBO via EWS, and instead ask everyone to use Smart Connector for this type of integrations as the Smart Connector EWS Client (and Managed Client) has code to deal with this, and a few other quirks.

To your questions.

1. Yes this is expected and it is possible to re-use a session, but it requires customizing your SOAP client. You will need to use cookies, the cookies are returned from EBO in their SOAP response. This cookie lasts 5-10 minutes before needing to be refreshed. There will need to be logic to handle the refresh.

2. The sessions automatically expire (after like 5-10 minutes), there is no way to force it to log off (without rebooting EBO).

3. Yes about 1000 in around a 5 minute period, going over that will result in a socket error.

4. Yes, see above. You will need to wait for the timeout period for the sockets to be released. Keep in mind, this socket error does not only affect your application, as it will actually make it so that no one at all can access EBO.

Best Regards,

-Jeff

[henrik_alarmdir]

Hi Jeff

Thanks for your reply.

I'm aware of your (SE) preference for us to use SC, however we had to go with EWS since there are missing some functionalities in SC, at least there were at few years back, haven't checked up lately as we have used EWS successfully for some time but on one installation we have seen these issues EBO 3.2.1.630 - and are trying to analyze the issue.

I'll look in to your suggestions 🙂

Regards

Henrik