计算机本科毕设的外文翻译.docx

1、计算机本科毕设的外文翻译附录原文： Windows Management InstrumentationWindows Management Instrumentation (WMI) (or Windows Management Interface) is a set of extensions to the Windows Driver Model that provides an operating system interface through which instrumented components provide information and notification. WM

2、I is Microsofts implementation of the Web-Based Enterprise Management (WBEM) and Common Information Model (CIM) standards from the Distributed Management Task Force (DMTF).WMI allows scripting languages like VBScript or Windows PowerShell to manage Microsoft Windows personal computers and servers, b

3、oth locally and remotely. WMI is preinstalled in Windows 2000 and newer OSs. It is available as a download for Windows NT, Windows 95 and Windows 98.1 Purpose of WMIThe purpose of WMI is to define a non-proprietary set of environment-independent specifications which allow management information to b

4、e shared between management applications. WMI prescribes enterprise management standards and related technologies that work with existing management standards, such as Desktop Management Interface (DMI) and SNMP. WMI complements these other standards by providing a uniform model. This model represen

5、ts the managed environment through which management data from any source can be accessed in a common way.2 OverviewIn order to unify the management techniques for the sake of simplicity, the DMTF defined CIM to represent real-world manageable entities in a unified way.The CIM object model is an obje

6、ct database model using terms and semantics that are unique to all constructors and software developers. This object model is implemented in a database called the CIM repository.Based on the CIM model, WMI includes real-world manageable components, available from the DMTF standards with some specifi

7、c extensions that represent the various Windows components. Moreover, WMI exposes a collection of COM-scriptable objects that allow various applications to take advantage of the management information.As part of the installation process, most of the Microsoft applications available today (e.g. SQL S

8、erver, Exchange Server, Microsoft Office, Internet Explorer, Host Integration Server, Automated Deployment Services) extend the standard CIM object model to add the representation of their manageable entities in the CIM repository. This representation is called a WMI class, and it exposes informatio

9、n through properties and allows the execution of some actions via methods. The access to the manageable entities is made via a software component, called a “provider” which is simply a DLL implementing a COM object written in C/C+. Because a provider is designed to access some specific management in

10、formation, the CIM repository is also logically divided into several areas called namespaces. Each namespace contains a set of providers with their related classes specific to a management area (i.e. RootDirectoryDAP for Active Directory, RootSNMP for SNMP information or RootMicrosoftIISv2 for Inter

11、net Information Services information).To locate the huge amount of management information available from the CIM repository, WMI comes with a SQL-like language called the WMI Query Language (WQL).3 Development processBecause WMI abstracts the manageable entities with CIM and a collection of provider

12、s, the development of a provider implies several steps. The major steps can be summarized as follows:Step 1 Create the manageable entity model Define a model Implement the modelStep 2 Create the WMI Provider Determines the provider type to implement Determines the hosting model of the provider Creat

13、e the provider template with the ATL wizard Implement the code logic in the provider Register the provider with WMI and the systemStep 3 Test the providerStep 4 Create consumer sample code4 Importance of WMI providersSince the release of the first WMI implementation during the Windows NT 4.0 SP4 era

14、 (as an out-of-band download), Microsoft has consistently added WMI providers to Windows. Under Windows NT 4.0, Microsoft had roughly 15 WMI providers available once WMI was installed. When Windows 2000 was released, there were 29 WMI providers as part of the operating system installation. With the

15、release of Windows Server 2003, Microsoft included in the platform more than 80 WMI providers. Windows Vista includes 13 new WMI providers,5 taking the number close to around 100 in all, and Windows Server 2008 includes some more including providers for IIS 7, PowerShell and virtualization. This has

16、 been a sign for many customers that WMI became at Microsoft, the “ubiquitous” management layer of Windows, even if this commitment has never been explicit from Microsoft.During these last years, due to a constant increasing exposure of management data through WMI in Windows, more and more people in

17、 the IT systems management field started to develop scripts and automation procedures based on WMI. Beyond the scripting needs, most leading management software in the world, such as MOM, SMS, ADS, HP OpenView for Windows (HPOV), BMC Software or CA, Inc. are WMI-enabled and capable to consume and pr

