This document is part of the Operations Manager Management Pack Authoring Guide
Resources For IT Professionals
This document is part of the Operations Manager Management Pack Authoring Guide
A management pack can only use elements in another management pack if the management pack with the elements is sealed. The referencing management pack can be sealed or unsealed as shown in the following diagram.
Valid management pack references
.gif)
When a management pack is created by using the Authoring console, it automatically adds the standard set of references shown in the following table. The versions shown are for the Authoring console for Operations Manager 2007 R2 . Updates to the console can create updated versions of these references.
| Alias | Management Pack | Version |
|---|---|---|
|
SC |
Microsoft.SystemCenter.Library |
6.1.7221.0 |
|
Windows |
Microsoft.Windows.Library |
6.1.7221.0 |
|
Health |
System.Health.Library |
6.1.7221.0 |
|
System |
System.Library |
6.1.7221.0 |
Each management pack reference includes the parts shown in the following table.
|
Alias |
The alias is a short string that represents the referenced management pack throughout the current management pack. You can set the alias. It applies only to the current management pack. You can use any string of letters and numbers, although we recommend a short and descriptive string. References that are created by the Operations Console have an alias automatically assigned. It can only be changed by exporting the management pack and editing the alias with an XML editor or the Authoring console. References created by using the Authoring console have an alias automatically created, but they can be changed at any time. The Authoring console will update any uses of the alias throughout the management pack. |
|
ID |
The ID of the reference is the name of the referenced management pack. |
|
Version |
The version of the reference is the minimum version of the management pack required by the reference. The version of the referenced management pack installed in the management group must be the same to or a later version than the version specified in the reference. |
|
Public Key Token |
The public key token is a unique character string representing the certificate that is used to seal the referenced management pack. This ensures that the management pack is provided by the expected source. If a management pack with the same name as the referenced management pack, but sealed with a different certificate, is installed in the management group, the token does not match. |
The diagram below shows an example of the references for the Microsoft.SQLServer.2008.Monitoring management pack 6.0.6648.0. All of the management packs listed in the references must be installed in the management group before the Microsoft.SQLServer.2008.Monitoring can be installed. The minimal version of the Microsoft.SQLServer.Library and Microsoft.SQLServer.Discovery management packs are 6.0.6648.0. The version of these management packs installed in the management group must bnagement pack is provided by the expected source. If a management pack with the same name as the referenced management pack, but sealed with a different certificate, is installed in the management group, the token does not match.
The diagram below shows an example of the references for the Microsoft.SQLServee equal to or later than 6.0.6648.0.
The other management packs require version 6.0.5000.0 or higher. These are library management packs that are included with Operations Manager 2007. Version 6.0.5000.0 of the management packs were included with the release version of the product. The library management packs for Operations Manager 2007 Service Pack 1 are version 6.0.6278.0 whereas the library management packs for Operations Manager 2007 R2 are 6.1.7221.0. These references ensure that the management pack installs on the release version of Operations Manager 2007. If a later version of the product were required for this management pack, a later version would be specified in the references.
The key token is identical for all of the references because these are all management packs provided by Microsoft and have been sealed with the same certificate.
Sample management pack references
.gif)
You have the option of implementing your management pack in a single file or multiple sealed files that reference one another. It may be simpler to create just a single management pack file, but you may consider multiple files for the following reasons.
You create a library management pack that includes a set of
abstract classes and other elements to support management packs for multiple versions of your application. Classes specific to different versions of your management pack are stored in other management pack files that reference the library. Even if you
currently don’t require multiple versions of the
For example, the SQL Server Management Pack includes a library file called Microsoft.SQLServer.Library that includes abstract classes for each of the SQL Server components and other elements common to all version of SQL Server such as views and groups. Each
version of SQL Server has its own set of management pack files with classes that inherit from the base classes in the library. Groups and views in the library are able to include objects discovered by all versions of the management pack because they all inherit
from the common set of base classes.
Management Pack files are deployed in their entirety to any agent with at least one discovered instance of at least one target class in the management pack file. Most management packs will have at least one discovery that targets a broad class such as Microsoft Windows Computer. Even though every other discovery, monitor, and rule in the management pack targets classes specific to the application, this single discovery would be enough to require the management pack file to be delivered to every Windows agent in the entire management group. Separating the management pack into multiple files for very large management packs can reduce the size deployed to agents that do not have the application installed.
For example, the SQL Server management packs are separated into Discovery and Monitoring management pack files. The Discovery management packs include only definitions of the SQL Server classes and their discoveries. The discoveries for classes such as Database Engine and Reporting Services target Microsoft Windows Server Computer meaning that the entire management pack file is deployed to every Windows Server in the management group. The Monitoring management pack file is much larger as it contains all monitoring and product knowledge. Its monitors and rules though only target classes that are defined in the Discovery management pack file, so this file is only deployed to agents where SQL Server is installed.
Your management pack may be required to run on Operations Manager 2007 R2, but you would like to provide a feature such as dashboards for those users that have System 2012 Operations Manager. In this case, you can use management pack files configured with the schema for Operations Manager 2007 R2 (which is supported by any later versions of Operations Manager) for most of the management pack elements. One or more separate management pack files using the System Center 2012 schema can then be created for the dashboards.
Management Pack files are deployed to agents in their entirety. Even though a change may be made to one portion of a management pack file, the entire file must be tested and installed when it is updated. You can separate major features of a management pack into multiple files so that an update can be made without affecting other areas of the management pack.
You may have features in your application that only some users may want to implement. You can allow the user to control the features of your management pack that they implement by separating major features into separate files. A user can choose to not install those files that contain the features that they don’t want to implement.