User-modifiable
files
The installation includes system files, configuration files, ASL rule set files, scripts,
templates, as well as third-party software files that the software uses.
Never alter system files, such as executables, shared libraries, MODEL files, and setup files.
Do not alter third-party software system files provided with the Java Runtime
Environment.
As part of the configuration process, you will need to make changes to
some of the user-modifiable files. The following are examples of
user-modifiable files:
- Configuration files, such as ics.conf, clientConnect.conf, and serverConnect.conf (you are required to edit these)
- ASL rule sets, such as syslog_mgr.asl
- Sample actions, such as ics-ping and ics-telnet
- Template files used to import data, such as service.data.template and topology-group.data.templateOriginal versions of configuration files, ASL rule sets, scripts, and template files are installed to the /conf, /rules, and /script directories. When you need to alter a file in one of these directories, make those changes to a local copy of the file. By default, local copies of user-modifiable files should reside in /local or one of its subdirectories. software is designed to first search for user-modifiable files in /local or one of its subdirectories. If a modified version of a file is not found in the local area, software then searches appropriate non-local directories.To edit a file, invoke the sm_edit utility from the /bin directory. When used, sm_edit automatically opens a local copy of the specified file and saves the modified file to its appropriate location. ModifyingVMware Smart Assurance Service Assurance Managerfiles provides further information about how to use the sm_edit utility.You should:
- Onlymodify local copies of user-modifiable files.
- Alwaysretain the original, unedited, version of these files.Subdirectories for user-modifiable files identifies the default subdirectories that include user-modifiable files found under /local. The subdirectories vary by product suite.
Installation path
| Directory
| Description
|
|---|---|---|
/local
| /actions
| Tool scripts
|
/conf
| Configuration files
| |
/data
| Import files
| |
/rules
| ASL rules files
|
The
/local
directory has been reserved for directories with local copies of
user-modifiable files as well as writable files such as logs and repository
files. It typically contains directories listed in
Subdirectories for user-modifiable files. During
installation,
software may create empty
subdirectories under the
/local
directory. These directories are reserved for use for future service packs and
Rolling Patches. The exception is the
/local/bin
directory that contains files necessary for the successful installation of
software.
In addition, the /local/conf
directory contains the runcmd_env.sh file, which is created during installation. The
runcmd_env.sh is a file for setting environment variables, including the default
location for the . You can edit this
file to change the default location of the or to define any wide environment variable.
“Methods for
setting environment variables for ITOps software” on page 138
provides
information about setting environment variables. The product-specific naming convention used for subdirectories under
/local/conf
and
/local/rules
(as well as their non-local counterparts) typically reflects the
product or module within a
product suite that uses the files.
You can alter the location for rules files, as described in
“Controlling the
location for rule set files” on page 27.
If
VMware Smart Assurance Service Assurance Manager
installs a site-specific patch at your location, then
additional directories may be included under /local. Never alter files in any of these
additional subdirectories.