Host Monitor and Visual LANSA Slave Repositories
LANSA for iSeries stores the Master LANSA Repository and the Visual LANSA Systems contain the Slave Repositories. Again, one or more Visual LANSA development environments may be connected to the LANSA for iSeries System.
The LANSA for iSeries Master Repository is used to store the master definition of all LANSA objects in a partition. As development work is completed on a Visual LANSA slave system the new or modified object should be checked into the Master Repository leaving a read-only copy of the object in the slave repositories. The master definition may then be checked out for update into one of the slave repositories as required. Refer to Example Development Cycle (with Master).
The Visual LANSA Slave Repositories will initially be empty (aside from Demonstration objects). Typically the slave repository is populated by copying the required object definitions from the LANSA for iSeries Master System to the Visual LANSA Slave System. Objects may be copied using the export or check out from master repository features. The objects may be copied as read-only (i.e. the slave systems cannot change the object definition but can view the latest definition from the Master Repository) or the objects may be checked out for update.
Task Tracking is used in LANSA to control access to objects to ensure an object's definition is not being changed by multiple developers at the same time. Repository Synchronization or 5.2.5 Refresh Master Object List is used to make sure that any changes made to the Master System are reflected in the specified Slave Systems.
Also see