tJMSOutput properties for Apache Spark Streaming

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, enter the password in double quotes in the pop-up dialog box, and click OK to save the settings.

Message Type

Select the message type, either: Topic or Queue.

To

Type in the message target, as expected by the server.

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 that will be processed and passed on to the next component.

The tJMSOutput schema is read-only. It is made of one column: message when the processing mode is Raw Message or messageContent when this mode is Message Content.

Since the message column requires valid JMS messages as input, you need to use a tJava component to write these JMS messages, while when the messageContent column is used, you can use a Write component to provide data.

Delivery Mode

Select a delivery mode from this list to ensure the quality of data delivery:

Not Persistent: This mode allows data loss during the data exchange.

Persistent: This mode ensures the integrity of message delivery.

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.

Connection pool

In this area, you configure, for each Spark executor, the connection pool used to control the number of connections that stay open simultaneously. The default values given to the following connection pool parameters are good enough for most use cases.

• Max total number of connections: enter the maximum number of connections (idle or active) that are allowed to stay open simultaneously.

  The default number is 8. If you enter -1, you allow unlimited number of open connections at the same time.

• Max waiting time (ms): enter the maximum amount of time at the end of which the response to a demand for using a connection should be returned by the connection pool. By default, it is -1, that is to say, infinite.

• Min number of idle connections: enter the minimum number of idle connections (connections not used) maintained in the connection pool.

• Max number of idle connections: enter the maximum number of idle connections (connections not used) maintained in the connection pool.

Evict connections

Select this check box to define criteria to destroy connections in the connection pool. The following fields are displayed once you have selected it.

• Time between two eviction runs: enter the time interval (in milliseconds) at the end of which the component checks the status of the connections and destroys the idle ones.

• Min idle time for a connection to be eligible to eviction: enter the time interval (in milliseconds) at the end of which the idle connections are destroyed.

• Soft min idle time for a connection to be eligible to eviction: this parameter works the same way as Min idle time for a connection to be eligible to eviction but it keeps the minimum number of idle connections, the number you define in the Min number of idle connections field.

Usage rule

This component is used as an end component and requires an input 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.