When the Smarts NOTIF processor starts up on a server or the Remote > Reload server option in the Smarts NOTIF Editor is selected, Smarts NOTIF browses the BASEDIR/smarts/conf/<config> and local/conf/<config> directories for files that end in ".ncf". The *.ncf files are Smarts NOTIF configuration files. Smarts NOTIF loads each*.ncf file into the Smarts NOTIF processor and combines them to create the running configuration on the Adapter Platform or SAM server where Smarts NOTIF is running.
The use of *.ncf files in Smarts NOTIF is a major architectural change from previous versions of NOTIF. Smarts NOTIF now loads configurations from *.ncf files, one at a time, rather than connect to an Smarts repository.
Smarts NOTIF configuration files (*.ncf files) are XML files that you can edit using the Smarts NOTIF Editor. “VMware Smart Assurance NOTIF Editor functionality” on page 19 provides an overview of how the Smarts NOTIF Editor works.
When Smarts 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 Smarts 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 Smarts NOTIF or select the Remote > Reload server option in the Smarts NOTIF Editor.
When you install the Smarts Service Assurance Manager version 9.2, Smarts NOTIF is not enabled by default. You must start Smarts NOTIF by performing the steps described in “Starting Smarts NOTIF” on page 66.
