An agent is pretty much a connector between vCAC and Endpoints, such as vCenter.
There are different agents available, a list can be found HERE
During the installation one agent was already installed. This is a vSphere agent. Remember you had to give your first agent a name (vCenter). There is a 1:1 mapping of Agent to vCenter, hence the requirement to give it a descriptive name (remember, I just named it vCenter).
You can even check the agents using the Windows Explorer on your IaaS server
Let’s connect to our vCenter. As said, we already have the agent installed. Now vCAC needs to know how to connect to the vCenter server and which credentials to use.
Here you need to login using an Infrastructure Admin – as earlier – all I did was allowing domain admins, so I am logging into the shell-ui using my domain admin.
Go to Infrastructure > Endpoints > Credentials and Click New Credentials
My vCenter I want to connect to is on the same domain, so I simply use the domain admin here (my lab only allows domain admins and the SSO admin)
Hit the green tick to proceed
Now we got the credentials for an Endpoint (vCenter), let’s add one (vCenter)
Click Endpoints and add a vCenter Endpoint
Fill out the required details (note the address is the full HTTPS FQDN including /sdk) and click OK
vCAC Install Content
1. vCAC Requirements
2. vCAC Install Identity Appliance
3. vCAC Install vCAC Appliance
4. Install vCAC IaaS Components
5. Adding a Tenant
6. Configure Agents & Endpoints
7. Configure Resource Allocations
8. Create Blueprints
9. Create Service Catalogs
10. Create Entitlements & Testing
11. Other vCAC Bits (SMTP etc.)