I'm personally unsure - I haven't tried using it at all yet. When asking about specific plug-ins or products, it is better to post your question to the Orchestrator communities at VMware. The authors here AND, even better, the engineering teams of VMware monitor the communities and regularly answer questions there.

Please download the package that is linked at the end of the tutorial and compare what we have in our package against what you have done - that will help you identify where you went wrong. We cannot provide webex support and assistance for the tutorials we write here as our schedules and responsibilities do not allow for it.

I'm confused - you quoted "No need to set a value for this one, the Workflow will when completing"... then you state "I am not sure what values to assign to these" .... You don't assign values, you just do the bindings... the workflow sets the values when it runs - just like what you quoted...

I think they're stored in an archive on the server that is unpacked when the service starts up. You do NOT edit any html files directly on the server. You have to export the files from your webview to a local folder, edit them, then import them back to the server and re-publish the webview to see your changes.

It sounds like you may not have restarted the vCenter Orchestrator Server service after installing the Microsoft AD Plug-in. You must restart the service after ANY Plugin installations so that the install may be completed. After the restart, vCO should recognize all the AD: objects ;)

Hello Dan, thanks for pointing out the typo - it is fixed now :)

Thanks for pointing out the typo - it should be fixed now :)

I never did get around to doing that... it's quite easy though - I'll post as a comment to the thread on the Communities for everyone's benefit so go take a look ;)

Yes, at this time, vCO offers a SOAP based api that you may use to kick off workflows from your external system. Check the vCO documentation to learn more :)

Please notify VMware directly on any issues with this plugin. Thank you.

Check your "server.log" file after receiving a validation error. It will tell you which field is giving the validation error and most likely help you identify what is going wrong with your inputs.

The API Explorer is your friend. Start by locating the host (VC:HostSystem) scripting object. Look through the properties for something that looks like VM. You'll find a property named .vm that returns an array of VC:VirtualMachine objects. Now all you need is the count of the array - for javascript, that is the .length property. So, assuming your variable name is host, your code would look like this: var hostVMCount = host.vm.length; Do the same routine to identify vm count on a datastore (assuming variable name of "datastore", this would look like the following)... var datastoreVMCount = datastore.vm.length;

No, you are not able to revert to a previous version, yes it is essentially to let you document changes. The versioning mechanism is used when importing/synchronizing elements to/from your vCO server. The version number is evaluated against what is on the target server to determine if the number is greater and if so, shows a green arrow in the summary to indicate the newer item will be imported. True versioning has been a long-standing request from internal (VMW) and external users of vCO.

The two most common items resulting in this issue are: 1) Insufficient RAM. In older versions of vCO, 2GB was sufficient. However, with 4.x versions, the requirement is 4GB for production use. If you only allocate 2 GB for a current version of vCO, the service is very unlikely to start. 2) VIX Plugin. Many people neglect to unzip the VIX library files and add the path to those unzipped files to the vCO server PATH environment variable. While this does not prevent the service from starting, it does prevent most workflows from executing. Please check the two items above. If there are still issues, it would be best for you to post to the VMware Communities for support or call GSS. Be sure to have your log files ready for review in either case.

Please check the VMware Communities regarding this issue.. I believe Joerg Lew posted a comment about reading the release notes for a configuration change. http://communities.vmware.com/message/1845183

