tWebService Standard properties - 7.3

Webservice

Version
7.3
Language
English
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 Real-Time Big Data Platform
Module
Talend Studio
Content
Data Governance > Third-party systems > Webservice components
Data Quality and Preparation > Third-party systems > Webservice components
Design and Development > Third-party systems > Webservice components
Last publication date
2024-02-21

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

The Standard tWebService component belongs to the Internet family.

The component in this framework is available in all Talend products.

Basic settings

Property type

Either Built-in or Repository.

 

Built-in: No property data stored centrally. Enter properties manually

 

Repository: Select the repository file where properties are stored. The fields that come after are pre-filled in using the fetched data.

Service configuration

Click the [...] button next to the field to open the component editor.

In this editor, you can:

-select the Web service you want to use,

-configure the input parameters of the Web service,

-configure the output parameters of the Web service. These parameters will be used to retrieve and output specific data.

Mapping links display as

Auto: By default, the links between the input and output schemas and the Web service parameters are in the form of curves.

Curves: Links between the schema and the Web service parameters are in the form of curve.

Lines: Links between the schema and the Web service parameters are in the form of straight lines. This option slightly optimizes performance.

Connection Time out

Set a value in seconds for Web service connection time out.

Receive Time out

Set a value in seconds for server answer.

Input schema

A schema is a row description. It defines the number of fields that will be processed and passed on to the next component. The schema is either built-in or remote in the Repository. This field is used to process the input schema. The option for this schema may be:

- Built-in: No property data stored centrally.

- Repository: Select the Repository file where properties are stored. The following fields are pre-filled in using fetched data.

Edit Schema

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.

Sync columns

This button is available when an input link has been created. Click this button to retrieve the schema from the previous component connected in the Job.

Output schema

This field is used to process the output schema. The schema is either built-in or remote in the Repository and is configured the same way as the input schema is.

Warning:

The input schema is not necessarily identical with the output schema.

Use NTLM

Select this check box if you want to use the NTLM authentication protocol.

Domain: Name of the client domain,

Host: Client IP address.

Need authentication

Select this check box and enter a username and a password in the corresponding fields if this is necessary to access the service.

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.

Use http proxy

Select this check box if you are using a proxy server and fill in the necessary information.

Trust server with SSL

Select this check box to validate the server certificate to the client via an SSL protocol and fill in the corresponding fields:

TrustStore file: enter the path (including filename) to the certificate TrustStore file that contains the list of certificates that the client trusts.

TrustStore password: enter the password used to check the integrity of the TrustStore data.

Die on error

Clear this check box to skip the rows in error and to complete the process for the error free rows.

Advanced settings

Temporary folder (for wsdl2java)

Set or browse to a temporary folder that you configured in order to store the wsdl files.

tStatCatcher Statistics

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

Enable parallel execution

Select this check box to perform high-speed data processing, by treating multiple data flows simultaneously. Note that this feature depends on the database or the application ability to handle multiple inserts in parallel as well as the number of CPU affected. In the Number of parallel executions field, either:
  • Enter the number of parallel executions desired.
  • Press Ctrl + Space and select the appropriate context variable from the list. For further information, see Talend Studio User Guide.

Note that when parallel execution is enabled, it is not possible to use global variables to retrieve return values in a subJob.

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.

NB_LINE: the number of rows processed. 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

Usage rule

This component can be used as an input or as an intermediate component. It must be linked to an output component.

Limitation

A JDK is required for this component to operate.