Domain-specific configuration files

Edit online

You can use different configuration settings for different domains by saving domain-specific versions of the configuration files that you edit. Not all files can be made domain-specific.

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.

Most of the following types of files can be made domain-specific:

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

Do not make domain-specific copies of the following files. Either there is no benefit to doing so, or it can cause unexpected behavior.

  • Active Object Class files, that is, all files ending in .aoc
  • ClassSchema.cfg
    Note: You can add or update classes that are intended for use in only some of your domains, but class IDs must be unique. All classes must be defined in only one ClassSchema.cfg file, which is used by all domains.
  • ServiceData.cfg
  • broker_1883.cfg

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