Note: Nov 23rd 2015:
Current active release version for PCS Rest api is bpm/api/3.0
Firstly, a very big thanks you to my colleague Ralf M. for his input here.
Here is my process -
I pick up the wsdl from the management page in Composer -
I use this to create a new project in SOAP-UI.
Here is my request -
Here is the task in Workspace -
Now to the construction of the REST call -
I discussed in a previous post how one can use the REST api
to retrieve processDefId, serviceName and operation.
Now to the payload parameter -
I use the soap-ui request as the basis for the payload value.
Here it is again -
Here is my .json file -
You can download it here
I use ns1 and ns2 instead of nial and _qy
Regarding escape characters - I used this site to validate.
Here is the curl request -
curl -u phillip:welcome1 -H "Content-Type:application/json" -H "Accept:application/json" -X POST -d @NCCreateInstance.json http://YourCloudInstance/bpm/api/1.0/processes
Simple stuff!
Current active release version for PCS Rest api is bpm/api/3.0
Firstly, a very big thanks you to my colleague Ralf M. for his input here.
Here is my process -
I pick up the wsdl from the management page in Composer -
I use this to create a new project in SOAP-UI.
Here is my request -
Here is the task in Workspace -
Now to the construction of the REST call -
I discussed in a previous post how one can use the REST api
to retrieve processDefId, serviceName and operation.
Now to the payload parameter -
I use the soap-ui request as the basis for the payload value.
Here it is again -
Here is my .json file -
You can download it here
I use ns1 and ns2 instead of nial and _qy
Regarding escape characters - I used this site to validate.
Here is the curl request -
curl -u phillip:welcome1 -H "Content-Type:application/json" -H "Accept:application/json" -X POST -d @NCCreateInstance.json http://YourCloudInstance/bpm/api/1.0/processes
I check in Workspace -
Simple stuff!
2 comments:
Like the approach but where did you find the frevvo schema definition?
This should be in the ORCL documentation
Post a Comment