Managing Local Patches and Dependencies

If you create a homegrown patch for either a CO or an NCO, you can upload your component and mark it as a patch.

For example, your organization has a software developed in-house. Some time later, it is discovered that this software has a security issue. The component is patched to fix the security issue and is packed again.

Without Sun Update Connection – Enterprise, you would have to uninstall every instance of the software and install the new one. With Sun Update Connection – Enterprise, everything is handled automatically. You upload the new version to the knowledge base, and in the Add Software window, you mark the upload as a Security Fix.

You run a Security Check (Running Predefined Profiles). Wherever the earlier version was installed, the agents upgrade it to the secured version.