Domain-specific configuration files

You can use different configuration settings for different domains by saved domain-specific versions of the configuration files that you edit.

If a domain-specific configuration file is found, those configuration settings are used by the relevant processes in that domain. If a domain-specific configuration file is not found, the settings from the default configuration file are used.

To save a domain-specific version of a configuration file, add the domain name to the end of the file name immediately before the file extension. For example, the configuration file for the ncp_ctrl process in the domain NCOMS is called CtrlServices.NCOMS.cfg.

Note: You must manually merge any changes to any domain-specific configuration files when installing a fix pack, if the default file changes. For example, the default ModelNcimDb.cfg file is changed when the NCIM database schema is changed.

Although in practice there are some files that you are unlikely to need to alter, in principle all of the following types of files can be made domain-specific:

  • Configuration files, that is, all files ending in .cfg
  • Discovery agent files, that is, all files ending in .agnt
  • Active Object Class files, that is, all files ending in .aoc
  • Text-based stitcher files, that is, all files in a stitchers directory ending in .stch

In the Network Manager documentation, these files are referred to using their default names unless noted otherwise.