Quantcast
Channel: VMware Communities : Discussion List - vRealize Orchestrator
Viewing all articles
Browse latest Browse all 6251

vCO sample plugin "SolarSystem" and custom resources in vCAC

$
0
0

Hi guys,

 

i'm fiddeling around using the SolarSystem sample plugin for vCO. Compilation works when done using the eclipse plugin and the import is successfull. I see my SolarSystem plugin in vCO and i'm able to run workflows using it.

Now i want to use it for an advanced service in vCAC - so basically I build a custom workflow which provisions a new SolarSystem:Planet object. From the java source files as far as i know a SolarSystem:Planet object needs 4 parameters: id, name, gravity and circumference. So my workflow simply collects those parameters as input parameters and binds them to the SolarSystem:Planet output parameter object.

 

I double-checked the object is created by printing the object properties in the system console after creation. So next I created a custom ressource (type: SolarSystem:Planet) and a new service for planet creation, which takes my vCO createPlanet workflow and is bound to the SolarSystem:Planet custom ressource as output of the service.

 

The problem is that when a user runs the advanced service, the vCO workflow is run (and finished successfully ) but within vCAC it gets stuck. When looking at the "requests" panel i see that the advanced service is "in progress" but no object (or in vCAC terminology "item" ) is created.

I checked some default workflows (vm copy) for any difference - no luck so far. Now the question remains if it may be something within the custom vCO-Plugin (SolarSystem) that is missing some kind of "object return" which is used by vCAC. Since this was my first shot i have no knowledge about the detailed plugin structure requirements needed for vCAC compatible plugins.

 

 

Any ideas what I'm missing here?

 

 

 

 

greets robert


Viewing all articles
Browse latest Browse all 6251

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>