Using the VCS Integration Feature to Check Elements In and Out of a VCS

Designer enables you to create, maintain, and manage custom integration packages for use by the webMethods Integration Server. Often, many enterprise organizations employ a version control system (VCS) for the development of software solutions, providing automatic auditing, versioning, and security to software development projects. Such products include Microsoft Visual SourceSafe and IBM Rational ClearCase.

With the VCS Integration feature installed in your development environment, you can check packages or elements in to and out of your version control system (VCS). For example, to modify a flow service element, you would:

1. Check out the flow service. This automatically checks out its supporting files (node.ndf and flow.xml).

2. Modify the flow service in Designer and save the changes.

3. Check in the flow service element. This also checks in the node.ndf and flow.xml files and makes the files read-only when they are checked in.

Alternatively, if you want to work on other elements in addition to the flow service, you can check out the entire package.

For information about configuring VCS to work with Integration Server, see Configuring the VCS Integration Feature.

Note: The VCS Integration feature provides functionality similar to that of local service development. However, the VCS Integration feature and local service development are not the same. For information about how the VCS Integration feature compares to local service development, see How Does Local Service Development Differ from the VCS 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.