tJMSInput - 6.1

Talend Components Reference Guide

EnrichVersion
6.1
EnrichProdName
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
task
Data Governance
Data Quality and Preparation
Design and Development
EnrichPlatform
Talend Studio

Function

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

Purpose

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

If you have subscribed to one of the Talend solutions with Big Data, this component is available in the following types of Jobs:

tJMSInput properties

Component Family

Internet

 

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.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. The schema is either Built-In or stored remotely in the Repository.

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

Advanced settings

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

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

Log4j

If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide.

For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.

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. For details, see https://help.talend.com/display/KB/How+to+install+external+modules+in+the+Talend+products or the section describing how to configure the Studio in the Talend Installation Guide.

Related scenarios

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

tJMSInput properties in Spark Streaming Jobs

Warning

The streaming version of this component is available in the Palette of the studio on the condition that you have subscribed to Talend Real-time Big Data Platform or Talend Data Fabric.

Component Family

Messaging / MOM and JMS

 

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.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. The schema is either Built-In or stored remotely in the Repository.

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

Advanced settings

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 authentication information.

For further information about tSetKeystore, see tSetKeystore.

 

Properties

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

Usage in Spark Streaming Jobs

In a Talend Spark Streaming Job, it is used as a start component and requires an output link. The other components used along with it must be Spark Streaming components, too. They generate native Spark code that can be executed directly in a Spark cluster.

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.

Log4j

If you are using a subscription-based version of the Studio, the activity of this component can be logged using the log4j feature. For more information on this feature, see Talend Studio User Guide.

For more information on the log4j logging levels, see the Apache documentation at http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html.

Spark Connection

You need to use the Spark Configuration tab in the Run view to define the connection to a given Spark cluster for the whole Job. In addition, since the Job expects its dependent jar files for execution, one and only one file system related component from the Storage family is required in the same Job so that Spark can use this component to connect to the file system to which the jar files dependent on the Job are transferred:

This connection is effective on a per-Job basis.

Related scenarios

No scenario is available for the Spark Streaming version of this component yet.