A DCF silent installation is an installation procedure that continues without user interaction.

Table 1. Variables Properties and Description
Properties Description
USER_INSTALL_DIR Choose Install Folder, =/opt/DCF.

Prerequisites

Create a configuration file for the installer to execute the installation. To create configuration file:
  1. Copy the sample configuration file from the distribution (dcf-10.1.9.0-3-silent-installer.properties) to a directory on the server where you are installing DCF.
  2. Use any editor (vi/vim) to modify this file.
  3. Define each of the properties in this file for server type, according to Table Variables Properties and Description. Save the changes to the file. 
# Replay feature output
# ---------------------
# This file was built by the Replay feature of InstallAnywhere.
# It contains variables that were set by Panels, Consoles or Custom Code.

#Choose Install Folder
#---------------------
USER_INSTALL_DIR=/opt/DCF

Procedure

  1. Login to server as root.
  2. Type ./vsa_dcf-10.1.9.0-3.bin –i silent -f dcf-10.1.9.0-3-silent-installer.properties to run the installer in the silent installer mode, press Enter.
    Note: Any user interaction is not required for this installer. Once it completes, a message displays indicating that installation is completed, and you are returned to the shell prompt. Logs are available at <DCF_INSTALL_DIRECTORY>/DCF_Logs.
    Note: In case, both files ( dcf-installer.properties and dcf-10.1.9.0-3-silent-installer.properties) are present with different values to same variables then dcf-installer.properties file will get the precedence.
    Note: If you are providing special characters password in the dcf-10.1.9.0-3-silent-installer.properties, then you must specify the password in double quotes ("password$").

What to do next

After successful DCF installation, Install VMware Smarts Notification Collector to pull all the events from Smarts Presentation SAM and publish the same to KAFKA for consumption.
Note: If you shutdown or stop IP/ESM server which has Cisco ACI / VCD / Cloudify discovered and restart the server with the same repos / topology using --ignore-restore-errors or --clean-topology then no issues. However if you shutdown ESM server and restart with --norestore option then old monitoring collectors for Cisco ACI / VCD / Cloudify will be running and those need to be stopped manually.