SmartConnector Processor - using ILongRunningProcess interface instead of Configuration Schedules?

[mike_meirovitz]

Hi,

We have the following problem (at a customer site in the USA). 

Our Update Processor is running every X seconds, where X is defined as Configuration Schedule. For example: every 5 seconds.

Our processor logs in into the EBO each time it runs (every 5 seconds). As a results of these logins, we see an event created in the EBO watch window every 5 seconds. For example: "User Logged on" (where User is the user name defined in our SmartConnector update processor. 

These multiple logins creates a backup file with 2GB size within 1-2 months. The files are created in this folder: C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db_backup

These backup files might cause the hard disk free space close to zero within few months.

My questions are:

1. Can the EBO avoid adding these events to the backup file?

2. Can we change our update processor to use ILongRunningProcess interface and login only once at startup? Or, should we login at least once in 60 minutes due the Access Token expiration?

Thank you.

Mike

[Erwin-vd-Zwart]

Are you using http or https as EWS address? If http did you disabled redirect to https in the security settings of EBO? If not the connection is renewed all the time as far as i know..

So either change your ews to https or disable the redirect option..

[mike_meirovitz]

Hi Erwin,

Thank you for your answer. Assuming we will change the EWS to https, will the logins done every X seconds by our Processor won't create events in the EBO every X seconds?

Thanks,

Mike

[Erwin-vd-Zwart]

Hard to say as I don’t know your exact code, but i know HTTP as EWS address with redirect enabled is often a issue wearing connection threats out.. This is what i would check first..

[ardak]

I second this. Without knowing your code it's impossible to say, but making sure you're using HTTPS is the first step.

BR

Armend

[mike_meirovitz]

Hi Armend,

Thank you for your answer. I shall send you the code privately.

Assuming the customer will use HTTPS instead of HTTP, will the login events in the EBO be avoided?

Thanks.

Mike

[ardak]

I have not received any code, but I have confirmed locally that a HTTPS connection doesn't do this.

BR

Armend

[mike_meirovitz]

Hi Armend,

Thank you. I am waiting for the customer (SE USA) to confirm that when HTTPS is used, there are no login events in the EBO.

If so, we main stay with the current processor implementation.

Mike

[mike_meirovitz]

Hi Armend,

The customer is working with Schneider Electric USA. They tried to work with HTTPS instead of HTTP. 

Now the problem is that they get the following error in the SmartConnector log file:

2022-02-28 19:03:49.2869,Error,Processor,<no principal>,Could not establish trust relationship for the SSL/TLS secure channel with authority '10.0.0.19'.
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
The remote certificate is invalid according to the validation procedure.

It looks that the certificate in the EBO is properly defined.

Any idea how to solve this problem?

Can someone connect to the customer's computer and verify that the certificate is properly installed?

Thank you.

Mike 

[ardak]

Hello Mike,

I have answered you in the new thread you have created.

BR

Armend