from PI System Explorer, in the development environment, right click the Elements object. Then select "Export to File..." and select the following items:
Then copy the generated file to the test/production environment and select "Import from File" in the Elements right click menu. In most cases this will work. On the other hand it would be better all the previously existing elements in the production environment before importing.
Thank you for your reply. However I do not understand your last sentence:
" On the other hand it would be better all the previously existing elements in the production environment before importing.",
Do you mean:
"On the other hand it would be better to delete all the previously existing elements in the production environment before importing".
Please let me know....
I am looking for a procedure that synchronizes instead of the need to manual delete objects and templates. Software should support the synchronization. Deleting in production is very tricky and causes manytimes problems...
you are right I was meaning delete.
It is necessary if you remove some elements from the development DB. When you import the file in the production environment, if you do not delete the existing elements, import will only add new elements and edit the existing ones, but not delete the ones deleted in the dev envirnment.
On the other hand you can simply import the file and then manually remove any element deleted in the development environment.
Thanks again for your reply.
I understand the procedure.
However, I find it rather tricky, manual delete: How do you know what/where to delete, especially if you have a large AF-structure.
How can you be sure that you have deleted everything. This is my worrie...
Is there a compare tool to compare 2 AF-structures?
that is the reason why I suggested to delete all elements.
About comparing, as long as I know, there is no such tool. On the other, in order to search missing elements, you could simply import to excel dev and production DB's in different sheets using PI Builder and use a VBA or a VLOOKUP function to compare path and element name...
1 of 1 people found this helpful
You have to be really careful with this as from what I can tell, event frames are tied to a certain parent element's GUID. If you go to backfill the event frames and deleted the original element and replaced it with an import, you will likely end up with duplicate event frames. I too am curious on how exactly one keeps a development/test/prod environment in sync, especially when you are moving things around or deleting them in the hierarchy. It is not a trivial task and much more manual than it should be.
I may be wrong here, but I have run into several examples where the only way to sync the environments is to keep good notes and make manual changes.
Good point Jim! Deletes before imports is usually a very dangerous idea if Event Frames tied to elements/Event Frames tied to analysis are to be preserved for back-filling.
3 of 3 people found this helpful
If you have a DT(A)P environment, you could use changesets to control your updates. The steps involved:
- You start with a Dev and Test that is in sync with your Prod
- You develop your change on Dev
- When done, you capture the changes in a PI Builder script
- You run the script on Test to see if the change script works and the functionality works ok
- When released, you can push the change script to Production.
This is a relatively simple way to control your changes through a DTAP environment. It does require quite careful capture of the changes in PI Builder though, but once you get used to that...
I think Roger Palmen's has the best current solution. Currently there's no automated way of doing this.
We have this KB article about moving AF Elements between PI Systems that contains a lot of relevant information: https://techsupport.osisoft.com/Troubleshooting/KB/KB01602/
Of Course, this KB is about moving AF Elements specifically and not an entire AF Database.
Finally we have this enhancement request on User Voice which I believe everyone on this thread should up vote: Native configuration promotion from test to production servers – Customer Feedback for OSIsoft & the PI System
A small note on the language in the enhancement, PI Server refers to both the PI Data Archive and PI AF. Please add comments on your use case or any other specifications you are looking for.