Hello,
I've recently started working with WinCC OA so this is my first post in this forum.
Can any of you help me in how to correctly checkout (and commit) a WinCC OA project from the SVN?
As explained in the section "Implementation of SNV" of the WinCC OA documentation, a colleague of mine has commited a project without the /bin, /db, /log and /printers folders.
- If I checkout this project in an empty folder, I cannot open it with WinCC OA due to many Severe errors because the db is not found (logic as the /db folder is not in the SVN)
- If I create an empty project with WinCC OA and checkout our project inside the folders of this empty project, I can open it but many elements are missing (there are a lot of "missing xxx element" messages in the log).
Therefore, what has to be done to correctly and fully checkout a WinCC OA project from the SVN (knowing that it makes no sense to commit the whole /db folder)?
Or maybe the person who commits the project has to perform some kind of additional step or configuration?
Thank you
Best regards,
Joan
Commit and checkout a WinCC OA project in SVN
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Commit and checkout a WinCC OA project in SVN
If several persons are working on the same project committing the db folder into the SVN repository will not work as the last commit will overwrite changes by another person.
The WinCC OA database is always a complete set of files and you cannot do a commit which includes only local changes which can then be merged into the exisiting database.
If you want to save your changes in SVN you can possibly use the ASCII export/import. In SVN the ASCII file is checked in and the file is then imported in your local project.
Best Regards
Leopold Knipp
Senior Support Specialist
The WinCC OA database is always a complete set of files and you cannot do a commit which includes only local changes which can then be merged into the exisiting database.
If you want to save your changes in SVN you can possibly use the ASCII export/import. In SVN the ASCII file is checked in and the file is then imported in your local project.
Best Regards
Leopold Knipp
Senior Support Specialist
- teemu_ylonen
- Posts:10
- Joined: Tue Jun 30, 2020 3:51 pm
Re: Commit and checkout a WinCC OA project in SVN
Hello, you first have to create empty WinCC OA project to your local folder (same name as in repository is good idea). After that do checkout from the repository to your local folder and you should have up to date status excluding database. Tortoise SVN will warn you when doing checkout to your local non empty folder but just click "Checkout" anyway
Regards, Teemu
Regards, Teemu
- GTDGmbH
- Posts:2
- Joined: Wed Nov 04, 2020 1:35 pm
Re: Commit and checkout a WinCC OA project in SVN
Thank you for your replies, Leopold and Teemu
I have already tried what you propose Teemu but it is not enough because when I open the project I've checked out, many elements are missing (there are a lot of "missing xxx element" messages in the log). This is due to the fact that the database is not in the SVN and WinCC OA does not know how to generate it.
Leopold, if I understand it correctly, you propose that, before commiting a project, I (or whoever makes a modification) have to export to an ASCII file all the contents of the project, commit it, and, after a checkout I have to import that ASCII file in my project?
Is this export/import done via the System Management -> Database -> ASCII Manager panel?
Regards, Joan
I have already tried what you propose Teemu but it is not enough because when I open the project I've checked out, many elements are missing (there are a lot of "missing xxx element" messages in the log). This is due to the fact that the database is not in the SVN and WinCC OA does not know how to generate it.
Leopold, if I understand it correctly, you propose that, before commiting a project, I (or whoever makes a modification) have to export to an ASCII file all the contents of the project, commit it, and, after a checkout I have to import that ASCII file in my project?
Is this export/import done via the System Management -> Database -> ASCII Manager panel?
Regards, Joan
- teemu_ylonen
- Posts:10
- Joined: Tue Jun 30, 2020 3:51 pm
Re: Commit and checkout a WinCC OA project in SVN
We have also a few developers in a project and scenario is that everybody uses same database which is in one dedicated PC (server) where WinCC OA is installed. We discussed about this in training course and it should be possible. I think that in developer PC you have to use "server" PC event and data manager and when using para-module, it has to point also to that server PC. We have not tried that yet, maybe Leopold could enlighten more about the setup ?
Regards, Teemu
Regards, Teemu
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Commit and checkout a WinCC OA project in SVN
Yes, the idea is to use the ASCII manager to do the export and import of database information.GTDGmbH wrote: ↑ Wed Nov 11, 2020 5:18 pm Leopold, if I understand it correctly, you propose that, before commiting a project, I (or whoever makes a modification) have to export to an ASCII file all the contents of the project, commit it, and, after a checkout I have to import that ASCII file in my project?
Is this export/import done via the System Management -> Database -> ASCII Manager panel?
Best Regards
Leopold Knipp
Senior Support Specialist
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: Commit and checkout a WinCC OA project in SVN
If you have a central development server where you can run WinCC OA you can use the following setup:
-- Start the main WinCC OA project on the server
-- On the UI clients only start a UI manager which connects to the server, e.g. with config entries or start parameters
If data in the database is changed the information is saved on the server and any other user connected to the same server sees immediately the changed datamodel.
Best Regards
Leopold Knipp
Senior Support Specialist
-- Start the main WinCC OA project on the server
-- On the UI clients only start a UI manager which connects to the server, e.g. with config entries or start parameters
If data in the database is changed the information is saved on the server and any other user connected to the same server sees immediately the changed datamodel.
Best Regards
Leopold Knipp
Senior Support Specialist