Date: Tue, 19 Mar 2024 10:56:19 +0000 (UTC)
Message-ID: <821517201.19575.1710845779370@change.sos-berlin.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_19574_1875820595.1710845779370"
------=_Part_19574_1875820595.1710845779370
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Introduction
YADE records the file transfer history for all transfers and, if require=
d, stores this information in a central file transfer history in a database=
. The file transfer history provides detailed information about each file t=
ransfer such as point in time, duration, individual files, source & tar=
get of a transfer and execution result. The file transfer history can be re=
ad using JOC.
The transfer history shows detailed information
- when a file transfer has been performed:
- If multiple transfers for the same files have been executed, e.g. due t=
o transfer errors, then such transfers are grouped for better visibility.=
li>
- what files have been transferred:
- If file groups have been transferred, e.g. by use of wildcard filters, =
then the transfer history shows each file name.
- If files have been renamed between source system and target system then=
the transfer history the original file name and the resulting file name.=
li>
- where files have been transferred from and to:
- The source system and target system of a transfer is resolved to show h=
ost names and IP addresses.
- Should jump hosts have been used then the same applies information is p=
rovided for servers in the DMZ.
- about the execution result:
- If a file transfer was successful for all files or for some files out o=
f a group of files.
The transfer history is created by the YADE Client JITL Job
- The JOC History Viewer is used to present the transfer history:
- It allows easy access to the transfer history by search functions and f=
ilters.
- It displays all details of the transfer history.
- It can be used for ongoing monitoring of the transfer history as transf=
er information is constantly being added.
------=_Part_19574_1875820595.1710845779370--