Service Optimization

Service Optimization uses patches to maximize the efficiency of distributing periodic updates to the packages in a service. Later, the packages contain revisions and additions to files published in earlier packages.

A patch is a published package of data (bytes) that is needed to upgrade or fix an application that is already published and installed on an agent computer. Since a patch contains only the differences between the packages, deployment of a patch takes less time and requires less network bandwidth. Patches should be built only for file changes that can be distributed more efficiently as patches than as replacement files.

The Service Optimization works as follows:

  1. The HPCA Administrator Packager or the HPCA Administrator Publisher calculates the message-digest algorithm (MD5) signature of the file as it is being published. The MD5 algorithm can take input and create a 128-bit fingerprint (message digest) of the input. This information is then stored in compressed form in the Configuration Server. For more information about MD5 signature, visit:
    www.faqs.org/rfcs/rfc1321.html
  2. The PATCH Domain in the CSDB contains the list of available patches in the PATCH Class. The file signatures of a patch are used to identify the associated instance that contains the data for the patch. For more information about the PATCH Domain, see HP Client Automation Configuration Server Database Reference Guide.
    Note: Prior to deploying patches to users, change the ZOBJPTCH variable from N to Y in the USER Class of the POLICY Domain.
  3. In the HPCA Administrator CSDB Editor, Optimize Service is an option on the Application (ZSERVICE) instance shortcut menu. It enables the administrator to create, display, and delete patches for selected application components.


© 1993 - 2012 Hewlett-Packard Development Company, L.P.