This chapter describes the recommended deployment topologies for vRCS. vRCS can leverage vRA for VM provisioning. There are a couple of possible deployments:

• vRCS and vRA on the same single appliance (recommended for small POCs where vRCS and vRA are both lab/evaluation systems)
• vRCS and vRA on two separate appliances (recommended for large POCs or production)

• vRCS and vRA on two separate appliances where vRA is HA enabled (recommended for large POCs or production)
• Artifactory deployed as an external entity

vRCS does not support connecting to an external vRO and does not support its own HA setup, but it can integrate with an external HA setup of vRA for VM provisioning:

• vRCS and vRA (vRA) on the same single appliance
• vRCS and vRA on two separate appliances
• vRCS and vRA on two separate appliances where vRA is HA enabled
• Artifactory deployed as an external entity

Please be aware of the following when configuring the deployment:

• If the deployment of vRCS and vRA is in same appliance, it can lock up the whole appliance. Since the HA setup of vRA has its own SSO server, and there is no identity federation support, vRCS must use a shared user account to access vRA.
• Please configure the vRA endpoint as a shared account and not per user session. vRCS integrates with Advanced Service Designer (ASD) forms, and there is a new plugin named ASD that is shipped with vRCS 1.2. This plugin only works with an internal vRA.