This manual explains how to get started with OMI. It is by no means a complete reference, but hopefully after reading it you will be able to:
OMI is a software service that runs on managed nodes. It provides the manageability infrastructure for building distributed systems management applications based on DMTF management standards, including:
These standards define:
A software service that implements these standards is a CIM Server, also known as a CIM Object Manager (CIMOM). For more information on these standards, visit the DMTF (Desktop Management Task Force) web site: http://dmtf.org.
| Note: WBEM (Web-Based Enterprise Management) comprises several standards, including CIM (Common Information Model) and WS-Management (which is now specified in ISO/IEC 17963:2013). WBEM refers to the broader set of standards. For this reason, the server is named OMI. |
In general, a CIM server enables client applications to perform operations on managed resources, such as CPUs, disks, networks, and processes. Typical operations include:
But CIM servers do not perform these operations on resources directly. Instead servers furnish developers with a framework for building pluggable modules called providers. Providers are modules that interact directly with one or more resources. For example, a "process provider" interacts with operating system processes. Providers are packaged as shared libraries with a main entry point (used by the server to initialize the provider).
OMI enables clients to perform the following CIM/WBEM operations on providers:
OMI clients initiate these operations through these protocols:
The server accepts client requests and routes them to the appropriate provider. Provider responses are routed back to the requesting client.
OMI software is currently freely available for use by anyone under the terms of the Apache 2.0 license (http://www.apache.org/licenses/LICENSE-2.0.txt).
OMI supports the following platforms.
OMI also builds on Windows with a few functional limitations.
OMI was expressly designed to work on very small systems. Conventional CIM servers are too large for embedded and mobile operating systems, but OMI will fit easily on these systems. Memory consumption is low, and the object size of the server is less than 265 kilobytes when built with the following flags:
# ./configure --favorsize --enable-32bit \ --disable-localsession --enable-sections
Additional size savings can be achieved by disabling other features if appropriate.
This chapter explains how to build and install OMI. It assumes you have obtained the OMI source distribution (omi-1.0.0.tar).
| Note: Throughout this manual, we use omi-1.0.0 to represent the OMI version that you are using. In any of the examples provided, you should replace omi-1.0.0 with your actual OMI version. |
OMI depends on the following software. Be sure these are installed on your system before building.
The following commands build and install OMI (these steps are expounded in the sections below). Note again that you should replace omi-1.0.0 with the release version of OMI that you are using.
# tar xf omi-1.0.0.tar # cd omi-1.0.0 # ./configure # make # make install
The make install command installs all files under the /opt/omi-1.0.0 directory.
The OMI source distribution is a tar file. Unpack the distribution with the tar utility as follows:
# tar xf omi-1.0.0.tar
This command creates a directory named omi-1.0.0, which contains the source distribution.
To configure the build, run the ./configure script from the root of the source distribution. Type the following to print a help message explaining how to use the script.
# ./configure --help
This will also list any new options that have been added in recent releases of OMI.
The options allow you to change where components are installed. For example, to install the programs under /usr/local/bin and everything else under /opt/omi, configure as follows.
# ./configure --prefix=/opt/omi --bindir=/usr/local/bin
The default prefix is /usr/omi-1.0.0. After installing, you will find all OMI programs (with a omi prefix) under /usr/local/bin.
OMI 1.0.6 added support for configuring the build outside of the source distribution. To do this, create a build directory outside of the source distribution and then invoke the configure script from that build directory using a relative path. For example (assuming version 1.0.6):
# tar xvf omi-1.0.6.tar # mkdir build # cd build # ../omi-1.0.6/configure # make
After configuring, build by typing make, where make refers to GNU make. For example:
# make
This builds all components.
After building the source distribution, install by typing:
# make install
You may configure and build as any user. But you must install as root since the install script creates files under root-owned directories. Even if the --prefix option specifies a non-root owned directory, the PAM authentication file (omi.pam) must be copied to a root-owned directory.
Note that wherever OMI is installed, you will find a script called omiuninstall. This script removes all installed components, but leaves any third-party components (e.g. providers and registration files) intact.
Sometimes it is useful to install all the components under a "DESTDIR" for the purposes of building an RPM or deploying the binaries to a target machine. For example, consider these steps:
$ ./configure --prefix=/opt/abc $ make $ make install DESTDIR=/tmp/destdir
So instead of installing under:
/opt/abc
OMI is installed under here instead:
/tmp/destdir/opt/abc
This procedure isolates all of the installable files for packaging or for building an install manifest.
Following the example above, a binary distribution for a given platform can be created as follows:
$ cd /tmp/destdir/ $ tar cvf omi-1.0.0-linux-x86.tar opt
Later this can be installed by simply un-tar-ing the package in the root directory of a Linux system.
After installing, you will find the installed files in the locations specified by the ./configure options. For example, if you configured with ./configure --prefix=/opt/omi, you will find the following files after installing.
/opt/omi/bin/omicli /opt/omi/bin/omigen /opt/omi/bin/omireg /opt/omi/bin/omiserver /opt/omi/bin/omiagent /opt/omi/etc/ssl/certs/omi.pem /opt/omi/etc/ssl/certs/omikey.pem /opt/omi/etc/omicli.conf /opt/omi/etc/omiregister/root-omi/omiidentify.reg /opt/omi/etc/omigen.conf /opt/omi/etc/omiserver.conf /opt/omi/lib/libmicxx.so /opt/omi/lib/libomiclient.so /opt/omi/lib/libomiidentify.so /opt/omi/share/omischema/CIM_Schema.mof ... /opt/omi/share/omi.mak /opt/omi/include/MI.h /opt/omi/include/omiclient/handler.h /opt/omi/include/omiclient/linkage.h /opt/omi/include/omiclient/client.h /opt/omi/include/micxx/atomic.h /opt/omi/include/micxx/propertyset.h /opt/omi/include/micxx/dinstance.h /opt/omi/include/micxx/instance.h /opt/omi/include/micxx/field.h /opt/omi/include/micxx/context.h /opt/omi/include/micxx/datetime.h /opt/omi/include/micxx/micxx.h /opt/omi/include/micxx/types.h /opt/omi/include/micxx/arraytraits.h /opt/omi/include/micxx/array.h /opt/omi/include/micxx/linkage.h /opt/omi/include/micxx/string.h
In addition to these files, the installer also copies a PAM (Pluggable Authentication Module) file called omi.pam under the /etc/pam directory.
The following sections discuss these installed files.
The bin directory contains all OMI programs, including:
omiserver
– the server program.
omiagent
– the provider agent program.
omigen
– the provider generation tool.
omireg
– the provider registration tool.
omicli
– the command-line client tool.
The etc directory contains system-wide configuration files used by various programs, including:
omicli.conf
– configuration file for omicli program.
omigen.conf
– configuration file for omigen program.
omiserver.conf
– configuration file for omiserver program.
The omicli
and omigen
programs look first for configuration files
named .omiclirc
and .omigenrc
in the current and home directories
(in which case the system-wide configuration file is ignored).
The lib directory contains libraries. These include:
libmi.so
– The C-language MI API support library.
libmicxx.so
– the C++ provider support library (Note that this
library has been deprecated).
libomiclient.so
– the C++ binary protocol client library.
libomiidentify.so
– the identify provider (OMI_Identify class).
The include directory contains C and C++ header files required for provider and client application development. These include:
MI.h
– C provider header file.
micxx/micxx.h
– main C++ provider header file (Note that
this has been deprecated).
omiclient/client.h
– main C++ client header file.
The omischema directory contains MOF files that define the CIM schema. These files are used by the provider generator tool (omigen) while generating provider sources. The directory contains hundreds of MOF files. The main MOF file is called CIM_Schema.mof (which includes all others).
As of omi-1.0.8, the CIM schema version being used is CIM-2.32.0.
The etc/ssl/certs directory contains PEM-formatted certificates for SSL (private and public). These include:
omi.pem
– the public certificate.
omikey.pem
– the private certificate/key.
The etc/omiregister directory contains a namespace directory for each CIM namespace. Each namespace directory has the same name as the corresponding CIM namespace, except / characters are translated to - characters. For example, for the CIM namespace root/cimv2, there is a directory named root-cimv2. The server scans the etc/omiregister directory during startup to obtain a list of supported namespaces.
Each namespace directory contains provider registration files (with a .reg extension). Each registration file corresponds to a single provider library. These files are created by the omireg utility. The following registration file (named omiidentify.reg) registers a provider that implements the OMI_Identify class.
LIBRARY=omiidentify CLASS=OMI_Identify
Placing this file in the etc/omiregister/root-omi directory, registers the provider for that namespace. The server scans all namespace directories to discover provider registrations during startup.
The share directory contains the omi.mak file. This file is included by provider makefiles generated by the omigen tool.
This chapter explains how to use the server program. It explains how to start, validate, and stop the server. It also explains various options and where to find the log files.
You may run each program by specifying its fully-qualified path, or for convenience, you may wish to add the bin directory to your path. The examples below assume you have done so.
To get help with server options, type the following.
# omiserver -h
This prints a help message that explains the usage, arguments, and options.
To start the server in the foreground, type this.
# omiserver
To start the server in the background, use the -d (daemonize) option.
# omiserver -d
Multiple instances of the server may run on the same host subject to the following constraints:
--port
command-line option or port
configuration file option.
If these constraints are not met, attempting to run a second server results in an "already running" message.
To validate that the server is working correctly, use the omicli tool to send it a request. Type omicli -h for help with this tool. When initially installed, the server only has one provider, which provides the OMI_Identify class. To enumerate all instances of this class, type the following command (id is short for identify).
# omicli id
If the server is working properly, this command should print a single instance to standard output. For example (if the OMI version were 1.0.0):
instance of OMI_Identify { [Key] InstanceID=2FDB5542-5896-45D5-9BE9-DC04430AAABE SystemName=linux ProductName=OMI 1.0.0 ProductVendor=Microsoft ProductVersionMajor=1 ProductVersionMinor=0 ProductVersionRevision=0 ProductVersionString=1.0.0 Platform=LINUX_IX86_GNU OperatingSystem=LINUX Architecture=IX86 Compiler=GNU ConfigPrefix=/tmp/omi ConfigLibDir=/tmp/omi/lib ConfigBinDir=/tmp/omi/bin ConfigIncludeDir=/tmp/omi/include ConfigDataDir=/tmp/omi/share ConfigLocalStateDir=/tmp/omi/var ConfigSysConfDir=/tmp/omi/etc ConfigProviderDir=/tmp/omi/etc ConfigLogFile=/tmp/omi/var/log/omiserver.log ConfigPIDFile=/tmp/omi/var/run/omiserver.pid ConfigRegisterDir=/tmp/omi/etc/omiregister ConfigSchemaDir=/tmp/omi/share/omischema ConfigNameSpaces={root-omi, interop, root-cimv2} }
This instance identifies various characteristics of the server and system.
To stop the server, type the following.
# omiserver -s
This stops the server by sending a signal to the process whose process id (pid) is contained in var/run/omiserver.pid. The server removes this file when it shuts down.
To enable logging, start omiserver with the option: –loglevel <level number>. To generate HTTP trc files, start omiserver with the option: –httptrace. Without these options, logging and trc files will not be enabled.
Server log messages are directed to var/log/omiserver.log. The server spawns agent processes (omiagent) in order to run providers as specified users (determined by the provider hosting model). Log messages from agents are written to files whose name has the form:
var/log/omiagent.<UID>.<GID>.log
<UID> and <GID> are the user id and group id of the agent process's owner. To browse logs, look for files under var/log whose name matches omi*.
Sometimes it is helpful to know where the server expects to find various files. Where is the server log file? Where is the provider registration directory? To obtain a list of server and file locations, type the following command.
# omiserver -p
Running this on a system where OMI was installed under /opt/omi prints the following.
prefix=/opt/omi libdir=/opt/omi/lib bindir=/opt/omi/bin localstatedir=/opt/omi/var sysconfdir=/opt/omi/etc providerdir=/opt/omi/lib certsdir=/opt/omi/etc/ssl/certs datadir=/opt/omi/share rundir=/opt/omi/var/run logdir=/opt/omi/var/log schemadir=/opt/omi/share/omischema schemafile=/opt/omi/share/omischema/CIM_Schema.mof pidfile=/opt/omi/var/run/omiserver.pid logfile=/opt/omi/var/log/omiserver.log registerdir=/opt/omi/etc/omiregister pemfile=/opt/omi/etc/ssl/certs/omi.pem keyfile=/opt/omi/etc/ssl/certs/omikey.pem agentprogram=/opt/omi/bin/omiagent serverprogram=/opt/omi/bin/omiserver includedir=/opt/omi/include configfile=/opt/omi/etc/omiserver.conf socketfile=/opt/omi/var/omiserver.sock
This chapter explains how to use the command-line client tool. This tool sends requests to the local CIM server and prints the responses to standard output. For example, omicli ei root/omi OMI_Identify sends the ei request (enumerate-instances) to the server and then prints the following on standard output (assuming, here, that the OMI version is 1.0.0):
instance of OMI_Identify { [Key] InstanceID=2FDB5542-5896-45D5-9BE9-DC04430AAABE SystemName=linux ProductName=OMI 1.0.0 ProductVendor=Microsoft ProductVersionMajor=1 ProductVersionMinor=0 ProductVersionRevision=0 ProductVersionString=1.0.0 Platform=LINUX_IX86_GNU OperatingSystem=LINUX Architecture=IX86 Compiler=GNU ConfigPrefix=/tmp/omi ConfigLibDir=/tmp/omi/lib ConfigBinDir=/tmp/omi/bin ConfigIncludeDir=/tmp/omi/include ConfigDataDir=/tmp/omi/share ConfigLocalStateDir=/tmp/omi/var ConfigSysConfDir=/tmp/omi/etc ConfigProviderDir=/tmp/omi/etc ConfigLogFile=/tmp/omi/var/log/omiserver.log ConfigPIDFile=/tmp/omi/var/run/omiserver.pid ConfigRegisterDir=/tmp/omi/etc/omiregister ConfigSchemaDir=/tmp/omi/share/omischema ConfigNameSpaces={root-omi, interop, root-cimv2} }
Each instance of { ... } construct represents an instance of a CIM class. The braces contain properties and their values. Key properties are annotated with the Key qualifier.
The general usage of the tool is:
# omicli COMMAND ARGUMENTS
The COMMAND is one of the following:
noop
– send a no-op request to the server.
gi
– send a get-instance request to the server.
ci
– send a create-instance request to the server.
mi
– send a modify-instance request to the server.
di
– send a delete-instance request to the server.
ei
– send an enumerate-instances request to the server.
iv
– send an invoke (extrinsic method) request to the server.
a
– send an associators request to the server.
r
– send an references request to the server.
id
– send an identify request to the server.
The ARGUMENTS are command-specific and are described below.
To print a help message, type the following.
# omicli -h
The message explains the syntax of key commands.
By default, when omicli and omiserver are built together (with the same prefix), the omicli program contains the location of the server's socket file. But when they are built separately, or if you want to communicate with multiple instances of the server, you must specify the socket file location using the --socketfile option. The socket file is located here: */var/run/omiserver.sock, where * is the prefix the server was built with.
The following command sends a no-op request to the server.
# omicli noop
This tests whether the server is running and responsive. If so, it prints a message indicating success. If the server is not responsive, the command will time out.
The following command enumerates instances of OMI_Identify within the root/omi namespace.
# omicli ei root/omi OMI_Identify
The following command gets a single instance of the OMI_Identify class from the root/omi namespace.
# omicli gi root/omi \ { OMI_Identify InstanceID 2FDB5542-5896-45D5-9BE9-DC04430AAABE }
The expression in braces represents the instance name for the given instance. This instance name has a single key, although an instance name may have multiple keys. Consider, for example, the following class.
class MyClass { [Key] String Key1; [Key] Uint32 Key2; [Key] Boolean Key3; ... };
And now consider the following instance of that class.
instance of MyClass { Key1=XYZ Key2=123 Key3=false ... };
The instance name for this instance is expressed as follows on the command line.
{ MyClass Key1 XYZ Key2 123 Key3 false }
In general, instance names are expressed as a class name followed by name-value pairs, all enclosed in brackets. Failing to specify values for a complete set of keys results in an error.
To invoke an extrinsic method, use the iv command, whose usage is:
# omicli iv NAMESPACE INSTANCENAME METHODNAME PARAMETERS
For example, consider the SetState extrinsic method defined by the following CIM class.
class OMI_Frog { [Key] Uint32 Key; Uint32 SetState( [In] String NewState, [In(false), Out] String OutState); };
The following command invokes the SetState method on the instance of OMI_Frog named { OMI_Frog Key 123 }.
# omicli iv root/omi { OMI_Frog Key 123 } SetState { NewState Hopping }
This command prints any output parameters to standard output. For example, the above command might print this:
{ OldState Sitting }
Use the queryexpr="select" statement to subscribe to an indication, as illustrated below.
An alert indication class derives from the standard CIM_Indication class. For instance:
class XYZ_DiskFault : CIM_Indication { string detailmessage; };
In order to subscribe to this XYZ_DiskFault indication class, run:
# omicli sub root/sample -queryexpr="select * from XYZ_DiskFault"
Consider as an example a class derived from CIM_Process:
class XYZ_Process : CIM_Process { uint32 runningTime; [static] uint32 Create( [in] string imageName, [out] CIM_Process REF process ); uint32 GetRunTime( [in] uint32 pid, [out] uint32 runningTime ); };
To subscribe to the lifecycle creation indication for instances of the XYZ_Process indication class, run:
# omicli sub root/sample -queryexpr="select * \ from CIM_InstCreation \ where SourceInstance ISA XYZ_Process"
The omiclient client library defines a C++ API that enables client applications to connect to and send requests to the CIM server. It uses a local binary protocol for communicating with the CIM server. As a result, the client application must reside on the same host as the CIM server. This chapter explains how to get started using this library.
Please note, however, that the omiclient client library is deprecated and may not be supported in future releases.
The following source files (under the source distribution) illustrate how to use the client library.
./omiclient/tests/test_client.cpp ./cli/cli.cpp
The first is the unit test for the omiclient library. The second is the main source file of the omicli tool discussed above. The examples below show how to do simple things with the client library. For more detail, see these examples.
The base name of client library is omiclient. The full name is platform dependent. For example, on Linux the full name is libomiclient.so. This library resides in the lib directory (selected when the distribution was built). The client application must be linked with this library.
Client applications must include <omiclient/client.h>. This header file defines the full client interface. It resides in the include directory (selected when the distribution was built).
The first step is to connect to the local CIM server, illustrated by the following program.
01 #include <omiclient/client.h> 02 03 using namespace std; 04 05 int main() 06 { 07 const Uint64 timeout = 30000000; 08 09 Client c; 10 String locator; 11 String username; 12 String password; 13 14 if (!c.Connect(locator, username, password, timeout)) 15 { 16 // Error! 17 } 18 29 return 0; 20 }
Line 1 includes <omiclient/client.h>, the main header file for the client interface. This header is located under the installation include directory. Consult this file to more details about the interface. Use of the omiclient library is experimental. The new C client, miapi, provides the same functionality.
Line 9 instantiates an instance of the Client class. This function takes an optional Handler instance, which is required when calling the asynchronous member functions. The examples below use the synchronous methods and so no handler is needed.
Line 14 establishes a synchronous connection with the local CIM server. The Client::Connect function takes four arguments: locator, username, password, and timeout. The locator is a string that specifies the Unix domain socket file used to connect to the server. If the locator is empty, the client uses the default socket file, located under the run directory with the name omiserver.sock.
To connect to a server whose socket file is not in the default location, set the location parameter to the the full path of that socket file, such as /opt/omi/var/run/omiserver.sock.
The username and password parameters are used to authenticate the user with the server. There are two kinds of authentication: explicit and implicit. With explicit authentication, the username and password parameters hold the log on credentials for a given user. With implicit authentication, these parameters are empty, in which case the user is authenticated using the identity of the current user (obtained with the getuid system call).
The timeout parameter specifies how long to wait (in microseconds) before failing. In this example, the timeout is 30 seconds (30,000,000 microseconds).
Developers may call the Client::Disconnect() method to explicitly disconnect from the server. Otherwise, the connection is closed implicitly by the Client destructor.
The code fragment below enumerates instances of the OMI_Identify class.
01 const String nameSpace = "root/omi"; 02 const String className = "OMI_Identify"; 03 const bool deepInheritance = true; 04 const Uint64 timeout = 2000000; 05 Array<DInstance> instances; 06 MI_Result result; 07 08 if (!c.EnumerateInstances(nameSpace, className, deepInheritance, 09 timeout, instances, result)) 10 { 11 // Error! 12 } 13 14 if (result != MI_RESULT_OK) 15 { 16 // Error! 17 } 18 19 for (Uint32 i = 0; i < instances.GetSize(); i++) 20 instances[i].Print();
Line 8 performs an enumeration request. It obtains instances of the given class from the given namespace. The resulting instances are in the instances parameter upon return.
The deepInheritance parameter specifies whether to return instances of classes derived from OMI_Identify (if true) or to return instances of OMI_Identify only (if false).
Line 19 through 20 print the resulting instances.
Use EnumerateInstances with regard for memory usage. It places all instances into memory at once, which may exhaust available memory when there are many thousands of instances. To avoid memory exhaustion, use the asynchronous form, called EnumerateInstancesAsync. All asynchronous functions use the Handler class, which defines virtual functions for delivering instances one at a time. See Appendix B for a fully asynchronous example.
The code fragment below shows how to get a single instance from the server.
01 // Construct an instance name: 02 const String className = "OMI_Identify"; 03 DInstance instanceName(className, DInstance::CLASS); 04 05 // Add a key property: 06 const String propertyName = "InstanceID"; 07 const String instanceID = "2FDB5542-5896-45D5-9BE9-DC04430AAABE"; 08 const String isNull = false; 09 const String isKey = true; 10 instanceName.AddUint32(propertyName, instanceID, isNull, isKey); 11 12 // Perform get instance: 13 const String nameSpace = "root/omi"; 14 const Uint64 TIMEOUT = 2000000; 15 DInstance instance; 16 MI_Result result; 17 if (!c.GetInstance(nameSpace, instanceName, TIMEOUT, instance, 18 result)) 19 { 20 // Error! 21 } 22 23 if (result != MI_RESULT_OK) 24 { 25 // Error! 26 } 27 28 instance.Print();
Lines 1 through 10 build an instance name (using the DInstance class). Lines 2 through 3 construct a DInstance whose class name is OMI_Identify. Lines 6 through 10 add a key property to the instance name called InstanceID.
Lines 13 through 18 perform the get instance request. Upon return, the instance parameter contains the result.
Finally, Line 28 prints the resulting instance to standard output.
This section shows how to invoke an extrinsic method. Recall the definition of the OMI_Frog class.
class OMI_Frog { [Key] Uint32 Key; Uint32 SetState( [In] String NewState, [In(false), Out] String OutState); };
The code fragment shows how to invoke the OMI_Frog.SetState method.
01 // Initialize instance name: 02 DInstance instanceName("OMI_Frog", DInstance::CLASS); 03 instanceName.AddUint32("Key", 123, false, true); 04 05 // Initialize input parameters: 06 DInstance in(T("SetState"), DInstance::METHOD); 07 in.AddString(T("NewState"), "Hopping", false, false); 08 09 // Invoke method: 10 const Uint64 TIMEOUT = 5000000; 11 DInstance out; 12 MI_Result result; 13 14 if (!c.Invoke( 15 "root/omi", 16 instanceName, 17 "SetState", 18 in, 19 TIMEOUT, 20 out, 21 result)) 22 { 23 // Error! 24 } 25 26 if (result != MI_RESULT_OK) 27 { 28 // Error! 29 } 30 31 out.Print();
Lines 2 through 3 initialize the instance name, which identifies the instance of OMI_Frog whose method will be called. This specifies a single key named Key with the value 123.
Lines 6 through 7 initialize the input parameters for the method. In this example, there is a single parameter named NewState with the value Hopping.
Lines 14 through 21 invoke the SetState method. Upon return, out holds any output parameters (the OldState parameter in this case). The out parameter always has a parameter named MIReturn, which contains the return value of the function (the return value of OMI_Frog.SetState in this example). In CIM, all functions are required to return a value.
| Note: This information in this chapter is experimental. |
MI on Windows is the Windows Management Infrastructure, also known as WMIv2. It is documented online in the MSDN Library, at http://msdn.microsoft.com/en-us/library/jj152383.aspx.
For OMI, the miapi client library can be used by including MI.h in your C source file:
#include <MI.h>
and by adding the following flags in the GNUmakefile:
–L$Omi/lib –lmi
MI introduces CDXML (cmdlet-definition XML), an XML schema for mapping Windows PowerShell cmdlets to CIM class operations or methods. PowerShell cmdlet developers use CDXML files to define cmdlets that call a CIM Object Manager (CIMOM) server such as WMI in Windows to manage the server. Cmdlets defined in CDXML communicate with remote CIM servers using the WsMan protocol, implemented by the WinRM service in Windows. This enables management of end-points that don't have PowerShell installed on them, such as a computer running Windows Server with PowerShell remoting disabled, or a computer running a CIM server like OMI or other CIM server software.
For documentation of CDXML, see http://msdn.microsoft.com/en-us/library/jj542522.aspx.
The Management Infrastructure API contains the interfaces, enumerations, structures, and unions used to developer native WMI providers and clients. It is documented online at http://msdn.microsoft.com/en-us/library/hh404805(v=vs.85).aspx.
Examples of MI operations performed using the OMI libraries are located in the OMI distribution in the samples/MIAPI folder. In general, these examples show how to perform each operation both synchronously and asynchronously.
The synchronous example generally calls MI_Operation_GetInstance in a loop to iterate through the results of the operation, whereas the asynchronous example initializes a MI_OperationCallbacks structure with the event and callbacks needed to process the results asynchronously.
The following operations are illustrated:
This chapter provides a very quick overview of the provider development process. It shows the minimum steps for building a simple instance provider. For a more complete discussion of provider development, see the next chapter.
Appendix A contains a complete listing of all file in this example. These files are also included in the source distribution under omi-1.0.0/doc/omi/samples/frog (assuming OMI version 1.0.0).
First we define the class schema shown in the schema.mof file below.
class XYZ_Frog { [Key] String Name; Uint32 Weight; String Color; };
Next we generate the provider sources and the makefile using the command below.
someuser@linux:~/gadget> omigen --cpp -m frog schema.mof XYZ_Frog Creating XYZ_Frog.h Creating XYZ_Frog_Class_Provider.h Creating XYZ_Frog_Class_Provider.cpp Creating schema.c Creating stubs.cpp Creating module.cpp Creating module.h Creating GNUmakefile
The stubs.cpp file that omigen produces contains wrapper functions that encapsulate an MI_Context* pointer within a context object, and passes that context into the cpp skeleton as a reference.
Because the context object lives on the stack, however, it is destroyed as soon as the call rewinds to the caller. Therefore, if a provider needs to save the context and use it later, the provider must use a copy of the context instead of the reference to it (which is actually a pointer).
In the following example, for instance, the call that creates a new SCX_Agent_ThreadParam passes in context.context( ) rather than just context:
MI_EXTERN_C void MI_CALL SCX_Agent_EnumerateInstances( SCX_Agent_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_PropertySet* propertySet, MI_Boolean keysOnly, const MI_Filter* filter ) { SCX_Agent_Class_Provider* cxxSelf =((SCX_Agent_Class_Provider*)self); Context cxxContext(context); cxxSelf->EnumerateInstances( cxxContext, nameSpace, __PropertySet(propertySet), __bool(keysOnly), filter ); } void SCX_Agent_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { SCX_PEX_BEGIN { std::wcout << "EnumerateInstances: Context: " << &context << ", keysOnly: " << keysOnly << std::endl; SCX_Agent_ThreadParam* params = new SCX_Agent_ThreadParam( context.context( ), keysOnly ); new SCXCoreLib::SCXThread( EnumerateInstancesThreadBody, params ); } SCX_PEX_END( L"SCX_Agent_Class_Provider::EnumerateInstances", SCXCore::g_MetaProvider.GetLogHandle( ) ); }
Next we implement the EnumerateInstances stub. The generated stub looks like this:
void XYZ_Frog_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); }
The implementation below provides two frogs.
void XYZ_Frog_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { XYZ_Frog_Class frog1; frog1.Name_value("Fred"); frog1.Weight_value(55); frog1.Color_value("Green"); context.Post(frog1); XYZ_Frog_Class frog2; frog2.Name_value("Sam"); frog2.Weight_value(65); frog2.Color_value("Blue"); context.Post(frog2); context.Post(MI_RESULT_OK); }
| Note: In CIM, a property either has a value or is null (has no value). The XYZ_Frog.Name_exists function returns true if the Frog.Name property has a value or false if the property is null (has no value). If the property has a value, one may call the XYZ_Frog.Name_value function to obtain it. |
Next we register the provider as follows:
# make reg /opt/omi/bin/omireg libfrog.so Copied provider to /opt/omi/lib/libfrog.so Created /opt/omi/etc/omiregister/root-cimv2/frog.reg
This creates frog.reg under the registration directory for the default namespace root/cimv2 and it copies the provider to the installed directory.
To test the provider, send an enumerate request to the provider as shown below.
# omicli ei root/cimv2 XYZ_Frog instance of XYZ_Frog { [Key] Name=Fred Weight=55 Color=Green } instance of XYZ_Frog { [Key] Name=Sam Weight=65 Color=Blue }
While this chapter has given a brief overview of the provider development process, the next chapter goes into provider development in more detail.
This chapter shows how to develop providers, a process consisting of 6 stages:
We discuss each stage, showing how to develop providers that implement the following operations:
OMI supports two provider language bindings: C and C++. This chapter only shows how to use the C++ binding. Whether you build C or C++ providers, the development stages are the same although the details of the interface vary. For more information about the C interface, see the <MI/MI.h> header file and experiment with generating C providers.
The first stage is to define the MOF classes comprising your schema. You may extend an existing CIM class like this:
class XYZ_MyComputerSystem : CIM_ComputerSystem { ... };
Or you may define a new root class (with no super class):
class MyClass { ... };
The MOF language is defined in the CIM Infrastructure Specification (DSP0004), which may be found at (http://dmtf.org/standards/cim).
The provider developed below implements the following class definitions (which are placed in a file called schema.mof).
// schema.mof class XYZ_Widget { [Key] Uint32 Key; Uint32 ModelNumber; String Color; }; class XYZ_Gadget { [Key] Uint32 Key; Uint32 ModelNumber; Uint32 Size; Uint32 ChangeState( [In] Uint32 NewState, [In(False), Out] Uint32 OldState); }; [Association] class XYZ_Connector { [Key] XYZ_Widget REF Left; [Key] XYZ_Gadget REF Right; };
Notice that all classes define above have the XYZ_ prefix. Similarly, all classes in the CIM schema begin have the CIM_ prefix. All classes should have a suitable prefix but for brevity, this prefix is omitted henceforth.
The Connector class is an association, as indicated by the Associator qualifier. Each instance of Connector, connects one instance of Widget with one instance of Gadget.
The second stage involves generating the provider sources. The following command generates provider sources from the schema.mof file defined above.
omigen --cpp -m xyzconnector schema.mof \ XYZ_Gadget=Gadget XYZ_Widget=Widget XYZ_Connector=Connector Creating Gadget.h Creating Gadget_Class_Provider.h Creating Gadget_Class_Provider.cpp Creating Widget.h Creating Widget_Class_Provider.h Creating Widget_Class_Provider.cpp Creating Connector.h Creating Connector_Class_Provider.h Creating Connector_Class_Provider.cpp Creating schema.c Creating stubs.cpp Creating module.cpp Creating module.h Creating GNUmakefile
The --cpp option creates C++ sources (instead of C sources by default). The -m xyzconnector option creates GNUmakefile with rules for building, regenerating, and registering the provider. This makefile creates a library whose base name is given by the -m option (xyzconnector).
| Tip: You may regenerate sources by typing make gen or by retyping the command above. The generator will never overwrite editable files. Instead it attempts to patch them. Some files are non-editable and are regenerated completely. |
The generator creates sources for classes XYZ_Gadget, XYZ_Widget, and XYZ_Connector. The command above defines aliases for each class name, allowing shorter names to be used throughout the source code. For example, XYZ_Gadget=Gadget causes Gadget.h to be generated instead of XYZ_Gadget.h. Alias can be used to completely rename a class. For example: CIM_ComputerSystem=CompSys.
To learn more about the omigen options, type omigen -h to print a help message.
The purpose of each generated file is given below.
Gadget.h
– defines C++ class for the CIM Gadget
class.
Widget.h
– defines C++ class for the CIM Widget
class.
Connector.h
– defines C++ class for the CIM Connector
class.
Gadget_Class_Provider.h
– defines Gadget_Class_Provider
class.
Gadget_Class_Provider.cpp
– defines Gadget_Class_Provider
class.
Widget_Class_Provider.h
– defines Widget_Class_Provider
class.
Widget_Class_Provider.cpp
– defines Widget_Class_Provider
class.
Connector_Class_Provider.h
– defines Connector_Class_Provider
class.
Connector_Class_Provider.cpp
– defines Connector_Class_Provider
class.
schema.c
– internal definitions.
stubs.cpp
– internal definitions.
module.cpp
– defines MI_Main library entry point.
module.h
– defines Module class.
GNUmakefile
– defines rules for building the provider library.
Many of these files are not intended to be edited. Developer edits may be made to the following files.
Gadget_Class_Provider.h
Gadget_Class_Provider.cpp
Widget_Class_Provider.h
Widget_Class_Provider.cpp
Connector_Class_Provider.h
Connector_Class_Provider.cpp
module.h
module.cpp
For example, to implement the get-instances operation for the Gadget class, modify the Gadget_Class_Provider.cpp file.
This section shows how to implement the following provider operations:
This section implement the enumerate-instances operation for the Gadget
class. This implementation provides the following instances (shown in MOF
format).
instance of XYZ_Gadget { Key = 1003; ModelNumber = 3; Size = 33; }; instance of XYZ_Gadget { Key = 1004; ModelNumber = 4; Size = 43; };
To implement the enumerate-instance operation for the Gadget
class,
start by examining the generated stub (see Gadget_Class_Provider.cpp).
void Gadget_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); }
This function is invoked by the CIM server. The implementer may respond on the same thread or he may create a new thread if the request is long running. The lifetime of the request is bound to the lifetime of the context parameter. All parameters remain in scope until the provider calls Context::Post. The provider may create a new thread to handle the request, in which case the parameters may live beyond the invocation of EnumerateInstances.
We provide an implementation that provides two instances of the Gadget class. The following implementation handles the request on the calling thread.
void Gadget_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { // Gadget.Key=1003: { Gadget_Class g; g.Key_value(1003); g.ModelNumber_value(3); g.Size_value(33); context.Post(g); } // Gadget.Key=1004: { Gadget_Class g; g.Key_value(1004); g.ModelNumber_value(4); g.Size_value(43); context.Post(g); } context.Post(MI_RESULT_OK); }
This function constructs instances of the Gadget class and passes them to the Context::Post function. When all instances have been posted, the provider passes the result status to the Context::Post function. This finalizes the request.
| Tip: By passing the --nogi CLASSNAME option (no get-instance) to the generator tool, the server uses the enumerate-instances implementation to satisfy all get-instance requests. Only use this technique if the number of instances is small, otherwise the provider will be very slow. |
Next we show how to implement the get-instance
operation for the
Gadget
class. Here is the generated stub for the get-instance
request.
void Gadget_Class_Provider::GetInstance( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const PropertySet& propertySet) { context.Post(MI_RESULT_NOT_SUPPORTED); }
The instanceName
parameter holds the keys for the target instance.
Here is the full implementation of this function.
void Gadget_Class_Provider::GetInstance( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const PropertySet& propertySet) { if (instanceName.Key_value() == 1003) { // Gadget.Key=1003: Gadget_Class g; g.Key_value(1003); g.ModelNumber_value(3); g.Size_value(33); context.Post(g); context.Post(MI_RESULT_OK); } else if (instanceName.Key_value() == 1004) { // Gadget.Key=1004: Gadget_Class g; g.Key_value(1004); g.ModelNumber_value(4); g.Size_value(43); context.Post(g); context.Post(MI_RESULT_OK); } else { context.Post(MI_RESULT_NOT_FOUND); } }
We examine the key and return the matching instance. If neither condition matches, we post the MI_RESULT_NOT_FOUND result.
This section implements the ChangeState extrinsic method. The generator produces the following stub.
void Gadget_Class_Provider::Invoke_ChangeState( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const Gadget_ChangeState_Class& in) { context.Post(MI_RESULT_NOT_SUPPORTED); }
The instanceName parameter is the instance whose ChangeState method has been invoked (this parameter is omitted for static methods). The in parameter contains the input parameters. The implementation should perform the following tasks:
The following implementation performs each of these steps.
void Gadget_Class_Provider::Invoke_ChangeState( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const Gadget_ChangeState_Class& in) { Gadget_ChangeState_Class out; // Print the input parameter: if (in.NewState_exists()) { printf("NewState=%u\n", in.NewState_value()); } // Perform desired action here: ... // Set the output parameter: out.OldState_value(2); // Set the return value: out.MIReturn_value(0); // Post the "out" object. context.Post(out); // Post the result status. context.Post(MI_RESULT_OK); }
This section shows how to implement the enumerate-instances operation for the Connector association class. This operation produces the following instances (shown in MOF format).
instance of XYZ_Connector { Left = "XYZ_Widget.Key=1001"; Right = "XYZ_Gadget.Key=1003"; }; instance of XYZ_Connector { Left = "XYZ_Widget.Key=1002"; Right = "XYZ_Gadget.Key=1004"; };
Here is the implementation.
void Connector_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { // Connector.Left="Gadget.Key=1001","Widget.Key=1003" { Widget_Class w; w.Key_value(1001); Gadget_Class g; g.Key_value(1003); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); } // Connector.Left="Gadget.Key=1002","Widget.Key=1004" { Widget_Class w; w.Key_value(1002); Gadget_Class g; g.Key_value(1004); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); } context.Post(MI_RESULT_OK); }
The following example implements get-instance for the Connector association class.
void Connector_Class_Provider::GetInstance( Context& context, const String& nameSpace, const Connector_Class& instanceName, const PropertySet& propertySet) { if (instanceName.Left_value().Key_value() == 1001 && instanceName.Right_value().Key_value() == 1003) { // Connector.Left="Gadget.Key=1001","Widget.Key=1003" Widget_Class w; w.Key_value(1001); Gadget_Class g; g.Key_value(1003); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); context.Post(MI_RESULT_OK); } else if (instanceName.Left_value().Key_value() == 1002 && instanceName.Right_value().Key_value() == 1004) { // Connector.Left="Gadget.Key=1002","Widget.Key=1004" Widget_Class w; w.Key_value(1001); Gadget_Class g; g.Key_value(1003); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); context.Post(MI_RESULT_OK); } else { context.Post(MI_RESULT_NOT_FOUND); } }
Note that instanceName.Left_value()
returns an instance of type
Gadget
(see MOF definitions). And so
instanceName.Left_value().Key_value()
returns the Key property
of the associated Gadget
instance.
This section shows how to implement the associator-instances operation. This
operation finds the other end of an association. For example, it might find
the Gadget
instances that are associated with a single Widget
instance (through a Connector
instance). For example, consider the
following MOF definitions.
instance of XYZ_Connector { Left = "XYZ_Widget.Key=1001"; Right = "XYZ_Gadget.Key=1003"; }; instance of XYZ_Connector { Left = "XYZ_Widget.Key=1002"; Right = "XYZ_Gadget.Key=1004"; };
The associator-instances operation starts with the instance name of an instance and finds associated instances. For example, the associator-instances of:
XYZ_Widget.Key=1001
include:
XYZ_Gadget.Key=1003
The generator produces two stubs to handle associator-instances requests.
The first yields associators in which the instanceName
parameter matches
the first reference property (Connector.Left
). The second yields
associations in which the instanceName
parameter matches the second
reference property (Connector.Right
). The stubs are defined as follows.
void Connector_Class_Provider::AssociatorInstancesLeft( Context& context, const String& nameSpace, const Widget_Class& instanceName, const String& resultClass, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); } void Connector_Class_Provider::AssociatorInstancesRight( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const String& resultClass, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); }
The following implementation yields associators of Widget
instances.
void Connector_Class_Provider::AssociatorInstancesLeft( Context& context, const String& nameSpace, const Widget_Class& instanceName, const String& resultClass, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { if (instanceName.Key_value() == 1001) { // Gadget.Key=1003: Gadget_Class g; g.Key_value(1003); g.ModelNumber_value(3); g.Size_value(33); context.Post(g); context.Post(MI_RESULT_OK); } else if (instanceName.Key_value() == 1002) { // Gadget.Key=1004: Gadget_Class g; g.Key_value(1004); g.ModelNumber_value(4); g.Size_value(43); context.Post(g); context.Post(MI_RESULT_OK); } else { context.Post(MI_RESULT_NOT_FOUND); } }
The reference-instances operation takes an instance name and finds the reference instances that refer to it. Consider the following MOF definitions.
instance of XYZ_Connector { Left = "XYZ_Widget.Key=1001"; Right = "XYZ_Gadget.Key=1003"; }; instance of XYZ_Connector { Left = "XYZ_Widget.Key=1002"; Right = "XYZ_Gadget.Key=1004"; };
For example, the reference-instance of XYZ_Widget.Key=1001
includes the
first MOF instance shown above. As with associator-instances, the generator
produces two stubs:
void Connector_Class_Provider::ReferenceInstancesLeft( Context& context, const String& nameSpace, const Widget_Class& instanceName, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); } void Connector_Class_Provider::ReferenceInstancesRight( Context& context, const String& nameSpace, const Gadget_Class& instanceName, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { context.Post(MI_RESULT_NOT_SUPPORTED); }
The implementation of ReferenceInstancesLeft
is shown below.
void Connector_Class_Provider::ReferenceInstancesLeft( Context& context, const String& nameSpace, const Widget_Class& instanceName, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { if (instanceName.Key_value() == 1001) { // Connector.Left="Gadget.Key=1001","Widget.Key=1003" Widget_Class w; w.Key_value(1001); Gadget_Class g; g.Key_value(1003); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); context.Post(MI_RESULT_OK); } else if (instanceName.Key_value() == 1002) { // Connector.Left="Gadget.Key=1002","Widget.Key=1004" Widget_Class w; w.Key_value(1002); Gadget_Class g; g.Key_value(1004); Connector_Class c; c.Left_value(w); c.Right_value(g); context.Post(c); context.Post(MI_RESULT_OK); } else { context.Post(MI_RESULT_NOT_FOUND); } }
Please note that indications should only be posted from a separate thread within the provider (a “background thread”). They should not be posted using the omiserver thread during a call into a provider. For example, during an EnumerateInstances call, the provider should directly post its instances and final result. It should not directly post indications within that function call. Instead, it should post indications on a separate background thread. Violation of this policy may trigger unexpected behavior in omiserver. The following examples illustrate appropriate techniques for posting alert and lifecycle indications.
As an example, consider the following MOF schema:
/* Indication class derived from the CIM standard indication class */ class XYZ_DiskFault : CIM_Indication { string detailmessage; };
The generated code snippet looks like this:
void MI_CALL XYZ_DiskFault_EnableIndications( XYZ_DiskFault_Self* self, MI_Context* indicationsContext, const MI_Char* nameSpace, const MI_Char* className ) { /* TODO: store indicationsContext for posting indication usage */ /* NOTE: Call one of following functions if and ONLY if a termination error occurs, to finalize the indicationsContext, and terminate all active subscriptions to current class: MI_Context_PostResult MI_Context_PostError MI_Context_PostCimError */ } void MI_CALL XYZ_DiskFault_DisableIndications( XYZ_DiskFault_Self* self, MI_Context* indicationsContext, const MI_Char* nameSpace, const MI_Char* className ) { /* TODO: stop background thread that monitors subscriptions */ MI_PostResult( indicationsContext, MI_RESULT_OK ); } void MI_CALL XYZ_DiskFault_Subscribe( XYZ_DiskFault_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_Filter* filter, const MI_Char* bookmark, MI_Uint64 subscriptionID, void** subscriptionSelf ) { /* NOTE: This function indicates that a new subscription occurred */ } void MI_CALL XYZ_DiskFault_Unsubscribe( XYZ_DiskFault_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, MI_Uint64 subscriptionID, void* subscriptionSelf ) { /* NOTE: This function indicates that a subscription was cancelled */ MI_PostResult( context, MI_RESULT_OK ); }
The implementation of this indication class is shown below (see the sample code in the Indication/Alert subdirectory under the samples directory for the complete implementation):
void MI_CALL XYZ_DiskFault_EnableIndications( XYZ_DiskFault_Self* self, MI_Context* indicationsContext, const MI_Char* nameSpace, const MI_Char* className ) { /* TODO: store indicationsContext for posting indication usage */ /* NOTE: Call one of following functions if and ONLY if a termination error occurs, to finalize the indicationsContext, and terminate all active subscriptions to current class: MI_Context_PostResult MI_Context_PostError MI_Context_PostCimError */ int code; memset( self, 0, sizeof(XYZ_DiskFault_Self) ); self->self.context = indicationsContext; self->self.postindication = TriggerIndication; code = Thread_Create(&self->self.thread, fireIndication, (void*)self); if ( code != 0 ) { /* Failed to create thread */ MI_Context_PostError( indicationsContext, MI_RESULT_FAILED, MI_T("MI"), MI_T("Failed to create thread") ); } } void MI_CALL XYZ_DiskFault_DisableIndications( XYZ_DiskFault_Self* self, MI_Context* indicationsContext, const MI_Char* nameSpace, const MI_Char* className ) { /* TODO: stop background thread that monitors subscriptions */ MI_Uint32 retValue; self->self.disabling = MI_TRUE; Thread_Join( & self->self.thread, &retValue ); MI_PostResult( indicationsContext, MI_RESULT_OK ); }
This section describes how to implement lifecycle indication support in a normal class.
Consider a common process class as an example:
/* A class derived from CIM_Process */ class XYZ_Process : CIM_Process { uint32 runningTime; [static] uint32 Create( [in] string imageName, [out] CIM_Process REF process ); uint32 GetRunTime( [in] uint32 pid, [out] uint32 runningTime ); };
The generated code snippet looks like this:
void MI_CALL XYZ_Process_EnumerateInstances( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_PropertySet* propertySet, MI_Boolean keysOnly, const MI_Filter* filter ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_GetInstance( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Process* instanceName, const MI_PropertySet* propertySet ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_CreateInstance( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Process* newInstance ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_ModifyInstance( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Process* modifiedInstance, const MI_PropertySet* propertySet ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_DeleteInstance( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Process* instanceName ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_Invoke_RequestStateChange( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_Char* methodName, const XYZ_Process* instanceName, const XYZ_Process_RequestStateChange* in ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_Invoke_Create( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_Char* methodName, const XYZ_Process* instanceName, const XYZ_Process_Create* in ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); } void MI_CALL XYZ_Process_Invoke_GetRunTime( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_Char* methodName, const XYZ_Process* instanceName, const XYZ_Process_GetRunTime* in ) { MI_PostResult( context, MI_RESULT_NOT_SUPPORTED ); }
Implementation of lifecycle indications within this class takes a form like the following:
void MI_CALL XYZ_Process_Load( XYZ_Process_Self** self, MI_Module_Self* selfModule, MI_Context* context ) { MI_Result r; *self = &g_self; memset(&g_self, 0, sizeof(g_self)); /* get lifecycle context and store the context for * posting indication usage */ r = MI_Context_GetLifecycleIndicationContext( context, &(*self)->context); CHECKR_POST_RETURN_VOID(context, r); /* register a callback, which will be invoked if subscription * changed, i.e., client cancelled a subscription or create a new * subscription */ r = MI_LifecycleIndicationContext_RegisterCallback( (*self)->context, _LifecycleIndicationCallback, (void*)(ptrdiff_t)(*self)); CHECKR_POST_RETURN_VOID(context, r); /* notify server that what types of lifecycle indication * supported by current class */ r = MI_LifecycleIndicationContext_SetSupportedTypes( (*self)->context, MI_LIFECYCLE_INDICATION_CREATE); CHECKR_POST_RETURN_VOID(context, r); /* intialize global data */ r = _Initialize(context, *self); if (r != MI_RESULT_OK) { _Finalize(*self); *self = NULL; } else { int code; (*self)->self.context = (*self)->context; (*self)->self.postindication = TriggerIndication; /* * Please note that lifecycle indications should only be posted * from a background thread. * * This XYZ_Process example spawns a background thread that will * periodically fire CIM_InstCreation indications to simulate * process creation events. */ code = Thread_Create(&(*self)->self.thread, fireIndication, (void*)(*self)); if ( code != 0 ) { /* Failed to create thread */ r = MI_RESULT_FAILED; _Finalize(*self); } } MI_PostResult(context, r); *self = &g_self; } void MI_CALL XYZ_Process_Unload( XYZ_Process_Self* self, MI_Context* context) { MI_Uint32 retValue; /* Shutdown the spawned thread */ self->self.disabling = MI_TRUE; Thread_Join( & self->self.thread, &retValue ); /* cleanup */ _Finalize( self ); MI_LifecycleIndicationContext_PostResult(self->context,MI_RESULT_OK); MI_PostResult( context, MI_RESULT_OK ); _Finalize(self); } void MI_CALL XYZ_Process_EnumerateInstances( XYZ_Process_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_PropertySet* propertySet, MI_Boolean keysOnly, const MI_Filter* filter ) { MI_Uint32 i; MI_Result r; for( i = 0; i < PROCESS_COUNT; i++ ) { r = XYZ_Process_Post( &self->processes[i], context ); if( r != MI_RESULT_OK ) break; } MI_PostResult( context, r ); } /* * Callback function to trigger lifecycle indication (CIM_InstCreation) * for XYZ_Process. * This function simulates the process creation events by posting a * CIM_InstCreation indication. * * In reality, the provider may utilize the system API to monitor the * system-wide process creation event, and generate a corresponding * CIM_InstCreation indication via the lifecycle context; the same goes * for CIM_InstDeletion, CIM_InstModification, CIM_InstRead, * CIM_InstMethodCall, etc. */ MI_Uint32 MI_CALL TriggerIndication( _In_ void* callbackdata) { XYZ_Process_Self* self = (XYZ_Process_Self*)callbackdata; MI_LifecycleIndicationContext* context = self->context; MI_Uint32 seqno = self->seqno++; MI_Uint32 index = seqno % PROCESS_COUNT; /* * When practical, the provider developer needs to get the process * creation event, for example by monitoring a system event or * responding to a system API, and then trigger a Cim_InstCreation * indication. * * In order to trigger a CIM_InstCreation indication, the XYZ_Process * instance needs to be created first. * After that, call MI_LifecycleIndicationContext_PostCreate function. * * The following sample code shows how to create a XYZ_Process * instance and trigger a CIM_InstCreation indication of XYZ_Process. */ if( self->types & MI_LIFECYCLE_INDICATION_CREATE ) { XYZ_Process process; MI_Result r; r = MI_LifecycleIndicationContext_ConstructInstance( context, &XYZ_Process_rtti, &process.__instance); if (r == MI_RESULT_OK) { r = _SetPropertyValue(index, &process); if ( r == MI_RESULT_OK ) /* Post CIM_InstCreation indication from background thread */ MI_LifecycleIndicationContext_PostCreate(context, &process.__instance); /* Destroy the instance */ MI_Instance_Destruct(&process.__instance); } } return 1; } /*=================================================================== ** ** Thread proc to post the indication periodically ** **===================================================================*/ MI_Uint32 THREAD_API fireIndication(void* param) { SelfStruct* self = (SelfStruct*)param; MI_Uint32 exitvalue = 1; if ( !self || !self->context || !self->postindication ) { exitvalue = 0; goto EXIT; } /* initialize random seed: */ SRAND(); /* produce and post indication */ while( MI_TRUE != self->disabling ) { if ( 0 == self->postindication(self) ) break; /* randomly sleep */ Sleep_Milliseconds(rand() % 1000 + 500); } EXIT: Thread_Exit(exitvalue); return exitvalue; }
An alternative way to generate a lifecycle indication is to define an indication class that derives from the lifecycle indication class. For example, consider the ABC_Process class below. ABC_ProcessCreation is defined so as to generate a CIM_InstCreation indication for the ABC_Process class:
class ABC_Process : CIM_Process { uint32 runningTime; [static] uint32 Create( [in] string imageName, [out] CIM_Process REF process ); }; class ABC_ProcessCreation : CIM_InstCreation { };
For more detailed examples of indication implementations, please see the Indication subdirectory under the samples directory.
To build the provider with the generated GNUmakefile
just type
make
. This creates a shared library, containing the provider. On Linux,
this file will be named libxyzconnector.so.
To register the provider, use the omireg tool, which creates a registration file (xyzconnector.reg) under the registration directory and copies the provider to the lib directory. For example:
$ omireg libxyzconnector.so Created /opt/omi/lib/libxyzconnector.so Created /opt/omi/etc/omiregister/root-cimv2/xyzconnector.reg
By default the provider is hosted in the same process as the server. To host the provider in a separate process see the --hosting option.
Also by default the provider services the root/cimv2 namespace. To change the namespace, see the --namespace option.
For more help with the omireg tool, use the -h option.
The contents of the xyzconnector.reg file are listed below.
# omireg /home/someuser/connector/libxyzconnector.so HOSTING=@inproc@ LIBRARY=xyzconnector CLASS=XYZ_Connector{XYZ_Widget,XYZ_Gadget} CLASS=XYZ_Gadget CLASS=XYZ_Widget
It is better to use omireg
to re-generate these files rather than
editing them directly. If you do edit them, you should only need to change
the hosting model. The supported hosting models include:
To validate the provider, use the omicli tool to send requests to the new providers. The following command enumerates instances of the new Widget provider.
# omicli ei root/cimv2 XYZ_Widget
class XYZ_Frog { [Key] String Name; Uint32 Weight; String Color; };
/* @migen@ */ /* **===================================================================== ** ** WARNING: THIS FILE WAS AUTOMATICALLY GENERATED. PLEASE DO NOT EDIT. ** **===================================================================== */ #ifndef _XYZ_Frog_h #define _XYZ_Frog_h #include <MI.h> /* **===================================================================== ** ** XYZ_Frog [XYZ_Frog] ** ** Keys: ** Name ** **===================================================================== */ typedef struct _XYZ_Frog { MI_Instance __instance; /* XYZ_Frog properties */ /*KEY*/ MI_ConstStringField Name; MI_ConstUint32Field Weight; MI_ConstStringField Color; } XYZ_Frog; typedef struct _XYZ_Frog_Ref { XYZ_Frog* value; MI_Boolean exists; MI_Uint8 flags; } XYZ_Frog_Ref; typedef struct _XYZ_Frog_ConstRef { MI_CONST XYZ_Frog* value; MI_Boolean exists; MI_Uint8 flags; } XYZ_Frog_ConstRef; typedef struct _XYZ_Frog_Array { struct _XYZ_Frog** data; MI_Uint32 size; } XYZ_Frog_Array; typedef struct _XYZ_Frog_ConstArray { struct _XYZ_Frog MI_CONST* MI_CONST* data; MI_Uint32 size; } XYZ_Frog_ConstArray; typedef struct _XYZ_Frog_ArrayRef { XYZ_Frog_Array value; MI_Boolean exists; MI_Uint8 flags; } XYZ_Frog_ArrayRef; typedef struct _XYZ_Frog_ConstArrayRef { XYZ_Frog_ConstArray value; MI_Boolean exists; MI_Uint8 flags; } XYZ_Frog_ConstArrayRef; MI_EXTERN_C MI_CONST MI_ClassDecl XYZ_Frog_rtti; MI_INLINE MI_Result MI_CALL XYZ_Frog_Construct( XYZ_Frog* self, MI_Context* context) { return MI_ConstructInstance(context, &XYZ_Frog_rtti, (MI_Instance*)&self->__instance); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Clone( const XYZ_Frog* self, XYZ_Frog** newInstance) { return MI_Instance_Clone( &self->__instance, (MI_Instance**)newInstance); } MI_INLINE MI_Boolean MI_CALL XYZ_Frog_IsA( const MI_Instance* self) { MI_Boolean res = MI_FALSE; return MI_Instance_IsA( self, &XYZ_Frog_rtti, &res ) == MI_RESULT_OK && res; } MI_INLINE MI_Result MI_CALL XYZ_Frog_Destruct(XYZ_Frog* self) { return MI_Instance_Destruct(&self->__instance); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Delete(XYZ_Frog* self) { return MI_Instance_Delete(&self->__instance); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Post( const XYZ_Frog* self, MI_Context* context) { return MI_PostInstance(context, &self->__instance); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Set_Name( XYZ_Frog* self, const MI_Char* str) { return self->__instance.ft->SetElementAt( (MI_Instance*)&self->__instance, 0, (MI_Value*)&str, MI_STRING, 0); } MI_INLINE MI_Result MI_CALL XYZ_Frog_SetPtr_Name( XYZ_Frog* self, const MI_Char* str) { return self->__instance.ft->SetElementAt( (MI_Instance*)&self->__instance, 0, (MI_Value*)&str, MI_STRING, MI_FLAG_BORROW); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Clear_Name( XYZ_Frog* self) { return self->__instance.ft->ClearElementAt( (MI_Instance*)&self->__instance, 0); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Set_Weight( XYZ_Frog* self, MI_Uint32 x) { ((MI_Uint32Field*)&self->Weight)->value = x; ((MI_Uint32Field*)&self->Weight)->exists = 1; return MI_RESULT_OK; } MI_INLINE MI_Result MI_CALL XYZ_Frog_Clear_Weight( XYZ_Frog* self) { memset((void*)&self->Weight, 0, sizeof(self->Weight)); return MI_RESULT_OK; } MI_INLINE MI_Result MI_CALL XYZ_Frog_Set_Color( XYZ_Frog* self, const MI_Char* str) { return self->__instance.ft->SetElementAt( (MI_Instance*)&self->__instance, 2, (MI_Value*)&str, MI_STRING, 0); } MI_INLINE MI_Result MI_CALL XYZ_Frog_SetPtr_Color( XYZ_Frog* self, const MI_Char* str) { return self->__instance.ft->SetElementAt( (MI_Instance*)&self->__instance, 2, (MI_Value*)&str, MI_STRING, MI_FLAG_BORROW); } MI_INLINE MI_Result MI_CALL XYZ_Frog_Clear_Color( XYZ_Frog* self) { return self->__instance.ft->ClearElementAt( (MI_Instance*)&self->__instance, 2); } /* **===================================================================== ** ** XYZ_Frog provider function prototypes ** **===================================================================== */ /* The developer may optionally define this structure */ typedef struct _XYZ_Frog_Self XYZ_Frog_Self; MI_EXTERN_C void MI_CALL XYZ_Frog_Load( XYZ_Frog_Self** self, MI_Module_Self* selfModule, MI_Context* context); MI_EXTERN_C void MI_CALL XYZ_Frog_Unload( XYZ_Frog_Self* self, MI_Context* context); MI_EXTERN_C void MI_CALL XYZ_Frog_EnumerateInstances( XYZ_Frog_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const MI_PropertySet* propertySet, MI_Boolean keysOnly, const MI_Filter* filter); MI_EXTERN_C void MI_CALL XYZ_Frog_GetInstance( XYZ_Frog_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Frog* instanceName, const MI_PropertySet* propertySet); MI_EXTERN_C void MI_CALL XYZ_Frog_CreateInstance( XYZ_Frog_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Frog* newInstance); MI_EXTERN_C void MI_CALL XYZ_Frog_ModifyInstance( XYZ_Frog_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Frog* modifiedInstance, const MI_PropertySet* propertySet); MI_EXTERN_C void MI_CALL XYZ_Frog_DeleteInstance( XYZ_Frog_Self* self, MI_Context* context, const MI_Char* nameSpace, const MI_Char* className, const XYZ_Frog* instanceName); /* **===================================================================== ** ** XYZ_Frog_Class ** **===================================================================== */ #ifdef __cplusplus # include <micxx/micxx.h> MI_BEGIN_NAMESPACE class XYZ_Frog_Class : public Instance { public: typedef XYZ_Frog Self; XYZ_Frog_Class() : Instance(&XYZ_Frog_rtti) { } XYZ_Frog_Class( const XYZ_Frog* instanceName, bool keysOnly) : Instance( &XYZ_Frog_rtti, &instanceName->__instance, keysOnly) { } XYZ_Frog_Class( const MI_ClassDecl* clDecl, const MI_Instance* instance, bool keysOnly) : Instance(clDecl, instance, keysOnly) { } XYZ_Frog_Class( const MI_ClassDecl* clDecl) : Instance(clDecl) { } XYZ_Frog_Class& operator=( const XYZ_Frog_Class& x) { CopyRef(x); return *this; } XYZ_Frog_Class( const XYZ_Frog_Class& x) : Instance(x) { } static const MI_ClassDecl* GetClassDecl() { return &XYZ_Frog_rtti; } // // XYZ_Frog_Class.Name // const Field<String>& Name() const { const size_t n = offsetof(Self, Name); return GetField<String>(n); } void Name(const Field<String>& x) { const size_t n = offsetof(Self, Name); GetField<String>(n) = x; } const String& Name_value() const { const size_t n = offsetof(Self, Name); return GetField<String>(n).value; } void Name_value(const String& x) { const size_t n = offsetof(Self, Name); return GetField<String>(n).Set(x); } bool Name_exists() const { const size_t n = offsetof(Self, Name); return GetField<String>(n).exists ? true : false; } void Name_clear() { const size_t n = offsetof(Self, Name); GetField<String>(n).Clear(); } // // XYZ_Frog_Class.Weight // const Field<Uint32>& Weight() const { const size_t n = offsetof(Self, Weight); return GetField<Uint32>(n); } void Weight(const Field<Uint32>& x) { const size_t n = offsetof(Self, Weight); GetField<Uint32>(n) = x; } const Uint32& Weight_value() const { const size_t n = offsetof(Self, Weight); return GetField<Uint32>(n).value; } void Weight_value(const Uint32& x) { const size_t n = offsetof(Self, Weight); return GetField<Uint32>(n).Set(x); } bool Weight_exists() const { const size_t n = offsetof(Self, Weight); return GetField<Uint32>(n).exists ? true : false; } void Weight_clear() { const size_t n = offsetof(Self, Weight); GetField<Uint32>(n).Clear(); } // // XYZ_Frog_Class.Color // const Field<String>& Color() const { const size_t n = offsetof(Self, Color); return GetField<String>(n); } void Color(const Field<String>& x) { const size_t n = offsetof(Self, Color); GetField<String>(n) = x; } const String& Color_value() const { const size_t n = offsetof(Self, Color); return GetField<String>(n).value; } void Color_value(const String& x) { const size_t n = offsetof(Self, Color); return GetField<String>(n).Set(x); } bool Color_exists() const { const size_t n = offsetof(Self, Color); return GetField<String>(n).exists ? true : false; } void Color_clear() { const size_t n = offsetof(Self, Color); GetField<String>(n).Clear(); } }; typedef Array<XYZ_Frog_Class> XYZ_Frog_ClassA; MI_END_NAMESPACE #endif /* __cplusplus */ #endif /* _XYZ_Frog_h */
/* @migen@ */ #ifndef _XYZ_Frog_Class_Provider_h #define _XYZ_Frog_Class_Provider_h #include "XYZ_Frog.h" #ifdef __cplusplus # include <micxx/micxx.h> # include "module.h" MI_BEGIN_NAMESPACE /* **===================================================================== ** ** XYZ_Frog provider class declaration ** **===================================================================== */ class XYZ_Frog_Class_Provider { /* @MIGEN.BEGIN@ CAUTION: PLEASE DO NOT EDIT OR DELETE THIS LINE. */ private: Module* m_Module; public: XYZ_Frog_Class_Provider( Module* module); ~XYZ_Frog_Class_Provider(); void Load( Context& context); void Unload( Context& context); void EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter); void GetInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& instance, const PropertySet& propertySet); void CreateInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& newInstance); void ModifyInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& modifiedInstance, const PropertySet& propertySet); void DeleteInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& instance); /* @MIGEN.END@ CAUTION: PLEASE DO NOT EDIT OR DELETE THIS LINE. */ }; MI_END_NAMESPACE #endif /* __cplusplus */ #endif /* _XYZ_Frog_Class_Provider_h */
/* @migen@ */ #include <MI.h> #include "XYZ_Frog_Class_Provider.h" MI_BEGIN_NAMESPACE XYZ_Frog_Class_Provider::XYZ_Frog_Class_Provider( Module* module) : m_Module(module) { } XYZ_Frog_Class_Provider::~XYZ_Frog_Class_Provider() { } void XYZ_Frog_Class_Provider::Load( Context& context) { context.Post(MI_RESULT_OK); } void XYZ_Frog_Class_Provider::Unload( Context& context) { context.Post(MI_RESULT_OK); } void XYZ_Frog_Class_Provider::EnumerateInstances( Context& context, const String& nameSpace, const PropertySet& propertySet, bool keysOnly, const MI_Filter* filter) { XYZ_Frog_Class frog1; frog1.Name_value("Fred"); frog1.Weight_value(55); frog1.Color_value("Green"); context.Post(frog1); XYZ_Frog_Class frog2; frog2.Name_value("Sam"); frog2.Weight_value(65); frog2.Color_value("Blue"); context.Post(frog2); context.Post(MI_RESULT_OK); } void XYZ_Frog_Class_Provider::GetInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& instanceName, const PropertySet& propertySet) { context.Post(MI_RESULT_NOT_SUPPORTED); } void XYZ_Frog_Class_Provider::CreateInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& newInstance) { context.Post(MI_RESULT_NOT_SUPPORTED); } void XYZ_Frog_Class_Provider::ModifyInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& modifiedInstance, const PropertySet& propertySet) { context.Post(MI_RESULT_NOT_SUPPORTED); } void XYZ_Frog_Class_Provider::DeleteInstance( Context& context, const String& nameSpace, const XYZ_Frog_Class& instanceName) { context.Post(MI_RESULT_NOT_SUPPORTED); } MI_END_NAMESPACE
#ifndef _Module_t_h #define _Module_t_h #include <MI.h> #include <micxx/micxx.h> MI_BEGIN_NAMESPACE /* An instance of this class is automatically created when the library is loaded, so it's a convenient place to store global data associated with the module */ class Module { public: Module(); ~Module(); }; MI_END_NAMESPACE #endif /* _Module_t_h */
#include <MI.h> #include "module.h" MI_BEGIN_NAMESPACE Module::Module() { } Module::~Module() { } MI_END_NAMESPACE
/* @migen@ */ /* **===================================================================== ** ** WARNING: THIS FILE WAS AUTOMATICALLY GENERATED. PLEASE DO NOT EDIT. ** **===================================================================== */ #include <ctype.h> #include <MI.h> #include "XYZ_Frog.h" /* **===================================================================== ** ** Schema Declaration ** **===================================================================== */ extern MI_SchemaDecl schemaDecl; /* **===================================================================== ** ** Qualifier declarations ** **===================================================================== */ /* **===================================================================== ** ** XYZ_Frog ** **===================================================================== */ /* property XYZ_Frog.Name */ static MI_CONST MI_PropertyDecl XYZ_Frog_Name_prop = { MI_FLAG_PROPERTY|MI_FLAG_KEY, /* flags */ 0x006E6504, /* code */ MI_T("Name"), /* name */ NULL, /* qualifiers */ 0, /* numQualifiers */ MI_STRING, /* type */ NULL, /* className */ 0, /* subscript */ offsetof(XYZ_Frog, Name), /* offset */ MI_T("XYZ_Frog"), /* origin */ MI_T("XYZ_Frog"), /* propagator */ NULL, }; /* property XYZ_Frog.Weight */ static MI_CONST MI_PropertyDecl XYZ_Frog_Weight_prop = { MI_FLAG_PROPERTY, /* flags */ 0x00777406, /* code */ MI_T("Weight"), /* name */ NULL, /* qualifiers */ 0, /* numQualifiers */ MI_UINT32, /* type */ NULL, /* className */ 0, /* subscript */ offsetof(XYZ_Frog, Weight), /* offset */ MI_T("XYZ_Frog"), /* origin */ MI_T("XYZ_Frog"), /* propagator */ NULL, }; /* property XYZ_Frog.Color */ static MI_CONST MI_PropertyDecl XYZ_Frog_Color_prop = { MI_FLAG_PROPERTY, /* flags */ 0x00637205, /* code */ MI_T("Color"), /* name */ NULL, /* qualifiers */ 0, /* numQualifiers */ MI_STRING, /* type */ NULL, /* className */ 0, /* subscript */ offsetof(XYZ_Frog, Color), /* offset */ MI_T("XYZ_Frog"), /* origin */ MI_T("XYZ_Frog"), /* propagator */ NULL, }; static MI_PropertyDecl MI_CONST* MI_CONST XYZ_Frog_props[] = { &XYZ_Frog_Name_prop, &XYZ_Frog_Weight_prop, &XYZ_Frog_Color_prop, }; static MI_CONST MI_ProviderFT XYZ_Frog_funcs = { (MI_ProviderFT_Load)XYZ_Frog_Load, (MI_ProviderFT_Unload)XYZ_Frog_Unload, (MI_ProviderFT_GetInstance)XYZ_Frog_GetInstance, (MI_ProviderFT_EnumerateInstances)XYZ_Frog_EnumerateInstances, (MI_ProviderFT_CreateInstance)XYZ_Frog_CreateInstance, (MI_ProviderFT_ModifyInstance)XYZ_Frog_ModifyInstance, (MI_ProviderFT_DeleteInstance)XYZ_Frog_DeleteInstance, (MI_ProviderFT_AssociatorInstances)NULL, (MI_ProviderFT_ReferenceInstances)NULL, (MI_ProviderFT_EnableIndications)NULL, (MI_ProviderFT_DisableIndications)NULL, (MI_ProviderFT_Subscribe)NULL, (MI_ProviderFT_Unsubscribe)NULL, (MI_ProviderFT_Invoke)NULL, }; /* class XYZ_Frog */ MI_CONST MI_ClassDecl XYZ_Frog_rtti = { MI_FLAG_CLASS, /* flags */ 0x00786708, /* code */ MI_T("XYZ_Frog"), /* name */ NULL, /* qualifiers */ 0, /* numQualifiers */ XYZ_Frog_props, /* properties */ MI_COUNT(XYZ_Frog_props), /* numProperties */ sizeof(XYZ_Frog), /* size */ NULL, /* superClass */ NULL, /* superClassDecl */ NULL, /* methods */ 0, /* numMethods */ &schemaDecl, /* schema */ &XYZ_Frog_funcs, /* functions */ }; /* **===================================================================== ** ** __mi_server ** **===================================================================== */ MI_Server* __mi_server; /* **===================================================================== ** ** Schema ** **===================================================================== */ static MI_ClassDecl MI_CONST* MI_CONST classes[] = { &XYZ_Frog_rtti, }; MI_SchemaDecl schemaDecl = { NULL, /* qualifierDecls */ 0, /* numQualifierDecls */ classes, /* classDecls */ MI_COUNT(classes), /* classDecls */ }; /* **===================================================================== ** ** MI_Server Methods ** **===================================================================== */ MI_Result MI_CALL MI_Server_GetVersion( MI_Uint32* version){ return __mi_server->serverFT->GetVersion(version); } MI_Result MI_CALL MI_Server_GetSystemName( const MI_Char** systemName) { return __mi_server->serverFT->GetSystemName(systemName); }
/* @migen@ */ /* **===================================================================== ** ** WARNING: THIS FILE WAS AUTOMATICALLY GENERATED.  PLEASE DO NOT EDIT. */ extern MI_Server* __mi_server; static MI_Module module; __mi_server = server; module.flags |= MI_MODULE_FLAG_STANDARD_QUALIFIERS; module.flags |= MI_MODULE_FLAG_CPLUSPLUS; module.charSize = sizeof(MI_Char); module.version = MI_VERSION; module.generatorVersion = MI_MAKE_VERSION(1,0,0); module.schemaDecl = &schemaDecl; module.Load = Load; module.Unload = Unload; return &module; }
HOST=$(shell hostname) include ../../../../output/$(shell hostname)/omi.mak PROVIDER = frog SOURCES = $(wildcard *.c *.cpp) CLASSES = XYZ_Frog $(LIBRARY): $(OBJECTS) $(CXX) $(CXXSHLIBFLAGS) $(OBJECTS) -o $(LIBRARY) $(CXXLIBS) %.o: %.c $(CC) -c $(CFLAGS) $(INCLUDES) $< $(CLIBS) -o $@ %.o: %.cpp $(CXX) -c $(CXXFLAGS) $(INCLUDES) $< -o $@ reg: $(BINDIR)/omireg $(CURDIR)/$(LIBRARY) gen: $(BINDIR)/omigen --cpp -m frog schema.mof XYZ_Frog clean: rm -f $(LIBRARY) $(OBJECTS) $(PROVIDER).reg
#include <cstdio> #include <omiclient/client.h> #define T MI_T using namespace mi; class MyHandler : public Handler { public: MyHandler() : done(false) { } virtual void HandleConnect() { printf("==== MyHandler::HandleConnect()\n"); } virtual void HandleNoOp(Uint64 msgID) { printf("==== MyHandler::HandleNoOp()\n"); } virtual void HandleConnectFailed() { printf("==== MyHandler::HandleConnectFailed()\n"); // Handler error! done = true; } virtual void HandleDisconnect() { printf("==== MyHandler::HandleDisconnect()\n"); done = true; } virtual void HandleInstance(Uint64 msgID, const DInstance& instance) { printf("==== MyHandler::HandleInstance()\n"); instance.Print(); } virtual void HandleResult(Uint64 msgID, MI_Result result) { printf("==== MyHandler::HandleResult()\n"); done = true; } bool done; }; int main(int argc, const char* argv[]) { int r = 0; // Create handler: MyHandler* handler = new MyHandler; // Construct client: Client client(handler); String locator; String username; String password; if (!client.ConnectAsync(locator, username, password)) { // Handle error! } const String nameSpace = "root/omi"; const String className = "OMI_Identify"; const bool deep = true; Uint64 msgID; if (!client.EnumerateInstancesAsync( nameSpace, className, deep, msgID)) { // Handle error! } // Wait here for 5 seconds for operation to finish. while (!handler->done) { client.Run(1000); } return r; }
This appendix explains how to build OMI with a cross compiler. Two such targets are supported today:
MONTAVISTA_IX86_GNU NETBSD_IX86_GNU
Additional platforms can be supported by extending the buildtool script (following MONTAVISTA_IX86_GNU target as an example).
The "host" platform is where the compiler is run to build OMI. The "target" platform is where the output binaries files will run. These can be the same, but in the case of cross-compiling they are different. This appendix uses the term "target" to refer to the platform where the binaries will be run.
By default, the configure script guesses the platform based on the host environment. But with cross-compiling, the platform is given by the –target option as shown below:
./configure --target=MONTAVISTA_IX86_GNU
Additional options are required to specify to location of the cross-compiler components. These include:
--with-cc=PATH Use C compiler given by PATH. --with-cxx=PATH Use C++ compiler given by PATH. --with-ar=PATH Use archive command (ar) given by PATH. --openssl=PATH Full path to the "openssl" command. --opensslcflags=FLAGS Extra C flags needed for OpenSSL. (e.g. "-I/usr/local/include"). --openssllibs=FLAGS Extra library options needed for OpenSSL. (e.g. "-L/usr/local/lib -lssl -lcrypto"). --openssllibdir=PATH The path of the directory containing the desired OpenSSL libraries (ssl and crypto).
So to run configure, one might have something like this:
./configure --target=NETBSD_IX86_GNU --with-cc=/opt/toolchain/bin/586-gcc --with-cxx=/opt/toolchain/bin/586-g++ --with-ar=/opt/toolchain/bin/586-ar --opensslcflags="-I /opt/toolchain/include" --openssllibdir=/opt/toolchain/lib64 --openssllibs="-L/opt/toolchain/lib64 -lssl -lcrypto"
Of course this is only an example. The exact location of these components will vary.
When cross-compiling, it is obviously no longer possible to simply type "make install" to install the components (since the components must be copied to another platform). Instead, components may be installed into an interim directory and then copied from there onto the target platform. The DESTDIR variable can be used for this purpose. For example, suppose that we configured like this:
./configure --target=NETBSD_IX86_GNU --prefix=/opt/omi --with-cc=/opt/toolchain/bin/586-gcc --with-cxx=/opt/toolchain/bin/586-g++ --with-ar=/opt/toolchain/bin/586-ar --opensslcflags="-I /opt/toolchain/include" --openssllibdir=/opt/toolchain/lib64 --openssllibs="-L/opt/toolchain/lib64 -lssl -lcrypto"
Next, the installable components can all be copied to an interim directory called "/tmp/install" like this:
make DESTDIR=/tmp/install install
Finally, the components can be copied from the /tmp/install directory to the target machine.
This document defines a C unit test framework and instructions for its use. This framework is a replacement for existing unit test infrastructure that makes debugging, maintenance, and code coverage significantly easier. The unit test framework encompasses several related components:
There are five different possible ways to link to the NITS package, each with its own consequences:
This section describes the basic source tree configuration steps required to access the NITS API. Once these steps are complete, product and test binaries are ready to start using the framework. The project will need access to the following files from the framework: nits.h, libnits.so, libpal.a, libnitsstub.a, nitsstub.obj and nits.
The recommended, supported project configuration is as follows:
For canonical up-to-date working examples, see the sample product and test code in the following directories:
The nits binaries are built only in the unittest environment, i.e. when the --dev option is passed to the ./configure script during configuration and build. the nits executable is created inside the <output>/bin/ directory (where "<output>" is the directory where output from the OMI build is saved. The libnits.so, libnitsstub.a, and libnitsinj.so are all present in the <output>/lib directory and can be used directly from there.
In order to run tests in all directories or in a single test directory, you can run:
make tests
This in turn invokes nits with appropriate command-line arguments and runs the single test or all test binaries.
The file <output>/tmp/nitsargs.txt contains the command-line arguments passed to nits during the test run, if you use the -file: option passed to nits to include it.
NITS provides facilities to allow private APIs to be callable at will without individually exporting all of them. This makes it convenient to link test shared libraries directly against product shared libraries, which in turn allows simple and reliable code coverage measurements. The alternative is linking the test code to product static libraries, which leads to product code existing in many binaries at once. While this is not technically broken, it is impossible to retrieve accurate coverage data in complex cases, and this has some tendency to encourage duplication of product code in multiple product binaries.
Public interfaces must be exported somehow. This may be done individually for each API, or function tables may be used (as in mi.h) to export an entire collection of APIs from one binary using a single export macro like MI_EXPORT. The latter technique leads to smaller binary size but requires more care to avoid introducing breaking changes to the contents of the table.
Non-public interfaces do not need to be exported in the same way. The recommended approach is to place all of the externally callable private APIs from a given product binary into a single NitsTrapTable, and then import that table into all the binaries that call any of the APIs. Macros can be used to hide this behavior from the calling binaries. A simple example is available in nits/sample/test.cpp.
NITS supports mocking private APIs that are already exposed through a function table using the NitsSetTrap API. The only additional change needed in the product is that all mockable calls in the product must invoke through the trap table, rather than directly calling the function. When NitsSetTrap is called, the function pointer in the table is replaced and all calls through the pointer are redirected to the mock. For a simplified proof of concept, see AutitTest in nits/sample/test.spp.
The usage pattern for NITS is the following: nits [option|test]*. The rest of this section describes the available options and test types, along with the possible results for each test.
Tests may be run using any of the following syntax forms:
The simplest way to discover a list of valid test names and variations for a particular module is to run the entire module with the -mode:Skip option.
Note: To run the NITS sample tests, use nits as follows:
./output/bin/nits -install -reset -trace \ -target:libnitssample.so,libnitssampleproduct.so \ ./output/lib/libnitssample.so |
Each test variation reports a result to the test framework. These results are printed and then summarized. The possible test results are as follows:
This section describes how to create basic unit tests under the NITS framework. This section shows only the most basic examples, using as few features as possible. See the following section for additional examples for advanced features. To run a test DLL containing a simple, "hello world" unit test, see the following example:
#include <nits/base/nits.h> NitsTest(Test1) NitsTrace(PAL_T("Test Body!")); NitsAssert(1 == 1, PAL_T("assert test!")); NitsCompare(1, 1, PAL_T("compare test!")); NitsCompareString(PAL_T("A"), PAL_T("A"), PAL_T("string test!")); NitsCompareSubstring(PAL_T("ABC"),PAL_T("B"),PAL_T("substring test!")); NitsEndTest
The code above contains a simple test body with some basic assertions and traces. Note that the assertion descriptions must be Unicode, but some other arguments may be either ANSI or Unicode. Inserting this code into hello.dll and compiling it produces a binary which can be run using the following command:
./output/bin/nits ./output/lib/libhello.so [Passed] ./output/lib/libhello.so:Test1 Summary: Faulted: 0 Passed: 1 Skipped: 0 Killed: 0 Failed: 0 Error: 0 Successes: 1 Failures: 0 Total: 1
This listing shows that the test named Test1 in libhello.so was run successfully. The test passed because the body ran one or more test assertions, all of which succeeded.
This section contains a partial list of available NITS features, roughly in order of increasing complexity. Each feature can be used independently of the others unless otherwise specified.
The API NitsTrace is available for tracing messages using the current source location as the call site. These messages will appear in stderr only if tracing is enabled.
The NitsAssert, NitsCompare, NitsCompareString, and NitsCompareSubstring APIs validate results obtained during the test. These functions return true if successful, but otherwise they are printed to stderr if assertions are enabled.
NITS defines a NitsCallSite class which is available on all linkages, though on some linkages it becomes trivialized. This class contains a source file, line, function name, and call site ID to be used for fault injection and source location identification. The APIs above use the current source line (returned by the NitsHere( ) macro) as the NitsCallSite. However, this is not appropriate in common helper functions where it is actually the caller"s location that is relevant. The following example shows how to carry a CallSite through to a helper function:
void TestHelper( NitsCallSite cs ) { //Prints location of NitsHere( ) below. NitsTraceEx( L"Helper function!", cs, NitsAutomatic ); } NitsTest(Test1) TestHelper(NitsHere()); NitsEndTest
The macros NitsTraceEx, NitsAssertEx, NitsCompareEx, NitsCompareStringEx, and NitsCompareSubstringEx are available for this purpose, each taking the same argument list as their counterparts, plus a call site argument. NitsCallSite objects may be created easily using either the NitsHere( ) or NitsNamedCallSite macros. For manual fault simulation, use NitsNamedCallSite(id), where the site ID is defined by the application. Otherwise, NitsHere( ), which is anonymous, generally suffices.
NITS tests are made from one or more Fixtures. Fixtures are reusable units of test code. They support composability; i.e. they can be composed out of other fixtures. They also allow you to share data between each other by letting you associate a type(a C struct) with them and providing an initialization value for that type. There are various types of fixtures:
These types of fixtures are described in the following sections, along with an illustration of how you can share data between fixtures using an auto-created abstraction called a NitsContext( ).
The most basic setup fixture involves bracketing some test code between NitsSetup(<fixtureName>) and NitsEndSetup macros. Here is an example of such a fixture:
NitsSetup(SimpleSetup) NitsTrace(PAL_T("SimpleSetup being run")); NitsEndSetup
| Note: NitsEndSetup and similar end macros are part of every fixture, and they help NITS provide a function continuation style of usage, in which all the fixtures from which your test is composed are on the same stack. This lets you use local variables throughout the entire lifetime of the test. |
To associate a data type with a Setup fixture, you need to define a C struct as the data type, and write test code between the NitsSetup0( <fixtureName>, <name of the data type> ) and NitsEndSetup macros. Below is an example that shows how to associate a type with a Setup fixture:
struct MyStruct { int x; }; NitsSetup0( Fixture0, MyStruct ) NitsContext( )->_MyStruct->x = 0; NitsEndSetup
The syntax for composing a Setup fixture with 1 other child fixture wold begin with the start macro:
NitsSetup1( <fixtureName>, <name of fixture data Type>, <name of child fixture 1>, <initialization value for child fixture 1> )
The test code would follow, and be ended by the NitsEndSetup macro.
Below is an example of how to compose a fixture from one other child fixture while also associating a data type with each fixture so that you can pass data back and forth in either direction:
struct FooStruct1 { int i1; }; struct FooStruct2 { int i2; }; NitsSetup0( FooSetup1, FooStruct1 ) NitsAssert(NitsContext()->_FooStruct1->i1 == 10, PAL_T("wrong value")); NitsContext()->_FooStruct1->i1 = 15; NitsTrace(PAL_T("FooSetup1 being run")); NitsEndSetup struct FooStruct1 sFooStruct1 = {10}; NitsSetup1( FooSetup2, FooStruct2, FooSetup1, sFooStruct1 ) NitsAssert(NitsContext()->_FooSetup1->_FooStruct1->i1 == 15, PAL_T("wrong value")); NitsContext()->_FooSetup1->_FooStruct1->i1 = 35; NitsContext()->_FooStruct2->i2 = 25; NitsTrace(PAL_T("FooSetup2 being run")); NitsEndSetup
NitsSetup<2/3/4/5>( <fixtureName>, <dataTypeOfFixture>, <child fixture1, <initialization value of child fixture1>, <child fixture2>, <initialization value of child fixture2>, <child fixture3>, <initialization value of child fixture3>, <child fixture4>, <initialization value of child fixture4>, <child fixture5>, <initialization value of child fixture5> )
(gdb) bt #0 FooSetup2 (_NitsContext=0x60e990) at NitsNewInterfaceTests.cpp:489 #3 0x00007ffff76c4e3b in FooSetup1 (_NitsContext=0x60e950) at NitsNewInterfaceTests.cpp:485 #13 0x0000000000400dd2 in main (argc=6, argv=0x7fffffffe558) at nits.cpp:146
The NitsDeclSetup<N>/NitsDefSetup<N> macros allow you declare fixtures in a .h file and define them in .cpp files. This lets you reuse the same Setup fixture in multiple files.
Here is an example:
Foo.h => struct MyStruct { int x; }; NitsDeclSetup0(Fixture0, MyStruct); Foo.cpp => NitsDefSetup0(Fixture0, MyStruct) NitsContext()->_MyStruct->x = 0; NitsEndSetup
Using Split fixtures, you can split the execution of tests into two or more tests. This lets you execute the same test code in multiple configurations. A Split fixture that splits a test into two child fixtures starts with a NitsSplit2 macro having the following syntax:
NitsSplit2( <fixtureName>, <data type of fixture>, <name of child fixture 1>, <name of child fixture 2> )
Place the test code after this macro, and end it with the NitsEndSplit macro.
Below is an example of a Split fixture composed of two child fixtures that define two child configurations in which the test will run:
struct MyContext { int a; }; NitsSetup0(MySetup1, MyContext) NitsContext()->_MyContext->a = 4; NitsEndSetup NitsSetup0(MySetup2, MyContext) NitsContext()->_MyContext->a = 8; NitsEndSetup NitsSplit2(MySplitSetup, MyContext, MySetup1, MySetup2) NitsAssert((NitsContext()->_MyContext->a == 4) || (NitsContext()- >_MyContext->a == 8), PAL_T("value is wrong")); NitsEndSplit
NitsSplit<3 or 4 or 5>( <fixtureName>, <data type of fixture>, <name of child fixture 1>, <name of child fixture 2>, <name of child fixture 3>, <name of child fixture 4>, <name of child fixture 5> )
Test is just one other kind of fixture in NITS. The implementation section above already defined NitsTest/NitsEndTest syntax for basic tests in NITS. This section describes syntax for more advanced tests that are composed of one or more other Setup or Split fixtures. A Test fixture composed of one child fixture starts with a NitsTest1 macro having the following syntax:
NitsTest1( <testFixtureName>, <child fixture 1>, <initializer for child fixture 1> )
Test code follows, and the fixture is ends with the NitsEndTest macro. Here is an example:
struct FooStruct1 { int i1; }; NitsSetup0(FooSetup1, FooStruct1) NitsAssert(NitsContext()->_FooStruct1->i1 == 20, PAL_T("wrong value")); NitsContext()->_FooStruct1->i1 = 35; NitsEndSetup struct FooStruct1 sFooStruct1 = {20}; NitsTest1(FooTest, FooSetup1, sFooStruct1) NitsAssert( NitsContext()->_FooSetup1->_FooStruct1->i1 == 35, PAL_T("wrong value")); NitsEndTest
NitsTest<2 or 3 or 4 or 5>( <testfixtureName>, <child fixture 1>, <initializer for child fixture 1>, <child fixture 2>, <initializer for child fixture 2>, <child fixture 3>, <initializer for child fixture 3>, <child fixture 4>, <initializer for child fixture 4>, <child fixture 5>, <initializer for child fixture 5> )
Cleanup fixture can be defined on any of the above type of fixtures (i.e. on Setup, Split, Test, or ModuleSetup fixtures). The Cleanup fixture is run at the end of the test body for Setup, Split, and Test fixtures, and at the end of the test module for ModuleSetup fixtures. Because a Cleanup fixture has access to the same NitsContext( ) as the fixture for which it is cleaning up, you can use it to clean up anything you need to.
A Cleanup fixture begins with a NitsCleanup macro that uses the following syntax:
NitsCleanup( <fixtureName for which the Cleanup fixture is defined> )
The code for the body of the test follows this start macro, and NitsEndCleanup. Here is an example:
NitsSetup(MySetup1) NitsTrace(PAL_T("MySetup1 being run")); NitsEndSetup NitsCleanup(MySetup1) NitsTrace(PAL_T("Cleanup for MySetup1 being run")); NitsEndCleanup
ModuleSetup fixtures let you define test code that is run at the beginning and end of the test module. This is useful in places where you want to run some piece of test code only once per test module at the beginning and end of it.
Here is an example:
NitsModuleSetup(MyModuleSetup1) NitsTrace(PAL_T("MyModuleSetup1 being run")); NitsAssert(PAL_TRUE, PAL_T("")); NitsEndModuleSetup NitsCleanup(MyModuleSetup1) NitsTrace(PAL_T("Cleanup for MyModuleSetup1 being run")); NitsEndCleanup
In the case where functions to be tested are inside a class written in C++, you need to write C wrappers for those functions. In class1:
class class1 { int foo1(); };
The corresponding NITSs C++ file containing traps should look something like this:
PAL_BEGIN_EXTERNC int class1_foo1() { class1* obj = construct_class1(); return obj->foo1(); } class1* construct_class1() { return new class1(); } PAL_END_EXTERNC NitsTrapValue(class1Traps) class1_foo NitsEndTrapValue
The corresponding NITS traps header file should look something like this:
NitsTrapTable(class1Traps,0) int (NITS_CALL* _class1_foo)(); NitsEndTrapTable NitsTrapExport(class1Traps)
A NITS test for the above product class might look like the following (assuming that the product binary is named libfoo.so):
struct Ptr { void* ptr; }; Ptr PtrVal = {NULL}; NitsSetup0(MyModuleSetup1, Ptr) NitsTrapHandle h = NitsOpenTrap("libfoo.so", class1Traps); NitsAssert(h != NULL, PAL_T("Failed to load cla11Traps")); NitsContext()->_Ptr->ptr = h; // Optionally, you could call a helper function too: CallHelperFunction() NitsEndSetup NitsCleanup(MyModuleSetup1) NitsTrapHandle h = NitsContext()->_Ptr-ptr; if(h != NULL) NitsCloseTrap(h); NitsEndCleanup NitsTest(MyModuleSetup1, PtrVal) NitsTrapHandle h = NitsContext()->_op1->_Ptr->ptr; int result = NitsGetTrap(h, class1Traps, _class1_foo)(); NitsAssert(result != 1, PAL_T("Test failed")); NitsEndTest
NITS provides automatic fault simulation functionality, which works as follows:
int Foo() { if(NitsShouldFault(NitsHere(), NitsAutomatic)) { // Simulate failure path behavior // failure return return -1; } // continue with implementation // success return return 0; }
On the NITS command line, use the +loglevel:<value> option to set the level of logging detail (loglevel) to one of the following values, which are NOT case-sensitive:
0 1 2 3 4 5 FATAL ERR WARNING INFO DEBUG VERBOSE
For example:
nits +loglevel:5 test_base.dll output/bin/nits +loglevel:verbose output/lib/libtest_miapi.so
The resulting log files are saved in the <topleveldir>/output/var/log/ directory as follows:
output/bin/nits +loglevel:verbose +logstderr:1 \ output/lib/libtest_base.so
Remember, however, that this works only for tests that do not use the MI API (i.e. everything other than test_cli and test_miapi). MI-API code closes the log every time the test closes the MI application. As a result, even if the test library tried to set the log to stderr so as to print to the console, output would be routed to the miclient.log every time the MI application closes and re-opens.
| Note: Because +loglevel:<value> and +logstderr:1 are not built-in NITS command-line options, they are not included in NITS usage help. They are implemented through the NITS module setup/cleanup constructs that let us run code at the beginning and end of a test module run. In this way, we use a common Setup/Cleanup fixture defined inside the ut\ directory to set the loglevels and route the log data to stderr at the beginning of the module level setup, and to close the log during the module level cleanup. |
Below is an example of using NitsModuleSetup/NitsCleanup from ut\omitestcommon.cpp. You can have multiple module-level setups and cleanups in a module. All Module setups will be run at the beginning of the test module and all cleanups at the end after running all tests within the module.
NitsModuleSetup(OMITestSetup) NitsTrace(PAL_T("OMITestSetup being run")); if(NitsTestGetParam(PAL_T("logstderr"))) { Log_OpenStdErr(); } else { PAL_Char finalPath[PAL_MAX_PATH_SIZE]; /* Create name and Open the log file */ if((CreateLogFileNameWithPrefix("omitest", finalPath) != 0) || (Log_Open(finalPath) != MI_RESULT_OK)) { NitsTrace( PAL_T("failed to open log file; routing output to stderr")); Log_OpenStdErr(); } } const PAL_Char *loglevelParam = NitsTestGetParam(PAL_T("loglevel")); if(loglevelParam && Log_SetLevelFromPalCharString(loglevelParam) != 0) { NitsTrace( PAL_T("loglevel parameter invalid; not setting loglevel")); NitsAssert(PAL_FALSE, PAL_T("loglevel parameter invalid")); } NitsAssert(PAL_TRUE, PAL_T("")); NitsEndModuleSetup NitsCleanup(OMITestSetup) NitsTrace(PAL_T("Cleanup of OMITestSetup being run")); Log_Close(); NitsAssert(PAL_TRUE, PAL_T("")); NitsEndCleanup