This sample demonstrates the use of the TIBCO StreamBase® Adapters for TIBCO eFTL®.
Before running this sample, be sure to install the TIBCO eFTL
tibeftl.jar file as described in TIBCO Middleware Dependencies in the TIBCO eFTL Publish Output Adapter or TIBCO eFTL Subscribe Input Adapter.
Before running this sample, make sure to have a running eFTL server either locally or using TIBCO Cloud Messaging.
In the Package Explorer, double-click to open the
eftl.sbappapplication. Make sure the application is the currently active tab in the EventFlow Editor.
Open the Parameters tab of the
eftl.sbappfile and edit the
AUTHENTICATION_KEYparameters for your eFTL connection.
Subscribeadapter is set up to subscribe to only messages containing a subject field; open the adapter properties and see the matcher field to change this setting.
Click the Run button. This opens the SB Test/Debug perspective and starts the application.
In the Test/Debug Perspective, open the Application Output view. If the adapter can connect to the eFTL server, two
Connectedstatus tuples appear, one from each TIBCO eFTL adapter instance.
In the Manual Input view, select the
PublishInstream and enter some information, then click . Additional tuples appear in the Application Output view from the
PublishStatusstreams, indicating the following:
The message was published by the eFTL Publish adapter.
The message was received by the eFTL Subscribe adapter.
When done, press F9 or click the Stop Running Application button.
In StreamBase Studio, import this sample with the following steps:
From the top-level menu, select→ .
to narrow the list of options.
Select TIBCO eFTL publish and subscribe adapters from the Other TIBCO Product Connectivity category.
StreamBase Studio creates a project for this sample.
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.
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:
See Default Installation Directories for the location of
studio-workspace on your system.