Caution: Articles written for technical not grammatical accuracy, If poor grammar offends you proceed with caution ;-)
Wow this one is currently a really hot topic. I must have been asked how to automate the installation of vCAC 50 or more times in the last week and I can’t even count over the last month, so here it is. As I’m sure everyone has learned there area a number of components to vCAC. When installing from the command line you will need to install each of them independently. What you will see in this post may be a bit confusing and it’s understandable as I’m merely sharing the commands without much explanation. I plan to go through my step by step tutorials and inject the options to the relevant steps in them. Hopefully I will find time to round back to this article and put much more time into explaining each option. For now I hope this helps anyone trying to do an automated installation.
Each of the examples is for performing an https install, however can change from https to http if you like. I should also point out in the vCAC 5.2 release this is much more simplified and much less complex. Please post any questions you have regarding this topic in the forum under the thread “vCAC Automated Installation Questions“.
Installing the Web Server / Report Portal / Model Manager
Below is the command for installing the base components.
msiexec /i “DynamicOps Virtual Resource Manager.msi” /qn /norestart /Lvoicewarmup! Install-Web.log VRM_LIC_FILE=filePath\fileName ADDLOCAL=ModelManagerWeb,ModelManagerData,Website,Website.IIS,Report.Website,Report.Website.IIS INSTALLLOCATION=directoryPath WEBFARM_SUPPORT=1 WEBSITE_DESCRIPTION=IISWebSiteName IIS_INSTALL_TYPE=Https HTTPS_PORT=httpsPort WEBSITE_PORT=existingPort INSTALLED_CERT=certificateThumbprintWithoutSpaces(optional) DATABASE_SERVER=DBServerName,port DATABASE_NAME=DBName AZMAN_STORE_TYPE=MSSQL CREATE_AZMAN_SQL_STORE=0 REPOSITORY_HOSTNAME=modelManagerWebServerFQDN REPOSITORY_USER=domain\user REPOSITORY_USER_PASSWORD=password SESSION_STATE_DATABASE_NAME=ASPState MANAGERSERVICE_HOSTNAME=managerServerFQDN MANAGERSERVICE_USER= domain\user MANAGERSERVICE_PASSWORD= password REPORTPORTAL_USER= domain\user REPORTPORTAL_PASSWORD= password
Installing the Manager Service
Below is the command for installing the Manager Service.
msiexec /i “DynamicOps Virtual Resource Manager.msi” /qn /norestart /Lvoicewarmup! Install-Mgr.log VRM_LIC_FILE=filePath\fileName ADDLOCAL=ManagerService INSTALLLOCATION=”directoryPath” WEBSITE_DESCRIPTION=IISWebSiteName IIS_INSTALL_TYPE=Https HTTPS_PORT=httpsPort WEBSITE_PORT=existingPort INSTALLED_CERT=certificateThumbprintWithoutSpaces(optional) DATABASE_SERVER=DBServerName,port DATABASE_NAME=DBName AZMAN_STORE_TYPE=MSSQL CREATE_AZMAN_SQL_STORE=0 EMAIL_SMTP_SERVER=smtpServerName EMAIL_FROM_ADDRESS=user@domain MANAGERSERVICE_START=1 MANAGERSERVICE_USER= domain\user MANAGERSERVICE_PASSWORD= password REPOSITORY_HOSTNAME=modelManagerWebServerFQDN MANAGERSERVICE_LOG_DIR=LogDirectoryforManagerService
Installing the Distributed Execution Manager
Below is the command for installing the Distributed Execution Manager.
msiexec /i WorkflowManagerInstaller.msi /qn /norestart /Lvoicewarmup! Install-DEM.log ADDLOCAL=All INSTALLLOCATION=”directoryPath” MANAGERSERVICE_HOSTNAME=managerServerFQDN REPO_HOSTNAME=modelManagerWebServerFQDN REPO_SERVER_URL=https://modelManagerWebServerFQDN:httpsPort/repository/ REPOSITORY_USER=domain\user REPOSITORY_USER_PASSWORD=password HTTPS_SUPPORT=1 HTTPS_PORT=httpsPort DEM_ROLE= “worker or Orchestrator” TRANSFORMS=”:DemInstanceId##;” MSINEWINSTANCE=”1″ DEM_NAME=”uniqueDEMName” SERVICE_USER_NAME=domain\user SERVICE_USER_PASSWORD=password
Note: The ## represents a two-digit ID for this DEM. This number must be unique for each DEM installed on a single system. You can use any IDs between 01 and 25, but it may be easiest to increment these in sequence (01, 02, 03…). Also, it is extremely important to keep a record of these for each server for ongoing maintenance and upgrades.
Installing a Proxy Agent
Below is the command for installing the vSphere Proxy Agent.
msiexec /i VrmAgentInstaller.msi /qn /norestart /Lvoicewarmup! Install-agentName.log TRANSFORMS=”:VrmAgentInstanceId##;” MSINEWINSTANCE=”1″ AGENT_INSTALL_TYPE=”InstallAgent” AGENT_NAME=agentName VRM_SERVER_NAME=managerServerFQDN HTTPS_SUPPORT=1 HTTPS_PORT=httpsPort AGENT_TYPE=”vSphere” ADDLOCAL=CoreAgent,vSphereAgent INSTALLLOCATION=”directoryPath” SERVICE_USER_NAME=domain\user SERVICE_USER_PASSWORD=password VSPHERE_AGENT_REPOSITORY_HOSTNAME=modelManagerWebServerFQDN REPOSITORY_USER=domain\user REPOSITORY_USER_PASSWORD=password VSPHERE_AGENT_ENDPOINT= vSphereEndpointName
Note: The ## represents a two-digit ID for this proxy agent. This number must be unique amongst all proxy agents installed on a single system. You can use any IDs between 01 and 25, but it may be easiest to increment these in sequence (01, 02, 03…). Also, it is extremely important to keep a record of these for each server for ongoing maintenance and upgrades.
3 Replies to “vCloud Automation Center – vCAC 5.1 – Automating the vCAC installation”
Hey Sid – please update this for 5.2 now that it’s GA!
TBH it would be nice if we could actually install the product following the reference architecture documentation rather than doing the single server approach that everyone is documenting out in the blogosphere, currently have an SR raised with VMware because like everyone else we can do the single server approach but for production purposes that wasn’t advisable or recommended.
Trying doing this with vCAC 5.2 now, perhaps we can work with this version instead (because at the moment even VMware haven’t managed to install vCAC 5.1 using the reference architecture design).