Using BagDropService and DCS direct connection
Configuration and regular status checks while the SBD is idle is described here: Configuration and status checking.
It is possible for the SBD to have direct communication with a DCS, including through a broker, and only use the BagDropService for local configuration/information and transaction logging (BagNotify). The sequence diagram below shows the use of BagDropService in this setting.
The SBD is responsible for managing all aspects of the DCS communication.
NB! All calls to BagDropService related to one bag delivery process must use the same TransactionId. See also Use of TransactionId.
|
|
