Blueprints are the mechanism by which repeatable service offerings are defined in vRealize Automation. A blueprint contains information about the types of virtual machine instances, networks, resources, software, and XaaS blueprints required to create a service. Once a blueprint has been defined, it must be published to the service catalog in order for it to be requestable by users. A user can then request the blueprint, if they’re so entitled, to receive the service defined by the blueprint.
Endpoints enable external communications from vRealize Automation to other systems that perform various functions from virtual machine hosting and provisioning to networking & security and orchestration.
In this part of the initial configuration, we'll cover the creation of some of the main endpoints you'll likely encounter in a vRealize Automation deployment, including vCenter, NSX, vRealize Orchestrator, and vRealize Operations Manager (vROPS).
For this example vRA v7.3 is assumed. vRO 7.3, NSX 6.4, and vROPS 6.6.1 are all assumed.