If you develop policies that require custom instrumentation, you can associate the policies and instrumentation using categories. This ensures that the management server automatically deploys the instrumentation when it deploys the policy.
To associate instrumentation with a policy, you must first add a category to the policy. You then copy the instrumentation to a specific folder on the management server. All instrumentation is in the following folder on the management server:
<data_dir>\shared\Instrumentation
This folder contains the "Categories" folder, within which you create a new folder with the same name as the category that you added to the policy. You can copy your instrumentation directly into this category folder.
NOTE:
The name of the category folder that you create must have no more
that 32 characters.
However, you may also need to deploy specific instrumentation to nodes that run on different platforms. To do this, you use a hierarchy of folders under the category folder. You then copy the platform specific instrumentation into these folders, use the same file name for each instance. The following figure shows the structure of the instrumentation folders. (Brackets show optional levels in the hierarchy.)
The instrumentation folder structure enables you to distinguish between nodes according to the following attributes:
Instrumentation\ExampleCategory\Windows\IA64\5.2
and
Instrumentation\ExampleCategory\Windows\5.2\IA64
on
the same management server, because IA64
appears twice
under Windows
.For more information on supported operating systems and agent binary formats, see the support matrix at HP Software Support Online.
The following figure shows an example hierarchy of folders for a category called ExampleCategory.
You can copy instrumentation to any folder in the hierarchy, and you only have to create the folders that you need. A good strategy is to create the most general folders possible. For example, if you can develop platform independent instrumentation, which is compatible with all nodes, you can create just the category folder and copy the instrumentation into it. This means that you only have to maintain one instance of the instrumentation on your management server.
If you have instrumentation files with the same name more than once within a category, the management server always deploys the most platform specific instrumentation. For example, if you have two instances of the same instrumentation in different folders:
Instrumentation\Categories\ExampleCategory\Windows\5.2\IA64\ExampleInstrumentation.vbs
Instrumentation\Categories\ExampleCategory\Windows\ExampleInstrumentation.vbs
NOTE:
Up to OVO version 7.50, the structure for instrumentation folders
was different. Therefore, if the management server was upgraded
from a previous version, you could have instrumentation folders
that follow the deprecated structure. For more information, see
Migrate existing
instrumentation.
CAUTION:
The management server deploys all instrumentation to the same
folder on managed nodes. Ensure that you do not inadvertently use
duplicate file names for different instrumentation anywhere in the
instrumentation folder hierarchy. (Only use duplicate file names
for platform specific instances of the same instrumentation.)
Related Topics: