August 17, 2023

tJMSInput – Docs for ESB 5.x



tJMSInput properties

Component Family




tJMSInput creates an interface
between a Java application and a Message-Oriented middle ware


Using a JMS server, tJMSInput
makes it possible to have loosely coupled, reliable, and
asynchronous communication between different components in a
distributed application.

Basic settings

Module List

Select the library to be used from the list.


Context Provider

Type in the context URL, for example
“com.tibco.tibjms.naming.TibjmsInitialContext Factory”.
However, be careful, the syntax can vary according to the JMS server


Server URL

Type in the server URL, respecting the syntax, for example


Connection Factory JDNI Name

Type in the JDNI name.


Use Specified User Identity

If you have to log in, select the check box and type in your login
and password.

To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.


Message Type

Select the message type, either: Topic or Queue.


Message From

Type in the message source, exactly as expected by the server;
this must include the type and name of the source. e.g.: queue/A or

Note that the field is case-sensitive.


Timeout for Next Message (in sec)

Type in the number of seconds before passing to the next


Maximum Messages

Type in the maximum number of messages to be processed.


Message Selector Expression

Set your filter.


Processing Mode

Select the processing mode for the messages.

Raw Message or Message Content


Schema and Edit

A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.

The schema of this component is read-only. You can click Edit
to view the schema.

Advanced settings


Click the plus button underneath the table to add lines that
contains username and password required for user


tStatCatcher Statistics

Select this check box to gather the Job processing metadata at a
Job level as well as at each component level.

Global Variables

ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.

NB_LINE: the number of rows read by an input component or
transferred to an output component. This is an After variable and it returns an

A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.

To fill up a field or expression with a variable, press Ctrl +
to access the variable list and choose the variable to use from it.

For further information about variables, see Talend Studio
User Guide.


This component is generally used as an input component. It must be
linked to an output component.


The activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User

For more information on the log4j logging levels, see the Apache documentation at


Make sure the JMS server is launched.

Due to license incompatibility, one or more JARs required to use this component are not
provided. You can install the missing JARs for this particular component by clicking the
Install button on the Component tab view. You can also find out and add all missing JARs easily on
the Modules tab in the Integration perspective
of your studio. For details, see
or the section describing how to configure the Studio in the Talend Installation and Upgrade

Related scenarios

For related scenarios, see Scenario: Enqueuing/dequeuing a message on the ActiveMQ server.

Document get from Talend
Thank you for watching.
Notify of
Inline Feedbacks
View all comments
Would love your thoughts, please comment.x