In my previous article How to install vCenter Orchestrator (vCO), I walked you through a screen-by-screen installation of vCO. The only major item lacking from that previous article is the ever-important configuration steps. In the past, many people have had troubles with getting the configuration of vCO correct. This article is an effort to help walk you through each of the screens to provide you insight and recommendations on how to get vCenter Orchestrator configured and working in your environment.

Since vCenter Orchestrator 4.1 PostgreSQL is not listed in the vCO configuration database tab drop down databases list. To enable it back: Edit vmo.properties in C:\\Program Files\\VMware\\Orchestrator\\app-server\\server\\vmo\\conf Add this line: ch.dunes.config.enable-unsupported-db-providers=true Please note that this is an unsupported configuration - Do not do this on production servers !

Since vCenter Orchestrator 4.1 OpenLDAP is not listed in the vCO configuration LDAP tab drop down directory services list. To enable it back: Edit vmo.properties in C:\\Program Files\\VMware\\Orchestrator\\app-server\\server\\vmo\\conf Add this line: ch.dunes.config.enable-unsupported-ldap-providers=true Please note that this is an unsupported configuration - Do not do this on production servers !

vCenter Orchestrator 4.1 has been just released as part of vSphere 4.1. Here is a summary of the main changes since version 4.0, along with our analysis. Improvements Performance and scalability: 5 to 10 times faster than vCO 4.0. 10,000 managed VMs per vCenter Orchestrator Server instead of 3,000 in 4.0! vCO Workflow engine and scripting engine code base has been optimized. Workflows are now processed faster, using fewer resources.

Not out of the box but it can with following these directions.

There are a considerable number of pre-built workflows that may be used to build your own orchestrator solutions. The environment this table is taken from has the VC, VIM3 (OPTIONAL), and Microsoft (OPTIONAL) vmoapps installed: WorkflowDescription \\Library \\Library\\JDBC --- JDBC URL generator Sollicits information to generate a connection URL for JDBC database connections. The workflow emits the connection string it generates as output via the system log, and confirms the string can create a connection to the specified database.

This second tutorial assumes you have completed part 1 and use the Provision VM workflow. Concepts covered in this article include: How to create a Workflow using subworkflows How to map inputs, outputs, and attributes How to use user interactions How to do basic presentations How to use validation presentation properties How to handle exception and write to the event log How to use vCO Server and System objects in scriptable boxes How to use the API search How to launch a Workflow from the vCenter Orchestrator Client How to launch a Workflow from a webview, using the vCenter Orchestrator Weboperator How to set rights on workflows How to set up the vCO mail plug-in NOTE: Webviews were deprecated and removed in vRealize Orchestrator 7.

There are VMware and VMware partner services such as: Consulting services (VMware and partners) - Requirement analysis, implementation workshops Orchestration Solution Centers (VMware and partners) - Design, develop vCO workflows. vCO Instructor Lead Training (VMware) - 5 days

Please contact your VMware sales representative to engage VMware or partners Professional Services. VMware has vCenter Orchestrator Subject Matter Experts in different regions and a development team delivering engagements worldwide.

By using the vCO SOAP or REST plug-in. By writing a vCO plug-in and a Web service client to consume it.