|
|
Multiple Distributed Mediation Servers register with a single Central Server. A directory with the DMS name is created in <Central Home>/conf/probe/ directory. The configuration files from the main /conf directory are copied to the <DMS Name>/conf directory. These default configurations are downloaded by the DMS at startup. Any configuration changes made through the runtime administration user interface are written in the Central Server, and the changes are downloaded by the DMS. The configuration files to be downloaded are defined in NOCDownloads.xml file located in <DMS Home>/conf directory.
Configuration Parameters in NOCDownloads.xml
Web NMS now provides an option where the configuration changes made locally (in DMS) can be dynamically uploaded to the Central Server. This configuration is effected in NOCDownloads.xml by providing an additional parameter called localUpdate with a value true or false. The dynamic upload happens only when the DMS is restarted. It can either be a cold-start or a warm-start.
The root element in this configuration file is <DOWNLOAD-CONF-FILES>. The details of files to be downloaded are specified as attributes of <FILE> node within <DOWNLOAD-CONF-FILES> node. The following table lists the configuration parameters in NOCDownloads.xml, and their descriptions.
|
Parameter Name |
Description |
|
nocDir |
The value is the name of the directory in which the configuration file is located in the Central Server. The relative path is specified.
|
|
regionDir |
The value is the name of the directory in which the downloaded configuration file is placed in the DMS. |
|
fileName |
The value is the name of the configuration file to be downloaded from the Central Server |
|
destFileName |
The value is the name in which the downloaded configuration file is stored in the DMS. |
|
localUpdate |
The value is either true or
false. If set as true,
any changes made in the configuration files in the DMS, will be uploaded
to the Central Server. If set as false
or if this parameter is not provided, upload does not take place. It is
mandatory that the DMS is restarted for the changes.
|
Sample Entry in the Configuration File
|
... <FILE nocDir="conf/" regionDir="conf/" fileName="logging_parameters.conf" destFileName="logging_parameters.conf" localUpdate="true" /> ... |
So, the steps to effect configuration upload from DMS to Central Server are,
Provide the entry for the configuration file to be uploaded, in NOCDownloads.xml as given above.
Stop the DMS if it is running
Restart (cold or warm start) the DMS.
Result
The ConfUploaderAPI's uploadFile() and downloadFile() methods are used to read this configuration file and effect the configuration files upload or download accordingly. Refer Customizing Upload From DMS for customization details.
|
|