Sun Update Connection - Enterprise 1.0 User's Guide

Uploading Linux Software

Though Sun Update Connection – Enterprise should automatically detect NCOs that are already installed on a host in the solution, sometimes you want to manually add your NCOs to your local knowledge base. Procedures for adding RPMs that belong to Linux distributions are slightly different than those for adding Solaris PKGs.

The procedures in this section include the following:

Using Console on Windows

You cannot upload 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.

Adding Undetected Linux Software

In this procedure, you add a local RPM to the knowledge base, when it has not been detected automatically. For example, you would use this procedure for uploading a third-party bundle of components from a CD.

You cannot upload 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.

ProcedureTo Upload a New RPM

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

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

    The Components list shows the components relevant to your selection. The NCOs that you add with this procedure will be added to the inventory of the displayed distribution.

  3. Select Local/Local RPMs/[category].

  4. Do one of the following:

    • From the tool bar, click the Add Component button.

    • Right-click the selected category and choose Local -> Add.

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

      The Add Software window opens.

    This screen capture shows the Add Software window.
  5. Select a source machine:

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

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


      Note –

      Remote upload is limited to 5 Mbytes. Console upload is unlimited. You should upload from the console whenever possible.


ProcedureTo Upload from the Console Machine

If you selected console, follow this procedure. If you selected Managed Host, go to To Upload 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 packages you want to add. Use the Control or Shift keys to make a multiple selection from one directory.

  3. Click Open.

    The Choose RPM window closes, and the path names appear in the File Name list of the Add Software window. Add as many packages as you want.

  4. Click Apply.

    The Status column indicates when the upload is done. You might have to wait until the console is updated with the changes. The time depends on your local environment configuration.

ProcedureTo Upload from a Managed Host

If you selected Managed Host, follow this procedure. Note that this procedure upload only one RPM at a time.

  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 Add Software 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. You might have to wait until the console is updated with the changes; time depends on your local environment configuration.


Example 5–2 To Upload NCOs with the CLI

The Add Software Package command allows you to give a path name of a package for upload. The package should be on the local machine or on a mount point. The Distribution parameter is required in this command (the -ld command outputs a list), and you add the package to a single distribution at a time. See Add Software Package (-asp) Command.


#! /bin/bash

echo -n “Enter your user name:” 
read user 
echo -n “Enter your password:” 
read password 

echo “The list of active distributions is:” 
uce_cli -ld -u $user -p $password 
echo -n “Type the exact name of the distribution for this software:” 
read distro 
echo -n “Type the source path name of the file:” 
read pathname 
echo -n “Is this software a secured version of a previous one? (y | n)” 
read secure 

if [ “$secure” = “y” ]; then 
   uce_cli -asp -f “$pathname” -secure -D $distro -u “$user” -p “$password” 
else 
  uce_cli -asp -f “$pathname” -D $distro -u “$user” -p “$password” 
fi

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.

ProcedureTo 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.


ProcedureTo 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.

ProcedureTo 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.