Application Integration (On-Premises) : Configuring the VCS Integration feature : Working in a Shared Development Environment : Implementing a Shared Development Environment : Working with Multiple Integration Servers and One VCS Server
Working with Multiple Integration Servers and One VCS Server
 
Sharing Packages Among Integration Servers
Locking Files in a Shared Development Environment
Importing a Package from Another Integration Server
In this environment, multiple software developers work on two or more Integration Servers, and each Integration Server is connected to the same VCS server. Setting up an installation for this environment involves the following general steps:
1. Configure each Integration Server for use with the VCS Integration feature. For more information, see Configuring Integration Server and Designer .
2. Configure the VCS-specific package on each Integration Server to connect to the same VCS server. For more information, see Configuring the WmVCS Package to Work with Visual SourceSafe.
3. For Visual SourceSafe and Subversion, map Integration Server users to Visual SourceSafe or Subversion users, respectively. For more information, see Configuring Access to the VCS Repository.
In this scenario, each Designer user is able to check Integration Server packages and elements in to and out of the VCS server. All Designer users connect to the same VCS server. There is a possibility that a package or element may be shown as available for check out when it is actually checked out by a user on another Integration Server. For an example, see Working with Multiple Integration Servers and One VCS Server.
Copyright © 2015- 2017 Software AG, Darmstadt, Germany. (Innovation Release)
Product LogoContact Support   |   Community   |   Feedback