Burke-'s Posts

When posting question regarding the maven plugin and doing java related tasks for Orchestrator, please post in this SDK group instead of the main Orchestrator Group. That other group is for workf... See more...
When posting question regarding the maven plugin and doing java related tasks for Orchestrator, please post in this SDK group instead of the main Orchestrator Group. That other group is for workflow development, not plug-in/SDK work like this post and your last one. This group should have people better suited to answer your requests
.. Moved to SDK Discussions ..
Moderator - please move this to Orchestrator Community.
.. moved to correct community ..
You mean on the same vCO server as where you created the workflow? If other users are in the group specified as vCO Admins, then they can modify/delete as desired. The exporting of a package with... See more...
You mean on the same vCO server as where you created the workflow? If other users are in the group specified as vCO Admins, then they can modify/delete as desired. The exporting of a package with those restrictions prevents users who IMPORT your package from being able to Modify/Delete/View/.... etc... the workflows contained within your package. If you wish to impose this restriction on your own server where this workflow is created then: 1) export a package with full rights -- leave all checkboxes checked 2) Export a restricted package -- uncheck the desired boxes 3) DELETE your workflow 4) Import your restricted package -- now, regardless of group membership, users are restricted on the workflow(s) that were imported via that restricted package.
Greetings - kind of right idea, wrong section of documentation... don't do anything ON the package, adjust checkboxes when EXPORTING package. See here: Export a Package
Please delete this duplicate post. Other post in Orchestrator community has been provided an answer by me here: Re: Schedule Task X days (or hours) after workflow started
This post should be moved to the Orchestrator community - the plug-in SDK community is for creating vCO Plug-ins. With that said, you'll want to install the SOAP plug-in for vCO. You can then ... See more...
This post should be moved to the Orchestrator community - the plug-in SDK community is for creating vCO Plug-ins. With that said, you'll want to install the SOAP plug-in for vCO. You can then use that to make SOAP based web service calls from vCO to external systems. There is also an HTTP-REST plug-in. https://solutionexchange.vmware.com/store/products/vmware-vcenter-orchestrator-soap-plug-in#.Uk1ppCTTSC0
Please see this KB:  http://kb.vmware.com/kb/2053312 for instructions: Turning off the HTTPS redirect for Web views and SOAP in vCenter Orchestrator (2053312)
Hmm, when I tried to import the o11nplugin-elasticservice-1.0.0-47.vmoapp into my vCO 5.1 server, I got an error: HTTP ERROR 500 Problem accessing /elasticservice-config/Default.action. Reaso... See more...
Hmm, when I tried to import the o11nplugin-elasticservice-1.0.0-47.vmoapp into my vCO 5.1 server, I got an error: HTTP ERROR 500 Problem accessing /elasticservice-config/Default.action. Reason:     PWC6117: File "/WEB-INF/pages/configure.jsp" not found Caused by: org.apache.jasper.JasperException: PWC6117: File "/WEB-INF/pages/configure.jsp" not found I had to click on the plug-in configuration again, then the page loaded properly.
For those interested in learning more about this Elastic Service plug-in, visit: http://www.vmware.com/support/pubs/vco_plugins_pubs.html -- choose "Elastic Service" from the drop-down box, then ... See more...
For those interested in learning more about this Elastic Service plug-in, visit: http://www.vmware.com/support/pubs/vco_plugins_pubs.html -- choose "Elastic Service" from the drop-down box, then hyou'll be provided to links the the .vmoapp download as well as your choice of formats for the plug-in documentation.
Mike, go to http://communities.vmware.com/community/vmtn/developer/forums/orchestrator , under "Resources" click the "Download" button. Login with your account and download the SDK and documentat... See more...
Mike, go to http://communities.vmware.com/community/vmtn/developer/forums/orchestrator , under "Resources" click the "Download" button. Login with your account and download the SDK and documentation - that is What Sergio was referring to.
In your workflow presentation for your Object type that is an input, did you specify the property "Show in Inventory" ?
Hmm.. so the next step in the install doc tells me to modify the maven-build.properties file, implying it was included in the projects I just created... unfortunately, all of the projects appear ... See more...
Hmm.. so the next step in the install doc tells me to modify the maven-build.properties file, implying it was included in the projects I just created... unfortunately, all of the projects appear to be missing all files except for the contents of the o11n-lib folder which contains: testng-5.7-jdk15.jar junit-4.2.jar struts2-core-2.0.11.jar xwork-2.0.4.jar servlet-api-2.4.jar xml-apsi-1.3.03.jar log4j-1.2.14.jar Note regarding my environment: OSX 10.6.7 java version 1.6.0_25 SpringSource Tool Suite 2.7.0.M1 Build Id: 201105101000 vCenter Orchestrator Server is installed on this system Extra note: We should recommend, and hopefully standardize on STS. Why? Includes SpringSource tc Server Developer Edition as a  pre-configured feature, reducing the need to have our SDK users install  Tomcat on their own Is a VMware Branded product Is based on Eclipse Before anyone jumps in and says it is because I'm using STS, I have an update - just downloaded a fresh copy of Eclipse Helios 64-bit for my OSX and tried creating project - same results - missing library, and no source files added to project.... Will check 32-bit version and see if there is any difference... Okay, just finished downloading and testing with 32 bit version of Eclipse Helios - same results as above - no source files in the projects, no maven properties files. That's it for me tonight... look forward to the next round of this SDK
I think it would be great if this SDK would be pre-configured to use relative paths from the installed zip file rather than having to go in after creating the projects and adding files. I'll dig ... See more...
I think it would be great if this SDK would be pre-configured to use relative paths from the installed zip file rather than having to go in after creating the projects and adding files. I'll dig around and try to get these resolved on my own.. this post is simply to say, let's get this resolved before making the SDK widely available. See Screenshot as below: Description    Resource    Path    Location    Type Project 'helloworld' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-sdkapi.jar'    helloworld        Build path    Build Path Problem Project 'helloworld' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-util.jar'    helloworld        Build path    Build Path Problem Project 'helloworld' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-webconfigurationapi.jar'    helloworld        Build path    Build Path Problem Project 'helloworld' is missing required library: '/opt/vmware/vcokit/samples/vCOPluginSDKSamplePlugin-HelloWorld/lib/jboss-common.jar'    helloworld        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/axis.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/commons-discovery-0.2.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/commons-logging.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/jaxrpc.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/jboss-common.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/o11n-sdkapi.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/o11n-util.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/o11n-webconfigurationapi.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/saaj.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem-soap' is missing required library: 'lib/webserviceutils.jar'    solarsystem-soap        Build path    Build Path Problem Project 'solarsystem' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-sdkapi.jar'    solarsystem        Build path    Build Path Problem Project 'solarsystem' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-util.jar'    solarsystem        Build path    Build Path Problem Project 'solarsystem' is missing required library: '/opt/vmware/vcokit/samples/lib/o11n-webconfigurationapi.jar'    solarsystem        Build path    Build Path Problem Project 'solarsystem' is missing required library: '/opt/vmware/vcokit/samples/vCOPluginSDKSamplePlugin-SolarSystem/lib/jboss-common.jar'    solarsystem        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/jboss-common.jar'    solasystem-rest        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/jersey-client-1.5.jar'    solasystem-rest        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/jersey-core-1.5.jar'    solasystem-rest        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/o11n-sdkapi.jar'    solasystem-rest        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/o11n-util.jar'    solasystem-rest        Build path    Build Path Problem Project 'solasystem-rest' is missing required library: 'lib/o11n-webconfigurationapi.jar'    solasystem-rest        Build path    Build Path Problem
Hmm... I haven't personally tried this one.. first thing I would do though, is go into vCenter Orchestrator Configuration (web interface on port 8282) and import the certificate from the POP serv... See more...
Hmm... I haven't personally tried this one.. first thing I would do though, is go into vCenter Orchestrator Configuration (web interface on port 8282) and import the certificate from the POP server I'm trying to use... see if that works, and report back here
Hello there, what you are describing is by design. The Configuration Attributes are intended to be Organization specific settings that should not be stored in exported packages. This way, VMwar... See more...
Hello there, what you are describing is by design. The Configuration Attributes are intended to be Organization specific settings that should not be stored in exported packages. This way, VMware PSO or your favorite partner can create a custom vCO solution that relies on some configuration settings for Infrastructure elements specific to the development environment. When you receive that package, if it had the developers settings, it would not work due to your infrastructure's unique settings and IDs. If you really need to back up your settings, then please see the following thread (Last post by: cdecanini) http://communities.vmware.com/message/1629233#1629233 Visit me at for vCenter Orchestrator tips and tutorials
You're certainly on the right track - well done ! The difference between the two is that one is indeed the API method being shown: VC / VcVirtualMachine.shutdownGuest()But the other is a v... See more...
You're certainly on the right track - well done ! The difference between the two is that one is indeed the API method being shown: VC / VcVirtualMachine.shutdownGuest()But the other is a vCO Action that utilizes that method:com.vmware.library.vc.vm.power.shutdownVM() The API explorer and search tools wil, as you have discovered, find references in the api, but also actions and/or workflows that have been built to utilize those methods. These actions and workflows can be dropped into your own custom workflows to develop as needed. While there are MANY actions pre-built to utilze various api calls, I don't think there is an action for every single call. In some cases, you may need to develop your own. Visit me at for vCenter Orchestrator tips and tutorials
Assumming you have already retrieved a Virtual Machine object and assigned the object a variable name of "vm", the following code in an action or Scriptable task will retrieve the guest IP addr... See more...
Assumming you have already retrieved a Virtual Machine object and assigned the object a variable name of "vm", the following code in an action or Scriptable task will retrieve the guest IP address: var guestIP = vm.guest.ipAddress; You can then return the guestIP variable as your output from that workflow/action. Visit me at for vCenter Orchestrator tips and tutorials