Running the Batch Deployment Tool - trillium_discovery - trillium_quality - Latest

Trillium DQ Repository Administrator Guide

Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Version
Latest
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium DQ Repository Administrator Guide
Copyright
2024
First publish date
2008
Last updated
2024-10-18
Published on
2024-10-18T15:31:00.219841

The Batch Deployment Tool (BDT) creates batch scripts from exported project definitions.

Note: The BDT is an optional installation component. If the BDT is not installed you cannot create batch scripts.

You can create a batch script directly from the Control Center, or you can export a project definition to a machine on which the BDT has been installed and run the BDT from the command line to create the batch script. This allows you to easily move the project to a different system before generating the script files, which ensures that the paths used in the project files are correct for the target system.

Note: If you create a batch script and subsequently move the project files to a different machine, you will have to modify paths in the script files. It is advisable to move the project definition to the destination system before running the BDT.

The BDT executable, bdt.exe, is located in your installation path in the \BDT\...\bin directory and takes arguments described here.

Table 1. BDT Command Arguments

Argument

Description

-project

Name of the project definition file. The default is project.prj. The path will default to the current working directory.

-proj_compress value

Source directory for creating the project definition zip file.

-proj_expand value

Project definition zip file to be unzipped.

-use_pipes

If this argument is specified, the generated script will pipe the data through the project’s processes.

-endian_extn

The extension (.len or .ben) to be used for any platform-specific files. The default for Windows and Linux platforms is .len; the default for UNIX is .ben.

-input_delimiter

If the job will use delimited input files, use this argument to specify the delimiter that will be used. Supported delimiters are Comma, Tab, Space, Semicolon, and Pipe (for example, -input_delimiter Tab). Be sure to type the delimiter with an initial cap.

-input_delimiter_encoding

If the job will use delimited input files, use this argument to specify the encoding of the delimiter that will be used. The default is NOTRANS.

-use_quotes

Include this argument if the delimited input files will have values surrounded by quotes.

-input_headers

Include this argument if the delimited input files will have header records.

-output_delimiter

If you require delimited output files, use this argument to specify the delimiter to be used. Supported delimiters are Comma, Tab, Space, Semicolon, and Pipe.

Note: Be sure to type the delimiter type with an initial cap.

-output_delimiter_encoding

If you require delimited output files, use this argument to specify the encoding of the delimiter to be used. The default is NOTRANS.

-use_output_quotes

Include this argument if the delimited output files will have values surrounded by quotes.

-use_headers

Include this argument if you want your delimited output files to have header records.

Values: 0 = none (default), 1 = header record if file contains data, 2 = header

-with_data

If the project definition includes start data, include this argument if you want the start data files to be included in the batch export. Do not use this argument if you want to work with delimited input files.

-target_platform

The target platform (Windows or UNIX) where the job will be run. The default is the same as the host platform. The value must be entirely in lower case.

-target_dir

Name of the directory where the batch export files are to be created. The default is ./batch, relative to the directory containing the project.prj. Enclose the path in quotes if it includes spaces.

-no_proj_dir

Do not create project directory.

-tsq_language

Language in which messages are to be output. Values are:

  • es (Spanish)
  • ja (Japanese)
  • pt_BR (Portuguese, Brazil)
  • de ( German)
  • fr (French)
  • zh_TW (Chinese, Taiwan)
  • zh_CN (Chinese, Mainland)
  • it ( Italian)
  • ko (Korean)
  • en (English, the default)

-tsq_report_encoding

Encoding to be used for the output reports. The value must be specified in uppercase. The default is UTF8.

-ts_quality

Name of the path where Trillium Quality has been installed. The default is as specified by the TS_QUALITY environment variable.

-help

Display help for BDT command.

-?

Display help for BDT command.

-realtime

Create a project structure that can be used to create a real-time project.

-no_data_compress

Generate uncompressed data in individual output files.