You can add content from an existing content endpoint.

Prerequisites

Verify that you have added a content endpoint.

Procedure

  1. Under Content Management, click Content.
  2. Click ADD CONTENT.
    Note:

    A content can be added either with the Add Content button or with an inline capture, if a version has already been captured.

  3. Choose whether to test or deploy the content package in addition to capturing it, and click PROCEED.
  4. Enter the capture details for the content package.
    1. From the Select Capture Endpoint drop-down menu, select the endpoint to capture content from.
    2. Select Get the latest content to retrieve the latest content dependencies rather than the dependencies the content was initially captured.
    3. Select the content type and content to capture.
    4. Enter a tag name and select Include all dependencies to capture any dependencies associated with the content.

      You can search for content by tag within the UI/API.

    5. Enter the vRO Package Name or select from the drop-down menu. Any spaces in the name are replaced with an _ underscore character and do not add any external URL to a vRO package name.

      The vRealize Orchestrator package only exist the Content Repository, which can be checked into source control. Once the package is created, you can deploy it to your content endpoint to further work with it. If the vRealize Orchestrator package is not captured before from a given content endpoint, a new version is created but the content might not be the same as the previous version. Deploy the added vRealize Orchestrator package to the vRealize Orchestrator content endpoint first to append the content. If you do not enter any package name, then the name of the vRealize Orchestrator package matches to the content that is captured with an added "-vro" as part of the name. All the discovered and captured vRO content, including individual workflows in the content files, appears in the vRO package that is created.

    6. If the content is ready for production, select Mark this version as production ready.
    7. Enter a description for this content version in the Comments field.
    8. Click Next.
    Note:

    When you list the content for the first time for an endpoint, the UI retrieves the content from the endpoint. However, once you have captured then the content is cached and an auto deploy is run in the background every 20 minutes. You can select the Get latest content option to retrieve the content in between this time.

  5. Enter test details for the content endpoint.

    This option appears only if you chose to test the content package.

    1. Select one or more content endpoints to specify the environments to run tests on.
    2. Select Deploy Content to deploy the content in the endpoint before running tests.
    3. Select Stop test deployment on first failure to stop the test deployment as soon as it encounters an error.
    4. Select Run unit tests to run available unit tests on the content.
    5. Select Stop unit tests on first failure to stop testing if any unit test fails.
    6. Select a server to run unit tests on from the Select a Unit Test Server drop-down menu.

      You must have a vRealize Orchestrator test package imported to use a unit test server.

    7. Click Next.
  6. Enter deployment details for the content package.

    This option appears only if you chose to test the content package.

    1. Select one or more content endpoints from the Select Release Endpoints drop-down menu to specify the production environments where the system releases the content.
    2. Select Stop release deployment on first failure to stop deployment as soon as the system encounters a failure.
    3. Enter a comment that explains why the content is being released in the Release Comment field.
  7. Click SUBMIT.