You are here: LANSA for i User Guide > 8. LANSA PC Development > 8.2 Repository Synchronization > 8.2.2 Work Groups

8.2.2 Work Groups

Configuration of repository synchronization does not require work groups to be created in order for changes to be propagated. When no work groups are defined, all propagations go to all repositories. A work group is a list of all the PCs that share the same work. The members of a work group can be in the same or different repository groups.

When a PC in a work group checks in objects to the IBM i using the host monitor, copies of all these objects are checked out to the repositories of the other members of the group. Where a work group contains two or more PCs defined in the same repository group, the propagations are sent only once to the repository gateway.

For example, the PCs of a group of developers working on financial applications for a company could form one work group so that they share the latest versions of objects.

A PC can be in many work groups or in no work groups at all. It does not have to belong to a repository group. A work group must contain at least two PCs.

If one work group exists, and the PC originating a change is not in a work group, the change is not propagated.

In order to configure work groups you just need to know which PCs share the same work and want to automatically receive changes that a co-worker makes.

If repository groups are set up but there are no work groups, all PCs are considered to be in one universal work group.