Managing multiple Automation Orchestrator integrations with project constraints

You can use project constraints to manage what Automation Orchestrator integrations are used in workflow subscriptions.

Automation Assembler supports the integration of multiple Automation Orchestrator servers that can be used in workflow subscriptions. You can manage what Automation Orchestrator integrations are used in cloud templates provisioned by your project with soft or hard project constraints. For more information on project constraints, see Using Automation Assembler project tags and custom properties.

Prerequisites

• Verify that you have cloud administrator credentials. See What are the VMware Aria Automation user roles.
• Configure two or more Automation Orchestrator integrations in Automation Assembler. See Configure an Automation Orchestrator integration in Automation Assembler.
• Add capability tags to your Automation Orchestrator integrations. See Using capability tags in Automation Assembler.

Procedure

1. Navigate to Infrastructure > Administration > Projects and select your project.
2. Select the Provisioning tab.
3. Enter the capability tags of your Automation Orchestrator integrations in the Extensibility constraints text box and set them as soft or hard project constraints.
4. Click Save.

Results

When you deploy a cloud template, Automation Assembler uses the project constraints to manage what Automation Orchestrator integrations are used in workflow subscriptions.

What to do next

Alternatively, you can use capability tags to manage multiple Automation Orchestrator integrations on a cloud account level. For more information, see Managing multiple Automation Orchestrator integrations with cloud account capability tags.