StreamBase Runtime Introduction

StreamBase Runtime Terminology

The StreamBase Deployment Runtime, which is based on TIBCO's Distributed Transactional Memory platform, uses the following terms:

  • A fragment is an executable part of a DTM application.

    • A complete StreamBase application solution is encapsulated as a single EventFlow fragment.

  • An engine is an execution context for a fragment.

    • StreamBase fragments run in the context of a JVM engine.

  • A node is a container for one or more engines.

    • A node can belong to one cluster.

    • A node can host one or more engines.

  • A machine is a physical or virtual computer that provides an execution context for a node.

    • One or more nodes can run on a single machine.

  • A cluster is a logical grouping of one or more nodes that communicate to support a DTM application.

    • One cluster hosts a single DTM application.

  • A DTM application is a program that provides organization-specific functionality, potentially on a large scale.

    • An application is run on one or more nodes.

    • An application contains one or more fragments.

The following diagram shows the relationships between these interdependent terms:

StreamBase Runtime Layers

An application running in the DTM fabric can be as simple as one composed of a single EventFlow fragment running on a single JVM engine, running on a single machine. This combination is a single-node cluster, and this is how EventFlow fragments are run and debugged in StreamBase Studio.

Once your EventFlow fragment is developed and ready, you can deploy it from the command line with the epadmin command. This allows you to specify multiple combinations of fragments and engines, including duplicate fragments to provide a high availability application.

Your application can eventually be built up to run on many nodes hosted on several machines, including machines geographically separated.

The epadmin Command

To run your EventFlow fragments outside of StreamBase Studio, StreamBase provides the epadmin command. To run epadmin, your command line environment:

  • Must include the TIBCO_EP_HOME environment variable pointing to the file system location of your TIBCO StreamBase installation. This is the same location identified by the STREAMBASE_HOME environment variable.

  • Must have TIBCO_EP_HOME/distrib/tibco/bin on its PATH.

These conditions are automatically met when using a StreamBase Command Prompt on Windows, or when your macOS or Linux shell startup scripts include `sb-config --env` as described in the Post-Installation Setup sections of the macOS and Linux Installation Guide pages.

The epdamin command has an extensive built-in help system invoked with epadmin help. For example, invoke epadmin help node for a list of all subcommands and options usable with the important node subcommand.

See also the online documentation page for the epadmin command.