You can create endpoints that allow vRealize Automation to communicate with the vSphere environment and discover compute resources, collect data, and provision machines.
About this task
For configurations that support vCloud Networking and Security or NSX, see Create a vSphere Endpoint with Network and Security Integration.
Log in to the vRealize Automation console as an IaaS administrator.
A system administrator must install a vSphere agent to correspond to your vSphere endpoints and credentials. See Installing and Configuring the Proxy Agent for vSphere.
The endpoint name you configure in vRealize Automation must match the endpoint name provided to the vSphere proxy agent during installation. If you do not know the endpoint name your system administrator provided to the proxy agent, see Troubleshooting Attached vSphere Endpoint Cannot be Found.
If your system administrator did not configure the proxy to use integrated credentials, you must store administrator-level credentials for your endpoint. See Store User Credentials.
- Select .
- Select .
- Enter a name in the Name text box.
This must match the endpoint name provided to the vSphere proxy agent during installation or data collection fails.
- (Optional) Enter a description in the Description text box.
- Enter the URL for the vCenter Server instance in the Address text box.
The URL must be of the type: https://hostname/sdk or https://IP_address/sdk.
For example, https://vsphereA/sdk.
- Select the Credentials for the endpoint.
If your system administrator configured the vSphere proxy agent to use integrated credentials, you can select the Integrated credentials.
- Do not select Specify manager for network and security platform unless your configuration supports vCloud Networking and Security or NSX.
This setting is for implementations that use vCloud Networking and Security or NSX and requires additional configuration.
- (Optional) Add any custom properties.
- Click OK.
vRealize Automation can now discover your compute resources.
Renaming vSphere assets after discovery can cause provisioning to fail.
What to do next
Add the compute resources from your endpoint to a fabric group. See Create a Fabric Group.