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

Prerequisites

Verify that you have added at least one vCenter endpoint in the Content Settings > vSphere Template Repository .

Procedure

  1. On the My Services Dashboard, click Content Management.
  2. Under Endpoints, click NEW ENDPOINT
  3. Click vCenter Server.
  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. For more information on policies, refer to the policy table provided in Working with Endpoints.
  9. Click Next and provide the vCenter sever details.
  10. Click Next.
  11. To import an existing data center, click Import LCM 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.