Docker Samples on GitHub

TIBCO provides a number of advanced Docker samples on its GitHub repository. You can load these samples into Studio like other samples:

  1. Invoke File>Import Samples and Community Content.

  2. Select the Include community samples check box:

    (If you have never accessed the community samples on this computer for any TIBCO Streaming release, you see the following link instead:

    See Using the GitHub Content for further notes on using this feature.)

  3. Click the Pull from remote repositories now link to make sure you have the latest sample versions and to configure your local clone to use the branch appropriate for this Studio release.

  4. In the search field, enter docker to narrow the list to the Docker related samples. At this writing, this results in the following:

  5. Select a sample such as Docker: 2-node EventFlow and click Import Now.

Consider the following notes on these samples.

  • These samples come into Studio as a compound project with the fragment project and application project in subordinate folders:

  • Instructions are generally found, not in the README.md files, but in the app project's src/site/markdown/index.md file.

  • The EventFlow module in the fragment project is generally empty. A StreamBase Application generated from the app project will install and run in Docker, but there is nothing to connect to in the container. You are free to copy any tested and known-working EventFlow module to replace the empty module, preserving its module name.

  • These samples are generally configured to be built by running mvn install at the command prompt. However, they do work in Studio if you remember to Maven-install the fragment first.

    For example, for the 2-node EventFlow sample, in the Project Explorer view, select the ef-2node-eventflow folder. Right-click and select Run As>Build... as described in Maven-Install the Fragment. Only then can you can generate the image from the 2-node-app folder as described in Build and Install the Docker Image.