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


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


  1. Under Content Management, click Endpoints.
  2. Click NEW ENDPOINT.
  3. Select Orchestration.
    For an Orchestrator content, you can capture workflows, configuration elements, and actions individually or in a folder where they reside.
    Note: If a folder is captured, a temporary content name starting with [FOLDER] is displayed. You can start a Content Pipeline to capture all content, this is then added to the vRO Package provided as input.
  4. Click Next.
  5. Enter the information for the vRealize 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 Sever FQDN/IP field, enter the fully qualified server name, IP address, or host name for the content endpoint server.
      If the vRealize Orchestrator instance is not embedded in vRealize Automation, include the port number in the server FQDN/IP. Typically the port number is 8281.
    4. Enter a user name and password to use to access this content endpoint.
  6. 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.
  7. Select vRO Package.
    The vRealize Orchestrator package can be captured from an endpoint and is associated with the content endpoint. Selection of a vRO package is a post deployment capability that imports the package once any other can has been deployed allowing localized or regional settings to be maintained.
    • Ignore modules when listing content: A comma-separated list of vRealize Orchestrator Actions or modules that are excluded when listing from an endpoint to reduce the number. With Lifecycle Manager 2.1, any module or folder with or without any dependencies can be excluded while capturing or listing the content. However, for Orchestrator-package these modules or folders are not ignored. Lifecycle manager 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 vRealize Orchestrator Workflow folders that are excluded when listing from an endpoint to reduce the number.
  8. Select the appropriate policies for the content endpoint, and click Next.
    Policy Description
    Mark as a source content endpoint to capture content Allows you to capture content from this endpoint and mark them as a source content.
    Allow Unit tests to run on this content endpoint Allows content to be tested on this endpoint and acts as a unit test server where vRealize Orchestrator workflows test content is placed.
    Mark as Production content endpoint Allows you to deploy content to production.
    Source Control Enabled Allows you to enable if you plan to check in or check out content to or from the vRO endpoint. Enabling source control is a best practice when working with multiple users or vRealize Orchestrator Endpoints in which the same content is worked on. This policy prevents non source-controlled versions be deployed to this endpoint, so that all git commit codes are maintained against this server.
  9. Verify that the content endpoint details are correct, and click Submit.