# tWebService Calls a method via a Web service in order to retrieve the values of the parameters defined in the component editor. Information noteWarning: This component requires a JDK to be functional. It should be noted that tWebservice will not run in Talend Cloud. tWebservice calls the defined method from the invoked Web service and returns the class as defined, based on the given parameters. ## tWebService Standard properties 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 | Properties | Description | | --- | --- | | 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.

Information noteWarning:

*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, enter the password in double quotes in the pop-up dialog box,
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 | Properties | Description | | --- | --- | | 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 about context variables, see Using contexts and variables.

Note that when parallel execution is enabled, it is not possible to use global
variables to retrieve return values in a subJob. | ## Global Variables | Variables | Description | | --- | --- | | 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 checkbox is
cleared, if the component has this checkbox.

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 more information about variables, see [Using contexts and variables](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/contexts-and-variables). | ## Usage | Usage guidance | Description | | --- | --- | | **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. | **Related concepts** * [Getting country names using tWebService](https://help.qlik.com/talend/en-US/components/8.0/webservice/twebservice-tfixedflowinput-tlogrow-tlogrow-getting-country-names-using-twebservice-standard-component-this)