Modifying configuration files

As part of the VMware Telco Cloud Service Assurance deployment and configuration process, you need to modify certain files. User-modifiable files include configuration files, rule set files, templates, and files (such as seed files and security configuration files) that contain encrypted passwords. Original versions of these files are installed into appropriate subdirectories under the BASEDIR/smarts/ directory.

Examples:

• The original versions of the Global Manager configuration files on UNIX are installed to /opt/InCharge/SAM/smarts/conf/ics

• Original versions of files should not be altered. If a file requires modification, it must be stored as a local copy of the file in BASEDIR/smarts/local or one of its subdirectories.

  Examples:

• A modified dxa-sam.conf file on UNIX should be saved to /opt/InCharge/SAM/smarts/local/conf/ics

• VMware Telco Cloud Service Assurance software is designed to first search for user-modifiable files in BASEDIR/smarts/local or one of its subdirectories. If a modified version of a file is not found in the local area, VMware Telco Cloud Service Assurance software then searches appropriate nonlocal directories.

  To facilitate proper file editing, VMware, Inc. provides the sm_edit utility with every VMware Telco Cloud Service Assurance product. When used to modify an original version of a file, this utility automatically creates a local copy of the file and places it in the appropriate location under BASEDIR/smarts/local. This ensures that the original version of the file remains unchanged. You can invoke sm_edit from the command line.

  To invoke the s m_edit utility from the command line, specify the path and the name of the file to edit under BASEDIR/smarts. If multiple VMware Telco Cloud Service Assurance products are running on the same host, invoke sm_edit from the bin directory of the product with the files to edit.

  Example:

  To edit the configuration file for the Global Manager, invoke the sm_edit utility as follows:

  # /opt/InCharge/SAM/smarts/bin>sm_edit conf/ics/dxa-sam.conf
              

  In this example, the sm_edit utility automatically creates a local copy of the dxa-sam.conf file in the /opt/InCharge/SAM/smarts/local/conf/ics directory and opens the file in a text editor. If a local version of the file already exists, the sm_edit utility opens the local version in a text editor. In addition, sm_edit creates any necessary subdirectories.

  The System Administration Guide provides additional information about the sm_edit utility.

  A number of configuration files exist for the Global Manager. The BASEDIR/smarts/local/conf/ics directory contains configuration files related to the Global Manager.

  Global Manager configuration files lists the configuration files for the Global Manager.

Table 1. Global Manager configuration files

Directory	Files	Description
conf	serverConnect.confclientConnect.confbrokerConnect.confsm_cloneDir.conf	Security files for configuring access to Service Assurance Manager. The System Administration Guide describes the syntax and configuration of these files.
conf/ics	service.data.template topology-group.data.template	Sample datafiles for importing services and groups into the Global Manager.
	actionconfig-sample.xml ics-config-sample.xml nlconfig-sample.xml policyconfig-sample.xml profileconfig-sample.xml userconfig-sample.xml mapgif-sample.xml	The XML files that define sample configurations for notification lists, user profiles, users, and custom map icons for the Global Manager.
	weights.conf	The configuration file for Business Impact Manager. The Business Impact Manager User Guide describes how to configure this file.
local/conf	runcmd_env.sh	Used to set environment variables for VMware Telco Cloud Service Assurance software.