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.1
Troubleshooting
Application framework

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
Learn about different Teracloud Streams tools and features to write, compile, run, and test streams applications.
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.
- Metrics
  Teracloud® Streams provides metrics to help evaluate the health of Teracloud Streams services, to aid in diagnosing performance issues, and to analyze throughput of requests. You can use the streamtool checkinstancemetrics, streamtool checkdomainmetrics, streamtool getdomainmetrics, and streamtool checkresourcemetrics commands to view the metrics data.
- 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.
- SPL Compiler
  The SPL compiler is an incremental compiler that generates artifacts needed to run your stream application. These artifacts include, for example, C++ code for several entities in your SPL program and an application bundle file.
- 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.

Application framework

Common problems and resolutions related to the TEDA application framework are explained.

The ITE application does not process any data but is healthy: It is normal behavior to pause the file processing if the Lookup Manager application is not initialized or updating the enrichment data in shared memory, or if the ITE application is running internal maintenance tasks.

Verifying the lookup data: The Lookup Repository Reader is a tool that you can use to verify the data written by the Lookup Manager.

Application setup does not create application structures: If your application structures are not created, set either the -b or -f parameters when you call the setup command.

Job submission fails

Lookup repository initialization fails: If the lookup repository does not initialize, check the global.applicationControlDirectory parameter in the config/config.cfg file, and then start the jobs again with the correct parameter values.

The submission of the Lookup Manager application leads to out-of-memory in new streams domain or streams instance: The new toolkit version 2.0.0 brings shared memory segment names in the Lookup Manager application that are unique concerning the user name and the absolute path to the control folder.

Lookup Manager is not reading shared memory segments: If the Lookup Manager is not reading shared memory segments, there are several situations that might have caused this error and that can be resolved to eliminate it.

Application control logic freezes in START or STOP state: If the application control logic freezes in START or STOP state because of failed ITE jobs, you can force a restart by writing the forced-restart string and a comma-separated list of the active ITE jobs to the action control file.

The context checkpointing files are missing after housekeeping with partitioned Bloom Filter: In general, the partitioned Bloom Filter operator evicts the too old data in the partitions automatically.

The ITE application doesn't archive a reprocessed file in the archive folder: If you try to process a file again or a file that has the same content as one of the processed files, then the ITE application doesn't detects duplicates.