WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud
  • Tanzu
    • Application Modernization
    • Tanzu services
    • Tanzu Community Edition
    • Tanzu Kubernetes Grid
    • vSphere with Tanzu
  • Home Lab
  • Nested Virtualization
  • Apple
You are here: Home / How to Find a vCO Workflow ID

How to Find a vCO Workflow ID

12.08.2011 by William Lam // 3 Comments

Recently while working on my blog post Leveraging vCD + vCO + Wavemaker Part 1, I needed to find the workflowId for the workflow I created in vCenter Orchestrator. The workflowId as one would expect is just a unique identifier for vCO to keep track of all the workflows in the system. When using the vCO Java Client, the workflowId is not something users need to worry about as the workflow names are presented through the client. Though if you are using the vCO API, such as calling the executeWorkflow method, then you will need to know the ID of the given workflow.

There are several ways you can locate the workflowId, here are three different methods:

Method 1:

After creating/editing a workflow, the vCO Java Client creates .vmware directory with some files locally in your home directory. (e.g. in Windows it would be under %userprofile%)

There is a file called "[username]-edited-list.xml" which contains a list of the most recently edited workflows.

When you open the file, you will noticed the very last entry is the workflow that you just created/edited and it displays only the workflowId but not the name. Assuming you are not using a shared account or logging in with same username, this is quick/dirty way of retrieving the workflowId but no easy way to confirm that it is in fact the workflow you are inquiring about.

Method 2:

In the vCO Configuration page, you can enable "DEBUG" logging which will also capture all workflow execution as part of the verbose output including both the name of the workflow that was executed and it's ID within the logs. Once you have captured the workflowId, you can easily revert "DEBUG" mode to "INFO" mode and does not require a restart of the vCO service.

Method 3:

Lastly, you can actually create a workflow in vCO to find the workflowId for a given workflow. Just create a new workflow and give it a name and configure it to take an input string for the name of the workflow and output string for the workflowId.

Here is the vCO script that queries for all workflow's and queries for the specific workflow in question:

Here is what you will see as the output when running the getWorkflowId workflow:

 UPDATE:

Method 4 (Thanks to Jorg Lew) :
You can actually retrieve the workflow ID by just selecting the workflow in the vCO Java Client and pressing CTRL+C (keyboard copy shortcut) and then pasting that into text editor. This will actually display the XML-representation of the workflow.

There are multiple ways to retrieve the workflowId in vCO, but method #4 is definitely what I would recommend as it is the easiest method within the vCO Java Client.

More from my site

  • Extending VSAN capabilities in the vSphere Web Client using vCO
  • Quick Tip - Automate the export of a vCenter Orchestrator workflow using the CLI
  • Changing GuestOS Type Using a Custom vCO Workflow in the vSphere Web Client
  • Org vDC to vCenter Resource Pool Workflow Using vCenter Orchestrator
  • Congratulations to Chris Greer for Winning Automating vSphere with vCenter Orchestrator

Categories // Uncategorized Tags // orchestrator, vCO, workflow

Comments

  1. architecture dissertation says

    03/02/2013 at 10:28 am

    Gratitude for the brilliant knowledge How to Find a vCO Workflow ID ! I just came across your blog and l like the content. I look forward to reading your blog posts in the future,

    Reply
  2. aenagy says

    01/12/2018 at 7:12 am

    The code seems to be missing from #3.

    Reply

Trackbacks

  1. Leveraging vCD + vCO + Wavemaker Part 2 | virtuallyGhetto says:
    03/02/2014 at 6:29 pm

    […] to your vCO server and the workflowId which can be obtained by following this blog post. The workflowInputs requires the name of the workflow input variable name and assuming you followed […]

    Reply

Thanks for the comment! Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Author

William Lam is a Senior Staff Solution Architect working in the VMware Cloud team within the Cloud Infrastructure Business Group (CIBG) at VMware. He focuses on Cloud Native technologies, Automation, Integration and Operation for the VMware Cloud based Software Defined Datacenters (SDDC)

Connect

  • Email
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • Vimeo

Recent

  • How to disable the Efficiency Cores (E-cores) on an Intel NUC? 03/24/2023
  • Changing the default HTTP(s) Reverse Proxy Ports on ESXi 8.0 03/22/2023
  • NFS Multi-Connections in vSphere 8.0 Update 1 03/20/2023
  • Quick Tip - How to download ESXi ISO image for all releases including patch updates? 03/15/2023
  • SSD with multiple NVMe namespaces for VMware Homelab 03/14/2023

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2023