Skip to main content Skip to complementary content

tUniservRTPost Standard properties

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

The Standard tUniservRTPost 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 (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.

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 "post" by default. Enter a new name if necessary (e.g. due to service suffix), between double quotation marks.

Use rejects

Select this check box to collect faulty addresses via the rejects connection. Usually they are the addresses with the post result class 5. Valid values for the result class are 1-5. The value must be between double quotation marks.

If this check box is not selected, the faulty addresses are output via the Main connection.

If the check box is selected but the rejects connection is not created, the faulty addresses are simply rejected.

Use File for ambiguous results

Select the check box to define a file for writing the selection list to it.

When an address cannot be corrected unambiguously, a selection list is created.

This list can be further processed via the AMBIGUITY connection. All potential candidate results then run via this connection. The schema of this connection is preinitialized with the arguments of the dissolved selection list of the service 'post'.

Advanced settings

Uniserv Parameters

Select this check box to define the corresponding parameters. For detailed information, please refer to the Uniserv user manual International Postal Framework.

tStatCatcher Statistics

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

"Full address" selection list

Select the check box Display to show all the columns. Or, select the check box next to a particular column to show it alone.

This option controls the content of the file for ambiguous addresses. Only selected columns would be written into the file.

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

tUniservRTPost requires an input set. Its postal validation will then be checked. In case of an unambiguous result, the corrected set will be output via the Main connection. If the address is ambiguous, the potential candidates will be output via the Ambiguity connection. If an address was not found, it will be passed on via the Reject connection.

Limitation

To use tUniservRTPost, the Uniserv software International Postal Framework and the required post servers must be installed.

 

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!