Hello Steve, That's a great idea :) and it is indeed possible. Perspectives has a webview that you interact with. Since this is the case, you should have a look at the article: http://www.vcoteam.info/learn-vco/create-a-simple-vco-self-service-vm-provisioning-portal-part-3.html . In that article, scroll down to the section titled "Working with Webview Files" and begin working there. While you're looking over the files and trying to figure out which classes of CSS to modify, it is best to use FireFox with the FireBug Add-On. For example, browse to your http://vcoserver:8280/vmo/perspectives. Login and then right-click up in your title-bar area and then select "Inspect Element". The Firebug pane opens in the bottom half of your browser with the source code of the page. As you mouse over different elements, that element highlights on the page. Click on the image/area/div you wish to see the style definition for and it will be displayed in the right pane. Once you have identified the elements you wish to change, modify the appropriate css file and place your images in the corresponding folder of your webviews export, then import to vCO and publish the webview to test!! Some relevant files (available after exporting the webview as outlined in that other article): /css/perspectives.css /css/perspectivesIE6.css /css/perspectives/IE7.css /images/perspectivesLogo.gif /components/layout/PerspectivesBorder.html The css and gif files are obvious, but the PerspectivesBorder.html file may throw up a question mark - this is essentially the main formatting file for all your Perspectives pages. To affect a change across all perspectives beyond just the CSS styling, this is the place to do it. Good luck!

This could be due to not having any msgs on the bus yet... Within vCD, have you enabled any blocking tasks or turned on non blocking notifications? after having one or both of those enabled, you should generate activity within vCD to initiate a message to the AMQP bus, creating the exchange... let us know if that works. I ran into the same issue when I first ran QA on this article.

Yes, it does

Thanks for the feedback We're a step ahead though with 2 articles currently drafted and in the process of being reviewed and finalized for publication in the near future!

DCoulter - Have you compared your work with that of the work provided in the solution package linked at the end of this article?

Please reference this post in the VMware Communities: http://communities.vmware.com/message/1296408#1296408: http://communities.vmware.com/message/1296408#1296408 Although that post is for an older version, the general location should be accurate for current releases as well.

If you continue to be stuck, you can go to the bottom of the part 3 and download the solution as a .package which may then be imported into your vCO server

SCP - please continue on with PART 3 as it has some updates to the permissions to allow this to really function.

Terry - Have you imported the package linked at the bottom of the article and compared your code against mine?

Hello John, seems you missed a step. After extracting the zip file, you need to review the Readme.html file: vCO JavaScript Interpreter To use the generated JavaScript in a vCO workflow 1. Create a new module in the Actions tab named "com.vmware.onyx". 2. Right-click on the new module and add the action array.action that is located in "\Extensions\Onyx.Interpreters.VcoJavaScript". 3. Copy the generated script into a scripting task and modify it to suit your needs. However, I personally don't even like that piece - I don't use it. All it is doing is creating an array of objects. So, when you see that code, you can recode the output script using a standard array. Also, be sure to pay attention to the comments in the code as they let you know what kind of objects you are dealing with. So a little bit of knowledge is certainly required to get Onyx generated scripts to work correctly - they don't work without modification.

Greetings Martin, indeed they can. Please see the section "Setting Permissions" on page: Create a simple vco self service vm provisioning portal part 3: http://www.vcoteam.info/learn-vco/create-a-simple-vco-self-service-vm-provisioning-portal-part-3.html

To make everyone's life just a little bit easier, I have just added a .package file to the end of the article that you are welcome to download. The file may be imported into your vCO client to see the full working solution of this tutorial. Enjoy!

Daniel, did you try importing the package file that is attached to this article? The webview in there should be fully functional. All the screenshots taken here were done as I developed the webview and then I packaged everything together and provided at the end of the article as a download.

Just in case anyone is interested and has access to VMworld sessions, a direct link to this session is here: http://www.vmworld.com/docs/DOC-4683

Jared - I think I have fixed the code for the Custom Send Interaction snippet - sorry about that, the CMS had messed things up due to the escaped quotes. I've re-checked the code that I now see after re-saving the article and that snippet now looks accurate and matches my vCO Server :) Karlo - What version of vCO are you using? 4.1? My environment does not require a span tag - the code snippet shown here is what I have in my webview. P.S. Package Solution File Added as download!

There appears to be a problem with the code being pasted into the Content Management System here... I'm working to resolve the issue now.

FYI: I've just added a download link for you to grab the package for this work just in case you ran into any problems.

Just a little note here - I will be co-presenting the Orchestrating the Cloud session in which I will highlight the use of a new vCenter Orchestrator plugin :)