Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

2. Designer

2. Designer

Specifying Deployment Details for a REST-based Process

Specifying Deployment Details for a REST-based Process

When you create a PDD file for a REST-based process, you must add the resource details and policies for the My Role and Partner Role endpoint references.
Partner Role
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.
My Role
For a My Role endpoint reference, ff 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>


Updated March 30, 2020