Ensayo Sobre La Vida

The StreamBase 29West LBM Subscribing Input adapter allows a StreamBase application to receive messages published to one or more LBM topics. The adapter is embedded in the StreamBase application and has two output ports: one that emits status tuples, and a second that emits tuples representing received LBM messages.

The adapter subscribes to one or more topics during startup, thenasynchronously and continuously receives and converts incoming LBM messages into StreamBase tuples, which it sends downstream.

The adapter supports all StreamBase data types, including tuples and lists, though lists may not contain elements of type list. The schema of the LBM message output port is set through the Edit Schema tab of the adapter's Properties view.

The adapter is configured throughseveral properties set in the adapter's Properties view in StreamBase Studio. The properties include an optional configuration file to configure the LBM library, the set of topics to subscribe to at startup, and the adapter's log level.

29West LBM Middleware Dependencies

This adapter requires access to the JAR file that implements the 29West LBM Java API on your system, and any files referenced bythat JAR file. The StreamBase installation kit includes version 4.0 of the LBM_4.1.1_jdk1.5.0_12.jar JAR file. If your site's LBM implementation requires a newer version of that file, copy the file to $STREAMBASE_HOME/lib/ext.

The LBM jar file, in turn, relies on various native library files, which are supplied as part of your LBM installation, and are not shipped with StreamBase. Make surethese files are locatable by the LBM JAR file on the PATH environment variable.

If you get an error message whose text refers to can't load lbmj: java.lang.UnsatisfiedLinkError: no lbmj in java.library.path, make sure the directory containing the LBM native libraries is on the path.

The LBM API implementation described in this section is a product of a third party, and its specifications andfile names are subject to change by 29West. See your LBM documentation for the latest information.

Adapter Properties

Property Description
LBM Configuration File
The name of an optional LBM configuration file used to override the default settings used by the LBM library. Configuration files can be shared between one or more LBM subscribing and publishing adapter instances. To support suchsharing, configuration files can have named sections, which are referenced by the LBM Configuration File Section property below. Named sections are identified by placing a section name inside square brackets within a comment:
#[MySection]
Lines that precede the first section name are considered part of the unnamed (default) section.
Lines that follow a section name are considered part of thatsection.
Section names must be unique within and across all referenced configuration files; a runtime error is flagged when a duplicate section name is encountered. Section names can include alphanumeric characters, digits, underscores, dots, and embedded spaces. They must start with an upper- or lower-case letter or an underscore.
LBM Configuration File Section The name of the LBMconfiguration file section from which to retrieve the parameters for configuring the LBMContext and LBMReceiver objects. If unspecified, parameters from the unnamed section are used. For enhanced performance, all LBM adapter instances that specify the same configuration file and section name share an LBMContext object.
Initial Subscription Topic(s) Zero or more topics to subscribe to at startup. Separatemultiple topics with spaces. For example, "top.topic1 top.topic2".
Initial Subscription Wildcard Topic(s) Zero or more wildcard topics to subscribe to at startup. Separate multiple wildcard topics with spaces. Wildcard topics use the form of regular expressions recognized by Perl; see http://perldoc.perl.org/perlrequick.html for details. Example wildcard topics include:
^[xy].?$ -- One- or...