Home
Developing
Learn about different Teracloud Streams tools and features to write, compile, run, and test streams applications.
Developing native functions
Extend SPL's computational capabilities by creating native functions written in C++ or Java.
Native function artifacts
Applications and toolkits can contain C++ native functions and Java™ native functions. Artifacts of native functions are located in the native.function directory.

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.
- Development concepts
  Development of stream applications consists of several components such as operators, streams, tuples, Streams Processing Language, toolkits, and more.
- Developing stream applications
  Try out tutorials and explore details about stream application development, SPL features, and best practices.
- Developing native functions
  Extend SPL's computational capabilities by creating native functions written in C++ or Java.
  - Native function artifacts
    Applications and toolkits can contain C++ native functions and Java™ native functions. Artifacts of native functions are located in the native.function directory.
  - Developing C++ native functions
    Native functions can be invoked from SPL by using the same syntax that is used for an SPL function.
  - Developing Java™ native functions
    You create Java™ native functions by adding Java annotations that describe Java public static methods as native functions to the SPL compiler.
- Developing custom operators
  Create custom operators if shipped toolkits do not provide the necessary logic or behavior needed for your stream applications.
- Developing custom toolkits
  Bundle and reuse custom functions and operators across several stream applications by creating custom toolkits.
- Working with files
  Applications and operators can read and write to files in several ways. If relative paths are used, the data directory is used as the root of relative paths. To enable logic to access the runtime application or toolkit directory hierarchies, language-specific functions can be used.
- Enabling Streams data exchange
  Teracloud® Streams provides a data exchange REST API for inserting and retrieving tuples within a job to easily integrate with other data services and external applications. Stream applications can enable the data exchange feature by using one or more Endpoint operators.
- Debugging stream applications
  Debug stream applications using the interactive, command line-based Streams Debugger (sdb).
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.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Native function artifacts

Applications and toolkits can contain C++ native functions and Java™ native functions. Artifacts of native functions are located in the native.function directory.

C++ native functions are created within an application or a toolkit by using function.xml files that are in the native.function directory. The files include the declarations of functions and their dependencies.

Java™ native functions are created by using annotations in the Java™ source code, in which case the corresponding native.function directories and javaFunction.xml files are automatically generated when the application or toolkit is built.

Locate the native.function directory under a namespace directory, similar to the primitive and composite operators. For instance, if a developer wants to place functions under the my.namespace namespace, a possible directory that might contain native.function is my/namespace.