VMware vCenter Orchestrator (vCO) Click Below for Plug-ins:

vCO Plug-in

Leveraging vCenter 6 vAPI REST endpoint

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
vCenter 6 has introduced an important new feature for anyone interested in Automation and integration : a REST based endpoint providing access to some of the recent functionality such as the tagging service, the content library and transfer service : It is called  "VMware vCloud Suite SDK" and codenamed vAPI. In addition to the REST API it provides language bindings for Java, Python, .NET, Perl and Ruby. If you want to know more about vAPI you can read the blog article I wrote on the VMware CTO Ambassadors blog.
The following article is an introduction to using the vAPI REST Endpoint from vRealize Orchestrator REST plug-in. The concepts in this article may be useful even if you plan to consume the REST service with any REST client.

Synchronize Presentation Settings from embedded workflow

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive
VMware's vRealize Orchestrator (vRO) is all about modular, reusable components. Many times you wish to call an existing workflow from your own custom workflow but don't want to manually re-create all the different presentation settings. It's not such a big task if there are only one or two workflows, but how about when there are 10+ ? Good news is that you don't have to! This quick little video demonstrates how to Synchronize the Presentation of an embedded workflow to your own.

Postman + vRO = HTTP-REST Plug-in Operations

User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

In a previous article, I stepped through the process of working with vRealize Orchestrator's (vRO) REST API using the RestClient add-on for FireFox. This was before I was introduced to my new favorite REST client: POSTMAN! (@postmanclient) In this article, I'll provide a little detail on an approach you can use to improve your work with REST APIs and consuming them with Orchestrator's REST plug-in. Throughout the article, I will use a FreeNAS 9.3.x Virtual Appliance as my target endpoint since it is freely available, quick to setup, and has nice API documentation. Please note that the technique described here can be used for any API that Postman can access!