There exist architecture best practices for a Dev & Test Environment for PI Server, AF and PI Vision?
We want to replicate all of those systems for development purpose.
Thanks in advance
This question has nothing to do with OSIsoft products, and is more of a general IT design philosophy for companies to adopt completely independent of PI products.
I personally prefer working with a Dev, Test, Staging, and Production environments, though sometimes Dev and Test are combined into 1. Having separate environments is a waste if you do not faithfully adhere to the philosophy. For instance, the belief is that you thoroughly deploy in Staging before you attempt to do so in Production. But a couple of years ago, I recall a post where the person did that EXCEPT his Staging environment at the start of the tests did not match his Production environment, thus invalidating the tests. At the start of the test, OS and product version numbers should match in Staging and Production.
Again, this works well with PI products but is a design completely independent of PI. I would think there are other resources else where that can help.
Thank you for your answer Rick, but I do believe there should be some best practices, just to mention few questions:
- how should be connected PI Server DEV with PI Server PRD?
- it's recommendable to integrate PI Server DEV with PI Interfaces?
- there should be PI Interfaces DEV?
- It's useful to connect PI AF DEV / PI Vision DEV with PI Server PRD?
It was my mistake, I didn't express myself in a good way and I wasn't talking about IT infrastructure.
In my opinion most of the answers to your questions depends on your needs. That's also the reason why I believe OSIsoft doesn't have best practices for these.
Please first think about the use cases and then decide on what you need to build.
thank you very much Carlos, it makes sense
Retrieving data ...