Some additional information that may be useful when doing a Remote ETL Engine installation using the silent installation workflow:
Do not use the /[TSCO Installation Image]/BCO/Disk1/silentInstallTemplates/BCO_ADDITIONAL_SERVER_REMOTE_EE.txt as the template for installing the Remote ETL Engine for a TrueSight Capacity Optimization (TSCO) deployment. That file is for a BHCO 20.02 SaaS Remote ETL Engine deployment, no TSCO 20.02 on-prem.
The URL_HOST specified should be the TSCO Application Server (AS) where the Datahub is running. The TSCO Remote ETL Engine installer will use this URL to access the https:///as_hostname.domain.com:8443/dh-services/controller/register service which resides on the TSCO Datahub AS, not a separate TSCO Web AS. In most, but not all, environments the TSCO Datahub is deployed on the Primary Scheduler AS but it is possible the Datahub could have been deployed separately from the Primary Scheduler AS.
As noted in the video, the IS_REMOTE_COMPONENT property of the BCO_ADDITIONAL_SERVER_EE.txt silent installation options file controls whether the ETL Engine will be deployed as a standard ETL Engine (EE) or a Remote ETL Engine (REE). Ensure that the IS_REMOTE_COMPONENT is set to 'true' for a REE installation.
Although the Oracle Client is not required for normal operation of a running Remote ETL Engine the installer will validate the Oracle Client installation image so a valid Oracle Client, configured per the documented requirements for a TSCO EE, should be deployed to the TSCO REE server.