18、ovide WMI information through various User Interfaces. This enables administrators and operators, not capable of scripting or programming on top of WMI, to enjoy the benefits of WMI without even learning about it. However, if they want to, because WMI is scriptable, it gives them the opportunity to

19、consume WMI information from scripts or from any Enterprise Management software that is WMI-aware.5 FeaturesFor someone willing to develop one or many WMI providers, WMI offers many features out of the box. Here are the most important advantages:(1) Automation interfaces: Because WMI comes with a se

20、t of automation interfaces ready to use, all management features supported by a WMI provider and its set of classes get the scripting support for free out-of-the box. Beyond the WMI class design and the provider development, the Microsoft development and test teams are not required to create, valida

21、te and test a scripting model as it is already available from WMI.(2) .NET Management interfaces:Because the System.Management namespace 6 relies on the existing COM/DCOM plumbing, the created WMI provider and its set of WMI classes becomes automatically available to all .NET applications independen

22、tly of the language used (e.g. C#, VB.NET). Beyond the WMI class design and the provider development, like for scripting, the Microsoft development and test teams are not required to create, validate and test new assemblies to support a new namespace in the .NET Framework as this support is already

23、available from WMI for free.(3) C/C+ COM/DCOM programming interfaces:Like most components in Windows, COM/DCOM programmers can leverage the features of the provider they develop at the COM/DCOM interfaces level. Like in previous environments (scripting and .NET Framework), a COM/DCOM consumer just n

24、eeds to interact with the standard set of WMI COM interfaces to leverage the WMI provider capabilities and its set of supported WMI classes. To make all management information available from the native APIs, the WMI provider developer just needs to interact with a set of pre-defined WMI COM interfac

25、es. This will make the management information available at the WMI COM level automatically. Moreover, the scripting COM interface object model is very similar to the COM/DCOM interface object model, which makes it easy for developers to be familiar with the scripting experience. (4) Remoting capabil

26、ities over DCOM and SOAP:More than simply offering local COM capabilities, as management is all about remoting, WMI offers the DCOM transport. In addition, SOAP transport will be available in Windows Server 2003 R2 through the WS-Management initiative lead by Microsoft, Intel, Sun Microsystems and D

27、ell. This initiative allows to run any scripts remotely or to consume WMI data through a specific set of interfaces handling SOAP requests/responses. The advantage for the WMI provider developer is that when he exposes all his features through WMI, Windows Remote Management/WS-Management can in turn

28、 consume that information as well (embedded objects in WMI instances are not supported in Windows Server 2003 R2. It is however a target for Vista). All the layering to WS-Management and the mapping of the CIM data model to SOAP comes for free out of the WMI/WS-Management solution. In the event DCOM

29、 must be used, implementing DCOM requires the presence of a proxy DLL deployed on each client machine. As WMI is available in the Windows operating system since Windows 2000, these issues are eliminated.(5) Support for Queries:WMI offers support for WQL queries out of the box. This means that if a p

30、rovider is not designed to support queries, WMI supports it by using an enumeration technique out of the provider.(6) Eventing capabilities:WMI offers the capability to notify a subscriber for any event it is interested in. WMI uses the WMI Query Language (WQL) to submit WQL event queries and define

31、s the type of events to be returned. The eventing mechanism, with all related callbacks, is part of the WMI COM/DCOM and automation interfaces. Anyone writing a WMI provider can have the benefit of this functionality at no cost for his customers. It will be up to the consumer to decide how it wants

32、to consume the management information exposed by the WMI provider and its related set of WMI classes.(7) Code template generator:To speed up the process of writing a WMI provider including all COM/DCOM interfaces and related definitions, the WMI team developed the WMI ATL Wizard to generate the code

33、 template implementing a provider. The code generated is based on the WMI class model initially designed by the developer. The WMI provider developer will be able to interface the pre-defined COM/DCOM interfaces for the WMI provider with its set of native APIs retrieving the management information to expose