• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 20 subscribers
  • Views 731 views
  • Users 0 members are here
Options
Related

What is the best way to test the Store and Forward feature when sending events using the AVEVA SDK

Sreelakshmi Chelat

I attempted to test it by stopping the HistorianServer under the HistorianGroup in the Operations Control Management Console (OCMC), then sending events to the Historian Server and checking the results in a query. The first time, I was able to see the events appear in the query after the server was restarted, but I couldn’t reproduce the same behavior the second time. How can I reliably test that events are being stored locally and forwarded to the server once the connection is re-established?

  • 0

    Time-series data values and events are not getting forwarded immediately when the connection to the historian server is restored. A minimum store/forward time duration must end up, also the server may be handling other forwarding jobs. So, you may need to wait for some time before you can see the forwarded data or events on the server side.

  • 0 in reply to Yevgeny Naryzhny

    I waited a long time to receive data and suspect that I may have stopped the Historian Server and disabled the Store and Forward option. I'm not very familiar with the AVEVA platforms, so I’d like to understand the correct way to stop the Historian Server and observe how Store and Forward works.
    I noticed options in the OCMC (Operations Control Management Console) and also saw several AVEVA-related services in Windows Services, but I'm unsure which specific service to stop.

    Could you please guide me on:

    1. The correct way to stop the Historian Server safely, to verify Store/Forward
    2. Which exact Windows service corresponds to the Historian Server that will give a result - false, when I check for connected to server status using SDK.
  • +1 in reply to Sreelakshmi Chelat

    In OCMC go to Historian => Historian Group => YOUR HISTORIAN NODE => Management Console => Status. Right click on it and select [Stop Historian]. Select the check-box [Do not stop IDAS configured for Store Forward]. Click [OK]. The same can be done programmatically by launching aahCommand.exe -stopx from the admin command line, which can be found in C:\Program Files (x86)\Wonderware\Historian.

    You can use Historian SDK classes HistorianConnectionStatus for determining the server's availability and HistorianStoreForwardStatus for determining if any data needs to be forwarded from your application. Check the Historian SDK documentation and samples for details.