VMware Cloud Community
oendelm
Enthusiast
Enthusiast
Jump to solution

vRealize Orchestrator 7 WebService EndPoint

Hi,

I was using orchestrator 6. I was using the webservice from the orchestrator to call the workflows. The endpoint of the webservice was https://orchestrator_server:8281/vco/vmware-vmo-webcontrol/webservice

Now I have installed the orchestrator 7, but when I try to access the endpoint of the webservice I receive this:

type Status report

message /vco/vmware-vmo-webcontrol/webservice

description The requested resource is not available.


What is the new endpoint to access the webservice? or is there some configuration that I must do? I'm using the appliance version of orchestrator



thanks.

1 Solution

Accepted Solutions
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

The old SOAP API, accessible at /vco/vmware-vmo-webcontrol/webservice, is removed/not available in vRO 7. There is a REST API at https://server:8281/vco/api/ that covers most of the functionality of the old SOAP API plus much more.

View solution in original post

6 Replies
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

The old SOAP API, accessible at /vco/vmware-vmo-webcontrol/webservice, is removed/not available in vRO 7. There is a REST API at https://server:8281/vco/api/ that covers most of the functionality of the old SOAP API plus much more.

Burke-
VMware Employee
VMware Employee
Jump to solution

The correct answer has already been provided here, but to help you get started with using the REST API, have a look at:

If my answer resolved or helped you, please mark it as Correct or Helpful to award points. Thank you! Visit http://www.vcoteam.info & http://blogs.vmware.com/orchestrator for vRealize Orchestrator tips and tutorials - @TechnicalValues on Twitter
FreddyFredFred
Hot Shot
Hot Shot
Jump to solution

Hi Ilian,

We currently use SOAP to start vRO workflows in version 6 via our own custom web portal.

I see nothing in the release notes for version 7 saying SOAP is gone and even the documentation still talks about both SOAP and REST.

I just want to confirm that SOAP really is gone in version 7 and I need to switch to REST before upgrading to version 7 despite the version 7 documentation seemingly making no mention of the change.

Thanks

Reply
0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

Hi,

I'm certain the SOAP is gone in vRO 7 because I removed it from vRO source code repository back in September 2015 Smiley Happy

It should be relatively easy to re-implement your SOAP-based workflow starting code on top of the REST API.

Reply
0 Kudos
FreddyFredFred
Hot Shot
Hot Shot
Jump to solution

I would say that's a pretty good confirmed Smiley Happy  Maybe you can get the documentation team to strip it from the vRO 7 docs and/or make a note of it in the release notes?

We have tried gong to REST back in the 5.1 days but had a problem with holder-of-token or key or something like that. I know things were made easier in newer versions some hopefully it will go better this time.

Thanks

Reply
0 Kudos
iiliev
VMware Employee
VMware Employee
Jump to solution

In current REST API (since 5.1 update 1, I think) there is support for Basic Authentication over SSO, so you may call the API using username/password instead of holder-of-key SAML tokens.

I'll check what is the situation with the documentation.

Reply
0 Kudos