Tutorial Overview

You can use the Ticker tracker tutorial to learn how to use the TIBCO BusinessEvents Views software to create and run a dashboard using step-by-step tutorial.

In this tutorial, step-by-step instructions explain how to do the following:

  • Define a simple metric that captures ticker price and volume.
  • Write a rule to populate the metric using data from an event sent via an HTTP channel
  • Define all the objects needed to render the information in the metric on a dashboard.

You will also configure a cache cluster. To successfully render a dashboard page requires two agents, an inference agent to populate the metric and a dashboard agent to serve the dashboard. Both agents are part of the same cluster.

Configured Tutorial Project

The tutorial project is located in the following directory:

BE_HOME/examples/views/TickerTracker/TickerTracker

To configure the provided project for use, follow instructions in the example’s readme.html file.

Before You Begin

This tutorial assumes you know the basics of creating projects and configuring cache object management.

If you are new to TIBCO BusinessEvents, learn about these topics by completing the tutorials in the TIBCO BusinessEvents Getting Started guide before you begin.

It is recommended that you complete the tutorial yourself, because “learning by doing” is the most effective way to become proficient. If completing the tutorial is not possible, however, you can read the tutorial documentation and refer to the fully configured tutorial example project, provided here: 

BE_HOME/examples/views/TickerTracker

Dependency of Interactive Readme File on a Higher Level Directory

The readme.html file uses resources in the BE_HOME/examples/_resources directory to enable you to send messages to the deployed example project using an HTTP channel. Therefore you must maintain the relative positions of these two directories.

Dependency Between Readme File and Project — Port Number

Each example project uses a different port for the HTTP channel, so you can run more than one example at a time on your machine. The readme file interacts with the channel on the specified port at runtime. FraudDetection uses port 8108, FraudDetectionCache uses port 8109 and FraudDetectionStore uses 8209.

If you change the example project’s port (in the HTTP Connection resource), make sure you change the port in the readme.html too. Open the readme.html in an editor and edit this line (showing the FraudDetection project port as an example): 

SendEventForm.setServer("http://localhost:8108");

Copy Example Directory Trees Before Importing

Because of this dependency between the readme.html file and the _resources directory (and also because it is good practice to work in copies of the shipped examples), it is recommended that you make a copy of the directory tree for any example you want to work with.

For example, copy BE_HOME/examples/views/TickerTracker, and paste it as a peer of the provided example, renaming the TickerTracker directory, for example, to TickerTracker2. As an alternative you can copy the entire BE_HOME/examples directories and then work with the copied set of examples.

In either case, you can use the readme.html file to test the deployed project.

At deploy time the only files that are used are the configured EAR and CDD files. When you construct a command to start an engine, these files must be available.