Install DCF in Silent
Mode
A DCF silent
installation is an installation procedure that continues without user
interaction.
Create a configuration file for the installer to
execute the installation. To create configuration file:
- Copy the sample configuration file from the distribution (Smarts_dcf-<Version>-silent-installer.properties) to a directory on the server where you are installing DCF.
- Use any editor (vi/vim) to modify this file.
- Define each of the properties in this file for server type, according to TableVariables 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
Properties | Description |
|---|---|
USER_INSTALL_DIR
| Choose Install Folder,
=/opt/DCF . |
- Login to server asroot.
- Type./Smarts_dcf-<Version>.bin -i silent -f Smarts_dcf-<Version>-silent-installer.propertiesto run the installer in the silent installer mode, pressEnter.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.In case, both files (Smarts_dcf-installer.propertiesandSmarts_dcf-<Version>-silent-installer.properties) are present with different values to same variables thenSmarts_dcf-installer.propertiesfile will get the precedence.If you are providing special characters password in theSmarts_dcf-<Version>-silent-installer.properties, then you must specify the password in double quotes ("password$").
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. 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.