YADE Parameter Reference - Profile

A profile is identified by this attribute value that is specified when invoking YADE. As multiple profiles can be stored in a YADE configuration this value is a unique identifier for the settings that are grouped in a profile.

• Schema: Operation, Operation

A file transfer Operation represents activities such as Copy, Move, Remove, GetList etc. that are specified with a transfer Profile.

• Schema: Client, Client

A file transfer includes roles that can be specified by use of the Client elements. The Client information is not required to perform the file transfer but is used for the transfer history.

• SupplyingClient: the client that is responsible for providing the source files
• ReceivingClient: the client that is responsible for accepting the target files

• Schema: JobScheduler, JobScheduler

YADE can be configured for use with JobScheduler. In this case the YADE JITL Job is used. Parameters can be specified to control the workflow of files processed by YADE.

• Schema: Logging, Logging

YADE uses the log4j framework for logging and makes use of the following loggers:

• rootLogger
• reportLogger

These loggers are configured by a log4j configuration file which determines that the

• rootLogger logs to stdout.
• reportLogger optionally logs to a file.

If the log4j configuration file is not found then a log4j base configuration is used which logs to stdout.

• Schema: NotificationTriggers, NotificationTriggers

E-mail can be specified to be sent in case of events that are configured with this element:

• OnSuccess: in case of successful execution of a file tansfer operation.
• OnError: in case of failed execution of a file tansfer operation.
• OnEmptyFiles: in case of exclusively empty files being detected during the execution of a file tansfer operation.

• Schema: Notifications, Notifications

Notifications can be sent by e-mail or by use of the YADE Background Service. The Notifications element allows included elements to reference NotificationFragments such as a MailServerFragment or a BackgroundServiceFragment.

Notifications can be added either at Profile level or at General level:

• Profile: a specific mail server or Background Service is used for notifications of file transfers from this profile.
• General: one mail server or Background Service is used for notifications from all Profiles.

• Schema: Assertions, Assertions

This element does not specify parameters for file transfers but assertions regarding the performance of file transfers. Assertions specify performance indicators that can be checked by a test suite.

• Schema: Documentation, Documentation

A Documentation can be added to a file transfer configuration that includes a description and a number of links.

The Documentation can be added either at Profile level or at General level:

• Profile: a specific documentation is used for file transfers from this profile.
• General: a general documentation is used for file transfers from all Profiles.

• Schema: SystemPropertyFiles
• Mapping:
  • system_property_files
• Release:
  • YADE-400 Availability starting with 1.11.

YADE allows to specify Java property files at a global level and individually per transfer fragment.

• Properties from Java property files are applied as system properties by YADE.
• Java property files are processed in the specified sequence. Properties that have previously been set will be overwritten by subsquent Java property files.
• First the global Java property files are applied, next the Java property files specified for a transfer fragment are applied.