Install Planner for VCS (Version Control System) Master Repository
These instructions are for setting up a LANSA development environment where the LANSA Master Repository will reside on a VCS (Version Control System) and the LANSA development PCs are not connected to either a Windows server or an IBM i server.
A Visual LANSA System used with a VCS Master is always an Independent Visual LANSA System. It is a single user LANSA development environment with a local database and repository. It is connected to other Independent Visual LANSA Systems via a VCS Master.
A VCS Master is a Version Control System of your choice. It is only required to be able to store and retrieve text files.
Security and Task Tracking are disabled and are replaced by the VCS method of controlling access to LANSA objects.
Independent Windows Workstations to a VCS Master
When they complete a unit of work they check in the new or changed objects to the VCS Master Repository. One of the Independent Windows Workstations will be designated as the Build Machine and the Deployment Tool will be used to move or export LANSA applications to Windows or the Deliver To facility will be used to move LANSA applications to IBM i or Linux on the designated Build Machine.
It is assumed that a VCS has already been configured and in use prior to setting up a LANSA development environment using the VCS as the LANSA Master Repository.
Download installation instructions for Scenario G
When you have configured your development environment and you have verified the installation as described in the instructions, you are ready to populate the LANSA development environment from the VCS Master. This environment may be compared to the Visual Studio development paradigm. Visual LANSA will be editing text files that have been checked out from the VCS or will be creating them to be put in to the VCS Master. The Repository is still used to contain the LANSA objects, but they are now reflected into a directory of which the VCS also has a view.