Home
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Developing toolkits and operators
You can create custom toolkits and operators for your applications.
Developing toolkits
Toolkits contain the building blocks for stream applications. In addition, you can add specialized toolkits or create your own toolkits.
Creating toolkits
A toolkit is created by organizing all the artifacts that are related to operators (composite and primitive) and functions (native or SPL) into namespace directories. Then, running the spl-make-toolkit program to index the toolkit.
Globalizing a toolkit
You can load and format string resources for different locales using the tools that are provided.
The <resources> element
To create a toolkit that loads and formats string resources for different locales, you must add a <resources> element to the toolkit information model file (info.xml).

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.
- Development concepts
  Development of stream applications consists of several components such as operators, streams, tuples, Streams Processing Language, toolkits, and more.
- Writing stream applications
  Teracloud® Streams provides features and functions to help you write your applications to fulfill your business needs.
- Enabling Streams data exchange
  Teracloud® Streams provides a data exchange REST API for inserting and retrieving Streams job data. You can add one or more endpoint operators to your Streams application to enable Streams data exchange. Providing a standard REST interface for Streams data exchange eases the integration of Streams data with other data services and externally hosted applications.
- Compiling stream applications
  The Streams Processing Language (SPL) Compiler is called sc and is included with the Teracloud® Streams installation package. You compile SPL to create files to run on your Teracloud Streams instance.
- Performance improvements for stream applications
  You can improve the processing of your stream application by following these guidelines and tips.
- Debugging stream applications
  The Streams Processing Language (SPL) Streams Debugger (sdb) provides a command line-based interactive debugger for debugging stream applications.
- Developing toolkits and operators
  You can create custom toolkits and operators for your applications.
  - Developing toolkits
    Toolkits contain the building blocks for stream applications. In addition, you can add specialized toolkits or create your own toolkits.
    - Application bundle files
      An application bundle file is a single, relocatable file that contains all the artifacts that are needed to run your application. You submit a application bundle file to run on an instance.
    - Toolkit structure
      A toolkit is organized as a directory in the file system and contains two kinds of artifacts, which are authored and generated. A toolkit information model file (info.xml) contains information about the toolkit, including its name.
    - Creating toolkits
      A toolkit is created by organizing all the artifacts that are related to operators (composite and primitive) and functions (native or SPL) into namespace directories. Then, running the spl-make-toolkit program to index the toolkit.
      - Toolkit information model file
        The toolkit information model is an optional file called info.xml. It contains the name, description, and version information about the toolkit. It also contains any dependencies that might exist on other toolkits, in the form of a list of toolkit names and versions or range of versions required.
      - Creating toolkit artifacts for use on multiple platforms
        Teracloud® Streams supports a varied set of hardware architectures and Linux™ distributions such as Red Hat Enterprise Linux (RHEL). If you plan to deploy a toolkit on multiple platforms, you can create toolkit artifacts that simplify the management of the various C++ libraries. These examples show how to maintain a common infrastructure that works across multiple Linux distributions and hardware platforms.
      - Mixed-mode SPL/Perl sources
        You often must parameterize application composition when you create parallel subgraphs, conditional segments, and variable length pipelines. The SPL compiler provides a Perl-based preprocessor for this purpose. SPL files that are authored with the preprocessor directives are named with the .splmm extension and are called mixed-mode SPL programs.
      - Globalizing a toolkit
        You can load and format string resources for different locales using the tools that are provided.
        The <resources> element
        To create a toolkit that loads and formats string resources for different locales, you must add a <resources> element to the toolkit information model file (info.xml).
        Creating and updating a resource file
        To load and format strings for different locales, you must create and update the resource file for the toolkit with translatable strings.
        Accessing resources from toolkit artifacts
        You can access resources, locale-sensitive data, from toolkit artifacts.
        Creating a unique API per message
        To generate a unique API per message, you must tag the <trans-unit> elements in the resource file with the extraData attribute. This attribute represents the name of a C++ macro or Perl subroutine.
        Substituting values in a message
        A substitution value is a value that is substituted into the message at format time to replace a specific placeholder.
      - Versioning guidelines
        Use a version scheme for toolkits that you develop. The toolkit version might be synced up with the version of a wrapped library, or it might depend on the feature set provided by the toolkit.
      - Packaging a toolkit
        You package a toolkit to allow other SPL application developers to access the operators and functions that are defined in the toolkit.
      - Installing a toolkit
        You install SPL toolkits by copying the toolkit directory to a location on a file system accessible to where Teracloud® Streams is installed.
      - Directing the compiler to the toolkit directory
        To use the operators and functions that are defined in a toolkit, you first need to point the SPL compiler to the toolkit root directory.
      - Documenting your SPL toolkits
        You can use SPLDOC markup and the spl-make-doc command to generate rich text documentation for your SPL toolkits.
    - Native functions
      Native functions are written in C++ or Java™ and are invoked from SPL by using the same syntax that invokes an SPL function.
    - Supporting multiple versions with a single toolkit
      Toolkits can support multiple versions of Teracloud® Streams with a minimum number of source files, if you follow the guidelines provided.
  - Developing operators
    You can develop many stream applications with only the operators available in the SPL standard toolkit or in the specialized toolkits. If these toolkits do not provide all of the function you need to implement your application, you can develop new operators as required.
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.

Adding a <resources> element to the toolkit information model file

To create a toolkit that loads and formats string resources for different locales, you must add a <resources> element to the toolkit information model file (info.xml).

Within the <resources> element, one or more <messageSet> elements are required. Each <messageSet> element corresponds to one resource bundle. The <messageSet> element has a name attribute, which identifies the base name of the resource bundle. The <messageSet> element has one or more <lang> elements, each of which specifies a resource file that is included in the resource bundle. The <lang> element has an optional default attribute, which, if true, identifies that resource file as the default language. One, and only one, <lang> element must be specified as the default.

Example

The following elements represent a complete toolkit information model file (info.xml). Within the <resources> element, the generated resources bundle is called MyResource.dat and is in the impl/nl directory. The default resource file is MyResource.xlf and is in the impl/nl/en/en_US directory. Two additional resource files are provided in the impl/nl/fr/fr_FR and impl/nl/tr/tr_TR directories.

<toolkitInfoModel
  xmlns="http://www.ibm.com/xmlns/prod/streams/spl/toolkitInfo"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xmlns:cmn="http://www.ibm.com/xmlns/prod/streams/spl/common"
  xsi:schemaLocation="http://www.ibm.com/xmlns/prod/streams/spl/toolkitInfo toolkitInfoModel.xsd">
  <identity>
    <name>My-toolkit</name>
    <description>My Toolkit</description>
    <version>1.0.0</version>
    <requiredProductVersion>3.0.0</requiredProductVersion>
  </identity>
  <dependencies>
    <toolkit>
      <cmn:name>test-pkg</cmn:name>
      <cmn:version>[4.5.6,5.2]</cmn:version>
    </toolkit>
  </dependencies>
  <resources>
    <messageSet name="MyResource">
      <lang default="true">en/en_US/MyResource.xlf</lang>
      <lang>fr/fr_FR/MyResource.xlf</lang>
      <lang>tr/tr_TR/MyResource.xlf</lang>
    </messageSet>
  </resources>
</toolkitInfoModel>