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
Customization and configuration recipes for the ITE application
Supporting several input formats

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.

Supporting several input formats

If you process data from different source systems, which typically means that you have different data formats, you must configure and customize the ITE application, so it knows how to handle the different formats. You provide for each data format a file reader composite operator. All file reader composite operators produce the same output format.

Before you begin

Prepare for each input format the file reader composite operator as described in “Preparing for an input format”.

Procedure

File type determination
Determine the file type by either evaluating the file name, the file path, or the file content.
1. Set the ite.ingest.customFileTypeValidator parameter to on, which activates the <namespace>.fileingestion.custom::FileTypeValidator composite operator.
2. Adapt the <namespace>.fileingestion.custom::FileTypeValidator composite operator. For further information about the optional and mandatory modifications, see the composite operator description in Customizing the ITE application and the instructions in the composite operator code.
Routing

Add for each input format a value to the ite.ingest.reader.parserList parameter. A value consists of an ID and a composite operator name that are separated with a pipe character (|). The ID must fit to the ID that you implemented in the <namespace>.fileingestion.custom::FileTypeValidator composite operator for this format. The composite operator is the name of the file reader composite operator that reads and parses files of this format.