tESBProviderFault - 6.1

Talend Components Reference Guide

Version
6.1
Language
English (United States)
Product
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for Big Data
Talend Open Studio for Data Integration
Talend Open Studio for Data Quality
Talend Open Studio for ESB
Talend Open Studio for MDM
Talend Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance
Data Quality and Preparation
Design and Development

Warning

This component is relevant only when used with one of the Talend solutions with ESB, as it should be used with the Service Repository node and the Data Service creation related wizard(s).

tESBProviderFault properties

Component family

ESB/Web Services

 

Function

Serves a Talend Job cycle result as a Fault message of the Web service in case of a request response communication style.

Purpose

Acts as Fault message of the Web Service response at the end of a Talend Job cycle.

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. The schema is either Built-In or stored remotely in the Repository.

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.

Click Sync columns to retrieve the schema from the previous component connected in the Job.

 

 

Built-in: The schema is created and stored locally for this component only. Related topic: see Talend Studio User Guide.

 

 

Repository: The schema already exists and is stored in the Repository, hence can be reused. Related topic: see Talend Studio User Guide.

 

EBS service settings

Fault title: Value of the faultString column in the Fault message.

Note

The Row > Fault flow of tESBConsumer has a pre-defined schema whose column, faultString, is filled up with the content of the field Fault title of tESBProviderFault.

Advanced settings

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 

NB_LINE: the number of rows processed. 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 further information about variables, see Talend Studio User Guide.

Usage

This component should only be used with the tESBProviderRequest component.

Limitation

A JDK is required for this component to operate.

Scenario: Requesting airport names based on country codes

This scenario involves two Jobs, one as the data service provider and the other as data service consumer. The former listens to the requests from the consumer via tESBProviderRequest, matches the country code wrapped in the request against a MySQL database table that has the country code/airport pairs via tMap, and finally returns the correct airport name via tESBProviderResponse or if no matches are found, the error message via tESBProviderFault. The Consumer sends requests to the Provider and receives the airport information or error reminders via tESBConsumer.

Building the data service provider to publish a service

The data service airport has already been defined under the Services node of the Repository tree view. Its schema has three major elements as shown below:

For how to define a service in the Studio, see Talend Studio User Guide.

Assigning a Job to the defined service
  1. Right-click getAirportInformationByISOCountryCode under the Web service airport and from the contextual menu, select Assign Job.

  2. In the [Operation Choice] window, select Create a new Job and Assign it to this Service Operation.

  3. Click Next to open the Job description window. The Job name airportSoap_getAirportInformationByISOCountryCode is automatically filled in.

  4. Click Finish to create the Job and open it in the workspace. Three components are already available.

Dropping and linking the components
  1. Drop tXMLMap and tMysqlInput from the Palette to the workspace.

  2. Link tESBProviderRequest to tXMLMap using a Row > Main connection.

  3. Link tMysqlInput to tXMLMap using a Row > Main connection.

  4. Link tXMLMap to tESBProviderResponse using a Row > *New Output*(Main) connection.

    In the new Output name pop-up window, enter the output table name, airport_response.

    Click OK in the pop-up window that asks whether to get the schema of the target component.

  5. Link tXMLMap to tESBProviderFault using a Row > *New Output*(Main) connection.

    In the new Output name pop-up window, enter the output table name, fault_message.

    Click OK in the pop-up window that asks whether to get the schema of the target component.

Configuring the components
  1. Double-click tMysqlInput to display its Basic settings view.

  2. Fill up the basic settings for the Mysql connection and database table.

    Click the [...] button to open the schema editor.

  3. Click the [+] button to add two columns, id and name, with the type of string.

    Click OK to close the editor.

    Click Guess Query to retrieve the SQL query.

  4. Double-click tXMLMap to open its mapper.

  5. In the main : row1 table of the input flow side (left), right-click the column name payload and from the contextual menu, select Import from Repository. Then the [Metadata] wizard is opened.