<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Invoke REST Operation || vRO connect to another vRO with HTTP_REST plugin in VMware Aria Automation Orchestrator Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496523#M3934</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Operation URL should be &lt;STRONG&gt;/vco/api/workflows/{workfloid}/executions&lt;/STRONG&gt; instead of &lt;STRONG&gt;/api/workflows/{workflowid}/executions&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jun 2018 13:29:43 GMT</pubDate>
    <dc:creator>iiliev</dc:creator>
    <dc:date>2018-06-19T13:29:43Z</dc:date>
    <item>
      <title>Invoke REST Operation || vRO connect to another vRO with HTTP_REST plugin</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496522#M3933</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Customer request to connect &lt;STRONG&gt;client vRO server&lt;/STRONG&gt; to &lt;STRONG&gt;new vRO server&lt;/STRONG&gt; and run the workflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I have connected new vRO server using HTTP_REST plugin and&amp;nbsp; I have created Rest Operation to execute the workflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When i try to invoke the Rest Operation , I am getting status code :&lt;STRONG&gt;302. &lt;/STRONG&gt; May be i am missing something in content.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please help me on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note :- I tested same thing in vRO Swagger, able to trigger the workflow (status code 202).&amp;nbsp; &lt;A href="https://192.168.1.23:8281/vco/api/docs/index.html#!/execution-controller/startWorkflowExecutionUsingPOST_3" title="https://192.168.1.23:8281/vco/api/docs/index.html#!/execution-controller/startWorkflowExecutionUsingPOST_3"&gt;https://192.168.1.23:8281/vco/api/docs/index.html#!/execution-controller/startWorkflowExecutionUsingPOST_3&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Content :&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Test-1&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp; "executionId": "string",&lt;/P&gt;&lt;P&gt;&amp;nbsp; "parameters": [&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;"value": {"string":{ "value": "&lt;STRONG&gt;InputValue&lt;/STRONG&gt;"}},&lt;/P&gt;&lt;P&gt;"type": "string",&lt;/P&gt;&lt;P&gt;"name": "&lt;STRONG&gt;Input1&lt;/STRONG&gt;",&lt;/P&gt;&lt;P&gt;"scope": "local"&lt;/P&gt;&lt;P&gt;},&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;"value":{"number":{"value": "&lt;STRONG&gt;20&lt;/STRONG&gt;"}},&lt;/P&gt;&lt;P&gt;"type": "number",&lt;/P&gt;&lt;P&gt;"name": "&lt;STRONG&gt;Size&lt;/STRONG&gt;",&lt;/P&gt;&lt;P&gt;"scope": "local"&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp; ]&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Test-2&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;&amp;nbsp; "parameters": [&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;"value": {"string":{ "value": "&lt;STRONG&gt;InputValue&lt;/STRONG&gt;"}},&lt;/P&gt;&lt;P&gt;"type": "string",&lt;/P&gt;&lt;P&gt;"name": "&lt;STRONG&gt;Input1&lt;/STRONG&gt;",&lt;/P&gt;&lt;P&gt;"scope": "local"&lt;/P&gt;&lt;P&gt;},&lt;/P&gt;&lt;P&gt;{&lt;/P&gt;&lt;P&gt;"value":{"number":{"value": "20"}},&lt;/P&gt;&lt;P&gt;"type": "number",&lt;/P&gt;&lt;P&gt;"name": "shareSize",&lt;/P&gt;&lt;P&gt;"scope": "local"&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&amp;nbsp; ]&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="RestOp.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/1665iC54F0CD009811AB7/image-size/large?v=v2&amp;amp;px=999" role="button" title="RestOp.PNG" alt="RestOp.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="invoke1.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/1677iD21FA0B911814302/image-size/large?v=v2&amp;amp;px=999" role="button" title="invoke1.PNG" alt="invoke1.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="invoke2.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/1679i3ED1CE4A3FC80A46/image-size/large?v=v2&amp;amp;px=999" role="button" title="invoke2.PNG" alt="invoke2.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="invoke3.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/1681iEEAEEAA6DC77E463/image-size/large?v=v2&amp;amp;px=999" role="button" title="invoke3.PNG" alt="invoke3.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 06:18:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496522#M3933</guid>
      <dc:creator>kumarsenthild</dc:creator>
      <dc:date>2018-06-19T06:18:43Z</dc:date>
    </item>
    <item>
      <title>Re: Invoke REST Operation || vRO connect to another vRO with HTTP_REST plugin</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496523#M3934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Operation URL should be &lt;STRONG&gt;/vco/api/workflows/{workfloid}/executions&lt;/STRONG&gt; instead of &lt;STRONG&gt;/api/workflows/{workflowid}/executions&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 13:29:43 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496523#M3934</guid>
      <dc:creator>iiliev</dc:creator>
      <dc:date>2018-06-19T13:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: Invoke REST Operation || vRO connect to another vRO with HTTP_REST plugin</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496524#M3935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I found this myself after two hours. Forgot to post here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very mate&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2018 17:57:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Automation/Invoke-REST-Operation-vRO-connect-to-another-vRO-with-HTTP-REST/m-p/496524#M3935</guid>
      <dc:creator>kumarsenthild</dc:creator>
      <dc:date>2018-06-19T17:57:26Z</dc:date>
    </item>
  </channel>
</rss>

