System Locking and Local Service Development
Designer and Integration Server support the concept of system locking. When an element’s server-side files are marked read-only on Integration Server, the element is system locked. Files are generally system locked when a server administrator accesses the file through the server’s operating system and marks the files as read-only. You cannot edit an element until the server administrator makes the element’s server-side files writable and you reload the package in which the element resides.
System locking is disabled for elements that are checked into the VCS with the local service development feature. The local service development feature will override any read/write status changes applied manually by a server administrator.
Note:
On the Integration Server used as the local development server, the watt.server.ns.lockingMode parameter must be set to system. If you set any other value for this parameter, the Local Service Development feature may not work as expected. For more information about this parameter, see webMethods Integration Server Administrator’s Guide.
Note:
If you are using Team Foundation Server as your VCS client, Integration Server system locks all elements and marks them as read-only. To unlock an element in preparation for editing it, select the Check out for edit option from the Team menu.