HP Insight Management WBEM Providers for HP integrated VMware ESXi 5.0 U1 June 2012 Profiles

18 HP Software Inventory and Update Profile Version 2.0.0

5.3.2 Retrieving the Component Bytes from a Software Repository Service

A client application would first get search the repository for the desired SoftwareIdentity from the Software

Repository Service. If the desired SoftwareIdentity was discovered, the client application would get the

reference to the SoftwareIdentity from the Software Repository Service. Then the application would use

SoftwareRepositoryService.GetSoftwareIdentityByteStream(), passing in the desired reference.

5.3.3 Retrieving the URI for a SoftwareIdentity in a Software Repository

A client application would first get search the repository for the desired SoftwareIdentity from the Software

Repository Service. If the desired SoftwareIdentity was discovered, the client application would get the

reference to the SoftwareIdentity from the Software Repository Service. Then the application would use

SoftwareRepositoryService.GetURIForSoftwareIdentity(), passing in the desired reference.

5.3.4 Software Repository Service with Heirarchical Collections

5.3.5 Client Uses GetSoftwareIdentityByteStream() then InstallFromURI()

In this example, the client application has a web server and can make installable components available

via URI.

The client application would first retrieve the component from the repository using

SoftwareRepositoryService.GetSoftwareIdentityByteStream() as described in section 5.3.1.

The client application would store the byte stream locally and call the target system’s InstallFromURI()

with a link to the file, as described in the profile 1025.

5.3.6 Using InstallFromURI() to Install Component From Repository

The client application would first get a URI to a SoftwareIdentity as described in section 5.3.2.

The client then calls the SoftwareInstallationService.InstallFromURI() method on the target system using

the URI retrieved from the repository.