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

Provider Implementation
Packaging and Release
Chapter 4 85
procedure, or by a client program that has been implemented specifically
for this purpose. In either case, it is imperative that the schema update
follow the Rules for Updating Schema described previously.
Upgrading an Existing Provider
The basic steps in upgrading a provider are:
• Check for prerequisites
• Disable the provider. (See section on Stopping the Provider in this
chapter.)
• Move component files to target locations
• Update schema if necessary
• Complete installation tasks such as configuration
• Enable the provider
In general, providers are installed while the CIM Server is running.
Client requests will be denied while the provider is disabled.
Please refer to the section on Rules for Updating Schema when it is
necessary to modify the schema definition. Some provider upgrades may
not modify supported class schema definitions but ALL provider
upgrades must change the registration MOF since the provider version
has changed.
If a provider is implemented to operate with an upgraded schema, it may
also be designed to function correctly if it is installed with a prior version
of schema, but this is not required.
Removal
The basic steps in removing (uninstalling) a provider are:
• Check for dependencies (does anything else depend on this provider?)
• Remove the provider (see section on Removing a Provider)
• Remove schema definitions. This step is not required, and generally
may be omitted.
• Remove files from system (using swremove if files were installed with
SD)
• Perform other cleanup operations, if necessary