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 480

providers remain loaded until a system administrator invokes a

command to stop and unload them. The cimprovider command is used

for this purpose, and is described in the cimprovider man page.

The steps required to stop and unload a provider so that a new shared

library can be installed are:

1. Stop the provider using the cimprovider command. (Note that this

command actually operates on the provider module and stops all

providers in the module.) For example:

$ cimprovider -d -m TestProviderModule

Disabling provider module...

Provider module disabled successfully.

In some cases, it may be necessary to change the Provider

Registration. This must be done by using the cimprovider command

to remove the Provider Registration instances, rather than simply

stop the provider as described in the previous step.

$ cimprovider -r -m TestProviderModule

Note that this form of the cimprovider command will remove

registration for all providers in the speciﬁed module. Registrations

for individual providers can be removed with:

$ cimprovider -r -m TestProviderModule -p ABCProvider

After registrations have been removed, new registration instances

must be created as described in the previous section, Installing and

Running a Provider.

2. The provider shared library ﬁle may now be replaced with the new

version:

$ mv <build-path>/libTestProviderModule.sl

<test-path>

Note that it is not generally possible to build the new provider

shared library directly into the location of an existing shared library

which is currently in use. HP-UX locks binary ﬁles that are in use,

and any attempt to modify will result in a message that the ﬁle is

busy. This is why it is necessary to direct the CIM Server to disable

and unload the shared library with the cimprovider command.

3. Finally, the provider can be re-enabled with the cimprovider

command: