Add vCenter Orchestrator as a vCloud Automation Center endpoint

Yesterday i was about to add vCenter Orchestrator 5.5 (vCO) as an EndPoint in vCloud Automation Center (vCAC) 6.0. The Enpoint option is not available if using the vCloud Suite license. There are quite a few blog posts about this already, you can find one by @viktoriouss here.

This problem will be solved in the near future but if you need to add a vCO endpoint to vCAC before the problem is solved you should be good to go with this solution. Just a little explanation to the names used in the screenshots.

• vcac60a = vCAC SSO Appliance
• vcac60b = vCAC Appliance including vCO
• vcac60c = vCAC IaaS
• vcdx56.com = domain used by all components

So the workaround in this case is to use the vCO workflow available in the vCAC appliance vCO instance. I used the following sequence to add the vCO as an vCAC endpoint.

• Run the vCO workflow “Add a vCAC Host”
  
• • I used the following values while adding the vCAC host.
    Important: The Host parameter should point to the machine where you installed the vCAC IaaS component and not the vCAC Appliance!
    
  • Do not add the domain in the “Authentication user name” text box because if you do, the workflow will fail.
    
    
• The next step is to create the vCAC Endpoint credentials unless you want to add it directly in the vCO workflow. I decided to add it in vCAC.
  
• The last step is to run the vCO workflow “Create a Management Endpoint”
  
  • Select the vCAC IaaS host you just added while running the “Add a VCAC Host” workflow.
    
  • Select vCO as the Endpoint type, remember to add the port/vco in the “URL for management endpoint” and select the vCAC created credentials.
  • 

When the vCO workflow has ended successfully you’ll see and be able to access the vCO Endpoint in vCAC.

Hopefully this issue/problem will be fixed in the vCAC 6.0 SP1 which is expected to be released in the near future.