Attaching Linux Software to Detected Listings

In this procedure, you learn how to attach a local RPM to an NCO name in the Components list. The name must already be in the Components list.

Table 5–1 Reasons for Performing the Attach Procedure

Environment	Indicator
Sometimes a package may be uploaded and automatically attached to the NCO listing, but you want to replace the package with one of your own choosing.	A local component listing that has a package already associated with it, is indicated by the full icon.
Sometimes the system dependency server may be unable to upload the package itself. Use this procedure to manually attach the correct software with the listing.	A software component listing without an attached software, is indicated by the empty icon.
Sometimes, after a package was uploaded, the Local Expansion technology may discover that this software has missing local dependencies; its rules require components that are not yet in the knowledge base. Until you fix this issue, the component can not be managed by Sun Update Connection – Enterprise.	An exclamation point in a red circle, on either a full (has software attached) or an empty (does not have software attached) listing, indicates that there are missing local dependencies.

Console on Windows

You cannot upload or attach RPMs with a console on Microsoft Windows. Use the Sun Update Connection – Enterprise CLI on a Linux machine to upload RPMs. See Example 5–2.

To Attach an RPM

1. Log in with full permissions or as the admin user.

2. From the drop-down list in the tool bar, select a distribution-architecture.

   The Components list shows the components relevant to your selection.

3. Select Local/Local RPMs/[category]/package group/<package>.

4. Do one of the following:

   • From the tool bar, click the Upload knowledge base File button.

   • Right-click the selected component and choose Local -> Upload.

   • From the Components menu, choose Local -> Upload.

     The Attach Target File window opens.

5. Check each distribution to which this NCO is applicable.

6. Select a source machine:

   • If the console has access to the NCO, select Console.

   • If a remote managed host has access to the NCO, select Managed Host.

     ---

     Note –

     Remote upload is limited to 5Mb; console upload is unlimited. It is recommended that you upload from the console whenever possible.

     ---

To Attach an RPM from the Console Machine

If you selected console, follow this procedure. If you selected Managed Host, go to To Attach an RPM from a Managed Host.

1. Click the Select File button of the File Name field.

   The Choose RPM window opens.

2. Browse to and select the relevant package.

3. Click Open.

   The Choose RPM window closes, and the path name appears in the File Name field of the Attach Target File window.

To Attach an RPM from a Managed Host

If you selected Managed Host, follow this procedure.

1. Click the Select Host button of the Host Name field.

   The Host Selection window opens.

2. Select the managed host that has the software, and click OK.

   The Host Selection window closes, and the host name appears in the Host Name field of the Attach Target File window.

3. In the File Name field, type the full path name of the package.

4. Click Apply.

   The Status column indicates when the upload is done. The Local Expansion technology generates deployment rules for the new package.