WMI and Host Integration Server Architecture
The architecture of the Windows Management Instrumentation (WMI) technology consists of the following components:
- Management applications
- Managed objects
- Management infrastructure, consisting of the WMI software (Winmgmt.exe) and the CIM repository
Management applications are Microsoft® Windows®-based applications or services on Microsoft Windows NT® or Windows 2000 that process or display data from managed objects. A management application can perform a variety of tasks in a Host Integration Server environment such as configuring HIS Servers, measuring performance, reporting outages, and correlating data.
Managed objects represent logical or physical enterprise components. Managed objects are modeled using the CIM, and they are accessed by management applications through WMI. A managed object in the Microsoft Host Integration Server 2000 environment can be any component of the system, from a link service device driver communicating with hardware to software configuration information on users and connected Logical Units (LUs).
The WMI providers supplied with Host Integration Server 2000 use the WMI COM API to supply the WMI repository with data from Host Integration Server managed objects, to handle requests on behalf of Host Integration Server management applications, and to generate notifications of events. The WMI providers included with Host Integration Server 2000 include the following:
- Host Integration Server configuration provider (wmiHIS)
- Host Integration Server MSMQ-MQseries Bridge provider (wmiMQBridge)
- Host Integration Server SNA configuration provider (wmisna)
- Host Integration Server SNA status provider (wmisnastatus)
- Host Integration Server SNA trace provider (wmisnatrace)
In addition, Windows 2000 includes several standard WMI providers, such as a registry provider, for accessing information from the system registry. Windows 2000 also supplies a Windows 2000 Event Log Provider that allows applications to receive notifications of Windows 2000 and Host Integration Server 2000 events and to access the information stored in the Windows 2000 event log. The Win32® WMI providers are also available for use with Windows NT 4.0 (Service Pack 5 or later) as part of the WMI Software Development Kit (SDK).Third-party vendors can create custom providers to interact with managed objects specific to their environment.
The management infrastructure consists of WMI and the CIM repository. WMI enables users to handle communications between management applications and providers. Users store their static data in the CIM repository. Applications and providers communicate through WMI using a common programming interface (COM API). The COM API, which supplies event notification and query processing services, is available in the C and C++ programming languages.
The CIM repository holds static management data. Static data is data that does not regularly change. WMI also supports dynamic data, which is data that must be generated on demand because it is frequently changing. Data can be placed in the CIM repository by WMI or network administrators. Information can be placed in the CIM repository using either the Managed Object Format (MOF) language and the MOF Compiler or the WMI COM APIs. The WMI providers supplied with Host Integration Server 2000 use both mechanisms.
The following MOF files are supplied with Host Integration Server 2000 for use by management applications:
Management applications can access the COM API directly to interact with WMI and the CIM repository to make management requests of Host Integration Server 2000. Applications can also use other access methods such as Open Database Connectivity (ODBC) and the Hypertext Markup Language (HTML) to make these requests. An ODBC Driver for WMI is included with Windows 2000. The protocol used for communication between local and remote components is Distributed Component Object Model (DCOM).