In case an alternative connection is used this should be sent to the Background Service and is written into the history file

Current Situation
We assume that an alternative connection for source and/or target is specified in the JADE profile and the "normal" connection to the source and/or target failed then the "normal" connection is nevertheless sent to the Background Service and written into the history file.

source_host = mySourceHost
source_port = 22
source_protocol = sftp
source_ssh_auth_method = password
source_password = xyz
source_user = test
alternative_source_host = myAlternativeSourceHost
alternative_source_port = 21
alternative_source_protocol = ftp
alternative_source_passive_mode = true
alternative_source_password = xyz
alternative_source_user = test

Desired Behavior
If the "normal" connection failed and an alternative connection is used then the alternative connection should be sent to the Background Service and written into the history file.
This relates to the fields for source_host, source_host_ip, source_user, target_host, target_host_ip and target_user. The order which is sent to the Background Service has the same parameter and the history file has the same fields but the alternative data as values.