# Defining the Web service

From the Services item of the Repository tree view, you are able to define the Web service of interest by creating a WSDL file or by importing an existing WSDL file. In this scenario, we will create a new WSDL file to define the airport Web service.

For more information on how to create a WSDL file from scratch, see [Creating a Service](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/creating-service) and [Editing a WSDL file](https://help.qlik.com/talend/r/en-US/8.0/studio-user-guide/editing-wsdl-file).

## Procedure

1. On the Repository tree view, right-click the Services node and from the contextual menu, select Create Service.

   ![New Service dialog box.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-create_service.png)
2. In the pop-up wizard, enter the information corresponding to the fields you need to complete. In this scenario, enter *airport* in the Name field. Click Next to go to the next step.
3. Select the Create new WSDL option.

   ![Assign WSDL dialog box.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-import_wsdl.png)
4. Click Finish to validate this creation.

   The service opens in the design workspace with a basic WSDL skeleton, which contains one service, one binding and one port type of one operation.

   ![Screenshot of the service in the design workspace.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-service_skeleton.png)
5. Right-click the port *airportPort* in the WSDL skeleton and select Show properties. In its Properties view, define its name in the Name field, for example, *airportSoap*. In the Address field, specify the address where you want the service to be published, for example, *http://localhost:8200/airport.service*.

   ![Port properties view.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-airport_port.png)
6. Click the binding in the WSDL skeleton. In its Properties view, define the name of the binding, for example *airportSoap*.

   ![Binding properties view.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-airport_binding.png)
7. Click the portType *airportPortType* in the WSDL skeleton. In its Properties view, define the name of the portType, for example *airportSoap*.

   ![PortType properties view.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-airport_porttype.png)
8. Click the operation *airportOperation* in the WSDL skeleton. In its Properties view, set its name as *getAirportInformationByISOCountryCode*.

   ![Operation properties view.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-airport_operation.png)
9. Save the WSDL file. We will use it to build the Web service.

   Then the newly defined Web service with exclamation icon displays under the Services node of the Repository view. The exclamation icon means that this defined Web service is not yet used.

   ![Screenshot of the new Web service in the Repository view.](https://help.qlik.com/talend/en-US/data-service-route-example/Resources/images/esb-airport_webservice.png)
10. Under the Services node, right-click *airport 0.1* and select Import WSDL Schemas.

    This option imports the WSDL metadata from the service into the Repository, under the Metadata > File xml, which allows you to share the operations details across services and other components.