In this post, you will learn to create REST enabled business services. We will create business service to call the Proxy Service created in previous post.
You can create Business Services directly using WADL if it’s available, or using REST binding wizard similar to Proxy Services. As mentioned earlier, REST Business services convert payload from SOAP to REST i.e. the internal interface is still based on WSDL, while the external business and proxy services expose REST endpoints.
Using WADL:
Drag REST binding into External Services swim lane in Service Bus overview editor as shown below.
Give name as EmployeeBS and Base URI and choose the option as shown below in Operation binding.
Select the WADL as shown below. You can also observe that you can choose resource from several places including MDS.
Click OK and verify that Operation Bindings are populated as shown below.
Click OK to finish the Business service creation.
Using REST Binding:
The steps for creating REST binding for business service are similar to Proxy Service. So follow the steps mentioned in section Creating REST Binding of previous post except giving the base URI.
Testing:
Run the business service and you will observe both SOAP and REST interfaces as shown below along with available operations.
/Employees Resource:
GET:
POST:
PUT:
/Employees/{employeeId} Resource:
GET:
DELETE:
Similarly, you can run SOAP interface of business service by choosing operation and observe the output.
Hi Siva,
I have a REST adapter Business service, Which is a POST operation.
I want to pass path parameter value to REST adapter.
value of path parameter is stored in a variable in pipeline
How to do this?
Can you please help.. i urgently need to complete this particular scenario
Greate article as soon as REST services are great in more web based integration interfaces, should provide lightweight resource schema, and therefore the performance should be better then SOAP. Have you compared the load-performance of pure SOAP vs REST(semi SOAP) services in 12c? This might be very interesting.
Yes. Did not look into it. Just trying to see if any limitations are there in REST support.