Application Integration (On-Premises) : Configuring the VCS Integration feature : Overview : Basic Concepts
Basic Concepts
 
Summary of VCS Commands
Hierarchical Operation
Typical Work Flow
The VCS Integration feature consists of the WmVCS package and a second package that is specific to the VCS you are using, as follows:
This package...
For this VCS...
WmSourceSafe
Visual SourceSafe
WmClearCase
ClearCase
WmSubversion
Subversion
You can connect to one VCS repository from each Integration Server.
Designer continue to be fully compatible with Integration Servers that do not have the VCS Integration feature installed; when Designer connects to an Integration Server where the VCS Integration feature is not installed, is disabled, or otherwise does not start, the basic locking functionality remains available in Designer.
To use the VCS Integration feature to check packages and elements in and out of your VCS repository from Designer, the VCS client software must be installed on the computer on which Integration Server is running. Additionally, the VCS client software must be executable by the user account under which Integration Server is running. You must also have Access Control List (ACL) write privileges on the Integration Server for the packages, folders, and elements with which you want to work.
The VCS Integration feature does not provide you with a direct connection to your VCS. If you cannot connect to the VCS through your VCS client software, you will receive an error message each time you attempt to check packages, folders, or elements in to or out of the VCS from Designer.
When you start Designer and connect to an Integration Server that has the VCS Integration feature installed, configured, and enabled, the File menu and the pop-up menu are modified to offer various VCS-specific commands. In addition, the existing Delete command (Edit > Delete on the main menu bar, and Delete on the pop-up menu) interacts with the VCS Integration feature.
You can apply the VCS Integration menu commands to folders and elements that appear in the Designer Package Navigator view, up to the package level.
Components of your webMethods solutions that do not appear in the Navigation panel (such as dynamic server pages, HTML documents, templates, and configuration files) must be manually checked in and out of the VCS repository with your VCS client.
In addition, when you use Designer to apply copy and paste, move, and rename actions to any package, folder, or element subject to VCS control, the VCS Integration feature automatically updates the VCS repository to reflect the changes. For example, if you copy a service from one folder to another, the copied service is automatically added to the VCS repository in the new location.
Similarly, if you move a folder or element, it will be removed from its original location in the VCS repository and added to the VCS repository in its new location. Renamed packages, folders, or elements are also automatically updated in the VCS repository.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)

Product LogoContact Support   |   Community   |   Feedback