When using remote vCenter endpoints with vRealize Automation, it is important to configure a vRealize Business for Cloud Remote Data Collector (or two) local to the remote endpoint.
Just noticed that vROps v6.6 now comes with an adapter for vRealize Business for Cloud, so obviously felt the need to configure it and see what it provides.
Upgrading multiple vRealize components in our lab to latest available, this time it was vRealize Business for Cloud to be upgraded.
As of vRB for Cloud v7.1, the integration between vRB and vRealize Operations Manager has changed to what the official documents describe as ‘seamless integration’.
We wanted to upgrade our EHC lab instance of vRealize Business Standard (v6.2.3) to vRealize Business for Cloud (v7.1.0). Using vRB v7.x has been a common request for some of our Financial customers who required vRB to support the Swiss Franc.
So after a quick glance at the vRB 7.x Install Guide, we realised that this is a migration, not an upgrade.
Going through a process of converting all self-signed certificates in our EHC environment to CA-signed certs. First we converted all of the vCenter Server certificates, available here, but then we were faced with updating the certificates used by the various other vRealize Suite components that integrate with vCenter.
vRealize Operations Manager was the first on the list of those components.
This post provides some high-level detail on what was required for us to migrate to CA-signed certificates on an existing vCenter Server installation. Our overall plan was to upgrade versions of the EHC solution (EHC v3.1 to EHC v3.5) which meant that we needed to upgrade from vSphere v5, using SSO, to vSphere 6, using the new PSC (Platform Services Controller).
One new configuration requirement that I have come across recently working with vRealize Automation is the increased integration and permissions between vRealize Business Standard, vCenter and vRealize Operations Manager.