Module List

Select the library to be used from the list.

Context Provider

Type in the context URL, for example com.tibco.tibjms.naming.TibjmsInitialContextFactory. However,
be careful, the syntax can vary according to the JMS server used.

Server URL

Type in the server URL, respecting the syntax, for
example tibjmsnaming://localhost:7222.

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.

Enable Durable Subscription

Select this check box to enable the durable
subscription.

ClientID

Enter the client ID for the durable subscription.

This field is available only when the Enable Durable Subscription check box is
selected.

Subscriber Name

Enter the subscriber name for the durable
subscription.

This field is available only when the Enable Durable Subscription check box is
selected.

Use JNDI Name Lookup Destination

Select this check box to look up a destination with the JNDI (Java Naming
and Directory Interface) name.

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 topic/testtopic

Note that the field is case-sensitive.

Timeout for Next Message (in sec)

Type in the number of seconds before passing to the next
message.

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 Schema

A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

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

Properties

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

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
integer.

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 +
Space to access the variable list and choose the variable to use from it.

For further information about variables, see
Talend Studio

User Guide.

Usage rule

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

Limitation

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. You can find more details about how to install external modules in
Talend Help Center (https://help.talend.com).

Module List

Select the library to be used from the list.

Context Provider

Type in the context URL, for example com.tibco.tibjms.naming.TibjmsInitialContextFactory.
However, be careful, the syntax can vary according to the JMS server
used.

Server URL

Type in the server URL, respecting the syntax, for example tibjmsnaming://localhost:7222.

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
topic/testtopic

Note that the field is case-sensitive.

Timeout for Next Message (in sec)

Type in the number of seconds before passing to the next
message.

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
Schema

A schema is a row description. It defines the number of fields
(columns) to be processed and passed on to the next component. When you create a Spark
Job, avoid the reserved word line when naming the
fields.

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

Use SSL/TLS

Select this check box to enable the SSL or TLS encrypted connection.

Then you need to use the tSetKeystore
component in the same Job to specify the encryption information.

Properties

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

Usage rule

This component is used as a start component and requires an output link.

This component, along with the Spark Streaming component Palette it belongs to, appears
only when you are creating a Spark Streaming Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents
only Standard Jobs, that is to say traditional
Talend
data
integration Jobs.

Spark Connection

This connection is effective on a per-Job basis.