Specifying Deployment Details for a REST-based Process

ActiveVOS Designer User’s Guide

Specifying Deployment Details for a REST-based Process

When you create a PDD file for a REST-based process, you must add the appropriate resource details and policies for the My Role and Partner Role endpoint references.

For a Partner role endpoint reference, select REST for the Invoke Handler. You can also add a HTTP Transport Policy Assertion to specify service timeout values.

There are no service bindings in the aeREST.wsdl so you can provide the endpoint reference by supplying the URL to the resource, such as:

 <wsa:Address>http://search.yahooapis.com:80/NewsSearchService/V1/newsSearch</wsa:Address>

To use variable replacements for the specific service of the domain, you can use parameters in the address, such as:

 <wsa:Address>http://nnnn.yahooapis.com:80/NewsSearchService/nn/newsSearch</wsa:Address>

The parameters can then be specified in the request message, as described in Creating a REST-based Receive or Invoke.

For a My Role endpoint reference

If the process is receiving REST requests, you must add a policy assertion for a REST-enabled service.

A REST service context policy example is as follows:

<wsp:Policy

     xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"

     xmlns:aep="http://schemas.active-endpoints.com/ws/

            2005/12/policy">

   <aep:RESTenabled description="short description of the service"/>

   <aep:usage>

    This demo returns search results from multiple

      search engines.

    The accepted url format is:

    http://{host[:port]}/active-bpel/services/REST/

    searchDemo?query=[keyword]

    keyword  - the phrase to be searched for

   </aep:usage>

   </aep:RESTenabled>

</wsp:Policy>