Running a Batch Project - trillium_discovery - trillium_quality - 17.2

Trillium Control Center
Product type
Software
Portfolio
Verify
Product family
Trillium
Product
Trillium > Trillium Discovery
Trillium > Trillium Quality
Version
17.2
Language
English
Product name
Trillium Quality and Discovery
Title
Trillium Control Center
First publish date
2008
Last updated
2024-07-01
Published on
2024-07-01T08:56:48.630530

When you create a batch script, either from the Control Center or using the Batch Deployment Tool command line interface, you must perform the following steps before running the script:

Copy the batch project to the server. Replace the input entity name if necessary.Check and update the configuration file.Check and update the script file. Check and update the environment variables.
Guidelines:
  • If you create a batch script and then move the exported files to a different environment, you must modify some of the settings in the batch files to reflect the new path.
  • If you move project definition files before using the Batch Deployment Tool to create the batch script, you do not have to modify the paths.
  • If you export a project that uses the Global Postal Matcher and you want to run it on a different server, you need to edit the SERVER setting. This setting must be set to the name of the server where the Global Postal Matcher will run. This applies to both batch exports and project definition exports.
  • If your batch project includes a Database Read/Write process, uses an ODBC data source that uses an ODBC driver (database adapter) and the Vendor-Supplied ODBC Adapter, and you run the exported batch script in a Linux environment (Trillium server installed on a Linux system), the batch script will fail. This scenario is supported only when the Trillium server is installed on a Windows system.

Input Entity Names

When you export a project for batch implementation from the Control Center, the input entity name after the export varies depending on your entity type.

  • Flat files. When the input entity is a flat file, the export will retain the original entity name.
  • Delimited files. When the input entity is a delimited file, the export will use the default entity name. The default entity name is the original entity name but the Control Center changes the file extension to ".dat". For example, customer_input.csv becomes customer_input.dat. Therefore you need to open the settings file for the first process and replace this name. Typically this is changed to the entity name that is used to replace the original entity.
Note: When pipes are used, all interim input/output entities use "stdin" and "stdout".

To change the input entity name for a batch project

  1. Locate the first process’s settings file. It is included in the settings folder in the batch project. For example, tranfrmr_p1.stx.
  2. Open the settings file in your text editor and locate the DATA_FILE_NAME argument in the INPUT_SETTINGS parameter section.
  3. Change it to your input entity name and its path.

    Example

    <DATA_FILE_NAME>E:\input\customer_input.csv</DATA_FILE_NAME>

Batch Script

To run a batch script

  1. Copy the batch project you exported to the server where TS Quality is installed. The server contains all of the batch binary files and the batch job must be run on the server.
  2. Check and update the configuration file. The configuration file (Config64.tbl) will be automatically created in the settings folder in the batch project when you run the script for the first time. This file will be used by the batch execution scripts. Check the paths to make sure that they reflect their environment.
    Note: If you change the values in the initialization file (EDQ.ini) and you want to apply the new values to your previously run project, you need to run the trilconfig64 program to update the configuration file. See Updating the Configuration File for details.
  3. Check and update the script file.

    The script file is located in the scripts folder in the batch project. Update the following settings in the file based on your needs:

    • The TS_PROJECT variable must be adjusted to point to the folder containing the project files on the server.
    • The maximum size of debug file is 2 GB by default. You can modify this limit by adding the TSQ_MAX_DEBUG setting in the batch script. The unit is in bytes. For example, if you want to limit the debug file to a maximum of 1000 bytes, set the variable as follows: Example: Set TSQ_MAX_DEBUG=1000
    • Set TSQ_DATEVAL to "Y" if you want to validate date format attributes (for example, ASCII JULIAN) in the schema file. By default, all date format attributes are set not to be validated (TSQ_DATEVAL = "N"). Example: Set TSQ_DATEVAL="Y"
    • If you are using Trillium-authenticated security and you are exporting a project that includes profiling processes, you must add your password to the MTB_PASSWORD setting in the script (for example, MTB_PASSWORD=mypassword). Otherwise the export will not successfully authenticate. If you are using Windows authentication or exporting a project with no profiling processes, you do not have to add your password. For more information about security authentication, see Security.
    • (Optional for language packs) Set TSQ_LANGUAGE if you want reports and logs to be created in a language other than English. The valid settings 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)

  4. Check and update the environment variables.

    Set TS_QUALITY to the Software folder of the Quality installation.

    Example: Set TS_QUALITY=C:/Program Files/Trillium Software/MBSW/17/tsq/Software

  5. Run the script to run the batch project.
Related tasks