Invocation of services
At this point you have deployed your SOAP and REST Data Services in the Denodo internal web container, let's see how to invoke each of them. Also, we will see how to invoke Denodo views as OData and GrahQL services.
Invoke a REST Web service
If you have completed the Basics Tutorial, you already know how to invoke a REST service. Specifically, in Basics Tutorial / Connecting from your App / RESTful Web service you learned how to query a RESTful web service. REST services will work the same way as the RESTful one but, in this case, you only have access to the views created with this REST service.
From a browser, open the URL shown in the Context path of the service:
http://127.0.0.1:9090/server/tutorial/customer.
The browser will ask for the user to connect (admin
/ admin
).
Then, it will load a page like this one:

See the examples below on how to query this service:
- http://127.0.0.1:9090/server/tutorial/customer/views/i_client_info -> should return all client data.
- http://127.0.0.1:9090/server/tutorial/customer/views/i_client_info?client_id=C005 -> should return the data for the client whose client_id equals 'C005'.
This is expected. Remember, you only created the interface to define the contract with your clients. We will add the implementation later.
Invoke a SOAP web service
SOAP Web services are invoked using a SOAP client, for this example, you can download and use SoapUI. It only needs the WSDL file to create a client for the service, after installation.
To get the WSDL for this service, you can open a browser and go to the URL of the service: http://127.0.0.1:9090/server/tutorial/customerws, click on the SOAP link and finally, click on the wsdl link to see the content of the .wsdl file.
Now, open SoapUI and create a new project using the URL of the WSDL. The application will create a request template for your operation. Don't forget to configure the authentication!:
- Username: admin
- Password: admin
- WSS-PasswordType: PasswordText

At this point, the infrastructure for our Web service is completed. Now, every team can work as their own:
- One team can work on the application side to modify the app which will use your new Denodo service.
- The other team (Denodo team), can work on the implementation of the service without modifying the Web service. All changes will be in the Denodo views, and there is no need to re-create the service (if the contract doesn't change).
The next section of the tutorial will show you how to add the implementation to your interface and how the services will return the results without needing to redeploy them.