Share via

3.2.3 Initialization

  • Article

A DSS MUST have some implementation-specific way of learning the FQDN or IP address and the TCP/IP port of the USS that it is configured to synchronize from (for example, manual configuration or specified as part of the Start Synchronization trigger). No other actions are taken until an event is triggered by a higher layer, as described below.<63>

  1. Start Synchronization trigger: The DSS MUST provide at least one way to trigger the start of the synchronization process that uses this protocol. The DSS implementation MAY use timer events to trigger the protocol initiation.<64>

  2. On receipt of the Start Synchronization trigger, the DSS MUST start the Authorization step given in section 3.2.4.1.

  3. Cancel Synchronization trigger: The DSS implementation MAY provide a higher layer with the capability to cancel a synchronization that is in progress. This protocol does not define when such a Cancel request is honored by the DSS and how to effect the cancellation. If the steps and message sequencing given in section 3.2.4 are followed, the protocol is designed to ensure that the DSS data store integrity is maintained after every step in the synchronization until processing is completed at the DSS.<65>

  4. Start Reporting Data Synchronization trigger: The DSS MAY provide an additional way to trigger the start of the reporting process that uses this protocol but skips the Deployments Synchronization and Content Synchronization steps.<66>

A DSS MUST have an implementation-specific way of learning its FQDN. It MUST also have an implementation-specific way of creating a GUID to identify itself.