VCAP6-CMA Deploy - Objective 1.2: Deploy and Manage vRA Appliances and IaaS Servers in a Distributed Configuration
VMware vRealize Automation VCAP6 VCAP6-CMA
Published on 25 January 2017 by Christopher Lewis. Words: 589. Reading Time: 3 mins.
Objective Overview
Objective 1.2 - Deploy and Manage vRA Appliances and IaaS Servers in a Distributed Configuration
- Deploy vRA Appliances in a distributed / highly available configuration.
- Deploy virtual appliance in segregated role configuration(s).
- Acquire IaaS installation media from the virtual appliance.
- Perform initial configuration of vRealize Appliances and IaaS Servers.
- Configure IaaS in segregated role configuration(s).
- Enable Microsoft Distributed Transaction Coordinator (MSDTC) to communicate between all servers in deployment.
- Configure Windows Firewall to allow vRA components to communicate.
Objective Prerequisites
The following prerequisites are assumed for this Objective:
- Either:
- Deploy the vRealize Automation 6.x Appliance ( HOWTO )
- Deploy and Configure vSphere 5.5 SSO or vSphere 6 PSC HA
- Deploy a Windows Virtual Machine to be used as a IaaS Server(s) x 4
- Deploy a Windows Virtual Machine to be used as a IaaS DEM / Agent Server(s) x 2
- Configure Service Account permissions on the SQL Server Database.
Objective Breakdown
Deploy vRA Appliances in a distributed / highly available configuration
This section is highlighting the fact that the vRealize Automation distributed / highly available HA install consists of the deployment of two vRealize Automation Appliances configured within a HA Pair. Within this scenario, the internal PostgreSQL Database is configured with Active/Passive asynchronous replication, so there is additional effort required to both appliances.
See HOWTO: Configure the vRealize Automation 6.x Appliance(s) (Distributed Install)
Deploy virtual appliance in segregated role configuration(s)
I’m not completely sure what is required here, I have covered the following topics previously and feel that this subject is covered sufficiently! (let me know if you feel its not!)
- HOWTO: Deploy the Identity Appliance for vRealize Automation 6.x
- HOWTO: Configure the VMware Identity Appliance for vRealize Automation 6.x
- HOWTO: Deploy the VMware vRealize Automation 6.x Appliance (OVA)
- HOWTO: Configure the VMware vRealize Automation 6.x Appliance (Minimal Deployment)
- HOWTO: Configure the vRealize Automation 6.x Appliance(s) in a HA Configuration
I haven’t covered vRealize Orchestrator or vRealize Automation Application Services as this is covered under a different objective.
Acquire IaaS installation media from the virtual appliance
See HOWTO: Obtain the vRealize Automation 6.x IaaS Installer Package
Perform initial configuration of vRealize Appliances and IaaS Servers
I believe I have covered this previously in the following posts:
- HOWTO: Configure the VMware vRealize Automation 6.x Appliance (Minimal Deployment)
- HOWTO: Install the VMware vRealize Automation 6.x IaaS Prerequisites
Configure IaaS in segregated role configuration(s)
- HOWTO: Deploy VMware vRealize Automation 6.x IaaS Database (Distributed Install)
- HOWTO: Deploy VMware vRealize Automation 6.x IaaS Web Servers (Distributed Install)
- HOWTO: Deploy VMware vRealize Automation 6.x IaaS Manager Server (Distributed Install)
- HOWTO: Deploy VMware vRealize Automation 6.x IaaS DEM Worker (Distributed Install)
- HOWTO: Deploy VMware vRealize Automation 6.x IaaS Proxy Agent (Distributed Install)
Enable Microsoft Distributed Transaction Coordinator (MSDTC) to communicate between all servers in deployment.
In a Distributed installation, it is important that all Windows based components have MSDTC configured correctly.
I have covered this in the Objective 1.1 post and there is no difference in the steps for completing this task in vRealize Automation Distributed deployment.
Configure Windows Firewall to allow vRA components to communicate
In a Distributed installation, it is important that all Windows based components have the Windows Firewall configured to allow MSDTC to communicate.
I have covered this in the Objective 1.1 post and there is no difference in the steps for completing this task in vRealize Automation Distributed deployment.
In addition, you may need to configure the Windows Firewall on the Microsoft SQL Server to allow communication for the SQL Server port (which is by default 1433 but is changeable).
Published on 25 January 2017 by Christopher Lewis. Words: 589. Reading Time: 3 mins.
- HOWTO: Obtain the vRealize Automation 6.x IaaS Installer Package ()
- HOWTO: Configure the vRealize Automation 6.x Appliance(s) (Distributed Install) ()
- HOWTO: Create a vRealize Automation 6.x vSphere Linked-Clone Blueprint ()
- VCAP6-CMA Deploy - Objective 1.5: Create Fabric Groups utilizing Reservations and Reservation Policies ()
- VCAP6-CMA Deploy - Objective 2.2: Create/Modify a Business Group ()
- Operating a Private Cloud - Part 3: Creating a Pricing Card in VMware Aria Automation
- Operating a Private Cloud - Part 2: Creating a Pricing Card in VMware Aria Operations
- Operating a Private Cloud - Part 1: Understanding Pricing Cards in VMware Aria
- Zero2Hero - Using Aria Automation to Deploy Multiple Machines with Multiple Disks - Part 5
- Zero2Hero - Using Aria Automation to Deploy Multiple Machines with Multiple Disks - Part 4