tMessagingConnection Standard properties - Cloud - 8.0

JMS

Version
Cloud
8.0
Language
English
Product
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 Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Messaging components (Integration) > JMS components
Data Quality and Preparation > Third-party systems > Messaging components (Integration) > JMS components
Design and Development > Third-party systems > Messaging components (Integration) > JMS components
Last publication date
2024-02-20

These properties are used to configure tMessagingConnection running in the Standard Job framework.

The Standard tMessagingConnection component belongs to the Messaging family.

Basic settings

Property Type

Either Built-In or Repository.

  • Built-In: No property data stored centrally.
  • Repository: Select the repository file in which the properties are stored. The database connection related fields that follow are completed automatically using the data retrieved.

JMS Provider

Select the type of the MQ server(s) to be connected from the drop-down list: ActiveMQ (JMS v1), ActiveMQ Artemis (JMS v2), or WebSphere MQ.

Server URL

Enter the URL of the MQ server.

MQ server URL needs to be in specific format. That is, tcp://localhost:61616 (for ActiveMQ and ActiveMQ Artemis MQ servers) or localhost(1414) (for WebSphere MQ servers), as prompted in the field.

Use Specified User Identity

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

To enter the password, click the [...] button next to the Password field to bring out the Enter a new password dialog box, enter the password in the text field, and click OK. Note that you can enter the password either in a JSON string in the pure password mode or as a Java expression in the Java mode. You can toggle between the two modes by clicking switch to Java mode or switch to pure password mode on the top of the text field.

Durable subscription

Select this check box to enable the durable subscription.

  • Client ID: enter the client ID for the durable subscription.
  • Subscriber name: enter the subscriber name for the durable subscription.

Advanced settings

tStatCatcher Statistics

Select this check box to collect log data at the component level.

Acknowledge mode

Select the acknowledge mode from the drop-down list: Auto acknowledge, Client acknowledge, DUPS ok acknowledge, Session/Transaction, or Do not acknowledge.

Advanced context properties

Set other properties as needed. To set a property in this table, click the plus button underneath the table to add a line, enter the property name in the Key column and enter the value in the Value column. This table supports global variables and context variables. Refer to Configure JMS producers for information about properties of ActiveMQ and ActiveMQ Artemis MQ servers; refer to WebSphere MQ connector properties for information about properties of WebSphere MQ servers.

Note: If you are using a WebSphere MQ JMS provider, you need to set the mandatory properties (that is, CHANNEL and QUEUE_MANAGER) in this table.

Global Variables

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 more information about variables, see Using contexts and variables.

Usage

Usage rule

This component is commonly used with other tMessaging* components, especially with the tMessagingCommit and tMessagingRollback components.

Limitation

This component supports ActiveMQ and WebSphere MQ servers.