To add a VMware Aria Automation Orchestrator, use the Content Management service in VMware Aria Suite Lifecycle.

A VMware Aria Automation Orchestrator endpoint is required to create VMware Aria Automation endpoints and to capture content.

Prerequisites

If you are using a VMware Aria Automation Orchestrator endpoint for unit testing, verify that the VMware Aria Automation Orchestrator instance has been configured as a unit test server.

Procedure

  1. On the My Services dashboard, click Content Management.
  2. Under Endpoints, click NEW ENDPOINT.
  3. Click VMware Aria Automation Orchestrator.
    For VMware Aria Automation Orchestrator content, you can capture workflows, configuration elements, and actions individually or in the folder in which they reside.
    Note: If a folder is captured, a temporary folder content name is displayed. You can start a content pipeline to capture all content. Add the pipeline to the VMware Aria Automation Orchestrator package as input.
  4. Enter the information for the VMware Aria Automation Orchestrator content endpoint.
    1. In the Name text box, enter a unique name for the endpoint.
    2. In the Tags text box, enter tags associated with the endpoint.
      Using tags allow you to deploy content to multiple endpoints at the same time. When you deploy content, you can select a tag instead of individual content endpoint names, and the content deploys to all endpoints that have that tag.

      To add multiple tags, press Enter after you enter each tag.

    3. In the Server FQDN/IP field, enter the fully qualified server name, IP address, or host name for the content endpoint server.
      If the VMware Aria Automation Orchestrator instance is not embedded in VMware Aria Automation, include the port number in the server FQDN/IP. For VMware Aria Automation Orchestrator, the port is not required.
      vRO-Server-FQDN:Port
    4. Enter a user name and password to use to access this content endpoint.
  5. Press TEST CONNECTION to test the connection to the content endpoint.
    If the connection test fails, verify that the information you entered for the content endpoint is correct and try again.
  6. Select vRO Package.
    The VMware Aria Automation Orchestrator package can be captured from an endpoint and is associated with the content endpoint. Mark the version as Production ready. Selection of a VMware Aria Automation Orchestrator package is a post deployment capability that imports the package once any other content has been deployed allowing maintained localized or regional settings.
    • Ignore modules when listing content: A comma-separated list of VMware Aria Automation Orchestrator Actions or modules that are excluded when listing from an endpoint to reduce the number. With VMware Aria Suite Lifecycle, any module or folder with or without any dependencies can be excluded while capturing or listing the content. However, for VMware Aria Automation Orchestrator-packages these modules or folders are not ignored. VMware Aria Suite Lifecycle validates the content dependencies available in the source endpoint while capturing with dependencies. This depends on the policy specified on the endpoints.
    • Ignore Workflows in these folders: A comma-separated list of VMware Aria Automation Orchestrator workflow folders that are excluded when listing from an endpoint to reduce the number.
    • A VMware Aria Automation Orchestrator package name cannot contain special characters and can cause issues when you capture, release or check-in a content. If you have a VMware Aria Automation Orchestrator package name with a space in between the name, then the space is converted to an underscore (_) during a capture and fails during a test and deploy.
  7. Select the appropriate policies for the content endpoint, and click Next. For more information on policies, refer to the policy table provided in Working with content endpoints in VMware Aria Suite Lifecycle.
  8. Verify that the content endpoint details are correct, and click Submit.