Integration Server 10.3 | VCS Integration Feature Configuration Guide | Overview | About the VCS Integration Feature | Locking Files Locally versus VCS Locking
 
Locking Files Locally versus 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. In this case, Integration Server files have to be checked in to and out of the VCS manually, outside of the Integration Server or Designer.
For more information on the details of basic locking operation, see Locking Administration and Best Practicesand the webMethods Service Development Help in 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.