Add a content endpoint to an environment to capture, test, deploy, or check-in a content package.


Verify that you have added at least one vCenter endpoint.


  1. Under Content Management, click Endpoints.
  2. Click NEW ENDPOINT.
  3. Select vCenter.
  4. Enter the information for the vCenter 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 a content to multiple endpoints at the same time. When you deploy a 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.
  5. In the Server FQDN/IP text box, enter the fully qualified server name, IP address, or host name for the content endpoint server.
  6. To access the endpoint, enter the User name and Password.
  7. Click Test Connection and click Next.
  8. Select the appropriate policies for the content endpoint, and click Next.
    Policy Description
    Allow content to be captured from this endpoint Allows you to capture content from this endpoint and mark them as a source content.
    Allow unit tests to be run on this endpoint Allows content to be tested on this endpoint and acts as a unit test server where a vCenter test content is placed.
    Mark as Production Endpoint Allows you to deploy content to production. When you select this check box to mark as a release endpoint, only then Enable vCenter Template support is enabled.
    Source-controlled Content only Allows deployment of content to an Endpoint that comes only from a Source Control branch. Where in the customization specification needed has to be code reviewed and checked in prior before releasing to vCenter Server. This setting is not used for vSphere templates as they are not checked in to the Source Control. The templates have versions in a vSphere Content Library.
    Enable vCenter Template Support When you enable this option, you are prompted with more fields. The vCenter details page stores information of where the template is deployed to, in each vCenter Server. During the release process, the templates are retrieved from the local Content Library and turned into a Virtual Machine Template.
  9. Click Next and provide the vCenter sever details.
  10. Click Next.
  11. To import an existing data center, click Import Data center.

    vCenter Server settings can be added to an LCM data center, once vCenter data collection is competed this endpoint is seen when importing from LCM and reduces the time to fill in the form as all the properties have been collected. Except the Virtual Machine folder path that is provides in the format /Templates/MyTemplates/ is not imported.

    Once the endpoint is created, it validates if the configuration is correct. It can connect through API and that the configuration of the local subscriber details is setup to point to the publisher as defined in Content Settings/vSphere Template Repository. If there is a problem, then the endpoint is disabled and an error is displayed when you cover of the warning.