UIM - Change Probe Configuration Settings On Multiple Robots in UIM

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)
• Unified Infrastructure Management for Mainframe

Issue/Introduction

You may want to change parameters for a probe on all robots where the probe is deployed. For example, you may want to change a cdm parameter such as the disk alarm threshold for all disks on all machines to 10%. Or you want to deactivate processor queue alarms on all cdm probes on all machines. This article will walk you through the process to do so.

Environment

- Any UIM Release

Cause

- cdm probe configuration changes

Resolution

Follow these steps:

1.  Extract the configuration file from a deployed probe by first dragging and dropping the probe into the archive and choosing configuration only when prompted. 

3.  Click on rename to provide a new package name so that the operation does not replace the original probe package.

4.  Double click on the new config only probe in the archive and note the cdm.cfx configuration file contained therein as shown here:

5,  Right click on cdm.cfx and choose Edit File... from the menu.

6.  Edit the file based on the following configuration file information:
 

The configuration file (.cfx)

The configuration files in the package have the same configuration file format as installed configuration files except for added formatting commands. These formatting commands determine the way the distributed files are merged with existing ones.

The layout of a configuration files looks like this:

<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

<section1>
key1 = value1
<section2>
key2 = value2
</section2>
</section1>
<section3>
key3 = value3
</section3>


Directives to determine merging behaviour are added to the beginning of a section. The following directives are supported:

‘ ‘ - No directive: add keys from this section if they are not already present in the target configuration file.

‘overwrite’ - Add keys from this section overwriting existing keys in the target configuration file.

‘delete’ - Remove keys mentioned.

‘clear’ - Remove the whole section. If the section contains any keys then re-create the section adding these keys.

Note that the same section may appear several times, for example:

<a> delete
key1 =
</a>
<a>
key2 = hei
</a>

This removes key1 from section a and adds key2 to section a.

Directives are not inherited by sub-sections but must be specified explicitly for each. The ‘clear’ directive is an exception to this since it will affect subsections.

Examples of use

Add a key if it does not already exist:

<setup>
loglevel = 0
</setup>


Set a key regardless of its earlier setting:

<setup> overwrite
loglevel = 0
</setup>

Remove a section:

<setup> clear
</setup>

Remove all keys from a section and add one:

<setup> clear
loglevel = 0
</setup>

Remove one key from a section and add another:

<setup> delete
logfile =
</setup>

<setup> overwrite
datafile = config.dat
</setup>
 

7.  You now have a package with configuration file changes which you can distribute to all your robots of the same computer/os type.
 

Additional Information

If you want to be able to distribute to ALL computer types, you can either change the OStype and OS parameters to reflect this or create one section for each computer type.

To distribute the customized probe, simply drag and drop the super package on to the hub, it will then distribute to all the robots under it.

Note that the changes are applied to existing probes only, so that if the probe is not installed, no action will be performed.