Installing the Remote ETL Engine

Use the information in this topic to install the Remote ETL Engine silently. Use the sample response file that is included in the Remote ETL Engine installation image to install the Remote ETL Engine silently. Modify the default settings in the sample file instead of creating a new file. The Remote ETL Engine and the Gateway Server must be installed on the same computer. 

To install the Remote ETL Engine

  1. In BMC Helix Portal, click the BMC Helix Continuous Optimization tile.
  2. In BMC Helix Continuous Optimization, navigate to Administration > System > Downloads.

  3. In the Remote ETL Installer tile, click Download.

  4. Copy the installation files to the computer where you want to install the Remote ETL Engine.

  5. Extract the downloaded files to the temporary directory, making sure that the temporary directory is different from the installation directory to avoid any file sharing conflict.

  6. Create an access key in BMC Helix Portal and assign the Capacity ETL Client role to it. For information about how to create the key, see Setting up access keys for programmatic access Open link

  7. To copy the key details (access key, secret key, and tenant ID) that are generated, click Copy all key details.

    The keys are copied in the following format: key details:<access key>::<secret key>,tenant id: <tenant ID>

    You will need to specify these keys while configuring the authorization token in the options file.

    Can I copy the keys later?

    No. If you do not copy the key details when it is generated or if you lose it, you must generate a new one. The keys are available for copying only when it is generated for the first time. Afterwards, it is saved in an encrypted form using the OpenBSD Bcrypt scheme. This encryption is irreversible. 

  8. At the shell prompt, change to the directory where you extracted the downloaded files and locate the sample response file.
    Example: BHCOtemp/BCO/Disk1/silentInstallTemplates/HO_ADDITIONAL_SERVER_REMOTE_EE.txt.

  9. Edit the HO_ADDITIONAL_SERVER_REMOTE_EE.txt file in a text editor.

  10. In the Authorization token section, paste the tenant ID, access key, and secret key that you have copied in Step 7.

  11. Modify other properties of the file according to your preferences as listed below, and save the file.

    Prefix tags for the silent installation properties:

    • -P: Precedes the directory properties

    • -A: Precedes the application features

    • -J: Precedes the Java properties

    Property nameDescription
    Installation settings

    -P installLocation

    Installation directory path.

    Default value: /opt/bmc/BCO

    Example: -P installLocation=/opt/bmc/BCO

    Helix host details
    -J URL_HOSTFully qualified domain name of BMC Helix Portal.
    Authorization token

    Unique identifier for the tenant.  

    Example: -J TENANT_ID=900025273


    Access key of the user. Copy the access key. 

    Secret key of the user. Copy the secret key. 

    Advanced properties

    To run the installer on the existing installation, choose one of the following modes. You can set only one of these properties to true because the installer can run only in one of these modes at a time:

    • Reconfigure: Use the reconfigure mode to modify certain values that you had provided during installation.
      Default value: false
    • Re-installation: Use the re-installation mode to re-install the ETL Engine. 
      Default value: false

    Use this property when you are migrating from existing Capacity Optimization instance to BMC Helix Continuous Optimization, and want to preserve the particular scheduler assignments, such as scheduled ETL tasks or Optimizer tasks on this Remote ETL Engine.

    Specify the ID of the scheduler that you want to register with this Remote ETL Engine.



    Do not modify these settings


    Retains the default installation type.

    Default value: EXTERNAL_SERVER


    -A <feature name>

    Installs the Remote ETL Engine component.

    Default value: featureCoreETL

    Example: -A featureCoreETL


    Retains the default value.

    Default value: true

    Example: -J IS_REMOTE_COMPONENT=true

    -J URL_PORTRetains the default port number. Default value: 443 Example: -J URL_PORT=443
    -J CUSTOM_CONNECTION_PROTOCOLRetains the default connection protocol. Default value: https

  12. Open a shell prompt and navigate to the directory that contains the installation files. BMC recommends that you install the Remote ETL Engine as a root user. 
    Example: /BCO/Disk1
  13. Launch the silent installer:


    If the path contains spaces, enclose the path and options file name in quotation marks.

    After the installation is complete a confirmation message about a successful installation is displayed.

To install the Remote ETL Engine by using the Proxy server

If you want to install the Remote ETL Engine by using the proxy server, perform the following steps in addition to the steps listed in the To install the Remote ETL Engine section:

  1. Encrypt the password that will be used in the proxy settings by using the utility.
  2. Run one of the following commands to encrypt the password.
    Copy the encrypted password. You will need to specify this password while configuring the proxy server connection in the options file.

    • ./ encrypt -key <access key>
    • ./ -encrypt -envvarname ENV_VAR_WITH_PWD -key <access key>
    • ./ -encrypt -toencode <text to encode> -key <access key>
      ./ -encrypt -toencode pa$$word -key U0262M32JQES27TJLGQFPLGF6PRBFO


  3. Edit the HO_ADDITIONAL_SERVER_REMOTE_EE.txt file in a text editor.

  4. Search for the # Proxy Server Connection section, and remove the '#' character from the properties to uncomment the properties.

    # Proxy Server Connection
    # Please note that password, in case it is required, it has to be encrypted
    # with utility
  5. Modify the properties according to your preferences as listed in the following table:

    Property nameDescription
    Proxy server connection

    Configuration of the proxy server.

    Default value: false 

    Example: -J IS_PROXY_CONFIGURED=true

    -J REE_PROXY_HOSTName of the proxy server host.

    -J REE_PROXY_HOST=<proxy_server_hostname>

    Example: -J


    Port number to communicate with the proxy server.

    Example: -J REE_PROXY_PORT=8090


    If the proxy server requires authentication, set this value to true and specify the proxy server user name and password.

    Default value: false 



    Proxy server user name.

    Example: -J REE_PROXY_USER=proxy_user


    Proxy server password. The password must be encrypted using the utility.

    Example: -J REE_PROXY_SECPWD=proxy_user_password

  6. Paste the proxy server password in the REE_PROXY_SECPWD property that you have copied in Step 2. 
  7. Save the file, navigate to the directory that contains the installation files, and launch the installer. 

(Optional) To test the proxy server connectivity from your Remote ETL Engine, use the curl command: 

Example: curl -x <hostname>:<port> -U<username>:<password> -I

Sample output: HTTP/1.1 200 Connection established

To verify the installation

  1. Log in with the user credentials that you used for installation.
    Example: cpit.

  2. Navigate to the installation directory.
    Example: /opt/bmc/BCO.

  3. Run the command: ./cpit status

  4. Verify that the Scheduler service is running.

To troubleshoot the Remote ETL Engine installation


404 Not found

or 502 Bad gateway

The host name is not correctly configured.

Check the value of the URL_HOST property in the silent installation template (HO_ADDITIONAL_SERVER_REMOTE_EE.txt) file.

The host name must be a fully qualified domain name of BMC Helix Portal in the format:

Make sure that https:// is not included in the host name.

403 ForbiddenThe user does not have rights to call the Supervisor API.

Assign the Capacity ETL client role to the user. For details, see Setting up roles and permissions Open link .

401 UnauthorizedInvalid authentication details or the key has expired.
  • Check the access key and secret key that you have used to configure the user.
  • Confirm that the key is not expired.
  • Make sure that the Capacity ETL Client role is assigned to the user.

Where to go from here

Installing the Gateway Server

Was this page helpful? Yes No Submitting... Thank you