Apps and tools built by our engineers that are intended to be played with and explored.




vCO-CLI aims to provide exploratory programming to the vCO ecosystem. It connects to a running vCO server and presents a JavaScript REPL (Read-Eval-Print-Loop) to the user. All vCO plug-ins, workflows and the entire scripting API can be accessed, invoked and experimented with from the shell. This turns vCO-CLI into a powerful educational and experimentation tool.

Access to the plug-in’s inventory is integrated into the UI for easy navigation to managed entities (vCenter objects, LDAP entries, remote systems, HTTP endpoints, etc).

For advanced users, vCO-CLI can improve productivity considerably by minimizing the turnaround time between designing and running a workflow. It can also display a REPL right in the middle of a workflow. This powerful technique, similar to a breakpoint, allows the workflow developer to troubleshoot and fix bugs faster.

System Requirements

You need to have JRE 1.6 or higher installed.


Simply install the vCOCLI plug-in on vCO Server (description below) and export the console or GUI based client on your machine (vcocli.bat/vcocli.sh or vcocli-gui.bat)

Step by step plug-in installation:
1.  Log into vCO Configurator.
2.  Click on Plug-ins and browse the o11nplugin-vcocli.vmoapp file.
3.  Click on Start-up Options and restart vCO service.
4.  To verify the installation, log in vCO Smart Client and check if vCO CLI plug-in is installed.


Change Log


Julian Vassev

vCO Team

Aleksandar Lazarov

vCO Team
Add Comment

8 thoughts on “vCO-CLI

  1. Mike Preston

    export the console or GUI based client on your machine (vcocli.bat/vcocli.sh or vcocli-gui.bat) ???

    Not too sure what this means – I have the plug-in installed, but that’s as far as I have gotten :)

    1. chouki2000

      I have the same question that Mike!

      “export the console or GUI based client on your machine (vcocli.bat/vcocli.sh or vcocli-gui.bat)” : what does it mean ?? how can we do it ?

      1. B

        I am in the same boat. Not sure if you figured it out now but this will help people later.

        In the download options, there are 3 downloads:
        1. is the actual plugin (install this into your Orchestrator like any other plugin)
        2. is the GUI or client scripts for Linux
        3. is the GUI or client scripts for Windows

        So basically you need to download the plugin, install it, then download the client for your OS.

        If you have a firewall between your client and Orchestrator server, ensure port TCP 8265 is allowed.

  2. Steven T

    I have installed the plugin and I can see it in the Orchestrator client. I cannot get the vCO CLI to connect. Can you provide any more detail on establishing a connection through the CLI GUI?

  3. Ronald Rink [d-fens]

    Very cool and long overdue. Good to see that vCO is actually making some progress towards a more usable developing environment.

  4. Paul Poppleton

    Great job! I just installed this in my dev environment and I am loving being able to have an interactive command shell! One thing that would be great to see in the output window though are the log messages. Maybe have an option to toggle those on and off?


Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>