|
|
What is Dynamic Update Manager?
The Dynamic Update Manager (DUM) is an interface provided to upgrade the data according to the version of the feature packs installed in the Central or the Distributed Mediation Server. The interface implementation is available only in the Central Server.
Dynamic Update Manager helps in providing support for different versions of a feature pack in the Central Server and the Distributed Mediation Servers registered with it . But, the Central Server must always be on a equal or higher version. Different versions of a feature pack can exist between different Distributed Mediation Servers.
The Distributed Mediation Servers are deployed in remote networks to serve some specific requirements. In addition to the features provided by Web NMS, some regions may require monitoring of some other resources like applications, system parameters, syslog etc. These features are provided as feature packs over Web NMS. The assumptions are:
All regions may not need all the feature packs.
All regions may not need an upgrade of a feature pack already installed.
The Central Server and Distributed Mediation Server need not be on the same feature pack version.
Difference Between DUM and SUM
SUM is provided to upgrade the service pack and feature pack versions, while the DUM takes care of upgrading the data if the data is from a DMS with a lower feature pack version.
The Dynamic Update Manager checks if the data coming from the DMS to the Central Server is of the same version, and upgrades if there is a version difference. It upgrades the module data between the DMS and the Central Server, and upgrades the configuration data between the Client and the Central Server. That is, a copy of the DMS configuration files for which runtime administration is possible, is maintained in the central server under <Central Home>/conf/probe/<dms name> directory. So, as and when a configuration change is effected from the client, it is ensured that the change is in sync with the entry in the corresponding configuration file in the DMS, because the entries displayed in the RTA user interface are the upgraded entries (as in the Central Server).
Note that only the data is upgraded, but the feature pack version itself does not change.
Flow Diagram
|
|
Note: In the above flow diagram, FP is the abbreviation for 'Feature Pack', and V is the abbreviation for 'Version'. |
Module Data Upgrade from DMS to Central Server and Vice Versa
An interface DUMIfc
is implemented in the upgrading class for the feature packs.
If there is a change in the version, this class is called before the data is given to the module listeners
The data from DMS to Central is upgraded to the version in the Central Server (as it is always on an equal or higher version)
The response from the Central Server is 'downgraded' to the version in the Distributed Mediation Server.
Configuration Data Upgrade Between the Client<>Central Server<>DMS
The configuration data of each DMS (that can be in lower version) is read and upgraded before they are shown in the RTA UI. The modified configuration data is downgraded before it is written into appropriate configuration file in the DMS.
The updated data is then sent to the DMS after upgrading or downgrading according to the FP version in the DMS.
The configuration file in which the Dynamic Update Manager details are available is DUM.xml located in <Central Home>/conf directory. The details available here are the feature pack name, and the name of the implementation class (can be any number of classes, separated by a comma) for upgrading the data. The elements and their corresponding attributes are listed in the table given below:
|
Tag |
Attributes |
|
<DynamicUpdateMgr> |
This is the root node containing other sub-elements. |
|
<Featurepack> |
name: Contains the name of the feature pack as its value.
updaterImplClass: Contains the name of the implementation class used for upgrading/downgrading the data. It can be a list of classes separated by a comma |
The name of the implementation class specified
here is an instance of DUMIfc. This class is called during the data transfer between the
DMS and the Central Server if there is a difference in the versions of
the feature packs installed. The DynamicUpdateMgr
class reads this configuration file and sends the data through the interface
(DUMIfc) implementation specified as value for the updaterImplClass
attribute.
Example Entry
|
<DynamicUpdateMgr
> ..... .... <DynamicUpdateMgr>
|
|
|
