Composite API/Configuration Tab
Allows you to define general characteristics of the web service representing your process
Title
Name of the Composite API.
Provider url
First part of URL to call Composite API : it is automatically filled up after Composite API creation and can't be modified.
Connector Url
Second part of URL to call Composite API : it is automatically filled up after Composite API creation and can't be modified.
Architecture
Protocol used to start your Composite API (process) : it is REST/XML-RPC
Method
Select the method to use to start the Composite API : GET, POST, PUT, DELETE
Accept media type
Select the media type that RunMyProcess will accept from the web service call to start Composite API (process). Choose "application/json" if you want to use your Composite API within a Web interface API call.
Header a received request are available in a variable called P_header
Input validation
Allows you to define a freemarker script to check if sent parameters within web service call fulfill given criteria. If not, a error message is automatically sent as an answer and Composite API is not started
Result media type
Select the media type that RunMyProcess will set in the response of the web service call. Choose "application/json" if you want to use your Composite API within a Web interface API call.
Result transformation
Allows you to define a freemarker script that will define response of Composite API call :
Code
<root>${P_computed.var1}</root>
Description
Description of Composite API
Please give details of the problem