Best practice: persistence?
Moderator: Support Team
-
Andreas
- Sr. Member
- Posts: 14
- Joined: 17 Sep 2012, 08:32
Best practice: persistence?
What is the best practice on how to persist the model and historical data so that it is intact even if the server is restarted?
-
Support Team
- Hero Member
- Posts: 3068
- Joined: 18 Mar 2011, 15:09
Re: Best practice: persistence?
Hi,
The persistence of address space and history of data and events is application specific and best practice depends on the type of application.
Regarding address space, most servers load the address space from product specific configuration files or product configuration where the configuration options did already exist before OPC UA was added to the product.
For history you can use either a data base or binary files with your own optimized storage format.
Best Regards,
Unified Automation Support Team
The persistence of address space and history of data and events is application specific and best practice depends on the type of application.
Regarding address space, most servers load the address space from product specific configuration files or product configuration where the configuration options did already exist before OPC UA was added to the product.
For history you can use either a data base or binary files with your own optimized storage format.
Best Regards,
Unified Automation Support Team
-
Andreas
- Sr. Member
- Posts: 14
- Joined: 17 Sep 2012, 08:32
Re: Best practice: persistence?
I guess our use of OPC is more advanced than average since we have a dynamic model (its not read from a configuration on startup). It would be nice to have some help from the tooling regarding serializing/deserializing the model. This could include historizing (if a default implementation was created) as well but until then we have to do it ourselves.