Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Using the VCS Integration Feature to Check Elements In and Out of a VCS | Locking Locally vs VCS Locking
 
Locking Locally vs VCS Locking
In a shared development environment, there is typically a mechanism for a developer to lock a file during modification, and to unlock it when the modifications are complete. This prevents other developers from working on the file at the same time.
Designer and Integration Server provide basic locking and unlocking of project files on the Integration Server only, with no built-in interaction with an external VCS. When locking and unlocking is used, Integration Server files must be checked in to and out of the VCS manually, outside of the Integration Server or Designer.
The VCS Integration feature extends and is fully compatible with the basic locking functionality of Integration Server and Designer. When the VCS Integration feature is not installed or is disabled on an Integration Server, only the basic locking and unlocking functionality will be available in Designer.