DMI 2.0 specifies the following responsibilities of the service provider layer:
The SP must coordinate the dynamic installation and removal of component instrumentations and management applications, and it must enforce that at least group 1 (the component ID group) is installed in each.
The SP must coordinate the registration of entities wishing to initiate management activities.
The SP is responsible for all run-time accesses to the MIF data. Implementations of the DMI SP may choose to store MIF files in an internal format (a MIF database) for performance and ease of access.
The SP is responsible for launching the component instrumentation, if necessary.
The SP must enforce command serialization to a component instrumentation and ensure that commands are allowed to run to completion. Multiple requests for a particular component instrumentation must be queued.
The SP must support event/indication subscription and filtering.
The SP must forward indications based on subscription and filters to each registered management application, and must time-stamp incoming indications before forwarding them.
The SP must send indications to all registered management applications that have subscribed for indications when components are installed or removed from the MIF database.
The SP must appear to management applications as a component with ID 1 (one). As a component, it must support the standard Component ID group. Additionally, the DMI SP must support the Subscription Indication and Filter standard groups. Also, like any component, it may define additional groups beyond the Component ID group.
The SP must support all of the NLS (Name Lookup Service) mechanisms contained in this specification, including Unicode and multiple NLS installations of schema for each component.
Because the Service Layer runs directly on the desktop computer, its memory footprint is crucial. The capability to efficiently run on existing systems, including low-end PCs, is critical for the success of DMI. One reason SNMP is not widely used on desktop computers and their internal components is heavy memory and processing requirements. For the DOS Service Layer, the DMTF specifies the TSR (Terminate and Stay Resident) to be 14 KB and loadable in high memory. In Windows, the Service Layer will be a DLL (Dynamic Linked Library). For memory-constrained systems, the local agent also can operate as a network surrogate, just as in SNMP.
REPORTS
Analyize In-Line NAC strategies and products.
ANALYTICS Plan and design your enterprise blade server deployments
InformationWeek U.S. IT Salary Survey 2008
Salaries for business technology professionals are falling. Here's what you need to know in order to make good hiring decisions and personal career choices. Purchase Today: $299
REPORTS
ANALYTICS
Follow 
