Home > Articles > Operating Systems, Server > Microsoft Servers

  • Print
  • + Share This
This chapter is from the book

A Compileable MOF File

While examining the syntax and semantics of the MOF language by reading examples is an important part of the learning process, it is far more beneficial to gain practical experience through typing and compiling your own examples. Type the following MOF file, which is based upon the previous examples, and follow the instructions to compile it. After you are confident with this process, then experiment and alter sections of the file to see the results.

In the example, we shall create our own namespace, to avoid cluttering any existing system namespaces. Microsoft recommends using the root/default namespace in developing schemas, although we shall create our own in this example.

To write a MOF file, you will need a simple ASCII text editor, such as Microsoft's WordPad or Notepad.

If you have Microsoft Developer Studio, you can configure the settings under Tools/Customize/Tools so the development environment will compile a MOF file for you. For more information, see Microsoft's Learn WMI tutorial at http://msdn.microsoft. com/downloads/sample.asp?url=/msdn-files/027/001/574/msdncompositedoc.xml.

First, open your ASCII text editor or Developer Studio. Within the window, type the MOF text in Figure 4.11.

Figure 4.11Figure 4.11 A compilable MOF (part 1 of 2)


The initial #pragma classflags("forceupdate") directive tells the compiler to update any existing class definitions in the CIM repository that match those with the class definitions supplied in this MOF file and to resolve conflicts where possible. The update process applies to properties, methods, and qualifiers contained within a class. If the changes within a class are extensive, then it is always better first to delete the existing class from the repository and then to compile the new one. Be aware, however, that doing this deletes all child class definitions!

The CIM repository employs inheritance, which leads to some very real consequences when adding new classes to the repository. For example, replacing an existing class in the hierarchy or changing one of the qualifiers in an existing base class can have direct consequences to the later classes.

Consider a parent class, Storage, and a child class, CDROM. Imagine that the child class is defined with the class qualifier Write set to true. If we try to add base class, Storage, with the class qualifier, Read, set to true, a conflict exists between the child class's qualifier and the base class. In this instance, with the forceupdate flag specified, WMI would remove the qualifier from the child class to make way for the base class. The only situation in which this would not occur is if the child class has instances. If the specified flag were safeupdate, then the update would fail at that point because of the conflict with the child class.

In addition to the forceupdate flag, a number of additional settings exist to resolve conflicts when adding classes. You can combine these options, although you should avoid combining two options that effectively cancel each other out, such as updateonly and createonly. The available options follow.

forceupdate. Upon conflict with existing classes, override this option with new settings. It fails if child classes have instances.

safeupdate. This option allows a safe update of the classes. Do not override existing settings with new settings.

updateonly. This option updates existing classes only. It fails if the classes do not already exist in the target namespace.

createonly. This option adds new classes only. It fails if classes already exist in the repository.

The second #pragma namespace( ) (see Figure 4.12) tells the compiler to place any classes or instances following the statement into the root namespace on the host machine. The instance declaration of type class __namespace tells the compiler to create a new namespace instance. This tells WMI to create a new namespace in the CIM repository with the value assigned to the name property. The __namespace class in the root namespace is a WMI system class that WMI uses to store all the namespaces held in the CIM repository. We have assigned the key property name a value of Example1. The CIM repository now has an additional namespace into which we shall place our example classes.

Figure 4.12Figure 4.12 The CIM repository with the new namespace, Example1


In Figure 4.13, this section of the MOF file starts by instructing the compiler to place all of the new classes and instances into the newly created Example1 namespace. It does this by specifying #pragma namespace ("\\\\.\\Root\\Example1"). In experimenting with new classes and associations within the CIM repository, it is good practice to keep all example classes away from the important systems management classes (such as those stored in the CIMV2 namespace) where they could accidentally cause problems. We do this by placing them in a separate namespace. When you have tested them and are satisfied that they are correct, you can merge them back into your target namespace (for example, the CIMV2 namespace).

Figure 4.13Figure 4.13 A compileable MOF (part 2 of 3)


The next statement declares an abstract base class called MySchema_Storage. This class has a single property called DeviceId, which is declared as both a read-only property and the key property. The read-only qualifier signifies that the value of the property cannot be changed after the instance has been created. From the perspective of a client application, this means that the value of this property cannot be altered. This property also is flagged as a key value because it will uniquely identify instances of the class.

Now type the code in Figure 4.14.

Figure 4.14Figure 4.14 A compileable MOF (Part 3 of 3)


Congratulations! You have created your first namespace, added classes to it, and created an instance of a class within the CIM repository.

NOTE

At this point, you could have used the MOF generator wizard that is part of the WMI Developer Studio to compile your sample MOF file into the CIM repository. We shall look at using the wizards in more detail in Chapter 5.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020