Specifying Protocol Settings for Distribution

If you specify HTTP as transfer protocol for a new depot, please make sure to specify HTTP for the distribution and for the respective distribution service. By default, the parent container inherits the protocols and the respective distributions service.

Using a single protocol on the depot

If the depot supports only one protocol, this protocol will be automatically used for distribution. This standard configuration is not efficient in some cases and may be customized manually.

Using multiple protocols on the depot

Install a local Management Point together with a distribution service in a site in which the distribution service will execute both the Work/Install distribution on the Master-Depot and the distribution to the local depots within the site.

How to configure the infrastructure:

After installing the Management Point, please specify the new distribution service as associated distribution service in the site and pass this setting on to all child depots:

  1. Select the Infrastructure view.
  2. Unlock the configuration database.
  3. Select the site in the Navigation window and then open the Configuration tab in the Detail window.
  4. Select the section Distribution > Associated Distribution Service in the configuration table.
  5. Enter the new distribution service and pass on the information to all child objects.

The second step is to configure the protocols used for distribution if the new depot is to support both SMB and HTTP.

  1. Select the site's Master Depot in the Navigation window and then open the Configuration tab in the Detail window.
  2. Select the section Distribution > Protocols used to access the depots [source depot, target depot].

Here you can specify which protocol will be used for Read access to the source and for Write access to the target - provided that the respective depots support the protocols.

  1. Select the source depot and the target depot. Please observe the rules listed below!
  2. Store the settings by closing the configuration table.

Important rules for setting up the target and source depots

If you are using both protocols (SMB and HTTP), please observe the following rules to guarantee a successful distribution between the source and target depot:

Rule 1: If HTTP is used for Write access to the depot, HTTP must also be used for Read access. SMB is unable to evaluate the time stamps written with HTTP correctly. Thus, data cannot be correctly synchronized between the source and target depot.

Rule 2: Do not use HTTP to write to the target depot's Install directory (be it a Site Master or local depot).

We recommend Rule 2 because it is currently impossible to unpack zip files directly via HTTP; the _NI5.zip files are unpacked individually in a local directory and then copied to the Install directory. Distribution may therefore take a long time.  

If HTTP is used as Read protocol, the _NI5.zip files must be copied to the distribution service's local directory anyhow and must be unzipped there as well. You can specify the local directory on the Management Point. Select the Management Point and open the section Distribution > Temporary directory for compressing and uncompressing packages in the Management Point's configuration to enter the local directory.

Overview and evaluation of the protocols between the example depots:

Central Depot

Master Depot Site 1

Local Depot Site 1

Connection

Evaluation

Read

Write

Read

Write

SMB

SMB

SMB

SMB

only SMB

possible

HTTP

HTTP

HTTP

HTTP

only HTTP

possible

HTTP

HTTP

HTTP

SMB

mixed mode

possible

HTTP

HTTP

SMB

HTTP

mixed mode

not valid *

HTTP

SMB

HTTP

HTTP

mixed mode

not recommended **

SMB

HTTP

HTTP

HTTP

mixed mode

not recommended **

SMB

SMB

SMB

HTTP

mixed mode

not recommended **

SMB

SMB

HTTP

SMB

mixed mode

possible

SMB

HTTP

SMB

SMB

mixed mode

not valid *

HTTP

SMB

SMB

SMB

mixed mode

possible

SMB

SMB

HTTP

HTTP

mixed mode

not recommended **

HTTP

HTTP

SMB

SMB

mixed mode

not valid *

SMB

HTTP

HTTP

SMB

mixed mode

possible

HTTP

SMB

SMB

HTTP

mixed mode

not recommended **

SMB

HTTP

SMB

HTTP

mixed mode

not valid *

* not valid due to Rule 1

** not recommended due to Rule 2