本文件已封存並已停止維護。

Service Model Design Overview

更新日期: 2010年1月

適用於: System Center Operations Manager 2007

Designing a service model for an application consists primarily of defining a set of classes to represent the different application components and relationships between those elements to support the desired monitoring functionality. Simple applications may be adequately monitored with a model as basic as a single class. An application that consists of little more than a single Windows service, for example, may have only one class that is discovered on the appropriate computers and can act as the target for rules and monitors by using information generated by the application.

More complex applications will typically require multiple classes to represent different application components. Applications that may be installed across multiple computers may also benefit from classes used for consolidated health rollups for the application itself and for different application features composed of multiple components.

章節內容

Defining Classes and Relationships
Basic process for defining a set of classes and relationships to represent the application.

Choosing a Base Class
Criteria and recommendations for selecting a base class for custom classes.

Defining Discoveries
Basic process for defining discoveries for each class in a service model.

Practices to Avoid
Common practices to avoid when designing a service model.

 
顯示: