vSphere Deployment Configurations

vSphere Automation
client applications communicate with services on the
Platform Services Controller
and
vCenter Server
components of the virtual environment.
vCenter Server
can be deployed with an embedded or external
Platform Services Controller
.

vCenter Server
with an Embedded
Platform Services Controller

vCenter Server
and
Platform Services Controller
reside on the same virtual machine or physical server. This deployment is most suitable for small environments such as development or test beds.
You can use the
in two ways to establish secure, authenticated sessions for your client application, by making requests to the Lookup Service and the
vCenter Single Sign-On
Service.
One way to use the
Platform Services Controller
is to request an authentication token that can be used to authenticate requests across services. The client connects to the Lookup Service and retrieves the
vCenter Single Sign-On
Service endpoint and the
vSphere Automation
API endpoint. The client then uses the
vCenter Single Sign-On
endpoint to authenticate with user credentials and receive a token that securely verifies the client's credentials. This allows the client to authenticate with a number of service endpoints without sending user credentials over the network repeatedly.
Alternatively, if the client connects directly to the
vSphere Automation
API endpoint, there is no need for the client to interact with the
vCenter Single Sign-On
Service. The client sends user credentials to the
vSphere Automation
API endpoint, which creates a session identifier that persists across requests.
vCenter Server
with Embedded
Platform Services Controller
vCenter Server and the Platform Services Controller are deployed
				on the same virtual machine or physical server. Client applications can
				retrieve service endpoints and authenticate by using the Lookup Service and the
				Single Sign-On Service running on the Platform Services Controller. Clients can
				also access registered service endpoints on different vCenter Server instances
				by directly connecting to the vSphere Automation Endpoint.

vCenter Server
with an External
Platform Services Controller

In the case of an external
Platform Services Controller
, the
vCenter Server
and the
Platform Services Controller
are deployed on separate virtual machines or physical servers. The
Platform Services Controller
can be shared across several
vCenter Server
instances. For larger deployments or to provide better availability, more than one
Platform Services Controller
can be deployed. When configured as replication partners within a single
vCenter Single Sign-On
domain,
Platform Services Controller
instances replicate all user and system data within the cluster.
A client application functions in a similar way as in a
Platform Services Controller
with embedded
vCenter Server
deployment. The only difference is that the client application can access services on multiple
vCenter Server
instances, or services only on a particular
vCenter Server
instance.
vCenter Server
with External
Platform Services Controller
vCenter Server and the Platform Services Controller are deployed
				on separate virtual machine or physical server. Client applications can
				retrieve service endpoints and authenticate by using the Lookup Service and the
				Single Sign-On Service running on the Platform Services Controller. Clients can
				also access registered service endpoints on different vCenter Server instances
				by directly connecting to the vSphere Automation Endpoint.