tRabbitMQOutput Standard properties

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.

Use an existing connection

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

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. When you create a Spark Job, avoid the reserved word line when naming the fields.

Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:

• View schema: choose this option to view the schema only.

• Change to built-in property: choose this option to change the schema to Built-in for local changes.

• Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.

  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

This component can have only one column with the name of message and the type of String. You need to add the column manually in the schema.

Host name

Enter the host name, for example, localhost.

Port

Enter the port number. The default is 5672.

Username and Password

Enter the username and the password for accessing the message queue.

Use TLS

Select this option to use TLS for the connection.

Exchange type

Select the exchange type from the drop-down list. Five options are provided: Default, Direct, Topic, Fanout, and Headers. See Exchanges and Exchange Types section of AMQP 0-9-1 Model Explained for related information.

Exchange name

Enter the exchange name in double quotation marks.

Routing key

Enter the routing key in double quotation marks.

Header properties

Add and customize message header properties.

To add a message header property, add a row in this field by clicking the plus button under the field and set the property values (that is, header key, header value, and header type) in the corresponding columns of the new row.

tStatCatcher Statistics

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

Use virtual host

Select this option to use a virtual host for publishing messages. Specify the virtual host to be used by entering the virtual host name in the Virtual host name field.

Durable

Select this option to declare the durable property for the queues. See Queues section of AMQP 0-9-1 Model Explained for related information.

Auto Delete

Select this option to declare the Auto-delete property for the queues. See Queues section of AMQP 0-9-1 Model Explained for related information.

Use alternate exchange

Select this option to enable alternate exchange. In this case, you need to enter the alternate exchange name in the Alternate exchange name field.

This option is available if you select Direct, Topic, or Headers from the Exchange type drop-down list in the Basic settings view.

Global Variables

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.

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.

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 rule