You can configure one or more vRealize Orchestrator integrations, so that you can use workflows as part of extensibility and cloud templates.

With the vRealize Orchestrator integration, you deploy a cloud extensibility proxy instance, that can be used for extensibility subscriptions and XaaS (Anything as a Service) operations used for cloud templates. This deployment includes a preconfigured vRealize Orchestrator 8.x instance that is created after you deploy and power on your cloud extensibility proxy. You cannot integrate external vRealize Orchestrator instances in vRealize Automation Cloud.
Important: Integration of new SaaS-enabled vRealize Orchestrator 7.6 instances is no longer supported. Existing vRealize Orchestrator 7.6 SaaS integrations will continue to operate, but you cannot update the configuration of these integrations. To migrate these vRealize Orchestrator 7.6 SaaS integrations to your new vRealize Orchestrator 8.x integration, see Migrating a vRealize Orchestrator 7.6 SaaS instance to the cloud extensibility proxy.
The vRealize Orchestrator integration in vRealize Automation Cloud uses a Cloud Services Platform (CSP) authentication that provides the same features as external vRealize Orchestrator deployments that use a vRealize Automation license.
Note: vRealize Orchestrator integration in vRealize Automation Cloud does not support changing the license provider for the integration.
For more information on license-based feature availability in vRealize Orchestrator, see vRealize Orchestrator Feature Enablement with Licenses in Installing and Configuring VMware vRealize Orchestrator.

Prerequisites

  • Download and deploy a cloud extensibility proxy. See Download and deploy a cloud extensibility proxy.
  • Verify that your organization has access to the Cloud Assembly service.
  • Verify that you have cloud administrator credentials. See Credentials required for working with cloud accounts in vRealize Automation Cloud.
  • Verify that the users you want to add to the vRealize Orchestrator integration have a Cloud Assembly Administrator or Cloud Assembly User service role. User roles in the vRealize Orchestrator integration are based on Cloud Assembly service roles. For a user to have administrator rights in the vRealize Orchestrator integration, they need the Cloud Assembly Administrator role. For a user to have workflow developer rights in the vRealize Orchestrator integration, they need the Cloud Assembly User role.

Procedure

  1. Select Infrastructure > Connections > Integrations.
  2. Click Add integration.
  3. Select vRealize Orchestrator.
  4. Enter a name for the vRealize Orchestrator integration.
  5. (Optional) Enter a description for the vRealize Orchestrator integration.
  6. Under vRealize Orchestrator URL, enter the fully qualified domain name (FQDN) of your cloud extensibility proxy.
    For example, https:// my_extensibility_va_FQDN.com:443.
  7. Under Cloud extensibility proxy, add your Cloud Assembly cloud extensibility proxy.
    Multiple vRealize Orchestrator integrations cannot share a cloud extensibility proxy.
  8. (Optional) Enter your vRealize Automation Cloud refresh token.
    Note: You can generate a new refresh token from the API Tokens tab of the My Account page. By entering a refresh token, you can access the vRealize Automation Cloud services from the client of the integrated vRealize Orchestrator deployment.
  9. To validate the integration, click Validate.
  10. (Optional) If prompted to do so, review the certificate information, and click Accept.
  11. (Optional) Add capability tags. For more information on capability tags, see Using capability tags in Cloud Assembly.
    Note: Capability tags can be used to manage multiple vRealize Orchestrator integrations. See Managing multiple vRealize Orchestrator integrations with project constraints.
  12. Click Add.
    The vRealize Orchestrator integration is saved.
  13. To verify that the integration is configured and that the workflows are added, select Extensibility > Library > Workflows.

Results

You have created a vRealize Orchestrator integration. After the integration, the vRealize Orchestrator service performs periodic subscription checks that confirm that your organization has access to the Cloud Assembly service. If your subscription to the Cloud Assembly service expires, you will be unable to access the vRealize Orchestrator integration.

What to do next

To create and edit vRealize Orchestrator content in your new integration, navigate to https://my_extensibility_va_FQDN.com:443.