6.3.2 What Are Repository Groups?

A repository group is a list of all the Visual LANSA PCs that have a repository that must be synchronized with a LANSA for i System. The Visual LANSA Repository can be part of either a workstation or a server configuration. The use of repository synchronization requires repository groups to be created on LANSA for i. Each Visual LANSA PC can only be in one repository group.

The word "group" can be misleading. There is just one Visual LANSA Repository allowed in each repository group. If you have three Visual LANSA Slave Workstation PCs, then you must create three separate repository groups. When Visual LANSA is used in a server configuration, there is still just one Visual LANSA Repository in each group, but there may be several PCs listed that use the repository. Hence, the group of PCs that share the single Visual LANSA Repository make up a "repository group".

How you set up repository groups depends on how the PCs and the repositories are connected to the IBM i repository:

In a repository group containing more than one PC, one PC must be identified as the repository gateway. This PC uses the Host Monitor to receive the propagations and store them in the Visual LANSA Repository. (In a slave workstation configuration, the single PC is the gateway as there is only one PC in the repository group.)

In a network server configuration, the PC selected to be the gateway must have the host monitor installed, but it does not have to be the PC with the repository. In this configuration, the gateway is often the server. If the PC identified as the repository gateway is deleted without another PC being identified as the new repository gateway, then the first PC in the repository group is considered to be the repository gateway for the repository group.

In order to set up repository groups, you need to answer at least the following questions:

A further refinement can be added to restrict which changes go to which repositories. This is referred to as a work group. When no work groups are defined, all propagations go to all repositories. (Refer to 6.3.3 What are Work Groups??)

Also See

6.3.1 Repository Synchronization Concepts

6.3.4 Rules for Repository Synchronization