Understanding Local Software

In this section, you will learn how to add, edit, and delete local software components that are Non-Certified by the Lab (NCOs). These procedures are available only to users with full permissions or the admin user.

NCO Detection and Rule Generation

If am NCO is installed on a managed host, Sun Update Connection – Enterprise automatically detects it and adds it to your local knowledge base. If the NCO is not yet installed (it is on a CD or other source), you can add it to the knowledge base on demand.

When an NCO is added to the local knowledge base, the Local Expansion technology generates rules for NCO deployment. (Be aware that rules generated on-site are not as rigorous as those created by Sun.)

NCOs in Component Lists

The NCO is placed in the Components list. If it is a new package, it is placed under Local RPMs or Local PKGs. If it is an unknown version of a known package (for example, if your organization creates a proprietary patch for an application), the NCO is placed under Software. You can use the Find feature (see To Find Components) to find it under a Software listing.

NCO Privacy

Your local knowledge base data (the package, its listing, its rules) are never pushed back to the universal server, nor are they overwritten by downloaded updates. The local knowledge base is secured for your private site.