tMomOutput – Docs for ESB 5.x

Component family

Internet

Function

Adds a message to a Message-Oriented middleware system queue in
order for it to be fetched asynchronously.

Purpose

tMomOutput makes it possible to
set up asynchronous communications via a MOM server.

Basic settings

Use existing connection

Select this check box and in the Component List click the
relevant connection component to reuse the connection details you already defined.

Failover

Select this check box to show the server address table.

In that table, you can define multiple MQ servers for
failover.

(Available when ActiveMQ is
selected in the MQ Server
list.)

MQ Server

Select the MOM server to be used from the list. According to the
server selected, the parameters required differ slightly.

Host/Port

Fill in the MOM server and Port Host name or IP address.

Username

Connection login to the server.

Password

Connection password to the server.

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.

To

Type in the message destination, respecting the syntax required by
the server; this must include the type and name of the target
folder. e.g.: queue/A or topic/testtopic

Note that the field is case-sensitive.

(Available when ActiveMQ or
JBoss Messaging is selected in
the MQ Server list.)

Message Type

Select the message type, either: Topic or Queue.

(Available when ActiveMQ or
JBoss Messaging is selected in
the MQ Server list.)

Message Body Type

Select the message body type, either: Text , Bytes or
Map

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.

In the context of tMomOutput
usage, the schema is read-only but will change according to the
incoming schema. Only one-column schema is expected by the server to
contain the Messages.

Websphere MQ

Channel

Fill this field with the name of the channel through which the
data connection is established. The default value is
DC.SVRCONN.

Queue Manager

A system program that provides a logical container for the message
queue and is responsible for transferring data to other queue
managers via message channels. Fill this field with the name of the
queue manager to which the data connection is made.

Message Queue

A queue from which message queueing applications can put messages
on, and get messages. Fill this field with the name of the message
queue.

Is using message id to set

Select this check box to set messages according to their
ids.

Advanced settings

Additional options

Define the failover transport options in the table. This table is
available only if you select the Failover check box in the Basic settings view.

For example, enter maxReconnectAttempts in the Option name field and then 0 in the Option
value field so that no attempt is made to retry the
connection when no server is available for the failover mode.

For more information about the transport options, see http://activemq.apache.org/failover-transport-reference.html.

Select a delivery mode supported by JMS:

Not Persistent: This delivery
mode does not require that the message be logged to stable
storage.

Persistent: This delivery mode
requires that the message be logged to stable storage as part of the
client’s send operation.

For further information about the delivery modes, see https://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzaw07.pdf.

(Available when ActiveMQ or
JBoss Messaging is selected in
the MQ Server list.)

Select this check box to transact the session. For further
information about this paramater, see https://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzaw07.pdf.

Select this check box to send the Jms headers through the mapping
from Jms fields onto MQ Series fields on the MQ server. When this
check box is checked, you can specify the header name and the header
value in the line(s) you added by clicking the plus button in the
Parameters table. For further
information about the usage of Jms headers, see https://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzaw07.pdf.

(Available when ActiveMQ or
JBoss Messaging is selected in
the MQ Server list.)

Select this check box to send the Jms properties mapped onto MQMD
fields on the MQ server. When this check box is checked, you can
specify the property name, the property type and the property value
in the line(s) you added by clicking the plus button in the
Parameters table. For further
information about the usage of Jms properties, see https://publib.boulder.ibm.com/iseries/v5r2/ic2924/books/csqzaw07.pdf.

(Available when ActiveMQ or
JBoss Messaging is selected in
the MQ Server list.)

Select this check box to specify the WebSphere message format in
the WebSphere Message Format field.
The default format is MQSTR.

For further information about WebSphere message format, see http://publib.boulder.ibm.com/infocenter/wtxdoc/v8r2m0/index.jsp?topic=/com.ibm.websphere.dtx.adapibmmq.doc/references/r_ibmmq_Message_Format_FORMAT.htm.

(Available when WebSphere MQ is
selected in the MQ Server
list.)

Select this check box to specify the header of the message:

MQRFH2 fixed Portion: Select this
check box and click the plus button to add one or more lines to
specify the Version, Encoding, Format, Flags,
NameValueCCSID and CodedCharSetId as needed for the fixed
portion of MQRFH2 header.

MCD folder: Select this check box
and click the plus button to add one or more lines to specify the
field name and the value for the properties that describe the format
of the message.

JMS folder: Select this check box
and click the plus button to add one or more lines to specify the
field name and the value for the transportation of JMS header fields
and JMSX properties.

USR folder: Select this check box
and click the plus button to add one or more lines to specify the
field name and the value for the transportation of
application-defined properties associated with the message.

For further information about MQRFH2 header, see http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r1m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Faq06920_.htm.

(Available when WebSphere MQ is
selected in the MQ Server
list.)

Select this check box to enable the CipherSpec list from which you
can specify the CipherSpec to be used with WebSphere MQ SSL.

For further information about CipherSpec, see http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=%2Fcom.ibm.mq.csqzas.doc%2Fsy12870_.htm.

(Available when WebSphere MQ is
selected in the MQ Server
list.)

tStatCatcher Statistics

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

Dynamic settings

Click the [+] button to add a
row in the table and fill the Code
field with a context variable to choose your MQ Server connection
dynamically from multiple connections planned in your Job.

The Dynamic settings table is available only when the
Use an existing connection check box is selected in the
Basic settings view. Once a dynamic parameter is
defined, the Component List box in the Basic settings view becomes unusable.

For more information on Dynamic settings and context
variables, see Talend Studio User Guide.

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 must be linked to an input or intermediary
component.

Log4j

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 relevant Websphere MQ, JBoss Messaging or ActiveMQ
server is launched.

This component requires installation of its related jar files. For more information about the
installation of these missing jar files, see the section describing how to configure the
Studio of the Talend Installation and Upgrade Guide.