My vCAC Journey: Deploy & Configure 2nd vCloud Automation Center Appliance

Written by Ross Davies on . Posted in vCAC

This entry is part 6 of 6 in the series vCAC 6 Install

Now that you have 1 vCAC vApp its time to configure the second one.

Provide a path to the ova file for the vApp and click on Next.



Click on Next



Read and accept the EULA then click on Next.



Enter a name for the vApp and choose a folder to store the VM.



Select the cluster / Resource pool that you wish to deploy this vApp into.



Select the datastore / datastore cluster that you wish to place the VM into.



Select the disk format of your choice.



Select the network to provision the vApp into.



Enter a default password for the vApp and the networking information that the vApp will use. Be sure to set the FQDN for the hostname property. Be sure to set the FQDN for the hostname property.



Verify the vApp details and click on Finish to deploy the vApp.



Pre-Power On

Check that “Synchronize guest time with host” is enabled in VM Properties

Set the Timezone (Should be the same as all other systems in your vCAC environment).



(If necessary) set the proxy configuration to allow this VM to reach the internet for updates.



Set the vApp to check for updates on a schedule of your choice.


Log in to this vCloud Automation Center Appliance using SSH.

Copy the following files from the primary instance of this vCloud Automation Center Appliance instance.

scp [email protected]<Enter the hostname/IP for the 1st vCAC vApp here>:”/etc/vcac/encryption.key /etc/vcac/security.properties /etc/vcac/server.xml /etc/vcac/setenv-core /etc/vcac/solution-users.properties /etc/vcac/vcac.keystore /etc/vcac/vcac.properties” /etc/vcac

scp [email protected]<Enter the hostname/IP for the 1st vCAC vApp here>:/etc/apache2/server.pem /etc/apache2/server.pem

Change the permissions on the files in /etc/vcac directory so that they are owned by the vcac user and grant read and write permissions to the owner only.

cd /etc/vcac

chown vcac:vcac encryption.key security.properties server.xml setenv-core solution-users.properties vcac.keystore vcac.properties

chmod 600 encryption.key security.properties server.xml setenv-core solution-users.properties vcac.keystore vcac.properties

Change the permissions on the file that you copied to /etc/apache2 so that they are owned by the root user and grant read permissions to the owner only.

cd /etc/apache2

chown root server.pem

chgrp root server.pem

chmod 400 server.pem

Update the cluster configuration for the vCloud Automation Center Appliance. cafe.node.X should equal the sequence number for this vApp – 1st vApp deployed = 1, 2nd vApp deployed = 2 etc.

sed -i ‘s/VCAC_OPTS=”$VCAC_OPTS -Dcluster.node.instance=cafe.node.1″/VCAC_OPTS=”$VCAC_OPTS -Dcluster.node.instance=cafe.node.2″/g’ /etc/vcac/setenv-core

Before you start the vCAC services set this vCAC node to not receive any traffic then start the vCAC services using the following command.

service vcac-server restart

Disable the unneeded services;

service vpostgres stop

chkconfig vpostgres off

service vco-server stop

chkconfig vco-server off

Wait approximately 15 minutes for the services to restart then log out of the vCloud Automation Center Appliance then place this new node into service within your load balancer configuration and test that sessions are being load balanced across your vCAC vApp servers.

Series Navigation<< My vCAC Journey: Deploy & Configure 1st vCloud Automation Center Appliance

Tags: , , ,

Trackback from your site.

Leave a comment