Develop > Presentation layer > Customize IBM Sales Center > Deploy customizations to the IBM Sales Center > Update mechanisms
Distribute updates independently
Once a set of features are installed on the client, it may later be necessary to distribute fixes and changes to the installed code. Just as the initial code took the form of plugins and features packaged into an Eclipse update site for installation, modifications are provided as updated plugins and features and again packaged into an Eclipse update site. This section explains how to distribute updates independently.
Eclipse Update Sites containing new revisions of features can be distributed exactly as if they were original features. The mechanisms of manual installation, provisioning using the embedded Tivoli DMS agent, and software distribution using non-integrated products like Tivoli Configuration Manager, can all be employed exactly as described earlier.
Use these mechanisms means that no new infrastructure or training is necessary to distribute version 1.0.1 of a feature than was necessary for version 1.0.0. It also permits version 1.0.1 to be distributed both to clients that had version 1.0.0 installed, and to clients that do not have any previous version. The platform runtime will detect and disable any previous version that is being overridden.
Related concepts
Deploy customizations to the IBM Sales Center