Skip to main content Skip to complementary content

tUniservRTMailBulk Standard properties

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

The Standard tUniservRTMailBulk component belongs to the Data Quality family.

Basic settings

Schema and Edit schema

A schema is a row description, it defines the number of fields to be processed and passed on to the next component. The schema is either Built-in or stored remotely in the Repository.

The schema of this component is read-only. You can click Edit schema to view the schema.

Host name

Server host name between double quotation marks.

Port

Listening port number of the server between double quotation marks.

Service

The service name is "mail" by default. Enter a new name if necessary (e.g. due to service suffix), between double quotation marks.

Advanced settings

Uniserv Parameters

For detailed information, please refer to the Uniserv user manual mailRetrieval.

tStatCatcher Statistics

Select this check box to collect log data at the Job and the component levels.

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.

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

Usage rule

tUniservRTMailBulk prepares the index pool for duplicate search.

Limitation

To use tUniservRTMailBulk, the Uniserv software mailRetrieval must be installed.

An input component and a map are needed to read the address from the database or a file. The component does not have an output connection.

 

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!