Command Line Deployment

This and the next several pages go through the steps to deploy an EventFlow or LiveView fragment into a node from the command line. See also the summary page for these steps in the Concepts Overview.

Six Steps to Deploy a Fragment

To deploy an EventFlow or LiveView fragment with command-line tools requires six steps:

In StreamBase Studio:
  1. Create a fragment archive file for the fragment you want to deploy.

  2. Create a new, separate project in StreamBase Studio of type StreamBase Application.

  3. Add the fragment archive created in step 1 as a Maven dependency for the StreamBase Application project.

  4. Create an application archive file for the StreamBase Application project.

At the command prompt:
  1. Install a node containing the application archive file, using epadmin install node.

  2. Start the node, thereby starting the fragment running, using epadmin start node.

Node Lifecycle Overview

The lifecycle of a StreamBase Runtime node when deployed from the command line is the same lifecycle for nodes managed by StreamBase Studio. Nodes cycle through four stages. To get a fragment running requires that its containing node be:

  • Installed

  • Started

When a node is started, the EventFlow or LiveView fragment in that node is now running. You can connect to the EventFlow fragment's API listening port with clients to view status and schemas, enqueue tuples to, and dequeue tuples from that fragment. For a started and running LiveView fragment, you can use a standard browser to view the tables managed by that fragment.

To shut down a running fragment, its containing node must be:

  • Stopped

  • Removed

See Node Lifecycle in the Concepts Overview for further details.