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

For the Automation Orchestrator integration, you must 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 Automation Orchestrator instance that is created after you deploy and power on your cloud extensibility proxy. You cannot integrate external Automation Orchestrator instances in VMware Aria Automation.
Important: Integration of new SaaS-enabled vRealize Orchestrator 7.6 instances is not 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 Automation Orchestrator integration, see Migrating a vRealize Orchestrator 7.6 SaaS instance to the cloud extensibility proxy.
The Automation Orchestrator integration in VMware Aria Automation uses a Cloud Services Platform (CSP) authentication that provides the same features as external Automation Orchestrator deployments that use a VMware Aria Automation license.
Note: Automation Orchestrator integration in VMware Aria Automation does not support changing the license provider for the integration.
For more information on license-based feature availability in Automation Orchestrator, see Automation Orchestrator Feature Enablement with Licenses in Installing and Configuring Automation 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 Automation Assembler service.
  • Verify that you have cloud administrator credentials. See Credentials required for working with cloud accounts in VMware Aria Automation.
  • Verify that the users you want to add to the Automation Orchestrator integration have an Automation Assembler Administrator or Automation Assembler User service role. User roles in the Automation Orchestrator integration are based on Automation Assembler service roles. For a user to have administrator rights in the Automation Orchestrator integration, they need the Automation Assembler Administrator role. For a user to have workflow developer rights in the Automation Orchestrator integration, they need the Automation Assembler User role.

Procedure

  1. Select Infrastructure > Connections > Integrations.
  2. Click Add integration.
  3. Select Orchestrator.
  4. Enter a name for the Automation Orchestrator integration.
  5. (Optional) Enter a description for the Automation Orchestrator integration.
  6. Under 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 Automation Assembler cloud extensibility proxy.
    Multiple Automation Orchestrator integrations cannot share a cloud extensibility proxy.
  8. (Optional) Enter your VMware Aria Automation 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 VMware Aria Automation SaaS services from the client of the integrated Automation 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 Automation Assembler.
    Note: Capability tags can be used to manage multiple Automation Orchestrator integrations. See Managing multiple Automation Orchestrator integrations with project constraints.
  12. Click Add.
    The Automation 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 an Automation Orchestrator integration. After the integration, the Automation Orchestrator service performs periodic subscription checks that confirm that your organization has access to the Automation Assembler service. If your subscription to the Automation Assembler service expires, you will be unable to access the Automation Orchestrator integration.

What to do next

To create and edit Automation Orchestrator content in your new integration, navigate to https://your_extensibility_va_FQDN:443.