Contents
The Bi-Directional BLOB Socket Input/Output Adapter can be used to send and receive data over a socket connection in BLOB format. This example shows how linked socket readers/writers work as both client and server. The example also shows how 2 different data transformers work (Serialized Tuple and BLOB).
The client in this example connects to the server and then sends an initial tuple of data. When the server receives data from
the client socket, it echoes the tuple directly without modifying it. The client waits, and when it receives a response from
the server it increments an integer in the response tuple by 1 and then sends the tuple back to the server. This handshaking
continues until the parameter ${FinishedValue} is reached.
-
In the Package Explorer, double-click to open the
BLOBServerWithSerializedTupleClient.sbappto open the example. Make sure the application is the currently active tab in the EventFlow Editor. -
Click the
Run button. This opens the SB Test/Debug perspective and starts the application.
-
For the example, in the Manual Input view select the
ControlClientStream, then enterCONNECTinto the command field, then click to send the tuple. -
In the Application Output view, observe tuples emitted on the
ReadDataServerandReadDataClientoutput streams. -
Select any tuple emitted from either stream and inspect tuple data fields in the Variables view below the output streams to analyze and understand their structure.
-
When done, press F9 or click the
Stop Running Application button.
This section describes how to run this sample in UNIX terminal windows or Windows command prompt windows. Running this sample in terminal windows does not provide the best illustration of the Web Reader adapter, because tuples emitted on its primary output port are not designed for human readability. Nevertheless, if you only have terminal access to a UNIX server running StreamBase, follow the steps in this section.
On Windows, be sure to use the StreamBase Command Prompt from the Start menu as described in the Test/Debug Guide, not the default command prompt.
-
Open three terminal windows on UNIX, or three StreamBase Command Prompts on Windows. In each window, navigate to your workspace copy of the sample, as described above.
-
In window 1, type:
sbd BLOBServerWithSerializedTupleClient.sbapp
-
In window 2, type:
sbc dequeue ReadDataClient
This window will display tuples dequeued from the adapter's primary output port.
-
In window 3, type:
sbc enqueue ControlClient
-
In window 3 type:
CONNECT,null,null,null
and press Enter.
-
Observe in window 2 that tuples are emitted from the
ReadDataClientstream. The tuples contain an integer field which is incremented each time it goes to the server and comes back to the client. -
In window 3, type Ctrl+C, then the following command to terminate the server and dequeuer:
sbadmin shutdown
In StreamBase Studio, import this sample with the following steps:
-
From the top menu, select → .
-
Select
Bi-Directional BLOB Socket Input/Output Adapterfrom the StreamBase Standard Adapters category. -
Click OK.
StreamBase Studio creates a single project containing the sample files.
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 the permission problems that can occur when trying to work with the initially installed location of the sample. The default workspace location for this sample is:
studio-workspace/sample_adapter_embedded_bi-directional-blob-socketSee Default Installation Directories for the location of studio-workspace on your system.
In the default TIBCO StreamBase installation, this sample's files are initially installed in:
streambase-install-dir/sample/adapter/embedded/bi-directional-blob-socketSee Default Installation Directories for the default location of studio-workspace on your system.