You can export a project into a batch script that can be run on a 64-bit Linux or Windows platform outside of the Control Center. When you export a project to batch, a script will be generated. You can select and run the appropriate script depending on your system environment.
Batch scripts for Linux
- runprojectN.sh
Batch scripts for Windows
- runprojectN.bat
Note:
N is the number of your project.
General Guidelines
- Batch scripts are for 64-bit processing only. For existing 32-bit projects, you must export the project again to recreate a batch script to run in 64-bit.
- Exporting a batch project requires the Batch Deployment Tool (BDT), which is an optional installation component. If the BDT is not installed, the batch script export feature is disabled.
- If your Trillium Quality 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.
- When running the Control Center Client on a different machine than the Server, the TS_QUALITY environment variable is required to set to use the Batch Deployment Tool. Ensure to set the TS_QUALITY user variable to point to any folder with write permissions on the Client, for example, C:\temp\Trillium Software.
- If you export a project that contains processes with multiple outputs (such as Global Data Router) into a batch script, you must run it inside the Control Center prior to the export.
- The batch export process removes all entity IDs from the exported project.
To export a project to a batch script