kumarsenthild
Enthusiast
Enthusiast

Invoke REST Operation || vRO connect to another vRO with HTTP_REST plugin

Jump to solution

Hi Friends,

Customer request to connect client vRO server to new vRO server and run the workflow.

So I have connected new vRO server using HTTP_REST plugin and  I have created Rest Operation to execute the workflow.

When i try to invoke the Rest Operation , I am getting status code :302. May be i am missing something in content.

Can you please help me on this.

Note :- I tested same thing in vRO Swagger, able to trigger the workflow (status code 202).  https://192.168.1.23:8281/vco/api/docs/index.html#!/execution-controller/startWorkflowExecutionUsing...

Content :   

Test-1

{

  "executionId": "string",

  "parameters": [

{

"value": {"string":{ "value": "InputValue"}},

"type": "string",

"name": "Input1",

"scope": "local"

},

{

"value":{"number":{"value": "20"}},

"type": "number",

"name": "Size",

"scope": "local"

}

  ]

}

Test-2

{

  "parameters": [

{

"value": {"string":{ "value": "InputValue"}},

"type": "string",

"name": "Input1",

"scope": "local"

},

{

"value":{"number":{"value": "20"}},

"type": "number",

"name": "shareSize",

"scope": "local"

}

  ]

}

RestOp.PNG

invoke1.PNG

invoke2.PNG

invoke3.PNG

Regards Senthil Kumar D
1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee

Hi,

Operation URL should be /vco/api/workflows/{workfloid}/executions instead of /api/workflows/{workflowid}/executions

The URL without /vco/ prefix was used in vCO 5.1 and in newer vRO it is still there but just redirects (for clients that are able to follow redirects properly) to the new URL. That's why you are getting status 302 (Found)

View solution in original post

2 Replies
iiliev
VMware Employee
VMware Employee

Hi,

Operation URL should be /vco/api/workflows/{workfloid}/executions instead of /api/workflows/{workflowid}/executions

The URL without /vco/ prefix was used in vCO 5.1 and in newer vRO it is still there but just redirects (for clients that are able to follow redirects properly) to the new URL. That's why you are getting status 302 (Found)

kumarsenthild
Enthusiast
Enthusiast

I found this myself after two hours. Forgot to post here.

Thank you very mate

Regards Senthil Kumar D
0 Kudos