When the NOTIF processor starts up on a server or the Remote > Reload server option in the NOTIF Editor is selected, NOTIF browses the BASEDIR/smarts/conf/<config> and local/conf/<config> directories for files that end in ".ncf". The *.ncf files are NOTIF configuration files. NOTIF loads each*.ncf file into the NOTIF processor and combines them to create the running configuration on the Adapter Platform or SAM server where NOTIF is running.
The use of *.ncf files in NOTIF is a major architectural change from previous versions of NOTIF. NOTIF now loads configurations from *.ncf files, one at a time, rather than connect to a repository.
NOTIF configuration files (*.ncf files) are XML files that you can edit using the NOTIF Editor. “VMware Telco Cloud Service Assurance NOTIF Editor functionality” on page 19 provides an overview of how the NOTIF Editor works.
When NOTIF reads an *.ncf configuration file and loads the entire configuration from the configuration directories (that is, the /conf/<icoi or /ics> or /local/conf/<icoi or /ics> directories), the cumulative configuration is written to an *.ncf file in the local/logs directory (for example, the INCHARGE-OI.<configfilename>.ncf file). In this way, you can determine the specific NOTIF configuration elements that are running on a particular server. The *.ncf file written to the local/logs directory is generated when you either start up NOTIF or select the Remote > Reload server option in the NOTIF Editor.
When you install the Service Assurance Manager version 9.2, VMware Telco Cloud Service Assurance NOTIF is not enabled by default. You must start NOTIF by performing the steps described in “Starting VMware Telco Cloud Service Assurance NOTIF” on page 66.
