Driver Reload

Netcool Configuration Manager provides the ability to dynamically load new drivers, so that drivers become available without the need to restart the server.

Newly created drivers will be detected and reloaded automatically. Drivers will also be reloaded when new custom drivers are created through the GUI or the command line. Users can trigger a driver reload manually using the Tools>Reload Drivers menu option. Typically this manual step will be taken after running the SmartModelUpgrade tool.

To enable dynamic reloading each JVM (worker or presentation) caches it's own copy of all driver jars and all third party dependencies. They are cached in a directory called ncm/drivers/lib_legacy_cache_<server_name>.

There are some instances where a restart will be required. If the jars stored in the cache change when a driver is installed, then a restart will be required. Also, if the driver interface jar is patched by the driver installer, a restart will be required. If a restart is required, the Driver Reload State column in the Server table will indicate this as "Restart Required". When the driver reload has been successful, the Driver Reload State column in the Server table will report this as "Reloaded".