Number and Distribution of the Distribution Services
In addition, a minimum requirement for packaging is: A Distribution Service must be available in every site that has a repository.
Physically, a
Distribution Service runs on a Management Point.
Logically, a Distribution Service is responsible for the distribution
of individual site structure objects. Therefore every object has an entry
in the configuration table specifying the responsible
Distribution Service.
Theoretically, one Distribution Service should
be adequate for all depots in the entire site structure. In practice,
a separate Distribution Service should be created for every network
(LAN) in order to reduce accesses between
networks as much as possible.
Rule of thumb: For each site, an individual Distribution Service
should be set up that is responsible for the site. Otherwise, copying
procedures within a site would
also transpire via the connection between two sites.
In addition, a minimum requirement for packaging is:
A Distribution Service must be available in every site that has
a repository.
Background: When preparing for distribution, the responsible Distribution
Service compresses the package’s installation files. We recommend not
to perform this action beyond LAN limits.
- In the figure below,
Region 1 contains Site 1 and Site 2. The master of Region 1 is also the
master of Site 1. Site 1 and Site 2 are connected via WAN.
The responsible Distribution Service for Site 2 is within in Site 2. It therefore only has to execute one of four distribution procedures via the WAN:
1) Reading the source (region master) – via the WAN
2) Writing on the Site 2 master - local (LAN)
3) Reading the source (Site 2 master) - local
4) Writing on the local depot - local
In the following graphic, the Distribution Service is shown on
a single computer to clarify the individual steps. Normally you install
the Distribution Service responsible for Site 2 on the Management
Point located in site 2.
If the Distribution Service responsible for site is in Site 1,
it would have to execute all four distribution steps via the slow connection.