How To Consume Web Service In Rest

REST stands for Representational Land Transfer. Information technology relies on a stateless, client-server, cacheable communications protocol. In virtually all cases, the HTTP protocol is used.

RESTful spider web services are Residual architecture-based spider web services. RESTful spider web services are lightweight, highly scalable, and maintainable, and are very normally used to create APIs for spider web-based applications.

At present we will walk through how to consume RESTful web services with Anypoint Studio.

Consume RESTful Web Service with Anypoint Studio

You lot can use the HTTP Request connector to consume RESTful web services. You demand to specify host, port, and optionally a host path for connector configuration. For Endpoint, you lot need to specify path and method.

Place the HTTP Listener to the source in the flow to receive the input message.

Image title

At present you can place the HTTP Requestor component to Message Processor in flow and configure it. Click Add Connector Configuration and it will open another window. Specify the host, port and, optionally base path and press OK.

Image title

Afterward pressing OK, set the path and method under the URL settings as shown below:

Image title

Passing Argument to RESTful Web Service

For the HTTP Request endpoint, you tin can add parameters:

URI parameters.
Query parameters.
Headers.

Now, y'all will see how to pass URI parameters with the HTTP Asking endpoint. You can apply flow variables to take hold of the query parameter from input request properties of HTTP Listener.

Image title

Under HTTP Request endpoint, ClickAdd Parameter, select uri-param, and specify name and value. Set uri-paramvalue to the dynamic value of Catamenia Variable that nosotros have used to shop the query parameter. The name tin can exist anything.

In this instance, we will utilise proper noun=destination, and then our Path will become /essentials/united/flights/{destination} instead of /essentials/united/flights/CLE.

Image title

Now, your value for the destination is non hard coded and it will be dynamic. It is not necessary to always choice values from the query parameter and store them in the Flow Variable.