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 Lookup Manager Applications
Advanced topics
Manually deleting output files from Lookup Manager

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.

Manually deleting output files from Lookup Manager

When testing your application, you need to manually delete the files output by the application to give it a fresh restart.

About this task

Determine the paths of the application’s directories from the values in the <PathToYourApplication>/config/config.cfg file. Then, delete the contents in the directories or the directories themselves.

Procedure

Find the directory that is configured with lm.commandsDirectory. You find your used command files in its archive subdirectory. To reuse a command file, move it back into the directory that is configured with lm.commandsDirectory
Find the directory that is configured with lm.file.directory. You find your used enrichment data files in its archive subdirectory. To reuse the enrichment data files, move them back into the directory that is configured with lm.file.directory. Pay attention to the required name scheme.
Remove the contents in the directory that is configured with lm.statisticsDirectory

When you restart your application now, it does not know that it ran before. Thus you can use the same set of input data again to do your testing.

CAUTION: Input data files for an ITE application are moved to the configured archive directory of the application. Additionally, the Lookup Manager application moves input data files to its archive directory, too, but adds a prefix to the file names with a time stamp string. Thus these files do not conform to the required input file naming schema any more. When you move input data from the Lookup Manager’s archive directory to the input directory for another test run, you must remember to rename the files by removing the time stamp prefix.