Solaris software and file formats are not known by Linux. Therefore, the procedures for adding Solaris software to your local knowledge base include creating a tar file of Solaris packages:
Expand the PKG, to create a directory of files; then tar the directory.
Using Sun Update Connection – Enterprise, you will upload the tar file. Sun Update Connection – Enterprise will recognize it as a Solaris software and make the PKG accessible for deployment in jobs.
The procedures in this section include the following:
You cannot upload PKGs with a console on Microsoft Windows. To upload single PKGs, on the SDS machine, use the script created for external upload. See Adding Solaris Software with a Script.
In this procedure, you add a Solaris PKG to the knowledge base, when it has not been detected automatically. This procedure is best used for single packages, when you feel more comfortable using the console rather than a command-line.
When you upload Solaris software, it must be in the form of a tarball, not a PKG.
Make sure the software is a directory of files, not a PKG.
Tar the directory: tar -cf name.tar /path/*
Copy the tarball to the console machine.
If you are using a console on Microsoft Windows, this procedure is not applicable. See Adding Solaris Software with a Script.
Log in with full permissions or as the admin user.
From the drop-down list in the tool bar, select the Solaris distribution-architecture.
Select Local/Local PKGs/[<category>].
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.
In Upload File From, select Console.
Click the Select File button of the File Name field.
The Choose RPM window opens. This window has the same name for both Linux (RPM) and Solaris (tarball).
Browse to and select the package you want to add. Use the Control or Shift keys to make a multiple selection from one directory.
Click Open.
The choose RPM window closes, and the path name appears in the File Name List of the Add Software window.
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.
If a software component is a security fix for an earlier version (see To Fix Local Software Missing Dependencies), check the Security Fix option.
In this procedure, you add a large amount of Solaris software to your local knowledge base. Use this procedure for upload of Solaris software CDs. This procedure does not use the console; it uses a web application created specifically to make Sun Update Connection – Enterprise support and management of Solaris more efficient. Notice that this procedure is also found in the Administrator’s Guide; it must be done after installation of the Sun Update Connection – Enterprise Agent on a Solaris machine, to enable the system dependency server to recognize Solaris software.
Make sure of the following:
You have standard NFS or direct access to the PKGs from the system dependency server machine. The CD is in the CD-ROM of the SDS machine; or the SDS has direct access to Solaris files. This procedure does not support FTP or HTTP.
Directories and files to be uploaded are readable by the nobody user.
If the software is in PKG format, expand the PKGs. Each creates a directory (and possible sub-directories) and places there the files of the package.
Open a web browser and in the URL address field, type:
https://SDS-hostname-or-IP-address:8002/upload.html |
In the Package path text box, type the full path to the directory that contains the Solaris software.
For example, if you specify the /tmp/tmpdsol directory, it should contain all the subdirectories and contents copied from the Products directory on the CD ISO image.
There is no recursive search, so the upload path must be only one level above the software directories.
Click Upload.
The packages are added to the Solaris knowledge base of the Sun Update Connection – Enterprise system dependency server. The browser window shows the automated actions: reading packages, adding packages, and searching for missing packages.
In this procedure, you will use a script from the Sun Update Connection – Enterprise CLI application to upload Solaris software. Use this procedure if you are unfamiliar with Solaris commands and having trouble unpacking the PKGs or tarring the directories.
Install the latest Sun Update Connection – Enterprise CLI.
The script is /usr/local/uce/cli/bin/pkg_loader.sh
Change to the following directory by typing:
cd /usr/local/uce/cli/bin/ |
Type the following command:
-p is required and its value is the path of the packages to be uploaded.
-r is optional and provides a recursive search through the given path.
-d is optional and provides debugging information.
./pkg_loader.sh -p path [ -r ] [ -d ] |
Type a Sun Update Connection – Enterprise user name with full permissions.
Type a password for the Sun Update Connection – Enterprise user.
For the channel, type the number of the distribution-architecture, according to the displayed list of Available Channels, to which the packages you want to upload belong.
At the prompt Would you like all found components to be added under specific category?, type y to put the packages in a user-defined category, and then at the Category name prompt, type the name of the category.
If the category does not yet exist in the Sun Update Connection – Enterprise components list, it will be created. If you type n, the packages are added under a default category in the components list.
pkg_loader.sh will tar the Solaris package directories. Then it uploads the tarballs to the knowledge base. Sun Update Connection – Enterprise recognizes them as Solaris packages and enables you to deploy them as PKGs.
In this procedure, you learn how to attach a Solaris software to a name in the Components list under Local/Local PKGs. The name must already be in the Components list. Use this procedure to: replace a package with another one; manually upload a package; fix missing dependencies. See Table 5–1 for more explanations of when to use an attach procedure.
If you are using a console on Microsoft Windows, this procedure is not applicable. See Adding Solaris Software with a Script, or delete an existing component (that you want to replace or fill), and use the scirpt to upload the new PKG.
When you upload Solaris software, it must be in the form of a tar file, not a PKG.
Make sure the software is a directory of files, not a PKG.
Tar the directory:
tar -cf name.tar /path/* |
Copy the tarball to the console machine.
Log in with full permissions or as the admin user.
From the drop-down list in the tool bar, select a distribution-architecture.
The Components list shows the components relevant to your selection.
Select Local/Local PKGs/[category]/package group/package.
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.
Check the relevant Solaris architecture-distribution.
In the Upload File From options, select Console.
Click the Select File button of the File Name field.
The Choose RPM window opens.
This window has the same name for both Linux (RPM) and Solaris (tarball).
Browse to and select the relevant package.
Click Open.
The Choose RPM window closes, and the path name appears in the File Name field of the Attach Target File window.
Click Apply.
The Status column indicates when the upload is done. The Local Expansion technology generates deployment rules for the new package.