Home
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Toolkits
A toolkit is a set of SPL artifacts, which are organized into a package. Toolkits make SPL or native functions and primitive or composite operators reusable across different applications.
Toolkits
Toolkit com.teracloud.streams.teda 4.0.0
Developing applications
Configuring Solutions
Configuring ITE Applications
First steps
Configuring output directories

Welcome
Learn about the core capabilities of Teracloud® Streams, its architecture, and key concepts.
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
- APIs
  Application programming interfaces (APIs) provide functions that simplify applications development.
- Job configuration overlays
  You can specify or change configuration parameters when you use the submitjob or updateoperators operations. The settings control submission constraints, host constraints and locations, and operator status. Parameters are captured and updated in the configuration JSON file. When you change the values in the job configuration overlay file, the changes override any previously set values.
- Commands
  Teracloud® Streams provides a number of commands you use to perform tasks.
- Operator model
  An operator model is an XML document that describes the basic properties of a primitive operator.
- Streams Processing Language (SPL)
  Streams Processing Language (SPL) is a distributed data flow composition language that is used in Teracloud® Streams. SPL has primitive types, program structures, and definitions that are tailored for streaming data.
- Toolkits
  A toolkit is a set of SPL artifacts, which are organized into a package. Toolkits make SPL or native functions and primitive or composite operators reusable across different applications.
  - Specialized toolkit requirements and restrictions
    Several of the specialized toolkits require RPMs that are not required by the Teracloud® Streams product. There are also toolkit restrictions on some platforms.
  - Toolkits
- SPLDOC markup
  You can use SPLDOC markup in the descriptions associated with the SPL artifacts in a toolkit. The spl-make-doc command generates HTML documentation from the marked up artifacts.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Configuring output directories

If you must output your data to directories different from the defined default directories, you assign the application the wanted directory paths.

About this task

Set the output directory paths by using the provided parameters.

Procedure

To define a non-default directory to receive checkpointing data, find the ite.checkpointing.directory parameter description in the <PathToYourApplication>/config/config.cfg file
Set the parameter to the wanted path, for example ite.checkpointing.directory=/home/streamsadmin/outputData/checkpointing
To define a non-default base directory for your production data output, find the ite.storage.directory.outputs parameter description in the <PathToYourApplication>/config/config.cfg file
Set the parameter to the wanted path, for example ite.storage.directory.outputs=/home/streamsadmin/outputData/productionData
To define a non-default directory to receive statistics data, find the ite.storage.directory.statistics parameter description in the <PathToYourApplication>/config/config.cfg file
Set the parameter to the wanted path, for example ite.storage.directory.statistics=/home/streamsadmin/outputData/statistics
By default all output files are written directly into these directories. If you prefer to sort your output data into subdirectories that depend on the input file or the date, you configure subdirectories with the ite.storage.outputDirectoryStructure parameter in the <PathToYourApplication>/config/config.cfg file
To create subdirectories that depend on the input file, set the parameter as follows: ite.storage.outputDirectoryStructure=perFile, alternatively, to create subdirectories that depend on the date set the parameter as follows: ite.storage.outputDirectoryStructure=perDay
By default all input files are archived into one directory. To change this behavior, find the ite.archive.inputFilesIntoDateDirectory parameter description in the file <PathToYourApplication>/config/config.cfg
To archive the processed input files of a day into a date subdirectory, set the parameter as follows: ite.archive.inputFilesIntoDateDirectory=on