This documentation supports releases of BMC Helix Continuous Optimization up to December 31, 2021. To view the latest version, select the version from the Product version menu.

Setting file access for parsers

In the File location tab you can select the file access method; different parameters might be requested depending on the selected protocol.

For more information, see the following sections:

Local directory

ETL configuration example - File location tab (Local directory option)
File location - local directory.jpg

  • Directory: Specify the complete directory path.
  • File list pattern: Specify file name pattern to be parsed, the pattern is defined by means of a regular expression; the default value allows the ETL to recognize all files except those with the .done suffix.
  • Recurse into subdirs?: Select yes if you want the ETL to navigate the repository subdirectories and parse files contained in subdirectories.
  • After parse operation: Specify the actions that should be performed after parsing a file; you can choose one of the following actions:
    • Do nothing: Do not perform any actions; if already parsed files are not removed after execution of the ETL, they will be parsed again in the next ETL run.

    • Append suffix to parsed files: Mark processed files as already parsed by appending a suffix to their filenames, so that they will not be parsed again during the next execution of the ETL. The suffix is defined by the Parsed file suffix parameter; the default suffix is done.

      Note

      The selected suffix should not match the pattern defined in the File list pattern parameter.

    • Archive parsed file in directory: Move parsed files in a subfolder defined by the Archive directory parameter.

      Note

      If the Recourse into subdirs? option is enabled, the selected subfolder should not match the pattern defined in the File list pattern parameter.

Windows share

Note

The Windows share option uses sudo mount for mounting the file system to the application server. Only sudo is supported for an su type command alternative, and BMC Helix Continuous Optimization does not support sesu. Also note that the cpit id must be able to sudo to get root privileges, as mount requires root access.

ETL configuration example - File location tab (Windows share option)
File location - Windows share.jpg

In addition to the configuration options defined for Local directory, Windows share configuration requires a valid account on the remote directory. If authentication is not required to access the remote directory, leave the Username and Password parameters empty.

Note

To apply the rules defined by the Append suffix to parsed file and Archive parsed file in directory parameters, a read/write account is required.

FTP

ETL configuration example - File location tab (FTP option)
File location - FTP.jpg

In addition to the configuration options defined for Windows share, FTP configuration requires the Remote host parameter, which provides the remote host name or IP.

SCP

ETL configuration example - File location tab (SCP option)
File location - SCP option.jpg

In addition to the configuration options defined for Windows share, SCP configuration lets you specify the files to be copied using wildcards, using the parameter Files to copy (with wildcards).

SFTP

Configuration is similar to the SCPprotocol.

ETL configuration example - File location tab (SFTP option)

File location - SFTP.jpg

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*