Contents
This topic describes how to run the TIBCO ActiveSpaces® operator sample application, which illustrates how to use the operators with an ActivesSpaces data grid.
For more information on this operator, see Using the TIBCO ActiveSpaces Operators.
This sample includes a number of ActiveSpaces operators, which by default connect to
an ActiveSpaces data grid named TestGrid
on localhost.
The sample data grid supplied with the ActiveSpaces installation is assumed to be
running on localhost already, by executing %TIBDG_ROOT%/samples/scripts/as-start.bat
on Windows systems or the
corresponding script on other platforms. To connect to other ActiveSpaces servers,
edit the sample's src/main/configurations/ActiveSpaces.conf
file appropriately.
Once connected, you can use the sample to put rows into and retrieve rows from the
sample table (named t1
) using the various ActiveSpaces
operators.
In StreamBase Studio, import this sample with the following steps:
-
From the top-level menu, select
> . -
Enter
activesp
to narrow the list of options. -
Select TIBCO ActiveSpaces Operators from the Other TIBCO Product Connectivity category.
-
Click
.
-
Before running you must configure the project to locate and load the ActiveSpaces libraries. Open
src/main/configurations/engine.conf
and adjust paths based on your own install locations for TIBCO ActiveSpaces and TIBCO FTL. -
Make sure the data grid that ships as an ActiveSpaces sample is up and running on the local machine (or, if running it on another machine, edit
ActiveSpaces.conf
to point the data grid definition to the right IP address). You can launch the data grid by running%TIBDG_ROOT%/sample/scripts/as-start.bat
. -
In the Project Explorer view, open the sample you just loaded.
If you see red marks on a project folder, wait a moment for the project to load its features.
If the red marks do not resolve themselves after a minute, select the project, right-click, and select
> from the context menu. -
Open the
src/main/eventflow/
folder.packageName
-
Open the
activespaces.sbapp
file and click the Run button. This opens the SB Test/Debug perspective and starts the module. -
Once the application has started, the ActiveSpaces Control operator connects to the data grid then sends a
Connected
tuple to the application. -
In the Manual Input view, select the
PutCmd
input stream. -
Enter the following values:
-
key:
1
-
value:
One
Click
and observe that thePutResults
output stream received a tuple with itsinput
field set to the given command tuple and itsrow
field set to null, indicating that the operation succeeded and finished. -
-
Still in the Manual Input view, select the
GetCmd
stream and enter1
as the value for the key field, then click . This fetches the row with key1
and emit it on the GetResults output stream, followed by a marker tuple (row = null) to indicate the operation finished executing. -
You may similarly send arbitrary queries to a table (for example,
SELECT * FROM t1 WHERE key > 0
) using the QueryCmd stream and remove rows using the DeleteCmd stream. Of note is the ControlCmd stream which allows you to send control commands to, for example, disconnect from the data grid. Finally, if you have defined your data grid connection to be transacted (by adding<setting name="transacted-session" val="true"/>
to the definition) you can commit or rollback your data grid operations using theTxCmd
input stream. -
When done, press F9 or click the Terminate EventFlow Fragment button.
This sample has the following files:
- activespaces.sbapp
-
Sample EventFlow application.
- engine.conf
-
Used by the StreamBase Server to correctly configure the Java environment to locate the ActiveSpaces libraries.
- ActiveSpaces.conf
-
Definitions for available ActiveSpaces data grids.
When you load the sample into StreamBase Studio, Studio copies the sample project's files to your Studio workspace, which is normally part of your home directory, with full access rights.
Important
Load this sample in StreamBase Studio, and thereafter use the Studio workspace copy of the sample to run and test it, even when running from the command prompt.
Using the workspace copy of the sample avoids permission problems. The default workspace location for this sample is:
studio-workspace
/sample_activespaces
See Default Installation
Directories for the default location of studio-workspace
on your system.