Configuration idea on REST driver

We are configuring REST driver which will communicate with REST APIs.
We done some basic configuration, but we don't have any such idea that how REST driver work.
Is there any way to make RESTFUL APIs from REST driver with basic authentication where outside application request that REST API and get response data?
Or there are any other mechanism where REST Driver communicate with target applications?
Please suggest something so we can proceed the complete configuration of REST driver.
Thanks in advance.
  • REST Driver is intended to communicate with RESTFUL APIs of Applications. So of course this driver can communicate in such a way and it will also come back to ITP with Responses or Input from those Applications.
    But first of course you will have to understand what the REST Driver will provide for you. This is similar to a text based (Delimited Text / XML) driver. It gives you a framework to communicate. Anything else you have to do.
    First set up a SOAPUI Project to get an idea about the wsdl and the functions / responses of your app.
    Then set up OTP Policies which will transform the standard XML Document from the driver into the correct wsdl-conform Document for your API. If you like, the driver will add the Auth header with username/password for you. But you can add the Auth header also by OTP Policies in case you want WSSE or some more complex Authentication.
  • On 9/7/2018 2:04 AM, ukrause wrote:
    >
    > REST Driver is intended to communicate with RESTFUL APIs of
    > Applications. So of course this driver can communicate in such a way and
    > it will also come back to ITP with Responses or Input from those
    > Applications.
    > But first of course you will have to understand what the REST Driver
    > will provide for you. This is similar to a text based (Delimited Text /
    > XML) driver. It gives you a framework to communicate. Anything else you
    > have to do.
    > First set up a SOAPUI Project to get an idea about the wsdl and the
    > functions / responses of your app.
    > Then set up OTP Policies which will transform the standard XML Document
    > from the driver into the correct wsdl-conform Document for your API. If
    > you like, the driver will add the Auth header with username/password for
    > you. But you can add the Auth header also by OTP Policies in case you
    > want WSSE or some more complex Authentication.


    I used to say the eDir to eDir was the hardest driver to learn, but SOAP
    and REST are also pretty tough or tougher.

    Though WSDL is for SOAP, WADL is for REST. (Nits, pick they selves!)