Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Service Development Help | Locking and Unlocking Elements
 
Locking and Unlocking Elements
 
What Is a Lock?
About Locking Elements
Viewing the Status of Locked Elements
Copying, Moving, or Deleting Locked Elements
Unlocking Elements
Troubleshooting
In Software AG Designer, you can manage changes to elements during development by locking them. This prevents two different users from editing an element at the same time. You can lock elements such as flow services, Java services, schemas, and specifications.
All elements in Designer’s Package Navigator view are read-only until you lock them. You can edit an element only if you own the lock on the element. However, you can use and run a service regardless of its lock status, as long as you have Execute access to the service.
Local locking on Integration Server is the default locking mode of Integration Server and Designer.
If you enable Designer’s VCS Integration feature, elements are locked and unlocked when you check them out of or into your version control system repository. When an Integration Server has the VCS Integration feature enabled, system locking is effectively disabled for elements that are checked into the version control system. The VCS Integration feature will override any read/write status changes applied manually by a server administrator. For more information about implementing the VCS Integration feature, see Configuring the VCS Integration Feature in the Software AG_directory \_documentation directory.
Note:
If you are using the local service development feature in Designer, the locking mode must be set to system. To do so, set the watt.server.ns.lockingMode parameter to system.