This TIBCO StreamBase® Adapter for Informatica Ultra Messaging ACK Output was formerly known as part of the 29 West LBM adapter suite.
This adapter allows a StreamBase application to ACK incoming LBM message based on a topic and sequence number. The adapter is embedded in the StreamBase application and has an input port that receives tuples for messages the require an ACK response.
The adapter is configured through several properties set in the adapter's Properties view in StreamBase Studio.
For this adapter to work correctly the 29West LBM Subscribing Input adapter must have the option 'Enable Explicit ACK Only' enabled.
This adapter requires access to the JAR file that implements the 29West LBM Java API on your system, and any files referenced by that JAR file. You will need to add your site's LBM implementation version of that file to your maven repository. The 29West sample includes a pom.xml file with comments on how to maven-install the required jar files for V6.0.
mvn install:install-file -DgroupId=Informatica -DartifactId=UMS -Dversion=6.0.0 \ -Dpackaging=jar -Dfile=path/to/Informatica/UMQ_6.0/UM_Java_API_6_0/UMS_6.0_jdk1.5.0_12.jar mvn install:install-file -DgroupId=Informatica -DartifactId=UMSPDM -Dversion=6.0.0 \ -Dpackaging=jar -Dfile=path/to/Informatica/UMQ_6.0/UM_Java_API_6_0/UMSPDM_6.0_jdk1.5.0_12.jar mvn install:install-file -DgroupId=Informatica -DartifactId=UMSSDM -Dversion=6.0.0 \ -Dpackaging=jar -Dfile=path/to/Informatica/UMQ_6.0/UM_Java_API_6_0/UMSSDM_6.0_jdk1.5.0_12.jar
Before launching any of the sample modules, you also need to setup the launch
configuration to include the
Path that includes the
location of the Informatica installation location. Also, an
LBM_LICENSE_FILENAME variable should be defined with the path to
the license file.
These variables ONLY TAKE EFFECT AT INSTALLATION OF A NODE. If you are using an existing node, these do not take effect.
Informatica purchased 29West and has since released an update of the LBM API, renamed Ultra Messaging Streaming Edition, or UMS. This adapter works with the UMS 6.x JAR files, but you cannot mix LBM and UMS installations. You must thoroughly uninstall any LBM 4.x kit before reinstalling a UMS 6.x kit. Since UMS is a workalike superset of LBM, this page uses "LBM" to refer to both.
If you get an error message whose text refers to
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 and file names are subject to change by 29West. See your LBM documentation for the latest information.
|Sequence Number Field Name||
The field name in the incoming tuple which represents the sequence number of the message to ACK
|Topic Field Name||
The field name in the incoming tuple which represents the topic of the message to ACK
|Log Level||Controls the level of verbosity the adapter uses to send notifications to the console. This setting can be higher than the containing application's log level. If set lower, the system log level is used. Available values, in increasing order of verbosity, are: OFF, ERROR, WARN, INFO, DEBUG, TRACE.|
The 29West LBM Subscribe ACK Output adapter uses typecheck messages to help you configure the adapter in your StreamBase application. In particular, the adapter generates typecheck messages when:
The sequence number field name given is blank or is not present in the incoming tuple or is not of type long.
The topic field name given is blank or is not present in the incoming tuple or is not of type string.
When suspended, the 29West LBM Subscribe ACK Output Adapter stops processing input tuples.
When resumed, the adapter begins processing input tuples once again.