HP WBEM Services Software Developer's Kit for HP-UX Provider and Client Developer's Guide A.01

Provider Implementation
Testing and Debugging Providers
Chapter 4 81
$ cimprovider -e -m TestProviderModule
Enabling provider module...
Provider module enabled successfully.
Again, if the provider was removed in order to update the Provider
Registration, rather than simply stopped, then it must be
re-registered with cimmof, rather than re-enabled with cimprovider,
as described in the previous section on Installing and Running a
Provider.
Testing With Clients
Once the provider has been installed for testing as described in the
previous section, it is available for testing. The shared library will be
automatically loaded and the provider initialized on the first client
operation on a CIM class served by the provider.
HP WBEM Services for HP-UX is delivered with a simple,
general-purpose command-line client suitable for testing providers:
wbemexec, described in the associated man page. It is used to send
xmlCIM messages containing CIM operations to the CIM server, which
will forward them to the appropriate provider. An example of an xmlCIM
request and response is included in Appendix B, XML Example.
The following example command illustrates how wbemexec can be used
to send this request to the CIM Server on the local (same) system,
redirecting the reply to a file for later analysis:
$ wbemexec enumInstNames.xml > reply.xml
The sample providers included with the SDK are accompanied by XML
requests that may be modified to test providers. The sample providers
are located in the /opt/wbem/sample/Providers directory.
The sample client programs included with the SDK illustrate the use of
EnumerateInstances and InvokeMethod client APIs. They may be
modified to test a given provider. Information on client development can
be found in the Client Implementation section of this document.