Choosing Local Server Locking or VCS Integration Locking
You can configure the webMethods Integration Server to support either of the following two forms of locking:
Local locking, applied within the
Integration Server file system.
Locking resulting from integration with a third-party version control system (VCS) repository; in this case, elements are locked and unlocked as you check them out of and in to the VCS repository.
The locking administration tasks described in this chapter refer to local locking on the Integration Server. If your server environment does not make use of a version control system, configure the Integration Server for local locking as described in the following sections.
You can use the local service development feature in Designer to work with a third party version control system. For more information about local service development, see the webMethods Service Development Help
If you want to use the Version Control System Integration feature to work with a third-party version control system, see Configuring the VCS Integration Feature in the Software AG_directory \_documentation directory of your webMethods installation. This guide provides information about how to implement and administer file locking with the Version Control System Integration feature.
Important: | The WmVCS package, which provides the functionality for using the VCS Integration Feature, is deprecated as of Integration Server version 9.9. Software AG recommends that you use the local service development feature (Local Version Control Integration) to check package elements and their supporting files into and out of a version control system (VCS) directly from Designer. |
