Skip to end of metadata
Go to start of metadata

Steps 1 and 3 of the process defined in the preceding Subclause shall be executed in accordance with the ECHO standard as implemented between the relevant parties. In case where the volume of a catalogue transfer would endanger normal operations, the process described in this Subclause as depicted in Figure 2 shall be used.

Step 2 of the process defined in the preceding Subclause shall be executed in accordance with the process described in this Subclause as depicted in Figure 2.

Step 4 of the process defined in the preceding Subclause shall be executed in accordance with the ECHO standard as implemented between the relevant parties. In case where the volume of a catalogue transfer would endanger normal operations or where message exchanges  have not yet been established, the process described in this Subclause as depicted in Figure 2 shall be used.

Figure 2: Using FTP to exchange Messages

The trigger to indicate that a Batch is complete is a ManifestMessage as defined in Clause 8.3 of this standard. In exceptional circumstances, such as the support of human intervention, it is permissible to use a zero-byte semaphore file to indicate the upload is complete. This semaphore has to be used instead of an XML manifest formatted in accordance with Clause 8.3. The use of such a semaphore file may trigger a flag on the recipient’s side, indicating the manual nature of the override.

The FtpAcknowledgementMessage is defined in the latest version of DDEX-AMEP.

The structure and file naming conventions are defined in the remainder of this Clause.

  • No labels
Write a comment…