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.

Note that when a Job contains the parent Job and the child Job,
Component List presents only the
connection components in the same Job level.

Failover

Select this check box to use the ActiveMQ failover transport.
For more information about the failover transport, see Failover Transport
Reference.

This check box is available only when ActiveMQ is selected from the MQ
server list and the Static
Discovery check box is cleared.

Static Discovery

Select this check box to use the ActiveMQ static transport
discovery mechanism. For more information about the static transport, see Static Transport
Reference.

This check box is available only when ActiveMQ is selected from the MQ server list and the Failover check box is cleared.

URI parameters

Enter the URI parameters.

This field is available only when the Failover or Static
Discovery check box is selected.

MQ Server

Select the type of the MQ server(s) to be connected from the
list: ActiveMQ, JBoss Messaging, or WebSphere MQ. According to the server type selected, the
parameters required differ slightly.

Use SSL Transport

Select this check box to use the ActiveMQ SSL transport. For
more information about the SSL transport, see SSL Transport
Reference.

This check box is available only when ActiveMQ is selected from the MQ server list.

Host

Enter the host name or IP address of the MQ server.

Port

Enter the listening port of the MQ server.

Username and Password

Enter the user authentication credentials.

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.

Channel

Specify the name of the channel through which the connection is
established. The default value is DC.SVRCONN.

This field is available only when WebSphere MQ is selected from the MQ
server list.

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 this field is case-sensitive.

This field is available only when ActiveMQ or JBoss
Messaging is selected from the MQ
Server list.

Message Type

Select the message type: either Topic or Queue.

This list is available only when ActiveMQ or JBoss
Messaging is selected from the MQ
Server list.

Message Body Type

Select the message body type: Text
Message, Bytes Message or
Map Message.

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.

QueueManager

Specify the name of the queue manager to which the connection
is established.

This field is available only when WebSphere MQ is selected from the MQ
server list.

MessageQueue

Enter the name of the message queue into which message queueing
applications can put messages.

This field is available only when WebSphere MQ is selected from the MQ
server list.

Set Transacted

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

Note that selecting this check box will ignore the settings in
the Acknowledgement Mode list in the
Advanced settings view of tMomInput.

Is using message id to set

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

This check box is available only when Text Message or Bytes
Message is selected from the Message
Body Type list.

Additional options

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

• Option name: the name of the
  option.

• Option value: the value of the
  option.

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 more information about the failover transport options, see
Failover Transport
Reference.

For more information about the static discovery transport
options, see Static Transport
Reference.

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

Set MQMD Fields

Select this check box to enable the Parameters table in which you can specify the value of the MQMD
fields.

This check box is available only when WebSphere MQ is selected from the MQ Server list.

Parameters

This table is available only when the Set MQMD Fields check box is selected.

For more information about the MQMD fields, see Fields for MQMD.

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.

Set Cipher Suite

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

For further information about Cipher Suite, see CipherSpecs and their equivalent CipherSuites
supported by IBM WebSphere MQ.

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

Custom Cipher Suite

Select this check box to allow you to custome Cipher Suite.

IBM Cipher Mappings: Use the IBM Java Cipher Suite to
IBM MQ Cipher Spec Mappings.

Oracle Cipher Mappings: Use the Oracle Cipher Suite to
IBM MQ Cipher Spec Mappings.

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

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 examples on using dynamic parameters, see Reading data from databases through context-based dynamic connections and Reading data from different MySQL databases using dynamically loaded connection parameters. For more information on Dynamic
settings and context variables, see Talend Studio
User Guide.

Limitation

Make sure the relevant Websphere MQ, JBoss Messaging or
ActiveMQ server is launched.

This component requires installation of its related jar files.