VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1 Release Notes

VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1 | 25 April 2014 | Build 1768706

VMware vCenter Orchestrator 5.5.1 | 11 March 2014 | Build 1617131

vCloud Automation Center 6.0.1 | 13 Feb 2014 | Build 1569764

Check frequently for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

Introduction to VMware vCenter Orchestrator Plug-In for vCloud Automation Center

The VMware vCenter Orchestrator vCloud Automation Center plug-in provides access and control over any vCloud Automation Center system. You can use the plug-in to interact with and manage catalog services, catalog items, advanced services custom resources, service blueprints, and resource actions, tenants, approvals and entitlements, work items, and blueprints. The plug-in also allows organizations to automate operations on vCloud Automation Center IaaS model entities. You can use the plug-in to integrate your existing business logic and models with an arbitrary vCloud Automation Center server. You can add a vCloud Automation Center as a policy-based, declarative multi-hypervisor, provisioning functionality to an existing top level service catalog portal. In addition, you can use the vCloud Automation Center plug-in policies to decide where to place a workload when a scale out is needed based on performance triggered by vCenter Operations.

The vCloud Automation Center plug-in enables workflow designers to include create, read, update, and delete operations for an arbitrary vCloud Automation Center model entity in any entity set. In addition, the plug-in provides the capability to dynamically connect to a vCloud Automation Center system and provision a virtual machine from a vCloud Automation Center blueprint.

The VMware vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1 release runs on VMware vCenter Orchestrator 5.5.1. For instructions about installing and configuring the plug-in, see Using the vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1.

For information about vCenter Orchestrator, vCenter Orchestrator plug-ins, or vCloud Automation Center see:

What's New in vCenter Orchestrator Plug-In for vCloud Automation Center 6.0.1

This release of the vCenter Orchestrator Plug-In for vCloud Automation Center introduces the following new functionalities:

  • Works with newer vCloud Automation Center features such as advanced services, multi-tenancy, and service catalogs.
  • You add separate hosts for vCloud Automation Center (vCAC host) and IaaS (IaaS host).
  • You can use the Add an IaaS Host for Infrastructure Administration to easily configure an IaaS host from your vCloud Automation Center host information.
  • You can configure a vCloud Automation Center host for each of your tenants and run workflows on their inventory objects.
  • vCloud Automation Center hosts show new inventory objects such as tenants, catalog items, catalog resources, requests, and work items.
  • The following workflows from vCenter Orchestrator Plug-In for vCloud Automation Center 5.2 have been deprecated and replaced:
    • Provision a virtual machine from a blueprint has been replaced by Request a catalog item
    • Create a Provisioning Group has been replaced by Create a business group
    • Delete a Provisioning Group has been replaced by Delete a business group

Known Issues

Some issues have been discovered through rigorous testing and the following information is intended to help you understand some behavior you might encounter in this release:

  • "Per-user session" authentication is not supported for vCloud Automation Center hosts

    When you configure vCloud Automation Center hosts, you must select "Shared Session" and provide credentials for authentication.

  • vCloud Automation Center 6.0.1 API documentation is still in development

    Workaround:You can download the latest versions of the API documentation from vCloud Automation Center Documentation.

  • Searching for business groups returns results for all hosts

    When you run workflows for updating or deleting business groups, or adding, updating, or deleting custom properties for a business group from the Workflows view, there is no option to restrict the search function to a particular vCloud Automation Center host.

    Workaround: Run these workflows from the Inventory view. Right-click the business group you want to update and select the workflow you want to run.

  • Error Messages for interactions with deleted objects

    If you attempt to execute workflows on deleted objects, for example if you attempt to update an identity store that has been deleted in vCloud Automation Center, the error messages you receive may not explain that the object no longer exists.

    Workaround: You can manually refresh the inventory in vCenter Orchestrator when objects are removed in vCloud Automation Center. Right-click the vCloud Automation Center host in the Inventory view and select Reload.

  • Out-of-the-box plug-in workflows do not provide the same validation as vCloud Automation Center UI

    The vCloud Automation Center user interface performs validation checks, but not all of this logic is accounted for in the workflows provided with the plug-in. For example, vCloud Automation Center prevents you from creating a tenant with a non-unique URL, but the plug-in workflow does not validate this. Ensure that your custom workflows take care of any validation required by vCloud Automation Center.

  • vCACCAFEAuthenticationGroupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType does not take groupType into account

    The vCACCAFEAuthenticationGroupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType(tenant, criteria, domain, parentGroup, groupType) method does not take groupType into account.

    Workaround: You can iterate on the result and filter for a group type, for example:

    var childGroupsOfAllTypes = groupService.getGroupsByCriteriaAndDomainAndParentGroupAndGroupType(tenant, criteria, domain, group.getPrincipalId().asString(), vCACCAFEType.fromValue("CUSTOM"));

    var childCustomGroups = new Array();

    for ( var i = 0; i < childGroupsOfAllTypes.length; i++) {

    if (childGroupsOfAllTypes[i].getGroupType() == vCACCAFEType.fromValue("CUSTOM")) {

    groupsOfAllTypes = childGroupsOfAllTypes[i];



  • The vCACCAFEAuthenticationGroupService.updateCustomGroup method removes all members of the updated group

    Workaround: Before using the vCACCAFEAuthenticationGroupService.updateCustomGroup method, retrieve the group members and reassign them to the group after the update, for example:

    // Create a vCACCAFEAuthenticationGroupService instance to perform operations, where host is the vcac host cofigured by the vcaccafe plug-in.

    var groupService = host.createAuthenticationClient().getAuthenticationGroupService();

    // Retrieve current members, where groupToBeUpdated is the target custom group

    var membersUsers = groupService.getUsersInGroup(tenant, groupToBeUpdated, criteria, pageable);

    var membersGroups = groupService.getGroupsByCriteriaAndDomainAndParentGroup(tenant, criteria, domain, groupToBeUpdated);

    // Update the group, retrieve the updated group, and reassign the members:

    groupService.updateCustomGroup(tenant, groupToBeUpdated);

    var updatedGroup= groupService.getGroup(tenant, groupToBeUpdated.getPrincipalId().asString());

    groupService.assignGroupsAndUsersToCustomGroup(tenant, updatedGroup, membersGroups, membersUsers);

Top of Page